No Task Sequence

[JigSaw1st]

Hallo everyone,

 

I have a sccm server 2007 SP2 installed. I'm planning to deploy Windows 7 in a company where i work.

During the PXE boot i can easily press the F12 button to boot in to the PXE (see the image). I get the messages that Windows is starting up and also the Network properties.

But later one, i get nothing form the Task Sequence (see the image). And the client computer reboots it self with no error (image 6). I followed the log file of CCM.log this is the output of it.

 

------------BEGIN-------------------

CCM.log

-------------------------------

======>Begin Processing request: "I1BIUWRQ", machine name: "DC1" SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Attempting to connect to administrative share '\\DC1.contoso.local\admin$' using account 'contoso\administrator' SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> The 'best-shot' account has now succeeded 470 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Connected to administrative share on machine DC1.contoso.local using account 'contoso\administrator' SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Attempting to make IPC connection to share <\\DC1.contoso.local\IPC$> SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Searching for SMSClientInstall.* under '\\DC1.contoso.local\admin$\' SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> System OS version string "6.1.7600" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

CWmi::GetObject(): GetObject() failed. - 0x80041010 SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Unable to get SMS_Client object from WMI on remote machine "DC1", error = 0x80041010. SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Target machine DC1 is a DC. Not processing this CCR SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Deleting SMS Client Install Lock File '\\DC1.contoso.local\admin$\SMSClientInstall.CON' SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

---> Completed request "I1BIUWRQ", machine name "DC1". SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

Deleted request "I1BIUWRQ", machine name "DC1" SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

<======End request: "I1BIUWRQ", machine name: "DC1". SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:05 PM 7188 (0x1C14)

Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:07 PM 2084 (0x0824)

Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:07 PM 2084 (0x0824)

Waiting for change in directory "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 2/8/2012 12:18:07 PM 2084 (0x0824)

 

-------------END--------------------

 

 

I have updated the x86 and x64 boot images and also the Windows install.wim file and the install package of Windows 7. There are all updated in the DP.

 

i did everything i can, but i can't solve this problem. Can anyone please help me.

 

 

Full image location:

http://karlosite.nl/problem/Windows7Boot1.png

http://karlosite.nl/problem/Windows7Boot2.png

http://karlosite.nl/problem/Windows7Boot3.png

http://karlosite.nl/problem/Windows7Boot4.png

http://karlosite.nl/problem/Windows7Boot5.png

http://karlosite.nl/problem/Windows7Boot6.png

 

 

Thanks.

[Jorgen Nilsson]

Hi,

I would start with enabling the "Enable Command support" for the boot image under properties, and then check for the SMSTS.log file under X:\ for errors.

Alos verify that you get an IP address and can resolve the SCCM server name both with FQDN and servername.

have you configurerd a Network Access account for the site?

Regards,

Jörgen

[JigSaw1st]

Hi Jorgen,

 

I will see what i can do tomorrow at work. But how do i make a Network Access account and where do i need to put that so i can use it. I have one account in my test lab and that's the Administrator account.

 

I also will enable the "Enable Command support" for the boot image under properties. And i will post what i can find.

But please tell me how and what to do with Network Access account and where to put it so i can use it.

 

Thanks.

[JigSaw1st]

Which secuirty and permissions must i give to the SMSread domain user?. Now i made a SMSadmin account and a SMSread account.

SMSadmin has the full administrative privileges om my sccm server (added to the Local administrative group). And SMSread is just a domain user and also the Network Accsess Account of my Computer Client Agent of SCCM. But still no luck for me to get the Task Sequence running.

[JigSaw1st]

No one:(?

[RebelRenegade]

Looks like you might not be getting an IP address. Once you have the F8 support enabled, hit it so the computer won't reboot and do an ipconfig.

[JigSaw1st]

If you see this image that i post http://karlosite.nl/...ndows7Boot1.png

My client is getting an ip address from my DHCP server. And what is F8 support and where can i enabeld it? sorry but im new to sccm. I worked with it alot but its my first time to deploy Windows 7.

[Peter33]

He means that you are not getting an IP in the PE phase. Did you aplly the network drivers to the boot wim?

[JigSaw1st]

In my clean Windows 7 install i did'nt inject any drivers mabye that the problem. But then i picked up the same laptop and installed a OS (Windows 7) plus all drivers of the Laptop and some apps. I will deploy and test the reference image the same way. Do i need to inject the network driver sepeart with the Boot.wim file?

 

Do you guys think that the problem? that i don't get any ip in the PE phase my clean Windows 7 install package. bec there i dind't inject any drivers.

[RebelRenegade]

The PE phase doesn't have full driver support. Sometimes you have to inject the drivers into your boot.wim. Instructions for doing that and enabling F8 command support are on this forum and also easily found on google.

[JigSaw1st]

Okay I will try It to inject the driver into the boot.wim file. But another question why do I get the task sequence when I make a bootable cd of it, but there I have to configure the ip address by hand otherwise i get an error that the task sequence couldn't be found.