[wds] PC's are keeping same computer name

[paulvernon63]

I'm deploying an image but the computers are keeping their original computer names. I have tried setting the naming policy and even stopping the computer from being added to the domain (which doesn't work either; it still is added to the domain). Not using any specific answer files and keeping things very simple. Anyone any ideas?

Thanks,

Paul.

[HallX]

Did you run Sysprep.exe on the computer you took the image from?

[paulvernon63]

Yes. It's an image we've deployed successfully before.

[tmcd35]

Are you deleting the computers from AD prior to imaging? What imaging system are you using and have the machines been imaged with it previously?

[paulvernon63]

Thanks for the reply. That might be the issue.

I'm using WDS. I probably need to explain in a little more detail what I'm attempting.

I tried to deploy an image to some Toshiba Satellite Pro NB10-A laptops but they will not let me PXE boot even if I flash the BIOS to allow access to the disable secure boot and select CSM boot options. I decided to deploy the image to the NB10 HDDs by putting the drives into some Tosh Sat Pro C50-A laptops - these laptops had already had the same image deployed to them. The image deploys OK but the computer name stays the same. The laptops also appear on the domain even if I tell WDS not to allow that. Deleting the original C50 computer accounts from AD might be the answer but the problem with doing so is that the original C50 laptops will also need re-imaging when I'm done with the NB10 drives; I guess that won't be too much of an issue, comparatively - I've done the drives in batches using only five C50 laptops so only need to redeploy to those five C50s.

Does that sound like it makes sense? DO you think the image will deploy correctly if I delete the AD account; ie with a new computer name / onto the domain if I select that option?

Paul.

[tmcd35]

I think the AD accounts are getting in the way, WDS+AD are pretty cleaver in that regard. Here's what I'd do...

 

Image all the machines, don't worry about the naming.

Then manually for each machine...

- Take it off the domain

- Delete all AD computer accounts

- Create new AD computer accounts in the right OU's

- Rename each machine accordingly

- Re-add all machines back to the domain

[paulvernon63]

Many thanks for the suggestion. Really appreciate your help.

[free780]

Either that or create a discover image using pendrives/cds. Can these netbooks not UEFI pxeboot. Bear in mind you need Server 2012 WDS to make this possible. I would never move the hard drive and expect it to work. Their are numerous GUIDS set for each PC/laptop etc. Have you thought about MDT ?

[tmcd35]

I would never move the hard drive and expect it to work. Their are numerous GUIDS set for each PC/laptop etc. Have you thought about MDT ?

 

Excellent point. If you do go down the manual route, then it'd be best to sysprep the machines after you've brought the image down but before you move the hard drive.

[free780]

If you do have to do the manual route. Which will be a pain if you have to re-image.

 

Get the wim file. I'm assuming its syspreped and that you just wan't a BIOS deployment not uefi.

 

Boot into some winpe environment. Use command prompt. You can do a script for this. If the wim file is on a network location you need a map a drive with credentials.

 

diskpart

sel dis 0

clean

cre par pri

format fs=ntfs quick

assign letter=c

active

 

imagex /apply c:\

bcdboot c:\windows

 

wpeutil reboot.

 

You need to manually set the pc name, join the domain, install virus check etc.

 

Though fixing the PXE would be better in the long term.

[paulvernon63]

Thanks for posting.

We use PXE boot ... I'm CSM booting because I understood that UEFI will not work with Windows 7 deployment ... we don't have Server 2012 on this network currently.

Not sure what MDT is. I'm essentially following some instructions put together by a colleague; I can follow some of it but can't tweak things very much without advice. It sounds as though there might be a better / alternative method. I was thinking the other day we will probably need another method if /when we begin deploying Windows 8.

[paulvernon63]

Excellent point. If you do go down the manual route, then it'd be best to sysprep the machines after you've brought the image down but before you move the hard drive.

 

Thanks. I'll give that a go. I've just deployed the image after deleting the ADUC computer account and a new computer name was generated, as per the format I have specified in WDS. Of course, I'll need to delete that new account if I want to use that laptop to deploy the image to another HDD.

Might this (not sysprepping) explain why the NB10 laptops can't identify / install drivers for an external drive (with drivers etc on it) after I've moved the HDD? I've had to remove the drive again to copy drivers onto it so I can install the network card.