I can suggest the following : a scheduled task running from a server such as a domain controller. This task could run something against each machine in the domain to restart the service.
When I am trying to get one machine to restart (such a my test deployment machine) I use a powershell script. Here is the code: param([string]$machine = "machine", [string]$service = "service") (Get-WmiObject Win32_Service -computer $machine -Filter "name = '$service'").stopservice() Start-Sleep –s 10 (Get-WmiObject Win32_Service -computer $machine -Filter "name = '$service'").startservice() Line 1 supplies the variable declarations. Line 2 stops the indicated service on the indicated machine. Line 3 waits 10 seconds for the service to definitely stop. Line 4 starts the service again. If you save the code as foo.ps1 you can remotely cycle the WPKG service from another machine by issuing the command: PS prompt:> ./foo.ps1 -machine "remotePC" -service "WPKGservice" Kind regards, Bill Prentice K.T.J.R. Striving for R.F.C. 1925 compliance -----Original Message----- From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of ????? ?????????? Sent: Wednesday, 24 March, 2010 09:07 To: wpkg-users@lists.wpkg.org Subject: Re: [wpkg-users] Periodical wpkg script execution from wprg client There are very top-ranking coleagues, that do not turn off their computers. For example, my director. My rank is too small to tell him, what he should do. Usually, such users says me that they do not need any updates. I am to deply applications and application updates quietly and transparent to users. ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
