locked
Computername reverting to MININT-XXXXXX instead of name in database. RRS feed

  • Question

  • I am adding an existing client device resource to a collection for OSD and booting from USB key to initiate a deployment.  In ConfigMgr 2007 the computername would be that of the device resource in the database, albeit another record would be created.  In ConfigMgr 2012 my rebuilt computer from USB is finishing with a MININT-xxxxxx name and this overwrites the existing name on the record.

    Only if I wipe the resource from the database prior to rebuild, re-import the computer information again and set the build going do I get the computername I want (as per the device resource already in the database.)  The device being built is obviously picking up the advertisement based on the existing device resource collection membershup and MAC address, but is not inheriting the existing name.

    If I perform an OS refresh from within the running OS the existing device resource and name is utilised, which is to be expected - otherwise we'd all be in a lot of trouble.

    Friday, May 11, 2012 1:19 PM

Answers

  • Are you using dynamic media?  This issue only seems to occur when using dynamic media.  Please try site-based media and see if it works as expected.  We're investigating this issue for a potential fix, but it would be great if you can confirm that this only happens with dynamic media.
    Monday, May 21, 2012 2:22 PM

All replies

  • Correction: This also happens even when I create a fresh device resource by importing the computer information.  The OSDComputername is not being set to the name I assigned to the imported device resource, but instead is being assigned a MININT-xxxxxx name.  Hmm, problem here.
    Friday, May 11, 2012 1:53 PM
  • there are a few ways to do it, and i'll show you two here

    for New computers, you can import them via a file

    http://www.windows-noob.com/forums/index.php?/topic/4505-how-can-i-import-computers-into-sccm-2012-using-a-file/

    or use the OSDComputerName collection variable as outlined here

    http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/

    it sounds to me like you have old remnants of computers information in your database and it's this which is causing your issues, either way, try the methods above and see does it help

    cheers

    niall



    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    Saturday, May 12, 2012 10:40 AM
  • Normally the name in database must be used during OSD for computername.

    Just have a look at my blogs also for more information:

    Before OS deployment: http://henkhoogendoorn.blogspot.com/2011/10/how-to-assign-computername-before-os.html

    During OS deployment: http://henkhoogendoorn.blogspot.com/2011/03/how-to-assign-dynamic-computername.html

    Or you can import the devices with ConfigMgr manually or by CSV file also.


    My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

    Monday, May 14, 2012 7:17 PM
  • I am seeing the same behaviour! I use the Import Computer Information to create an object in the CM12 database for the new machine, providing its MAC address and computer name.

    In CM07, the machine will build with the computer name assigned to the object, however in CM12 I am not seeing this same behaviour.

    Thursday, May 17, 2012 4:40 AM
  • using a direct membership query, search for the mac address of the computer in question, do you see one or more records showing up ?


    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    Thursday, May 17, 2012 8:44 AM
  • Hi Niall

    The existing object gets updated with the MININT name once the ConfigMgr client has performed its heartbeat. I performed a build via PXE (rather than using boot media) and it correctly set the computer name to the same name as pre-staged object in the ConfigMgr database, so it looks like a potential bug!

    Monday, May 21, 2012 5:47 AM
  • Are you building a WORKGROUP joined system or joined to the domain?  If it is the former, try adding the SMSMP=server.yourname.com switch to the Setup Windows and ConfigMgr step in your TS.
    Monday, May 21, 2012 10:19 AM
  • Machine joins the domain fine as its MININT computer name if built using boot media. The MSI property SMSMP is only used to specify name of the management point that the ConfigMgr client will be assigned to, so it won't affect the computer name of the machine being built.
    Monday, May 21, 2012 11:08 AM
  • Machine joins the domain fine as its MININT computer name if built using boot media. The MSI property SMSMP is only used to specify name of the management point that the ConfigMgr client will be assigned to, so it won't affect the computer name of the machine being built.

    When I was having this issue I examined the SMSTS.LOG and I would see that if I attempt to build a freshly imported system, I would see an entry for "Netbios name" corresponding to the correct machine name I wanted, but then moments later I would see a "Failed to retrieve machine name from database..." entry and from there on the system would remain named MININT-XXXXXX.

    Just for an experiment, what happens if you delete any resource you can find for that MAC Address/Name and import the machine record again but use a completely different name?  I notice that direct membership collection rules are a little bit clunky in 2012 (if you delete a resource from the DB then the direct membership rule is still there in the collection!) so maybe there's a name/membership quirk here somewhere - in particular when working with USB media (like I was too.)  Couldn't try PXE as the customer environment doesn't support this, yet.


    • Edited by MadLuka Monday, May 21, 2012 12:36 PM
    Monday, May 21, 2012 12:34 PM
  • Are you using dynamic media?  This issue only seems to occur when using dynamic media.  Please try site-based media and see if it works as expected.  We're investigating this issue for a potential fix, but it would be great if you can confirm that this only happens with dynamic media.
    Monday, May 21, 2012 2:22 PM
  • Hi Jim

    I was using dynamic media and I have just performed a build using site-based media and the computer name was set correctly. So I can confirm that issue is limited to dynamic media.

    Cheers

    Sam


    Monday, May 21, 2012 10:55 PM
  • Thanks for confirming, Sam.
    Monday, May 21, 2012 11:15 PM
  • I hope someone is still monitoring this thread.  Please see my post at http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/fa6a65e5-197e-4beb-a14b-43a9c0ef67d4

    To the best of my recollection, my MAC and MININT issues occur only with boot media.  PXE booted machines acquire the correct computername.  However, the behavior in my case is not consistent.  Boot media does work some of the time.  I am using site-based media.  In the environment in specific to the post above, there is only one MP and one DP up and running at this time.  Is this a bug?

    Thanks,

    Tom

    Monday, July 16, 2012 6:58 AM
  • Status Update - after a day of testing I have narrowed the problem down to "dynamic" boot media.  The BIOS GUID and MAC work reliably only when the Task Sequence media specifies the site and Management Point.

    Hope this saves someone some time,

    Tom

    Monday, July 16, 2012 8:24 PM
  • can confirm this bug as well with a dynamic media. hopefully it will be fixed in SP1. Anyone tried with the current CTP yet?

    Thursday, August 23, 2012 3:06 PM
  • I "solved" this problem by setting a custom variable on the client in SCCM "TSHostName". In the OSD TS for the prestaged media client I just run a VB Script (cscript RenameComputer.vbs) to rename the client before the domain join.

    dim env
    SET env = CreateObject("Microsoft.SMS.TSEnvironment")
    env("OSDComputerName") = "%TSHostName%"

    The script only affects the OSDComputerName variable which is the needed variable for the naming of the client. the _SMSTSMachineName variable could also be renamed by adding it in this script, but that just affects the logging name of the client and was not important in my case.
    Thursday, November 22, 2012 9:51 AM
  • forget my last post...you dont need a script
    It will be enough if you set the Hostname in the OSDComputerName Variable on the client in SCCM then it will name the client correctly
    Friday, November 23, 2012 11:25 AM
  • the issue has been fixed with the newly released Update CU2

    http://support.microsoft.com/kb/2780664?wa=wsignin1.0

    Wednesday, November 28, 2012 11:18 AM