Wrong PC name after deployment


A while ago, I noticed that the PC name specified during the "Import Computer Name" part of SCCM didn’t stick  trough out the entire deployment process..

The strange thing was that this wasn’t the case for all my task sequences. What I then noticed was that the name (when it changed) always took the WINPE random name like  "MININT-XXXXXX", which led me to think that it properly had something to do with the MDT integrated TaskSequences, and what do you know, it did!

It then got me thinking, that the MDT scripts properly updated sysprep.inf with the variable "OSDcomputername" (MDT variable) and not "_SMSTSMachineName" (SCCM variable).

I then added a "Set Task Sequence Variable" entry in my TS, were I defined  "OSDcomputername" with the value of "%_SMSTSMachineName%" and that actually did the trick. The name continued to be the name defined in SCCM.


I’m pretty happy this worked, as i think the MDT integrating supply you with a lot of features that i wouldn’t want to be without.  

By |2008-08-11T16:06:56+00:00August 11th, 2008|Configuration Manager (SCCM)|4 Comments

About the Author:

Michael Petersen
Twitter: @OSDeployLinkedin: Michael PetersenMicrosoft Community Contributor


  1. Yory November 19, 2015 at 21:14 - Reply

    Hi Mike,

    I’m currently working with SCCM R2. I’m trying to setup a Computer name base of AD or Device Collection on SCCM. I have tried your solution here but at the end of the deployment the PC still with the generic MININT…name. I’ll appreciate if you can please help me with a solution for this matter.

    Thank you I advance,

    • Kumar February 1, 2016 at 20:40 - Reply

      Hi Yory,

      Did you manage to get this working? I am in the same boat. Cheers.

    • Krish September 14, 2016 at 17:05 - Reply


      Is there any update on this? I am facing with the same issue.

Leave A Comment