|
How to Deploy Microsoft Windows Service Packs Using Active Directory John Gall - Gall Computer Consulting Elk River, MN |
||
| First visit
http://www.microsoft.com/windows and obtain the "Network" Installation
of the service pack. This differs from the "Express" version in that
you get ALL the required files whether you need them or not. Save the
file to a local drive or network location. Second run the file with a /x:<network path> this causes the service pack to expand to the network path you've provided. Example: Run c:\xpsp1a.exe /x:\\server1\apps\patches\xpsp1a This expands the service pack to the network location \\server1\apps\patches\xpsp1a Notice the UPDATE folder within the I386 folder this is critical for deploying via Active Directory
|
||
|
|
||
Third Open Active Directory Users and Computers and right click the Organizational Unit in which you want to store the Group Policy. Choose Properties then click the Group Policy tab. Click Add to add the new group policy. Give the policy a descriptive name. In the "Computer" "Software" section right click and choose "New Package" Make the package "Assigned" and then point to your \\server1\apps\patches\xpsp1a\i386\update\update.msi file. Click Ok and close Group Policy. Your package is now assigned to any PC within the OU you attach your group policy to. It also applies to any OU's below it unless you've blocked inheritance. When your PC's start if they do not have this service pack they will not let the user logon until the SP has finished its installation and rebooted. WARNING If you add group policy to OU's that are geographically separate create SEPARATE Group Policy Objects pointing to local file shares at each location. You cannot modify the original Group Policy Object or you will change the path for EVERYONE and users will pull 100+ MB service packs over WAN links. |
||
Microsoft Class Action Lawsuit Settlement Learn How To Submit Your Claim
Preparing Windows Servers for Sarbanes Oxley Section 404 Testing and Auditing