<div>
this topic was discussed at: <br />
<a href="https://www.experts-exchange.com/questions/21068118/Shutdown-All-Systems-On-A-Schedule-using-Active-Directory.html" rel="ugc">https://www.experts-exchange.com/questions/21068118/Shutdown-All-Systems-On-A-Schedule-using-Active-Directory.html</a>
</div>


this topic was discussed at:
https://www.experts-exchange.com/questions/21068118/Shutdown-All-Systems-On-A-Schedule-using-Active-Directory.html [https://www.experts-exchange.com/questions/21068118/Shutdown-All-Systems-On-A-Schedule-using-Active-Directory.html]

<div>
<div class="content wysiwyg-content">
I have a w2k3 domain and i am pushing out a software update/install to clients (all XP SP1, SP2 is not yet installed) by way of a GPO in active directory<br />
<br />
The only way i have found to make the install run is by rebooting the machine. &nbsp;Is this the only way to start the install?<br />
<br />
Second, if it is, how can i push out a reboot to all the machines in a particular Organizational unit so the install starts over a weekend when users arn't in the office.
</div>
</div>


I have a w2k3 domain and i am pushing out a software update/install to clients (all XP SP1, SP2 is not yet installed) by way of a GPO in active directory

The only way i have found to make the install run is by rebooting the machine.  Is this the only way to start the install?

Second, if it is, how can i push out a reboot to all the machines in a particular Organizational unit so the install starts over a weekend when users arn't in the office.

Reboot Clients

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).