Wednesday, January 07, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
Forgot Password ?



Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Subject: Task Sequence - Windows Updates
Prev Next
You are not authorized to post a reply.

AuthorMessages
BIGSUser is Offline

Posts:10

Send Message
10/16/2008 4:06 PM  

I have the Windows updates running in my task sequence and it is installing every available update. I know you can exclude individual updates by listing the WUMU_ExcludeKB1=925471 statement in the CustomSettings.ini but this would be tedious to do for every patch I do not want to install.

 

Can I designate somewhere to only have "High Priority/Critical" updates installed and exclude optional updates?

Thank you in advance for your help.

KonradUser is Offline

Posts:67

Send Message
10/16/2008 5:10 PM  
You could possibly edit ZTIWindowsUpdate.wsf in the scripts folder to check the severity of a patch before installing it.

Maybe if you add the following at line 260:
If lcase(item.MsrcSeverity) <> lcase("Critical") And lcase(item.MsrcSeverity) <> lcase("Important") Then
     bInstall = FALSE ' This patch is not important enough for us!
End If
I've not tested this so it may not work..

I'd actually advise against directly editing this script, but instead take a copy of it, edit the copy, and point your task sequence to use your copy instead.

Additional info:
http://msdn.microsoft.com/en-us/library/aa386099(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa386906(VS.85).aspx
BIGSUser is Offline

Posts:10

Send Message
10/20/2008 8:42 AM  
This did not work - actually stopped installing all updates now.
KonradUser is Offline

Posts:67

Send Message
10/20/2008 6:08 PM  
If I was in this situation the next thing I'd do would be to have the script write to log the actual values returned from "item.MsrcSeverity" to make sure that it is a valid property of the "item" object's class.
Something like:
oLogging.CreateEntry "Checking update:" & item.Name & " MsrcSeverity:" & item.MsrcSeverity, LogTypeError


Then check through the logs and see if the values include "Critical" and "Important".

Alternatively, you could try changing the inserted code to use the "InStr()" function rather than doing a "<>" operation:
If InStr(lcase(item.MsrcSeverity),lcase("Critical"))=0 And InStr(lcase(item.MsrcSeverity),lcase("Important"))=0 Then
     bInstall = FALSE ' This patch is not important enough for us!
End If
You are not authorized to post a reply.
Forums > Deployment Solutions > Lite Touch > Task Sequence - Windows Updates



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.



Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt