OSD deployment fails on preparing network connections

[Steve.sven 0]

My environment;

 

Running SCCM 2012 R2 on 2012 R2 server

DC Server 2012 R2

 

All running on VM's on Windows 8 hyper-v

 

When doing any deployment now OSD deployment fails on "preparing network connections" ?I have recently upgraded all my lab to 2012 R2 servers and SCCM 2012 R2 I have built from scratch again.My deployments did work ok when it was all server 2012/sccm 2012 sp1 .I was thinking possibly need some sort of network drivers in the boot image - but my lab is all on a windows 8 hyper-v vm's and did not need to inject driver packages when it was the previous svr 2012/sccm 2012 SP1 enviroment ?

 

Any ideas ?

[sccmjohn 2]

can we have the related log files.

[keety 1]

Probably network drivers.

 

Make sure you've enabled debugging and press F8 went it boots up, make sure you;re getting an ip address. Although with it being hyper-v i'd imagine they drivers are inbox drivers and should be part of winPE. I've not played with hyper V much but I know on vmware you can set to a default legacy NIC.

 

You can try re running teh task sequence by goign to x:\sms\bin\i38\tsbootshell.exe (for x86 use x64 for obviously x64)

 

With new models of kit I've found it a bit fiddly getting the right drivers, I tend to use drvrload to load them up and make sure they work before integrating them into the boot image.

[y0da 0]

few questions here....

 

at what point do you check if you have an ip address ?? i was told you have to time it right....once i hit f8 i typed ipconfig but no ip address......

 

can you please explain how do you use dvrload ?? is it an executable ?? where do i find it and how do i use it ??

 

also i had question about the log files......which log file do i check and where do i find it ???

 

thank you!!!

[oxyle 1]

You can find the log files for the client during OSD in the following location.

• Before the HDD formats: "x:\windows\temp\smstslog\smsts.log"

• After the HDD formats: "x:\smstslog\smsts.log"

• After the OSD applies the OS they are often located within "C:\Windows\CCM\Logs".

[Edenost 2]

I made a quick rough guide on how to add drivers to the boot image here:

 

http://www.windows-noob.com/forums/index.php?/topic/9720-cannot-load-generic-boot-images/

[psshutdown 0]

I had exactly the same issue today and went into debugging after preparing network connection and there was no IP. I injected the correct driver into the boot image, re-distributed and this time it worked.

[Steve.sven 0]

It turns out my network config was wrong on my virtual environment .I did not have 2 seperate address ranges - 1 for my internal vlan and one for my external internet routing .Once this was in place everthing started working a ok !Im now doing zero touch deployments no problem!

 

Thanks for you replies .

 

Cheers

 

Steve

[kyedj 0]

Hi,

 

I have a same problem but when I hit F8 I can run ipconfig /all and everything seems okay. It has a network driver / It has an IP Address / I can map network drives using net use and all seems fine.

 

But it still restarts soon as the "Prepearing Network Connections" comes up. Obviously it will stay on whilst I am in the CMD but soon as I close the CMD or type exit and it enter the machine will restart. Not sure where to go from here as most posts are saying about drivers but I'm not sure as I am getting network connectivity.

 

I have managed to get the smsts.log

 

Kind Regards

Kye

smsts.log

[kyedj 0]

I forgot to mention:

 

I am running:

Srv 2008 R2 SP1 DC

SQL 2008 R2 SP1

SCCM 2012 R2

 

I have rebuilt a couple of times from scratch and have had the same issue even when following the guides on how to install.

 

I have tried whilst using Srv 2012 R2 DC as well as trying with SQL 2012 and so on.

 

There must be a step or something that is causing the same issue?

 

Kind Regards

Kye

 

 

 

Hi,

 

I have a same problem but when I hit F8 I can run ipconfig /all and everything seems okay. It has a network driver / It has an IP Address / I can map network drives using net use and all seems fine.

 

But it still restarts soon as the "Prepearing Network Connections" comes up. Obviously it will stay on whilst I am in the CMD but soon as I close the CMD or type exit and it enter the machine will restart. Not sure where to go from here as most posts are saying about drivers but I'm not sure as I am getting network connectivity.

 

I have managed to get the smsts.log

 

Kind Regards

Kye

[Peter van der Woude 143]

Based on the error message below I think you're having some issues resolving the MP. Please check if the machine is able to resolve the MP.

 

[LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]

![LOG[unknown host (gethostbyname failed)]LOG]

[kyedj 0]

Based on the error message below I think you're having some issues resolving the MP. Please check if the machine is able to resolve the MP.

 

[LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]

![LOG[unknown host (gethostbyname failed)]LOG]

 

Okay thanks I shall have a look.

 

Kind Regards

Kye

[kyedj 0]

Based on the error message below I think you're having some issues resolving the MP. Please check if the machine is able to resolve the MP.

 

[LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]

![LOG[unknown host (gethostbyname failed)]LOG]

 

 

Brilliant thanks, I double checked my DHCP and low and behold it had changed my Server Options \ DNS Server as 127.0.0.1 by default so changed it and now seems to be booting and running the TS as I type this now so will let you know how it goes.

 

Kind Regards

Kye

[andrew1066 0]

Hi There I have a similar issue. When I try to deploy a new system I too get as far as "Preparing Network Connections" and the computer restarts. I have tries again and this time I pressed F8 to check if the network adapter was loaded and have a valid IP address. Not only was the correct NIC loaded, I also have name resolution to the SCCM DP. I have the same issue no matter what computer I attempt to apply the OSD.

 

I have attached a screen shot and the smsts log file.

 

Any ideas would be fantastic as I'm completely at a loss.

smsts.log

[Grubsy 0]

I've just started getting this issue and for the life of my can't work out why. As in the screenshot above my networking is all ok. I can ping by hostname, map drives to copy the log files etc. It does show the error below and I have no idea why. I definitely have two TS advertised as available to unknown computers and haven't changed these deployments for quite some time.

There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows)
 

Any ideas? I've re-created my boot image from scratch and added the required nic driver and end up back where i started with the message about no ts available to this computer

[Grubsy 0]

So I found this thread and looks like it was the same issue.

https://social.technet.microsoft.com/Forums/en-US/1a6f8faf-1553-466f-b11c-0f24c6ec23f5/unknown-computers-no-longer-seeing-task-sequences?forum=ConfigMgrCBOSD

In my smsts.log it showed:

Unknown machine GUIDs: f35d0b2b-43a4-4cbc-897d-aea9a2f85412 f3cf2a97-4b9a-46bd-83da-8c267b85878b - I'm thinking the 2nd GUID is the x64 unknown computers

I opened my SCCM database and then went to the dbo.System_DATA table. I then ran the query below

SELECT TOP 1000 [MachineID]
      ,[InstanceKey]
      ,[RevisionID]
      ,[AgentID]
      ,[TimeKey]
      ,[rowversion]
      ,[Name0]
      ,[SMSID0]
      ,[Domain0]
      ,[SystemRole0]
      ,[SystemType0]
  FROM [CM_ADL].[dbo].[System_DATA] where SMSID0 like '%f3cf2a97%'

The record that was found was the last machine I remember deploying successfully.

I deleted this 'Device' from Assets and Compliance -> Devices and then started the PXE boot again. This time the Task Sequence Wizard loads

I am running: CM 1702 / Console version: 5.00.8498.1711 / Site version: 5.0.8498.1000

[TrialandError 10]

Nice troubleshooting, sounds like you figured it out pretty quickly. It is a known issue and MS has released a hotfix that should take care of the root issue. See https://support.microsoft.com/en-us/help/4019926/update-rollup-for-system-center-configuration-manager-current-branch-v. Looks like the issue is more prevalent if the Previous button was used during the task sequence wizard.