KACE Product Support

paul.theelen | 53 mins ago |                           

I forgot to mention that they are AD accounts so no need to transfer the password.

If they are AD accounts create post tasks or 1000 script and all you need is

net localgroup administrators /add domain\user

I think your biggest challenge will be replicating the password for the account over. I'm not sure that can be done.

Wow, this looks like over kill to me.

Why not simply perform an sql query on the machine object and save it to a text file on c during the deployment process? The knit tools have sql available in them now for when you create boot media. Then read it back as a post task and use net user to set that user as a member of administrators?

We use an sql query here to set the 'assigned user' of an asset as the local administrator here.

For any users you want to create you can use post 2000 script or 1000 scripts for each user name you want to push to a certain machine or read the registry like they do for getcomputer.vbs script and apply the name with a modified apply computername.vbs

To do this as a script use the "net user" and "net localgroup" command to create the name, set password and make it an admin

http://support.microsoft.com/kb/251394

http://technet.microsoft.com/en-us/library/bb490706

To read the user from the registry you would want to load the software hive and read([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\lastloggedonuser].  store that key and then as post task read the stored key and either use a vb script, powershell or netuse to apply that as a variable for the user in the script.  set a default pw and force them to change it on first login.

The Get computer.vbs that comes with the K2000 looks like this.

Set fso = CreateObject("Scripting.FileSystemObject")
Set diskDrives = fso.Drives

regFound = False
'Search through fixed drives (Drivetype = 2) for required registry file.
For Each drive In diskDrives
    If (drive.DriveType = 2) and fso.FileExists(drive.DriveLetter & ":\WINDOWS\System32\Config\SYSTEM") Then
        systemDrive = drive.DriveLetter
        regFound = True
        exit for
    End If
NEXT

'Registry not found
If regFound = False Then
    WScript.Quit
End If

'Get the computer name from the registry
Set wshShell = CreateObject("WScript.Shell")
Set execStatus = wshShell.Exec("reg load HKLM\TEMP_SYSTEM " & systemDrive & ":\WINDOWS\System32\Config\SYSTEM")
'Wait for registry to load completely (max 10 seconds)
count = 0
Do While (count < 10) and execStatus.Status = 0
    WScript.Sleep 1000
    count = count + 1
Loop
If execStatus.Status = 0 Then
    WScript.Quit
End If
regKeyCompName = "HKLM\TEMP_SYSTEM\ControlSet001\Control\ComputerName\ComputerName\ComputerName"
compName = wshShell.RegRead(regKeyCompName)
WshShell.Exec("reg unload HKLM\TEMP_SYSTEM")
WScript.Sleep 1000

'Dump the computer name into a file named as the mac address inside T:
If fso.DriveExists("T:") then
 'Get mac adress
 Set objSysEnv = wshShell.Environment("PROCESS")
 macAddress = objSysEnv("MAC_ADDRESS")
    Set compNameFile = fso.CreateTextFile("T:\" & macAddress, True)
Else
 usbDrive = fso.GetDriveName(wscript.ScriptFullName)
    Set compNameFile = fso.CreateTextFile(usbDrive & "\KACE\ComputerName", True)
End If
compNameFile.WriteLine(compName)
compNameFile.Close

You could rework this to read the software hive and user keyset instead of system/machine name

One of the other Script wizards may be to look at this concept and give you the script you would need to do this