Sccm 2012 r2

[kevin_lane]

our sccm server has gone belly up and just before half term u please see attached

 

i'm trying at the moment to try and get this back online and i'm struggling for about a week I've tried recreating the boot images for sccm 64 bit and 32bit etc and still nothing works and im at the point now think about removing the dp point from sccm and reinstalling and seeing if that works. or create a new sccm server alone side the current one

 

I've tried the method of un-ticking / ticking the pxe from the DP settings and multiple reboots etc i've creating a blank vm and its doing the same thing the other thing,

 

the pc im trying to image is HP 8300 SFF and it does the same thing on other hardware, i know the drivers have to be injected to the boot file but i feel there is something else at play here and im not sure what

 

i was going to ask was would any one be able to give me a copy of your boot.wim 64 bit

 

and i feel like im doing the same thing over and over again

 

or if anyone has any suggestions im more than happy to setup a call / remote session, id be very greatful

Edited August 1, 2018 by kevin_lane

[Fazza]

Try uninstalling the ADK and then re-install the latest version - after that then try and recreate your boot images.

[Steve21]

Happy to have a quick squiz at it if you got Teamviewer or something on it, but could be a lot of things really. What was changed originally that broke it? Anything DHCP/switch wise? Version Upgrade?

 

Steve

[kevin_lane]

@Steve21 I've pm you

[itwasntme]

Having any issues other than OSD? As @Steve21 asked, what changes have been made recently? Do you integrate MDT? If issues are only OSD, does it make a difference when trying to OSD a known device vs unknown device?

[Davit2005]

If it is Windows 10 you are trying to image, deselect all the drivers, re-deploy and see what happens.

[kevin_lane]

just to give an update on the problem for some reason resides in that when you power on the pc it goes to boot\x86\pxeboot.n12 and not SMSBoot\x64\wdsnbp.com even though DHCP is telling the client to use the correct path...

[FN-GM]

DHCP options are not officially supported by Microsoft. Use IP Helpers on the switch (like you would use them for DHCP servers).

[kevin_lane]

Thanks @FN-GM I know what your saying but this use to work before the problem but I understand what your saying :/

[kevin_lane]

FYI these are my SMSPXE logs

 

https://social.technet.microsoft.com/Forums/en-US/5afe3981-fd00-4975-b024-289c40f779e3/any-ideas-?forum=ConfigMgrCBOSD

[FN-GM]

Thanks @FN-GM I know what your saying but this use to work before the problem but I understand what your saying :/

 

If it isn't working now I would use this chance to switch. You have nothing to loose.

[kevin_lane]

OK !! Update !! getting excited !! so after reading a lot of stuff and trying to understand how the matrix of the PXE and WDS and SCCM really integrate under the hood i decided to take the plunge and removed the MP and IIS and now im getting this and going past the f12 option so im taking this as a small win lol and carry on hacking the matrix of sccm

[kevin_lane]

so now i'm at this point for some reason this ts thinks the application is not to be found however i've checked the distro logs and it is there....i've tried removing the application that its unable to find and see what happens but then it complains of the next file in the list that it cant find ? suppose no one has came across this before have they ?

 

https://social.technet.microsoft.com/Forums/en-US/949574ac-c947-4ff4-a817-263014246ee2/osd-failed-package-cannot-be-located-on-distribution-point?forum=configmanagerosd

 

tried the above and recreate but unsuccessful

Edited August 8, 2018 by kevin_lane

[kevin_lane]

ok so i can please to say that everything (imaging wise is now back to normal and complete)

 

thanks for your help

 

p.s that last bit was the boundaries section i just forgot to create the group and assign it to the site

Edited August 8, 2018 by kevin_lane