Renaming local user account

[stev379]

We rename the guest user account when building new servers. The line below works great except if the user account has already been renamed.

The entire script sets a number of OS options...

But it errors on this line if the Guest account has already been renamed or removed. How can error handling be set on this line? I haven't found a good way to enumerate the local accounts in AutoIT to run an if statement.

$oNewUser = $oComputer.MoveHere($oUser.ADsPath, $NewUser)

Snippet

#include <Array.au3>

$oWshNet = ObjCreate("WScript.Network")
$ComputerName = $oWshNet.ComputerName

$OldUser = "Guest"
$NewUser = "guestuser"


$oUser = ObjGet("WinNT://" & $ComputerName & "/" _
                & $OldUser & ",user")


    
$oComputer = ObjGet("WinNT://" & $ComputerName)
; rename user
$oNewUser = $oComputer.MoveHere($oUser.ADsPath, $NewUser)
_SetPW()
        
        
Func _SetPW()
    $NewPW = InputBox("Reset Password", "Enter password here", "", "*", "", 100)    
    Run(@ComSpec & " /C Net User " & $NewUser & " " & $NewPW, "", @SW_MINIMIZE)
    Run(@ComSpec & " /C net user " & $NewUser & " /active:no", "", @SW_MINIMIZE)
EndFunc;_RenameUsr()

[SpookMeister]

We handle this through a an Active Directory group policy setting.

[memnon]

We handle this through a an Active Directory group policy setting.

so we do with the local administrator, problem is only, the documents and settings folder name is not beeing renamed to the new name....

[PerryRaptor]

Interesting concept...renaming. We prefer to disable the account as soon as the OS build checks in with the server.

Possibly your concept is stronger security wise; but it takes an Admin to unlock a disabled account.

[jefhal]

I haven't found a good way to enumerate the local accounts in AutoIT to run an if statement.

Try this from Scriptomatic AutoIT:

expandcollapse popup

; Generated by AutoIt Scriptomatic

$wbemFlagReturnImmediately = 0x10
$wbemFlagForwardOnly = 0x20
$colItems = ""
$strComputer = "localhost"

$Output=""
$Output = $Output & "Computer: " & $strComputer  & @CRLF
$Output = $Output & "==========================================" & @CRLF
$objWMIService = ObjGet("winmgmts:\\" & $strComputer & "\root\CIMV2")
$colItems = $objWMIService.ExecQuery("SELECT * FROM Win32_UserAccount", "WQL", _
                                          $wbemFlagReturnImmediately + $wbemFlagForwardOnly)

If IsObj($colItems) then
   For $objItem In $colItems
      $Output = $Output & "AccountType: " & $objItem.AccountType & @CRLF
      $Output = $Output & "Caption: " & $objItem.Caption & @CRLF
      $Output = $Output & "Description: " & $objItem.Description & @CRLF
      $Output = $Output & "Disabled: " & $objItem.Disabled & @CRLF
      $Output = $Output & "Domain: " & $objItem.Domain & @CRLF
      $Output = $Output & "FullName: " & $objItem.FullName & @CRLF
      $Output = $Output & "InstallDate: " & WMIDateStringToDate($objItem.InstallDate) & @CRLF
      $Output = $Output & "LocalAccount: " & $objItem.LocalAccount & @CRLF
      $Output = $Output & "Lockout: " & $objItem.Lockout & @CRLF
      $Output = $Output & "Name: " & $objItem.Name & @CRLF
      $Output = $Output & "PasswordChangeable: " & $objItem.PasswordChangeable & @CRLF
      $Output = $Output & "PasswordExpires: " & $objItem.PasswordExpires & @CRLF
      $Output = $Output & "PasswordRequired: " & $objItem.PasswordRequired & @CRLF
      $Output = $Output & "SID: " & $objItem.SID & @CRLF
      $Output = $Output & "SIDType: " & $objItem.SIDType & @CRLF
      $Output = $Output & "Status: " & $objItem.Status & @CRLF
      if Msgbox(1,"WMI Output",$Output) = 2 then ExitLoop
      $Output=""
   Next
Else
   Msgbox(0,"WMI Output","No WMI Objects Found for class: " & "Win32_UserAccount" )
Endif


Func WMIDateStringToDate($dtmDate)

    Return (StringMid($dtmDate, 5, 2) & "/" & _
    StringMid($dtmDate, 7, 2) & "/" & StringLeft($dtmDate, 4) _
    & " " & StringMid($dtmDate, 9, 2) & ":" & StringMid($dtmDate, 11, 2) & ":" & StringMid($dtmDate,13, 2))
EndFunc

[Danny35d]

We prefer to disable the account as soon as the OS build checks in with the server.

We do the same thing at work, we disable the admin account and rename the guest account to Administrator and change the description so it look like the real administrator account but with guest rights...