Hallo there, hope someone has an idea of what i missed... I'm new to SCCM and i'm trying to deploy Windows 7 machines with SCCM and thought I did everything, guess i must have missed something. I used the buildin boot image that comes with SCCM. I have everything except the Database hosted on the same server. I managed to create an image from a source device and loaded the image file to SCCM. Now when i want to deploy the image, the new device which i added manually to specific collection. It boots up fine in PXE which loads, next screen is the SCCM background image, where a small window says "network initializing" then this windows dissapear and nothing else happens for a while.......after about a minutes or so it reboots again. This time skipping PXE boot and complains that no OS is present... (which is true as this is a blank Harddisk) The image process simply don't ever start. There are many many log files and not sure in which to look. Can't find anything that makes sense. Hope someone have an idea Thanks Jesper

You are probebly missing the correct NIC driver in your Bootimage... For troubleshooting during WinPE, take a look at this post: http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

I agree with Peter, check that you've added the network driver to your boot image, enabling command prompt support in Windows PE will help you verify this (network connectivity), if you have no ip address or cannot ping the FQDN of your Configmgr server then you need network drivers added to your boot wim file, dont forget to update your boot wim images to the distribution points after adding the new NIC driver and don't add more drivers than you need cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Hi Borsk, could you post the smsts.log file for futher troubleshooting ? As Nial wrote, make sure you have the command prompt enabled, let your machine boot up and press F8 to open the command prompt. If you have network access, look at the machines Smsts.log file, should be in X:\Windows\Temp\SMSTS\smsts.log. If no network, add the driver to your boot image. Also make sure all the Packages used in your task sequence have a distribution point. If you have a driver package included, make sure that the package version is greater than 1. If not, update or refresh the distribution point for the driver package ... Regards, Stefan

Hi Peter Sorry for late reply here when you were this fast, i got cought up in a meeting and "forgot" about the post here... Looks like you are quite right Peter, I only tried to ping the machine right after it got the IP address in the boot section and that worked fine, so didn't consider this option :) As a test destination i'm trying to use a VMWare machine using the VMXNET3 I added the drivers from another x64 Windows 2008 R2's folder C:\Program Files\VMWare\VMWare Tools\Drivers\vmxnet3 I just still dont get an IP Address i PE. Any experience with doing this in VMWare environment? I will will try with a laptop tomorrow.

Hi Stefan After i did the above and found the right driver i got an ip address but it still failed. I looked at the log file you mentioned and used the log viewer, fast i identified that it seemed to be an access problem of the packages. I granted everyone full control of the package folders and now the image process start. Sub Question: If i load a Windows 7 disc in to the Operation System Install Package i can then create an automated installation that is completely hardware independant is that correct? (assumed i added the right drivers) Thanks Jesper

granting full control is a security risk, you should start with READ only and work up from there... as regards Deploying Windows 7, I'd recommend you use the Deploy 7 guide in this list, it will show you how to do it, step by step cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Hi Peter Sorry for late reply here when you were this fast, i got cought up in a meeting and "forgot" about the post here... Looks like you are quite right Peter, I only tried to ping the machine right after it got the IP address in the boot section and that worked fine, so didn't consider this option :) As a test destination i'm trying to use a VMWare machine using the VMXNET3 I added the drivers from another x64 Windows 2008 R2's folder C:\Program Files\VMWare\VMWare Tools\Drivers\vmxnet3 I just still dont get an IP Address i PE. Any experience with doing this in VMWare environment? I will will try with a laptop tomorrow. I know it's always tricky to get it working with the VMXNET3 -adapter, so for testing I would use the (more general) E1000 -adapter.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

After i did the above and found the right driver i got an ip address but it still failed. I looked at the log file you mentioned and used the log viewer, fast i identified that it seemed to be an access problem of the packages. I granted everyone full control of the package folders and now the image process start. Did you configure the Network Access Account (Site Settings > Client Agents > Computer Client Agent) ? This Account is used by WinPE during OSD to access the SCCM Distribution Point Shares. Normaly "Domain User" Rights should be enough for this Account. After configuring the Account, you have to update your Boot Images (Update Distribution Point). Sub Question: If i load a Windows 7 disc in to the Operation System Install Package i can then create an automated installation that is completely hardware independant is that correct? (assumed i added the right drivers) Yes, this is possible. For best results use a Virtual Machine to build your "Master Image". When deploying Win 7 you can assign the drivers depending on the hardware that it is targeted to. There is a very good article from Johan Arwidmark that describes the driver assignment stuff > http://www.deployvista.com/Default.aspx?tabid=70&EntryID=82 (Option 1). Regards, Stefan