Hi there,

I have the fantastic opportunity to play with SCCM 2012, I managed to deploy OS without any problems, create bootable media and capture images and then deploy those images and everything worked perfectly fine until this morning. I was testing an image that I captured the previous day, I deployed it on two machines and I was pleased with the result. Later on I was messing with multicasting as this will need to be implemented within our system. I made sure it is enabled on the distribution point (which it was), then i changed the settings on the image. Then I installed Admin Studio, because it was part of my task. Also I messed a little bit with the network discovery as it was not discovering computers which are not part of the domain(still no luck with that but this is another topic). After making the changes to the multicasting I thought alright lets see if it works. I used the same task sequence i used to deploy the captured image(which worked before!!!) and when i restarted the computers it would give me an error, something like TFTP Server: Access violation. I knew what the problem was as i had similar issue before, so i checked the DHCP and saw that "Magically" the path to the boot image had an additional "\" in the beginning. Deleted that "\", restarted the computers again. Now it would get an ip address as usual, then it would download the wdsnbp and then it would say something about Architecture: x64 (the machine is x86). Then it gave me the F12 option to boot, once pressed it would say again something about Architecture: 64, and then I will get a blue screen saying that  "The Windows Boot Configuration Data file does not contain a valid OS entry" and give me an error code of: 0x0000098. I read some topics about it and people were suggesting that the boot images are not distributed on the DP or the PXE is not enabled, which is weird as it used to work before, so I deleted the boot images from the DP and redistributed them to the DP making sure that PXE is enabled everywhere but still no luck. From what I understand is that it cannot locate boot images on the DP and I can confirm they are there. I restarted both the dc and the SCCM server but still no joy.

Any suggestions would be much appreciated.

On another topic, we are planning to change the domain (have entirely different domain controller). What changes have to be done in SCCM in order to work alongside with the new domain. Is it just a case of creating again a new container, giving permissions, setting up bounderies, creating new security accounts?

Thanks,

LP

Are you going to "change" the domain or add another one? You can't move a configmgr server from one domain to another. You can however support clients across domains.

Had this problem before and solved it as shown here

http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-task-sequence-fails-with-bcd.html

Are you going to "change" the domain or add another one? You can't move a configmgr server from one domain to another. You can however support clients across domains.

Yep...as Gerry said, installed a fresh CM in the new domain and let the clients join that CM as they are migrated over.

Had this problem before and solved it as shown here

Try using SMSboot\x64\wdsnbp.com as your DHCP option (are you using UEFI?). I'm assuming both boot images have been distributed to DP

As for licensing, use the same key - as the first environment will be decommissioned

I'd suggest not using any DHCP options. they are unreliable. Use IP Helpers.

Try using SMSboot\x64\wdsnbp.com as your DHCP option (are you using UEFI?). I'm assuming both boot images have been distributed to DP

As for licensing, use the same key - as the first environment will be decommissioned

No, the server is located as follows:

1. automatically if on the same subnet

2. via IP Helper (as John said - recommended)

3. DHCP scope option

Hello again guys,

We got the new domain up and running, I uninstalled SCCM 2012, done everything as it should be and we still have the same problem as described above. When we boot it grabs an IP address then it points to the correct TFTP server, but then I noticed that it tries to boot from a different file than what we specified, it tries to boot from:

Boot\x86\wdsnbp.com instead of SMSBoot\x86\wdsnbp.com

and again it would say something about x64 architecture.

I have checked more than 10 times the configuration on the DHCP options and it is correct.

I have validated and revalidated the content on the DP, send and resend the Boot images on the distribution point.

Now I followed Gerry's guide but no joy, I did a delayed service start of WDS and still nothing.

Any more suggestions would be much appreciated.

Lach

The easiest way to fix this is to NOT use DHCP options. I've never seen them work reliably. Get rid of them and configure IP helpers on the routers.

If everything in on one subnet you don't need to do anything, it should just work.