SCCM 2012 Starts Booting Into Win PE Flashes then restarts

[dsapikowski]

We have recently setup and are trying to deploy operating systems with SCCM 2012 on server 2012.

In out test vlan computers image just fine. When deploying images in the production environments we run into issues.

Currently when we pxe boot it never makes it to the OSD prompt it just reboots. It makes it to the preparing network connections and then flashes and restarts. We have verified the the drivers are there even when into the boot image x64 and applied the appropriate nic drivers. Still just reboots when it gets to that point.

Here is the trace log.

smsts.log

[Rocket Man]

Is your system getting a DHCP address at this stage before it reboots and can it ping the FQDN of the site server/DP?

[dsapikowski]

We are getting DHCP and we can ping the SiteServer/DP via IP address. Out Site server is in its own vlan and we have that bound with the vlan we are trying to image with, and from within that vlan we can't ping the actual FQDN but we can ping the IP address that is associated with it. Apologize for my lack of knowledge I am not a true sys admin so I will try and give you the most information I know or can figure out. Thanks In advance

[dsapikowski]

Also forgot to mention this seems to happen mostly after the computer fails to image for the first time and they are new computers to SCCM with no prepopulated information in SCCM for them. After they fail they do show up with unkown in SCCM and thats when we get the results as decribed above.

[Rocket Man]

We are getting DHCP and we can ping the SiteServer/DP via IP address

 

 

You should be able to ping it via FQDN which is very important, you may have a DNS issue in this particular VLAN that the test system resides.

 

For a test can you spin up VM on the server VLAN(SCCM site Server VLAN) and test this to see if it is successful at connecting to the site server to pull down TS policies.

Have you deleted these unknown objects from SCCM prior to trying your TS deployment again?

[dsapikowski]

Apologize for the delay in getting back to you. We where able to figure it out we have a program that was doing some network monitor of devices and it was blocking the ts deployment. Thanks for your help and suggestions.