Network Operations (AREV Specific)
At 15 JAN 2010 11:02:40AM Frederick Kurz wrote:
Currently we have a network with 50 workstations. When it is necessary to shutdown the server the network manger has to go around to all workstations running AREV, exit from AREV and log off the network. Is it possible using scripts written for Windows Management Interface or Windows Powershell to:
1) Compile a list of workstations accessing AREV,
2) Issue commands to shutdown workstations running AREV,
3) After network maintenance operations are completed restart the relevant workstations.
We are running AREV 2.03 with Microsoft Server 2003 Release 2 on the server and Windows XP/Pro on the workstations.
Thanks in advance
At 18 JAN 2010 10:37PM Eric wrote:
You're can load AREV from a batch file, in which case, you could use the batch file to log the user
echo %USERNAME%% ] x:\somepath\%USERNAME%
AREV ….
del x:\somepath\%USERNAME%
That's the logging part covered. It's easier for a windows executable than for a DOS one.
To shut down AREV, the best way would be to hook the indexing process to look for a semaphore file in a nominated network path to trigger the log off on each workstation. If you can OSOPEN the semaphore file from AREV, then you can PERFORM "OFF" and the workstation can log itself out.
To restart, a manual restart would be required.
At 19 JAN 2010 04:41AM Warren Auyong wrote:
To shut down AREV, the best way would be to hook the indexing process to look for a semaphore file in a nominated network path to trigger the log off on each workstation. If you can OSOPEN the semaphore file from AREV, then you can PERFORM "OFF" and the workstation can log itself out.
Provided that a dedicated indexing station is not being used.
At 19 JAN 2010 07:06AM Eric wrote:
You'll probably need to log that off as well…
At 22 JAN 2010 04:41AM Warren Auyong wrote:
The problem being when using a dedicated indexing station(s) background indexing is typically disabled on user workstations. If background indexing is disabled the post indexing hook does not get called and therefore a semaphore flag will not get checked.
At 22 JAN 2010 02:24PM Eric wrote:
I agree it's problematic.
At 25 JAN 2010 03:11PM Jared Bratu wrote:
Windows WMI has methods for connecting to remote computers. See Connecting to WMI on a Remote Computer
You could probably build a VB or PowerShell script to list through the running processes on remote terminals and terminate any arev.exe processes in memory. This would not be a clean shutdown so you might want to combine it with some hook inside your application to check for a shutdown file.