Updates to ZTIWindowsUpdate.wsf December 8, 2009
Posted by keithga in MDT 2010, Troubleshooting, VBscript, Windows 7.trackback
Hope everyone out there is keeping warm now that December has hit. I’ve been busy during the past few weeks working on a couple of consulting gigs. One Large company, one Medium Sized.
Both of them needed a good jump start getting MDT 2010 up and running in their environments. Like many IT departments out there, they are interested in Windows 7, and MDT 2010 is the de-facto reference design for Windows 7 Deployment.
Medium Sized LiteTouch Deployment
For the Medium Sized Company, we created a MDT 2010 Litetouch system with Windows 7, and packaged up around 50 applications, including the latest versions of: 7-Zip, Adobe Reader, QuickTime, iTunes, Adobe Flash Player, Silverlight, Java Runtime, VLC, Microsoft Office 2007 SP2, Microsoft Office Communicator, Microsoft Live Meeting, Citrix Online Plugin, Rumba, Microsoft App-V Client, and more including several internal tools! We also created a MDT 2010 Litetouch DVD boot media disk for their subsidiary sites, standardizing the desktop images throughout the company.
It then took about a day on-site to configure the server, run the validation tests, and personally go through the documentation and steps with the IT Staff.
Large Litetouch Deployment
For the Large Company, we are moving their existing MDT 2008 Update 1 system to MDT 2010. Remediating any scripts and configuration items as necessary. This is an experienced staff, who just needed an extra set of eyes to help ensure this upgrade goes as quickly and as smoothly as possible. (FYI: They have about 250 Applications defined in MDT 2008)
ZTIWindowsUpdate.wsf
One of the changes we needed to perform today at the Large Company was to fix a couple of bugs in ZTIWindowsUpdate.wsf when calling WSUS servers.
First off, was a fix for the WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS error in WSUS. This is a Large Company, with a well managed WSUS server(lots of updates), and they found out they were hitting the hard 200KB limit during Office Updates. So we needed to code a work around to just call ZTIWindowsUpdate.wsf *again* if the error is returend.
Secondly, since they were *only* using WSUS, we wanted to ensure the the ZTIWindowsUpdate.wsf script did not call Microsoft Update. So I added some code to skip Microsoft Update if the parameter “/SkipMicrosoftUpdate:YES” is on the command line.
We will run some tests tomorrow to ensure it’s performing as expected.
Link
Next
It’s been fun setting up Companies large and small with deployment solutions like MDT 2010! We are available for consulting in 2010, if you would like to get Windows 7 and your MDT 2010 environment up and running quickly, give us a call!
Keith and Tim
Keith Garner is a Deployment Specialist with Xtreme Consulting Group
Good points, I think I will definitely subscribe!
. I’ll go and read some more!
We are in a very similar situation as the “large LTI company” where we only want to obtain updates from our WSUS server and NOT from Microsoft updates.
I’m going to give the “/SkipMicrosoftUpdate:YES” a try.
Thanks!!!
Keith,
Does ZTIWindowsUpdate.wsf default to Microsoft Updates if no WSUS server is found?
I’ve got a number of manufacturing computers that are in a AD OU that is exempt from getting updates via the WSUS server. When these computers are refreshed, no WSUS server is found, so it appears they are going out to Microsoft Updates during the imaging process.
So I tried using your updated ZTIWindowsUpdate.wsf and /SkipMicrosoftUpdate:YES in the command line but those computers are still getting updates Microsoft Updates.
Any thoughts? Thanks in advance!