localzuk Posted October 21, 2015 Posted October 21, 2015 I am trying to get a Windows 10 image up and running in SCCM 2012 R2 (with all the latest updates, so it should fully support Windows 10), but for some reason when I image a machine, everything works fine until I look at the PC's name. Instead of the name I gave it in SCCM, it now has a name of "DESKTOP-XXXXXXX". It is joined to the domain too, but in Active Directory it is in as "WIN-YYYYYYYYYY"! So, the computer and its account don't match! I'm at a bit of a loss. There's nothing in the SMSTS log. The NetSetup log in C:\windows\debug has the correct name for a bit, then suddenly switches to WIN-YYYYYYYYY, and there is absolutely no mention of the DESKTOP-XXXXXXX name at all. On top of all that, the computer has changed its name in SCCM.
JoHimself Posted October 21, 2015 Posted October 21, 2015 Do you have any steps to set the name during the TS? Are you using a custom base image or the one from the Windows 10 disk?
Blue_Cookeh Posted October 21, 2015 Posted October 21, 2015 Do you mind posting your smsts.log by any chance? A fresh pair of eyes might help
Annabelle Posted October 22, 2015 Posted October 22, 2015 how is the computer name defined? did you define the variable OSDComputerName?
localzuk Posted October 22, 2015 Author Posted October 22, 2015 Ok, some more details. I've never done anything special to name computers for my Windows 7 deployments. The process I follow is: Build and Capture using the standard task sequence created by SCCM, except the installer is set to the installer rather than Image. Deploy using the standard task sequence, using the image captured using B&C, and an unattend.xml file in a package to set regional info correctly. All client computers are added to SCCM manually, using their MAC address, and given their name there. I have done the same thing with my Windows 10 image attempt. I'll rerun the image and get some smsts logs for you all too.
snagrat Posted October 22, 2015 Posted October 22, 2015 I had this when using OSDComputerName method but found that manually rebooting machine after the build sorted it
localzuk Posted October 22, 2015 Author Posted October 22, 2015 Hmm... still imaging that machine to get SMSTS logs, but I also imaged a different machine (different model also), and it has named the machine correctly. Only difference between the images is the drivers.
localzuk Posted October 22, 2015 Author Posted October 22, 2015 So, here are the SMSTS logs. https://www.dropbox.com/s/lbb7nega1pilghv/smsts.zip?dl=0
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now