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...