Hi all,

I have looked through the forum but cant see anything that answers this specific question so here goes.

We have built a Windows 7 SP1 reference machine using a VM. We want to capture this as a new WIM file using SCCM 2007 SP2. I have done this for Vista and Windows 7 RTM with no problems but it is not working for me now, I'd like to understand why.

The machine is domain joined and is running the SP2 SCCM client. I run the Capture Reference Machine task sequence from Run Advertised Programs.

It completes the Join Workgroup step and reboots the machine.

The task seqeuence does not continue after the reboot. The smsts.log file contains now errors, the TSManager.exe process is running after the reboot but nothing else is processed.

Is this an issue with Windows 7 SP1 not being fully supported in SCCM 2007 SP2, or am I doing something wrong?

Any help or advice would be greatly appreciated!

Cheers,

Tim

Timfy,

What I did is first unjoin my refrerence machine from the domain. Secondly I created a capture media which then syspreped my machine and I can then point it to where I want my wim saved.

Once syspreped the machine rebooted off the wim (included when you create the capture media) and successfully captured the image.

Hope this helps you,

Hello - Not sure, you have seen the options mentioned in the below thread.

http://social.technet.microsoft.com/forums/en-us/configmgrosd/thread/5E1C9664-14E6-46CF-B56E-2B8EDA6F638C

After the join to the workgroup, does the autologin work ?

The tasksequence will only continue if a admin user is logged in after the reboot...

It's not an issue, I captured the win7 sp1 ref machine without a problem using the TS:

set autologin registry

Join workgroup

Set TS Variable OSDTargetSystemRoot = c:\

Prepare ConfigMgr Client

Prepare OS

Capture the Reference Machine

Thanks for all the responses guys!

Adding the autologin details has solved the issue, the TS now continues after the reboot :-)

Many thanks jeroenda...

Spoke too soon :-(

The TS did restart but couldnt reinitialize the SCCM client, because now the machihne is in WORKGROUP the native mode cert is not valid. This has definitely worked before but I think I am being a bit dense... anyone got any ideas on this one?

Thanks,

Tim

For the machine to find your SCCM MP when it is in a workgroup you need to add this to the "Setup Winodws and ConfigMgr" step in your task sequence. (Installations Properties)

SMSSLP=sccmserver.domain.com

SMSMP=sccmserver.domain.com

FSP=sccmserver.domain.com

The enables the client to find the MP while it is in the workgroup for the capture.

I would strongly recomend that you create a TS using the "Microsoft Deployment Task Sequence" for the build and capture, once you have it all working it is easy to update and maintain going forward which is one of the goals of our project. Another goal is to only update it twice a year :) (core software and updates.)

Thanks for your response. I am trying to capture a reference machine that already exists, so in the TS I am currently using I do not have a Setup Windows and ConfigMgr step.

For info the TS looks like this:

1 Set Autologin reg

2 Join WORKGROUP

REBOOT

3 OSDTargetSystemRoot = C:\

4 Prepare ConfigMgr Client

5 Prepare OS

6 Capture Reference Machine

The issue is that after the reboot initiated at step 2 the TS progress UI appears and it says 'Initializing ConfigMgr Client', this then hangs and finally the TS fails before it has executed step 3 or anything further. The smsts.log reports that now the machine is not part of the domain the client certificate is not considered valid since the machine name does not match (it no longer has a FQDN).

How do I get the TS to continue after the machine as left the Domain?

Thanks!

Tim

Timfy,

What I did is first unjoin my refrerence machine from the domain. Secondly I created a capture media which then syspreped my machine and I can then point it to where I want my wim saved.

Once syspreped the machine rebooted off the wim (included when you create the capture media) and successfully captured the image.

Hope this help

I know this is an old closed post but I wanted to put this here in the event someone is experiencing the same problem. I was trying to capture the same way tim was. It would reboot after joining workgroup. I had thought nothing was happening but if I waited the machine would reboot again into PE and capture the image. The task sequence advertisement status shows that it was running "Prepare ConfigMgr Client for Capture" while the system was at Ctrl Alt Del screen.

I hope this helps someone searching this issue.