<div>
Hello,<br />
<br />
In general, the applications deployments takes 2 reboot (The first take the information about the GPO, the second install and need to reboot to complete)<br />
Sometimes 1 computer dont take the information from your DC, so it require an additionnal reboot..
</div>


Hello,

In general, the applications deployments takes 2 reboot (The first take the information about the GPO, the second install and need to reboot to complete)
Sometimes 1 computer dont take the information from your DC, so it require an additionnal reboot..

<div>
thats what i thought but i figured there might be a work around like a shutdown script that would implement a gpupdate /force would make a difference.
</div>


thats what i thought but i figured there might be a work around like a shutdown script that would implement a gpupdate /force would make a difference.

<div>
<div class="content wysiwyg-content">
I recently pushed dot net and some in house software out to multiple windows 7 boxes it seemed to push fine but it took anywhere from a minimum of two reboots to up to five for the systems to download and install the software. I noticed that if the computer was on while I put the GP in to effect and I rebooted the pc GP would state pending a reboot. At this time i would reboot the pc again and sometimes If would install. Is there anyway to ensure that after one reboot the new software will be installed... Like if I install it on shutdown instead of boot up. I should note that all installs were successful but the reboot times would very without ryme or reason. Any suggestions would be great for future projects.
</div>
</div>


I recently pushed dot net and some in house software out to multiple windows 7 boxes it seemed to push fine but it took anywhere from a minimum of two reboots to up to five for the systems to download and install the software. I noticed that if the computer was on while I put the GP in to effect and I rebooted the pc GP would state pending a reboot. At this time i would reboot the pc again and sometimes If would install. Is there anyway to ensure that after one reboot the new software will be installed... Like if I install it on shutdown instead of boot up. I should note that all installs were successful but the reboot times would very without ryme or reason. Any suggestions would be great for future projects.

GPO pending reboot server 2003

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

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).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.