The easy way of re-OSD, seems to be the impossible way

[johan.tingstedt]

I am currenty replacing SCCM 2007 with SCCM 2012.

Because of that, I have two fully working environments.

Performing a new OSD with a machine directly from the factory is easy in SCCM2012:
I simply import the compuer, with it's desired hostname, and the MAC adress of the machine, and point
towards a specific device collection, allowing the task sequence to run.
(I do not use unknown computer support in the 2012 enviroment, but we did in the previous 2007 environment).

Performing OSD that way, works like a charm!
I can even deploy the SCCM 2012 agent to a SCCM 2007 machine, making it communicating fully, then making the system
a member of the very same osd-collection, in that way triggering the OSD via PXE or from Windows in the Software Center.

I'm using Option 66 and 67 in my DHCP, on specific scopes.

Recently, I've been trying to educate my collegues, in how to use the SCCM 2012 console.
A collegue of mine simply asked: "what's the easiest way to reinstall a computer, that is currently in the SCCM 2007 system?"

Well, as I have the "Active Directory System Discovery" discovery method enabled, I can actually see the objects from our AD
under devices in SCCM 2012.
Deploying the SCCM 2012 agent to one of those object would work, and then making it a member of the collection.
But that's a bit unnecessary, right?
So, I just tried to rightclick on the object, which currently says Client=No (as the machine is a member of the sccm 2007, or none at all),
choose "add selected items" -> "add selected items to existing device collection", choosing my osd-collection.

Seems legit?

Trying to PXE a machine gives me the following:

"CLIENT MAC ADDR: BLABLABLA GUID: BLABLABLA
CLIENT IP: 172.X.X.X MASK: 255.255.255.0 DHCP IP: 172.X.X.X
GATEWAY IP: 172.X.X.X

Downloaded WDSNBP...

Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: MY SCCM WITH WDS (gateway: 172.x.x.x)...
No responsde from Windows Deployment Services server.
Launching pxeboot.com...

Press F12 for network service boot."

When pressing F12 I get this:

"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next".
3. Click "Repair your computer".

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configuration data."

Any thoughts on this?
Seem like doing a re-OSD the easy way, is an impossible way.

Thanks
Johan

[Rocket Man]

Try reseating the RAM on the problematic machine!

[johan.tingstedt]

Hrrm, this is not a problem with ONE particular machine, but all of them!

[johan.tingstedt]

Anyone else?

This is a "make or break" situation for me