Question How can the Aclient connections be reset on a regular basis?
Resetting the aclient service is helpful to get inactive aclients to reconnect to the Deployment Server. If aclients are consistently loosing their connection, and this is not due to engine hanging problems, the network is the most likely cause of the problem.
This script will help "band-aid" the problem by forcing the aclients to reconnect however often you schedule the script to run. This can be useful to get up and running while troubleshooting the underlying problem on the network.
Requirements of this script are:
Clients must be in a domain or have a common workgroup credential with which the script can authenticate.
RPC must be available (port 139 open). Can manually run "sc.exe \\<client ip> query aclient" successfully from the Deployment Server.
To install/run the script:
Download the attached RestartAclient.vbs
Open the script and modify any of the settings in the edit section to best suit your environment.
Save the script.
To run the script manually, double-click the .vbs. The log file should populate with data (note the user must have admin rights on all of the inactive clients).
To set the script up to run on a regular basis do the following on the Deployment Server:
Open windows task scheduler. Start > Programs > Accessories > System Tools > Scheduled Tasks
Double-click Add Scheduled Task.
Click Browse and select the RestartAclient.vbs
Select Perform Task Daily. Click Next (note that the execution frequency of the task will be adjusted later to occur more often).
Select a time. Click Next.
Enter in credentials that have rights to manage services on the clients. Click next.
Check the box to open the advanced properties. Click finish
Click on the schedule tab
Check to repeat the task every X minutes. It is suggested that you run this every 20 minutes. You can adjust this as needed.
Select 24 hours for the duration. This should cause the task to start every day and repeat every 20 minutes for 24 hours.
Note that if clients are not reconnecting you will want to check the .log file. Most probable causes that the client is not reconnecting are RPC is not enabled, client is offline or bad credentials.