Neelson
asked on
Capture Configured XP Image in SCCM
Hi,
I have built a new SCCM Server and successfully run a Build and Capture process which has captured a base Windows XP operating system image.
I have also successfully managed to deploy the captured image to another computer (well, some of the drivers in the driver package didn't install, but that's another matter).
So essentially I have a base operating system with no additional applications installed. What I would like to do is install all our standard applications, which includes a number of bespoke applications/programs/shor
I know the standard thing to do is to package up these applications and install them as part of the build and capture process - however most of the bespoke applications would take me months to package up and this is something I desperately want to avoid.
Would someone be able to tell me how I would go about doing this??
I have built a new SCCM Server and successfully run a Build and Capture process which has captured a base Windows XP operating system image.
I have also successfully managed to deploy the captured image to another computer (well, some of the drivers in the driver package didn't install, but that's another matter).
So essentially I have a base operating system with no additional applications installed. What I would like to do is install all our standard applications, which includes a number of bespoke applications/programs/shor
I know the standard thing to do is to package up these applications and install them as part of the build and capture process - however most of the bespoke applications would take me months to package up and this is something I desperately want to avoid.
Would someone be able to tell me how I would go about doing this??
ASKER
Hi, Thanks for the quick response - the first option is the only one I can go with as most of our bespoke applications defy being packaged in any form.
The capture process was automated as part of the build and capture sequence and didn't give me the option of any manual intervention, least of all installing a raft of applications.
How would I delay the capture part of the process so that I can manually install all required applications adn then kick off the image capture sequence?
The capture process was automated as part of the build and capture sequence and didn't give me the option of any manual intervention, least of all installing a raft of applications.
How would I delay the capture part of the process so that I can manually install all required applications adn then kick off the image capture sequence?
just add a new step in your task sequence.
Use "run command line" step and define "cmd.exe" as command to execute.
You should insert it below "Setup Windows and ConfigMgr" Step (see picture)
http://www.vroom.cc/4-TaskSequence.JPG
This will cause the process to stop until YOU close the cmd.exe process. During this time you can execute your steps
Use "run command line" step and define "cmd.exe" as command to execute.
You should insert it below "Setup Windows and ConfigMgr" Step (see picture)
http://www.vroom.cc/4-TaskSequence.JPG
This will cause the process to stop until YOU close the cmd.exe process. During this time you can execute your steps
ASKER
Thanks for that, I'll give it a crack today. Just another quick question - a lot of these applications require a reboot after installation which would require the cmd.exe process to close, would that trigger the capture process to start??
yes thats the disadvantage.
But here's a workaround. You have to use two Task Sequences.
One for Creating the reference machine and one for capturing it.
See the picture which task sequence should contain which steps.
4-TaskSequence.jpg
But here's a workaround. You have to use two Task Sequences.
One for Creating the reference machine and one for capturing it.
See the picture which task sequence should contain which steps.
4-TaskSequence.jpg
ASKER
Thanks for the quick response. What I've done is to duplicate the build and capture task sequence. On the original task sequence I've disabled the Capture build process, on the duplicate task sequence I've disabled the Build sequence. I've attached a couple of screen shots so you can see what I've done.
Do you think this will work?
Disable-Build.bmp
Disable-Capture.bmp
Do you think this will work?
Disable-Build.bmp
Disable-Capture.bmp
xes. as soon as you finished your customizing you can start the capture process
ASKER
Great, thanks a lot. I'm going to give this a try and let you know how I get on.
ASKER
Hi, I've tried the following on 2 seperate PCs:-
1. Imaged the PC using the captured Base XP image
2. Made minor changes, such as running windows updates and upgrading to IE8
3. Tried running the Capture sequence on the machine
4. The sequence fails - after checking SMSTS.Log the job seems to have failed becuase it was part of a domain and thus sysprep did not run.
This is a bit of a catch 22 as my SCCM server cannot communicate with the CCM Client on my PCs if it is not part of a domain - and it would appear that sysprep won't work if the PC is connected to a domain.
If added a screen shot beloe of my SMSTS.log file and also attached the file itself.
How have you managed to get an image at your company that has all the required software and setting and successfully captured it to SCCM?
SYSprep-error.bmp
smsts.log
1. Imaged the PC using the captured Base XP image
2. Made minor changes, such as running windows updates and upgrading to IE8
3. Tried running the Capture sequence on the machine
4. The sequence fails - after checking SMSTS.Log the job seems to have failed becuase it was part of a domain and thus sysprep did not run.
This is a bit of a catch 22 as my SCCM server cannot communicate with the CCM Client on my PCs if it is not part of a domain - and it would appear that sysprep won't work if the PC is connected to a domain.
If added a screen shot beloe of my SMSTS.log file and also attached the file itself.
How have you managed to get an image at your company that has all the required software and setting and successfully captured it to SCCM?
SYSprep-error.bmp
smsts.log
Why is your reference computer member of the domain? That's not possible. Either you do not join it to domain, or you remove domain membership before capturing it. Also if you define a network access account in SCCM, your reference client must not be member of the domain. The network access account must have access to the distribution point.
Here's some general information about that user:
http://technet.microsoft.com/en-us/library/bb680398.aspx
Check out this examples when to use a network access account:
http://technet.microsoft.com/en-us/library/bb932160.aspx
You need three Task Sequences
- the first to create the Reference Computer an stop to make manual changes possible
- the second to capture your computer
- the third to deploy your captured image to all clients (at this points you have to add the clients to the domain)
Here's some general information about that user:
http://technet.microsoft.com/en-us/library/bb680398.aspx
Check out this examples when to use a network access account:
http://technet.microsoft.com/en-us/library/bb932160.aspx
You need three Task Sequences
- the first to create the Reference Computer an stop to make manual changes possible
- the second to capture your computer
- the third to deploy your captured image to all clients (at this points you have to add the clients to the domain)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What did you base your Win PE boot image from? A generic or custom PE boot image?
1. Manually install the applications befor the capture of the reference computer is taking place
2. Automatically install the packaged application within the task sequence before the capture of the reference computer is taking place
2. Automatically install the packaged application within the task sequence when deploying the image to all clients