|
| 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 | |
chris@cfnsg.com
Posts:5
 | | 08/05/2008 7:28 AM |
| I have built several successful XP sp2 and Vista images with MDT 2008. I am trying to upgrade our XP Image to SP3. I have tried both an SP3 CD and a SP2 CD with SP3 slipstreamed in. I have upgraded to Patch 1 for MDT and I still get this error. The OS installs fine, but when it goes to boot into XP to begin the task sequences for isntalling apps, I get a deployment Error: Non-zero return code executing command "C:|MININT\Tools\X86\TsmBootstrap.exe" /env:SAContinue, re= -2147221164 Any ideas? | | | |
| Paul M. Hibbert
Posts:27
| | chris@cfnsg.com
Posts:5
| | 08/05/2008 8:07 AM |
| Thanks, but I don't think it does. I am using the Media method (deploy from DVD) and not onnecting back to the server. My image works perfectly if I switch from the SP3 OS back to SP2 | | | |
| Paul M. Hibbert
Posts:27
| | 08/05/2008 8:16 AM |
| | Have you considered installing Sp3 as an application? | | | |
| chris@cfnsg.com
Posts:5
| | 08/05/2008 8:17 AM |
| Yes, but as a last resort. I was hoping to do it this way, but if I can't get it working, I'm sure it will work as an application. Thanks | | | |
| David S.
Posts:10
| | 08/13/2008 1:50 PM |
| The Lite Touch Image Creation process relies on the fact that Windows XP Service Pack 2 will copy the Administrators settings to Default User (allowing default settings to be configured inside the image). This changes once you apply SP3 during the IC process, and under SP3 is disabled by default. This will just about ruin images that have a lot of customizations made during the imaging process.
Fear not, it's easy to fix. Just add UpdateServerProfileDirectory=1 to the [Unattended] section of Sysprep.inf before running Sysprep. For the MDT, I would add that line to the Sysprep.inf located in the ProgramFiles\DeploymentToolkit\Templates directory, that way whenever you create a new Task Sequence, the change will be in your new Sysprep.inf by default.
Also, if you are adding SP3 to your image, you'll need a new version of Sysprep. If you add SP3 as either an application or a custom task, you're fine and the new Sysprep will be available to the MDT scripts. If you slipstream or integrate SP3 into the WinXP source, you will have some issues - the OS files will be updated, but not the latest SYSPREP files (SUPPORT\TOOLS\DEPLOY.CAB). To fix this, just get a hold of the SP3 DEPLOY.CAB (from the MS Download Center), and just overwrite the SP2 SUPPORT\TOOLS\DEPLOY.CAB with the new SP3 version.
Here's a couple links on this:
http://support.microsoft.com/?kbid=887816
http://blogs.technet.com/deploymentguys/archive/2008/05/22/configuring-default-settings-for-windows-image-deployment-update-for-windows-xp-sp3.aspx
http://blogs.technet.com/mniehaus/archive/2008/05/14/need-new-sysprep-for-windows-xp-sp3.aspx | | | |
| chris@cfnsg.com
Posts:5
| | 08/20/2008 9:33 AM |
| | Thanks, but still no luck. I am using the Media deployment method. Basically, whenever we need to image a computer, we insert the DVD and install the OS and all of the custom applications with a custom task sequence. The error occurs after the OS installs when it logs into windows for the first time. I tried adding the line to the unattended section as you suggested, but no luck. | | | |
| chris@cfnsg.com
Posts:5
| | 08/26/2008 10:04 AM |
| | Figured it out. You were correct about needing the Deploy.cab I copied the deploy.cab from the SP3 update into the SP3 cd. What I neglected to mention was that I was using nLite to customize the XP installation. There was an issue with deploying SP3 when you use nLite on a Vista computer. I updated nLite and it works great. Thanks everyone for your help. | | | |
|
| | 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. |
| |
| |
|