Skip to main content

Renaming Remote Clients

So I am finally getting around to posting some of the code from this weeks PowerShell class.  As always, I’m listening to my class and I am not afraid to deviate from the lessons when someone comes up with a good idea.  While teaching about PowerShell remoting, I was asked if it is possible to rename remote clients.  Sure it is!

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

$Cred = Get-Credential -Credential MCTExpert\AdminAccount

$OldName = "CL1"

$NewName = "Client1"

 

Invoke-Command -ComputerName $OldName -ScriptBlock {

    Param($C, $NN)

    $Name = HostName

    $Splat = @{

        "NewName" = $NN

        "Restart" = $True

        "Force" = $True

        "PassThru" = $True

        "DomainCredential" = $C

    }

        Rename-Computer @Splat

 

} -ArgumentList $Cred, $NewName

Line Details
1 Ask for the domain credentials of someone who has the rights to rename the computer object in Active Directory
2 and 3 The new and old computer name. 
5 Creates a remote session with the client using the old name.
6 This is used to pass information from your client, to the remote client.  The first variable $C maps to the $Cred being passing in line 17.  The variable $NN maps to $NewName, also being passed in line 17.
7 Gets the host machine name for the Rename-Computer cmdlet.
8 This is where we create a splat for all the parameters that we will feed Rename-Computer.  If you go through the help file for Rename-Computer, you will see what each one does.
15 This is where we apply the splat and actually rename the computer.
17 This is where we pass information from your client, to the remote one.  The information is passed to the Param block on line 6.

This is very basic.  In practice, I would consider a CSV file containing one column with the old computer name, and another with the new name.  I would then pipe this CSV into a more advanced version of this code so I can make things happen a little faster and less manually.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.