Jump to content


pembertj

Windows 10 Enterprise Computer Name Problems (SCCM 2012 R2 SP1)

Recommended Posts

I'm having a strange issue, starting to mess around with building a Windows 10 Enterprise image for our campus and I seem to be having a problem with the task sequence properly reading in the computername that I give it.

Windows PE phase:

1. Prompt for OSDComputername using VB Script (same thing we have done with Win7/8.1 with no issues)

2. Use powershell to check variables: OSDComputername shows correct name and _SMSTSMachinename shows correct name. Checking $env:computername in PE shows MINIWINPC or something (which is normal)

3. After Apply Network Settings C:\windows\panther\unattend\unattend.xml shows the correct name

 

Windows phase:

1. Machine gets name WIN-XXXXXXX

2. Use powershell to check variables: OSDComputername shows correct name and _SMSTSMachinename shows correct name. Checking $env:computername in PE shows WIN-XXXXXX or later in the task sequence DESKTOP-XXXXXX

3. Machine joins domain and at end of task sequence has name of DESKTOP-XXXXXXX but seems to sometimes join domain under name WIN-XXXXXXX and end with DESKTOP-XXXXXX and cannot log into the machine (security database relationship error with domain controller)

 

Has anyone ran into anything like this in Win10 or Win7/8.1 and found a solution? Out of probably 20 imaging attempts and fiddling with various settings I have only got it to get the correct name once...

 

Thanks

 

~Tom

Share this post


Link to post
Share on other sites

I do the same thing (.HTA at the start of the TS to supply a computer name), and am seeing the same problem with the machine name. The computer is named DESKTOP-xxxxx at the end of the deployment.

 

What's your source image for the OS? I'm using a captured reference image with Office 2013. When I switch the image to the install.wim from the Enterprise .iso, the problem goes away.

 

Odd thing is, it was working for me, but then I recaptured my reference image to include .NET 3.5, as one of our apps requires it.

Share this post


Link to post
Share on other sites

Check the CCMExec.log on one of your DESKTOP-xxxx machines. If you scroll back to the beginning of the log, do you see time stamps from your original capture? (I am)

 

I'm wondering if the client isn't getting initialized properly during the capture and so we're deploying an image with remnants of the original client install.

 

Edit: Nevermind - just mounted the .wim of one of my older images that works fine and it has the logs from the original capture.

Share this post


Link to post
Share on other sites

Hi pembertj

 

I am seeing the same problem.

I made my .wim file on a SCCM 2012 R2 SP1 CU1 - without ADK 10 installed.

It's a regular Build and capture from the DVD media from Microsoft partner website (build 10240 x64)

 

My logfiles state the everything is all fine and dandy - but it gets ignored - just like your are seeing.

A scripted install though works just fine :) - but i would love it getting a build and capture to function too :)

 

Edit 1: Also had a look into c:\windows\panther\unatten\unattend.xml - to see if the computername is correct, which it is.

Edit 2: I took a closer look into c:\windows\debug\netsetup.log - to see what computername it thinks it has, and this shows me "Win-xxxxxx" - and i can see that it is successfully joined to the domain, afterwards i look on the domain, and love and behold, it is - BUT the computername of the machine is not "Win-xxxxx" it's "Desktop-xxx".

It's a bit strange.

 

Kind Regards

Letster

Share this post


Link to post
Share on other sites

I'm using the Win 10 ADK, so that does not appear to be the source of the problem. I'm also on 2012 R2 SP1 CU1 (have been on CU1 prior to beginning my Windows 10 testing).

 

I also ran into this problem when I first started testing SCCM and my build and captures were failing because of the "updates with multiple reboots" issue. The build would fail and end up at the login screen (rather than the Windows setup page) get captured like that, and subsequent deployments with that capture would get named MININT-xxxxx.

 

Even though I had the new "retry" option turned on for Software Updates, I disabled all software updates in my build and capture for Windows 10 and still have this problem.

Share this post


Link to post
Share on other sites

The ones I've been testing it on are Hyper-V VMs that have worked fine for win7/8.1 captures that we do. I'll test more on vmware vms and some physical machines and see if it is something with the hyper-v VMs...

 

~Tom

 

//edit: strange it worked on a vmware vm with no problems. I am going to attempt on another model Dell machine here (or two). I'm curious if it is just related to Hyper-V VMs for some reason...

Share this post


Link to post
Share on other sites

Hi to all,

 

I'm having this exact issue. Computers change to Desktop-xxx and the renames the workstation name on the SCCM. And when I try to logon the computer after installation is finished, I have this message:

 

The security database on this server does not have a computer account for this workstation trust relationship...

 

The OS is Windows 10 x64, and I have the unattend file on the Task Sequence. I don't know many forums where this issue is being posted online. I didn't test this with a physical hardware but from what I read here this could be related with Virtual Machines running under Hypver-v? Or does anyone know if this is also happening with physical hardware?

 

Thanks in advanced!

Share this post


Link to post
Share on other sites

Reviving a semi-old thread here...I'm also having the same experience with imaging my hyper-V VM with my captured Win10 image. I haven't had a chance to test this on a physical station however. Other thread that I've come across all share the same issue, but there is never a defined resolution. Has anyone made progress on this?

Share this post


Link to post
Share on other sites

Thanks for the info...I have it on my to-do list to get that upgraded, but have not had the time just yet. I will update to the latest versions of those and see if that makes a difference in my environment.

Share this post


Link to post
Share on other sites

Well I ran across some interesting information the other day...I forget why I was looking at this thread on reddit, but from what I can tell, this may be the issue: Hyper-V VM's need to Gen 2 for deploying Windows 10 successfully/correctly.

 

I'm using the same VM that I have for years at this point, and hadn't even thought of changing/checking the VM generation. I updated to the 1511 ADK the other day and noted that I was still experiencing the issue. When I created a new gen 2 VM on my workstation, however, it worked like a charm.

 

I hope this helps for anyone else who might run into this issue.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...