SCCM best practices, a question about building image for mass deployment.
I have been doing a lot of reading, some people so it's ok some say it's not. My question is should I included the SCCM client on the image?, is there a downside in doing this?
July 9th, 2011 9:21am

The only potential downside ia if you deploy the image to a system not intended for management by your ConfigMgr site. The client agent lives perfectly fine in the image and anyone whos claims to have issues with it in the image do so purely anecdotally. Note that if you use a ConfigMgr Buiild & Capture task sequence (clearly the best practice), then you have no choice but to put the client agent in the image. If you manually build the image or use a LiteTouch Build & Capture task sequence and wish the agent to be in your image, then you must prepare it properly otherwise you will have issues: http://technet.microsoft.com/en-us/library/bb694095.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2011 10:10am

Thanks Jason Here's the thing. I created my image with the SCCM client on it. I then created a task called capture in this task I do the following, before running the capture task I disconnect from the domain. 1.Prepare configMgr client for capture. 2.Prepare Windows for capture 3.Capture operating system. I get 0x00000004 error.
July 10th, 2011 9:43am

can you post the entire SMSTS*.log somewhere to review please ? My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 5:09pm

Here is my smsts.log file http://dl.dropbox.com/u/6202692/smsts.log Another thing is before I run the capture task, I disjoin from the domain, but then when I run the the capture task the machine no longer responds to advertisements, the machine is in the boundaries via IP range. Also when I am off the domain I keep getting connect to wmi namespace root cimv2 error access is denied when truing to to a policy refresh with Right click tools. When I am on the domain, I do not get the wmi namespace error, only when I am not on the domain. I am logged to my sccm server as Administrator. Any help would be awesome, as I am learning SCCM and have learned so much in 2 short weeks thanks to this forum.
July 10th, 2011 5:59pm

What's the point of including SCCM on the image? Doesn't the setup windows and configmgr step re-install the client anyway? Am I mistaken?
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 11:20pm

according to your smsts.log file the computer is still domain joined when you try to do the capture, see below, so in your apply network settings step, join a workgroup and all should be good cheers naill <![LOG[Computer is part of domain 'CLIVEBUCKWHEAT', disjoin and start image capture]LOG]!><time="09:29:05.258+240" date="07-10-2011" component="PrepareOS" context="" type="3" thread="2440" file="deployutil.cpp:565"> <![LOG[Machine does not meet OSD capture requirements. Capture can not continue.]LOG]!><time="09:29:05.258+240" date="07-10-2011" component="PrepareOS" context="" type="3" thread="2440" file="prepareos.cpp:1339"> <![LOG[Unable to sysprep the machine, hr=80040004]LOG]!><time="09:29:05.258+240" date="07-10-2011" component="PrepareOS" context="" type="3" thread="2440" file="prepareos.cpp:1400"> <![LOG[Sysprep'ing the machine failed, hr=80040004]LOG]!><time="09:29:05.258+240" date="07-10-2011" component="PrepareOS" context="" type="3" thread="2440" file="main.cpp:270"> <![LOG[Exiting with error code 4]LOG]!><time="09:29:05.258+240" date="07-10-2011" component="PrepareOS" context="" type="1" thread="2440" file="main.cpp:293"> <![LOG[Process completed with exit code 4]LOG]!><time="09:29:05.273+240" date="07-10-2011" component="TSManager" context="" type="1" thread="1256" file="commandline.cpp:1102"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:29:05.273+240" date="07-10-2011" component="TSManager" context="" type="1" thread="1256" file="instruction.cxx:3010"> <![LOG[Failed to run the action: Prepare Windows for Capture. My step by step SCCM Guides I'm on Twitter > ncbrady
July 11th, 2011 5:42am

When I am not on the domain, the computer never responses to the advertisement. The computer is in the boundaries via IP RANGE. Also when I am off the domain I keep getting connect to wmi namespace root cimv2 error access is denied when truing to to a policy refresh with Right click tools. When I am on the domain, I do not get the wmi namespace error, only when I am not on the domain. I am logged to my sccm server as Administrator.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 7:20am

the error in your SMSTS.log was because yuo were domain joined, remove it from the domain in the apply network settings step (by joining workgroup) as i've explained above and try again, My step by step SCCM Guides I'm on Twitter > ncbrady
July 11th, 2011 9:54am

Because if you use an OSD build and capture task sequence, anything after the setup windows and ConfigMgr task requires the use of the agent. Yes, a deployment TS will reinstall the client. There are a handful of reason for this and is cannot be changed.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2011 4:23pm

When I am not on the domain, the computer never responses to the advertisement. The computer is in the boundaries via IP RANGE. Also when I am off the domain I keep getting connect to wmi namespace root cimv2 error access is denied when truing to to a policy refresh with Right click tools. When I am on the domain, I do not get the wmi namespace error, only when I am not on the domain. I am logged to my sccm server as Administrator. We're only talking about the build and capture task sequence here though. Joining a reference system to the domain is bad practice as domains tend to leave an irreversible impression on a system. You should join a system to the domain in the deployment task sequence. How are you creating your image?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 12th, 2011 4:26pm

I did not use the build and capture feature, as I understand it the build and capture task in configuration manager actually installs windows and then captures it. I did not choose this because my image has already been manually built, I would just like to capture it now to a wim file. I created a custom task called capture that 1. Joins a workgroup (this is under network settings in configuration manager) 2.Prepare configMgr client for capture. 3.Prepare Windows for capture 4.Capture operating system.
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2011 7:13pm

You are correct in what it does. So what happens when you have to rebuild the image? Are you going to manually build it again?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 12th, 2011 9:26pm

I am just trying to get the basics of SCCM down, so I can understand a few key items. Yes I can capture my image using capture media and that works fine, but I was just trying to automate the process totally using SCCM. Once I have this procedure down pat, I will most certainly try to do an an automated build and capture but I am not there yet. Were I am is I created a custom advertisement with the following tasks in it. 1. Joins a workgroup (this is under network settings in configuration manager) 2.Prepare configMgr client for capture. 3.Prepare Windows for capture 4.Capture operating system. and it errors out thus far, these are the battles I face today.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 8:42am

For task #1, what exact task are you using? Unjoining a system from a domain also requires a reboot. If this is a manual reference build, why not manually unjoin it from the domain first? Where are you seeing WMI errors when the client is not part of the domain? As you can see, although it may seem simpler the way you are doing it, it's not really. A build and capture TS is a basic task and is quite easy to setup and use. Niall has some excellent guides out on windows-noob.com. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 13th, 2011 7:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics