Skip to main content

name machine deployment after label?

Thread needs solution
Beginner
Posts: 6
Comments: 6

Hello,
Is there any way to have the machine deployment automatically use the machine 'label' if set? I label all of the machines I deploy to, and I name the machines the same way during the deployment. I can't use the "{number}" method as our machine names and numbers do not follow a stanardized sequence, we usually do something like "username-machine number" (ie "derek-123"). But I can't name them all "username-{number}" because they all get different usernames.

I tried to search this and couldn't find anything about it. If it's not possible how do I submit a feature enhancement request? It would basically go like this for the machine name - "{label}"

Thanks,
-Derek

0 Users found this helpful
Regular Poster
Posts: 0
Comments: 202

#1

Hello, Derek

There is no such functionality.
You can try to create separate deployment tasks and templates with necessary name patterns to name each machine like "username-machine number".
For example:
DeploymentTemplate 1 - firstmachine{1}
DeploymentTemplate 2 - secondmachine{1}
DeploymentTemplate 3 - thirdmachine{1}
etc.

Beginner
Posts: 1
Comments: 1

#2

This really should be a feature. Is there any way to request it to be added. I have about 70 machines designated to different rooms and each mac address is attached to a name. I image these machines twice a year and the most annoy aspect of the process is going around and renaming/adding them to the AD.

Beginner
Posts: 1
Comments: 1

#3

Upon setting up a label, I also go into the and set a Machine name in the individual machine settings. Not ideal, but a workflow that is working for me.

Beginner
Posts: 0
Comments: 1

#4

Hi there

I was seeking the same thing posted by derek. It's incredible that there is no option to apply the label as a name pattern or automatically use it to auto-insert in the individual machine settings... What a mind job...This is not suitable in education environments and i wont recomend your products anymore if you wont correct this functionallity

Alex Segura, IT Consultant in control group spain

Beginner
Posts: 1
Comments: 5

#5

I wrote an Auto-It script to join newly imaged computers to our domain and rename them using just 1 reboot.  I use the "Run Once" registry entry to run a batch file on our network to call the script.  It's pretty simple and straightforward.  My particular organization uses the computer type and the serial number in our machine names, so writing a script to automatically generate names was pretty simple.  First you join the computer to the domain using whatever random name Microsoft picks, then you rename the computer.  Then you do a reboot to make everything happy and that's it.

Here's my Join Domain function:

func _JoinDomain($icompname,$strDomain, $iUserName = "", $iPassword = "",$joinOU=Null) ; compname is the CURRENT computer name
    const $NETSETUP_JOIN_DOMAIN = 0x01
    const $NETSETUP_ACCT_CREATE = 0x02
    const $NETSETUP_DOMAIN_JOIN_IF_JOINED = 0x20
    const $NETSETUP_DEFER_SPN_SET = 0x100
    const $NETSETUP_NO_ACCT_REUSE = 0x20000

   local $objComputer = ObjGet("winmgmts:{impersonationLevel=Impersonate}!\\" & @computername & "\root\cimv2:Win32_ComputerSystem.Name='"& @computername &"'")
    $oreturn = $objComputer.JoinDomainOrWorkGroup($strDomain,$strPassword,$username,$joinOU,$NETSETUP_JOIN_DOMAIN+$NETSETUP_ACCT_CREATE)
    if $oreturn > 0 Then
        Switch $oreturn
            Case 5
                $errmsg = "Access Denied"
            Case 1323
                $errmsg = "Unable to update the password."
            case 1326
                $errmsg = "Logon failure: unknown username or bad password"
            case 1355
                $errmsg = "The specified domain either does not exist or could not be contacted"
            case 2224
                $errmsg = "The account already exists: " & @computername
            case 2691
                $errmsg = "The machine is already joined to the domain."
            case Else
                $errmsg = "Unrecognized error: " & $oreturn
        EndSwitch
        MsgBox($MB_SYSTEMMODAL, "Error", $errmsg)
        SetError($oreturn)
        Return $oReturn
    Else
        Return 1
    EndIf
EndFunc

and a Rename Computer function by Kenneth Morrissey:

Func _RenameComputer($iCompName, $iUserName = "", $iPassword = "",$joinOU=Null) ; compname is the NEW computer name
    $Check = StringSplit($iCompName, "`~!@#$%^&*()=+_[]{}\|;:.'"",<>/? ")
    If $Check[0] > 1 Then
        SetError(2)
        Return 0
    EndIf
    If Not IsAdmin() Then
        SetError(3)
        Return 0
    EndIf

    $objWMIService = ObjGet("winmgmts:\root\cimv2")
    If @error Then
        SetError(4)
        Return 0
    EndIf
    For $objComputer In $objWMIService.InstancesOf("Win32_ComputerSystem")
        $oReturn = $objComputer.rename($iCompName,$iPassword,$iUserName)
        If $oReturn <> 0 Then
            SetError(1)
            Return $oReturn
        Else
            Return 1
        EndIf
    Next
EndFunc

 
Beginner
Posts: 0
Comments: 1

#6

I too share alex segura's comments about this being function.....it should be a basic function of the template whereby the machine name can be set the same as the label.

Also, when chosing to joinn the domain, user creditials have to be entered and then yet again when adding the machines to a deployment task - why so much repeativiness?

Please could ACRONIS look to streamline this process so it goes from bieng an OK tool, to a good tool and easy to use!

Cheers