OSD Task Sequence Does Not Complete

[VacTacks11]

Without been rude...You still have not answered the initial question........do the current systems in the SCCM console in the all systems collection currently have the site code? It does not matter if they have or have not the client installed, they should still have the site code!! If not then this in an indication that your boundary is not correct!!

 

As for the configMgr client from defintion I would be fairly sure it is recommened, make sure to tick the box to distribute to the content share in the properties of the new package!

 

Rocket Man

You know, looking back on it now, it seems like such an easy thing, but, yeah, the ConfigMgr package created by default didn't have a Program associated with it. I created a Program from Definition.

 

That being said, it still didn't work for me. I'm not quite sure where to look now. It finds the MP now, which is stellar, but after the TS configures ConfigMgr, it boots into Windows without officially completing anything.

 

I think I may have to recreate the Build & Capture Windows 7 image. I see a ton of Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type errors in the smsts.log file, which I've been able to ascertain is having used a license key in a VLK capture (something you're not supposed to do I guess).

 

Really just grasping at straws here.

[Rocket Man]

SMSMP=[sERVER]

 

Did you add SMSMP=sccmserver.fqdn to the properties of the configMgr properties in the TS.

 

The hardware specific driver package installs just fine, and the computer is added to the domain. With the exception of this problem, the OSD Task Sequence works great

 

Also are you building and capturing a physical machine??

[VacTacks11]

Did you add SMSMP=sccmserver.fqdn to the properties of the configMgr properties in the TS.

 

 

 

Also are you building and capturing a physical machine??

1) Just want to say thanks for your help so far. It's appreciated.

 

2) I didn't have the SMSMP in the TS Client install properties, as it wasn't in the TS Client install properties for the SCCM 2007 MDT Task Sequence. Didn't think I would need it here either. But I have entered it there now.

 

3) I built and captured a VM for my W7 machine, but I used VLK media to do so, and the messages I kept seeing in smsts.log indicated that I shouldn't have used a license key when I captured that image. While I doubt that would have anything to do with this, since I'm out of ideas here...

 

I'll write back when I've captured a new machine. See what happens there.

[VacTacks11]

That was it. It was the Build & Capture I created from the VM that caused this. I created a new VM using the Client in my domain and sure enough, it's working now.

 

Thanks again for all your help. Really.