pembertj Posted August 7, 2015 Report post Posted August 7, 2015 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 Quote Share this post Link to post Share on other sites More sharing options...
jones948 Posted August 10, 2015 Report post Posted August 10, 2015 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. Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted August 10, 2015 Report post Posted August 10, 2015 Captured image, I haven't tried with just the install.wim right from the DVD - not really a feasible option in the long term... Quote Share this post Link to post Share on other sites More sharing options...
jones948 Posted August 10, 2015 Report post Posted August 10, 2015 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. Quote Share this post Link to post Share on other sites More sharing options...
letster Posted August 11, 2015 Report post Posted August 11, 2015 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 Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted August 11, 2015 Report post Posted August 11, 2015 I have been using Win8.1 ADk as well, but from what I've read on here and a couple of other blog posts it seems like you might actually need Win10 ADK - I am going to attempt the process again today with Win10 ADK installed on my site. ~tom Quote Share this post Link to post Share on other sites More sharing options...
jones948 Posted August 11, 2015 Report post Posted August 11, 2015 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. Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted August 11, 2015 Report post Posted August 11, 2015 We just went to R2 SP1 CU1 as well. Whats strange as well is I've had it fail 20x on VMs but the first time I tried it on a physical machine it works fine... Quote Share this post Link to post Share on other sites More sharing options...
jones948 Posted August 11, 2015 Report post Posted August 11, 2015 Ah, interesting. What VM software are you using? I got excited and put 10 on my workstation and had to put the beta of VirtualBox 5 to do my builds and testing. Trying to recall if it ever worked correctly under the VirtualBox beta. Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted August 11, 2015 Report post Posted August 11, 2015 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... Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted August 12, 2015 Report post Posted August 12, 2015 I've now tested the same task sequence on 3 separate models of Dell machines with no problems. It seems to be tied to (in my case) only Hyper-V VMs... Quote Share this post Link to post Share on other sites More sharing options...
jones948 Posted August 13, 2015 Report post Posted August 13, 2015 Was able to test again today on a physical PC and it worked fine for me as well. Something odd going on with VMs apparently. Quote Share this post Link to post Share on other sites More sharing options...
ZeZe Posted November 10, 2015 Report post Posted November 10, 2015 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! Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted March 1, 2016 Report post Posted March 1, 2016 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? Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted March 2, 2016 Report post Posted March 2, 2016 I don't see this issue any more, but I am on SCCM v1511, ADK 10.0.10586 now - so either one could have had a bug fix that made the problem go away. Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted March 2, 2016 Report post Posted March 2, 2016 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. Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted March 4, 2016 Report post Posted March 4, 2016 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. Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted March 4, 2016 Report post Posted March 4, 2016 Strange, I think I tried that initially when I ran into this issue but can't remember if it fixed it for us or not. We still use Gen1 for all our Hyper-V testing VMs and it seems to be working fine... Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted March 4, 2016 Report post Posted March 4, 2016 Ha, gotta love that I mean, it is a fairly small inconvenience all things considered, but it makes me wonder what the real culprit is. Quote Share this post Link to post Share on other sites More sharing options...
