[sccm 2012] Unknown computer won't join domain

[mrbios]

Hi Chaps and chapettes

 

Seems I've pretty much got my imaging working nicely for a machine that is known to SCCM but for a machien that is unknown it fails to add the machine to the domain, I've even got an OSDComputerName variable so that unknown computers get the correct names we desire.

 

It doesn't tell me that it's failed to add to the domain, neither does it stop the process there, instead it continues on as normal right up until the installation of applications etc and then fails due to lacking the ability to connect to network shares that require authentication to the domain.

 

I'm using the same task sequence to do this as i have done with a known computer, so is there anything extra that needs to be done for unknown PCs?

 

Thanks

[Gatt]

When it fails, do you still have a network connection?

Sounds like the NIC drivers have got a bit screwed up during the deployment...

[mrbios]

When it fails, do you still have a network connection?

Sounds like the NIC drivers have got a bit screwed up during the deployment...

 

At the moment this is just running off VMs in VMware workstation on my machine, not had an issue with any drivers on there before now. The VM i have that is known images fine, the one that is unknown doesn't.

 

That said, i'm having another problem you might be able to help me with Gatt.....My VM that is known, i previously added by importing its mac address, i've tested sending an image to it a few times but now it's randomly stopped allowing me to PXE boot. Instead it just bypasses straight to the "PXE boot aborted, booting to next device" I've tried the "clear pxe advertisements" option, tried updating collection membership....I've no idea how to make it let me send images to it again, any ideas?

[Gatt]

Look in the devices collection and delete all "Unknown" devices

 

SCCM 2012 doesn't do this if it crashes - and you end up in a stuck PXE Abort loop..

[mrbios]

Perfect, thank you! that one had been really bugging me and google was dreadful at helping me solve it

[Gatt]

It did the same with me and it took me a lot of googling to find that nugget of information!

[mrbios]

Still can't get this to work, for some reason SCCM treats my PCs differently when they're "unknown" and my googlefu doesn't seem to have the required skills today.

 

On the brightside though, no more issues with known PCs at all

[mrbios]

Well this issue didn't seem like a driver problem, but after trying some physical machines that i'd made unknown, i ended up discovering that i hadn't deployed my driver packages to distribution points (I think one of my VMs has a different problem though)

 

Annoying really as you never get prompted to do so, as i create them when i import the drivers, so generally i don't go into the driver packages area to do it. Lesson learnt