Rename-Computer-Tool

This script allows you to rename a computer and even a DC

1) Install & Launch the tool

git clone https://github.com/SentinelSamuel/Rename-Computer-Tool.git

Tips :

 - You can create a .lnk to the launch.ps1 to make it easier to launch

 - You can change the default application used on a double click of a .ps1 to allow users to launch a .ps1 just double-clicking on it

 - You can create a Task in the task scheduler that will be run with highest priviledges and will be launched every logon

 - You can add a key : 
    The keys:
        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run - Runs programs for all users.
        HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run - Runs programs for current user.

source : https://stackoverflow.com/questions/24250303/additional-ways-of-running-programs-at-logon

For the task scheduler part :

The full script that is used here is (to have logs visibility) :
Action : Start a Program
Program/Script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add Arguments (optional) : -ExecutionPolicy Bypass -File C:\Rename-Computer-Tool\Windows Server 2012\Rename-DC-Tool.ps1 -WindowStyle Hidden

The full script that is used here is (to NOT HAVE logs visibility) :
Action : Start a Program
Program/Script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add Arguments (optional) : -ExecutionPolicy Bypass -File C:\Rename-Computer-Tool\launch.ps1 -WindowStyle Hidden
(Do not forget to rename the script name in the launch.ps1 script if you rename a DC)

2) Screenshots of the UI

3) Some Tips

- The maximum caracters of a computer name is 15
- You cannot add sapces in the computer name
- There is a file created during the process, named C:\old_computername.txt that will contains the old computer name and that allows you to not launch the script at every restarts of the computer
- So if you delete C:\old_computername.txt, the script launch the pop-up again
- The script is in Always On Top mod (it means that no Windows can go on the top of it so you are sure that you see it when it pops up)
- For Rename-DC-Tool : 
  - It uses a totally diffrent process, it uses DC-Modules.psm1 which is a PowerShell function file that will contain every functions used in the script
  - It rename (if possible) every present SPNs in the DC with the new name
  - It rename every DNS entries that were containing the old computer name pointing on the DC (TO BE DONE, IS NOT DONE ANYMORE BECAUSE THERE IS TOO MUCH ERRORS)
    (Rename every DNS Entries before changing the DC Name is not really pertinent because most of them will update themself)
  - It remove every certificates that contains the old computer name in the subject
  - It reset WinRM configuration (even if there is still a WinRM over HTTPS configured)
  - It configure WinRM over HTTPS (creating a certificate that is placed in the script directory with its password file)
  - It disable WinRM over HTTP (It try 3 times before saying that it didn't work)
  - It disable LDAP
  - It enable LDAPS (creating a certificate that is placed in the script directory with its password file)
  - It creates Firewall Rules for WinRM over HTTPS & LDAPS
  - It removes Firewall Rules for the disabling of LDAP
  - After hitting the OK button, everything is logged in the script directory "Rename-DC.log"

4) On error

Please report me errors if you have one. If you have an error about the powershell version about Get-ADDomain and that you are on a Windows Server 2012 R2, please download & install : https://aka.ms/WMF5Download Btw : The Windows Server 2012 R2 is not exporting the WinRM HTTPS & LDAPS self signed certificate (but is creating it of course)