Much trouble with OSD installation and first steps

[StefanWe]

Hello,

 

i installed in my test environment my sccm 2012 server. It is a windows 2008 R2 SP1 server in english. On this, a sql 2008 R2 server, also in english.

 

i don't install the wds role myself. After configuring my sccm environment i added the pxe option on the distribution point. All site roles are on the same sccm server.

 

For configuring OSD, i took a look in that howto on this page.

 

After a minute i could see that the wds role is installed automaticly. The directory RemoteInstall was created with his subdirectory. But at this time, no wdsnbp.com and the oder boot files are missing.

 

After some research, i copied these files from c:\windows\system32\reminst to my smsboot\x86 dir.

Booting from a client works, but in my esx test env i get a hardware missing error on boot. After adding all required drivers and updates the boot imae and the distribution point, nothing changed. Also the same hardware missing error.

 

I took a look in my eventlog and could see that WDSIMGSRV could not be initialized.

 

Ok, i think i reinstall all PXE components. So i did it. uncheck the PXE option on the distri point. uninstall the wds role and remove the remoteinstall dir on c:\ and take a restart of the sccm server.

 

After all i restarted and uninstalled, i check the pxe option again and could see, that the role is installed again and at this time, the smsboot dir is filled with all required files. (wdsnbp.com, also so on)

 

In my eventlog i could still see the error that WDSIMGSRV could not be initalized. Do i need this component?

 

I restart my sccm server again, now, my wds service hangs on starting.

 

Tomorrow i will reinstall the wds components, but this is not right.

 

Have you any ideas what goes wrong here ? What i can do different?

 

Kind regards

 

Stefan

 

PS: Nice forum

[anyweb]

i wouldnt manually copy the files to the folders above at all, instead verify you've distributed both architecture boot images to the distribution points, have you done that yet ?

 

on the DATA SOURCE tab of both architecture boot images, is 'deploy this boot image from PXE..' enabled ?

[StefanWe]

Hi anyweb,

 

thank you. I deployed my x86 boot image to my distribution point. At this moment, i boot up my win 7 client(vmware guest os). It becomes an ip from the dhcp server, but hangs after the message GATEWAYIP: 192.168.28.1. So the exptected Message "TFTP..." doesn't come up.My win 7 client cannot boot.

 

On the boot image i checked the option "Distributed image through PXE Service point". With or without this option, it is the same problem as described above.

 

(In my smsboot\x86\ directory are all needed files available)

[anyweb]

did you distribute BOTH architecture boot images to your dps ?

[StefanWe]

yes. i distribute both boot images. I checked it again with "content status" and could see that both images are to 100 percent completed on my dp.

[wmmayms]

In 2012 you don´t need to install the WDS manually, just make your DP a PXE point and it will handle everything :-)

If you have problem with a hanging wds service I generally recommend people to try setting it to delayed startup..

 

"In my eventlog i could still see the error that WDSIMGSRV could not be initalized. Do i need this component?" - i get this error to, don´t worry about it :-)

[StefanWe]

Ok. thanks.

 

my sccm configured wds automatically. At the moment wds is up and running. But my client doesn't get a answer from my pxe server. See the attached image.

If i shutdown my wds service. i get a message, that the tftp service is not available. But now, i hangs.

 

I deleted both boot images (x86 and x64). And imported a new image from a win 7 dvd, but only x86.

 

On my dhcp server as startup file, i configured smsboot\x86\wdsnbp.com. This file is also present in the right directory.

 

But why hangs my pxe boot?

[anyweb]

is the wds service hanging ? disable the PXE password on it (remove it) on the PXE tab of your distribution point, try restarting/starting the wds service

[StefanWe]

Hi,

 

now after restarting the wds service, it crashes on every start.

 

in the eventlog, i could find those entries:

 

Provider SMSPXE was loaded from c:\program files\...and initialized successful but the provider did not register the required callback funktioncs

 

and

 

an error occured while trying to initialize provider smspxe.

 

and the same error but with WDSPXE

 

 

What shit is this?

 

i unchecked the pxe option two times. i uninstalled the wds role again. and every time, sccm install it again, so much errors...

 

Use i a wrong windows version? Or need i some updates?

[wmmayms]

try installing WDS manually, configure it. Reboot and then remove the wds again and then let SCCM have a try.

 

And if you are using DHCP options remember to specify booth of these:

 

Options 66: 10.0.0.10

Options 67: SMSBoot\x64\wdsnbp.com

 

 

 

Oh and yet again, try using delayed startup for the WDS service.

I have seen this do miracles in my lab env more then once