|
| 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. | |
| | Author | Messages | |
jbrixey
Posts:9
 | | 10/15/2008 2:51 PM |
| I have been successful in getting a computer build to update with my WSUS server during the build task sequence. The issue I am running into is that those task steps will only work if the machine has been added to a domain, eliminating the possiblity of capturing an image from the machine. While these task sequences steps work, I would like to be able to get the image as up to date as possible via our approved updates. Granted, I could just deploy the OS and have the system check in with WSUS as normal download and install the approved updates, but it seems a better solution to have the most current updates possible already in the image, reducing the amount of updates that any new client has to download. Is it possible to get the task sequence to connect to the WSUS server and get updates without having the system added to the domain? | | | |
| Konrad
Posts:67
| | 10/15/2008 11:21 PM |
| I apply updates via WSUS to my Windows XP MDT builds without them being in the domain for the reason you've mentioned. To do this I use the task sequence step named "Windows Update (Pre-Application Installation)" which is actually just a "Run Command Line" task that runs the command: cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"
Is this what you're using?
You also need your CS.ini to include a pointer to your WSUS server:
WsusServer=http://myserver:8530 | | | |
| FarmerPete
Posts:168
| | 10/16/2008 11:05 AM |
| | Worst case scenario, if you can't get the automated WSUS update to work during your scripted image build process, you can always build your images by hand. Not the best solution if you have a lot of images to build, but if we are talking 1-5 images rebuilt a couple times a year, not that bad. | | | |
| jbrixey
Posts:9
| | 10/16/2008 3:23 PM |
| | I was able to get this to work as I intended, by removing the task sequence conditions in the apply updates task. By removing the conditions, the sequence doesn't look for the capture status and proceeds with the interrogating of the WSUS site specified in the CS.ini. If you are using update groups on your WSUS server you will need to name your build computer and run the build twice. This is because the initial build will register the name with the server, but it will be assigned to the unknown computers group. Once it registers initially, you will need to move the computer to the group of your choice to get the updates you want applied to your build. Re-running your build the second time will ensure that the group's approved updates are installed. I haven't tested this, but if you run updates both before and after the application install task, you may avoid having to run the build twice. | | | |
|
| | You are not authorized to post a reply. |
|
| |
ActiveForums 3.7 | |
|  | 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. |
| |
| |
|