Rename Windows Hostname based FileWave Client Name
Description
This Fileset renames a Windows computer so its Windows hostname matches the FileWave Client Name shown in FileWave Admin.
With this Fileset associated, the FileWave Client Name becomes the source of truth. If the Windows hostname is changed directly in Windows, Active Directory, or another tool, the Fileset changes it back to the FileWave Client Name the next time the rename workflow runs.
Use a FileWave Client Name that follows the Windows computer naming conventions. Avoid spaces, underscores, apostrophes, and names longer than the NetBIOS limit. There is no name-checking logic in these scripts.
Good name examples:
- FILEWAVE-PC
- TCE-3453234
- PRINT-SRV
Bad name examples:
- Jerry's Desktop Computer
- GO_BEARS!
- THISNAMEISMUCHLONGERTHAN15CHARACTERS
Ingredients
- FileWave Client for Windows
- Windows - Rename Windows Hostname (No Domain) PowerShell.fileset.zip
- Windows - Rename Windows Hostname (Domain Joined) PowerShell.fileset.zip
Older batch-file versions are still attached for reference, but the PowerShell Filesets are the current examples to start from:
- Windows - Rename Windows Hostname (No Domain).fileset.zip
- Windows - Rename Windows Hostname (Domain Joined).fileset.zip
Machines not joined to Active Directory
- Download, unzip, and import the Windows - Rename Windows Hostname (No Domain) PowerShell Fileset into FileWave Admin.
- Associate the Fileset with the Windows devices that should follow their FileWave Client Name.
- Rename the device in FileWave Admin.
- Update Model.
- Wait for the client to check in and run the Fileset. The included workflow is designed around the normal FileWave preflight/tickle timing.
- The user receives a reboot prompt, and the device reboots after the configured timeout.
- The Windows hostname is changed to the FileWave Client Name after reboot.
- FileWave Client communication is not affected by the rename.
Machines joined to Active Directory
- Download, unzip, and import the Windows - Rename Windows Hostname (Domain Joined) PowerShell Fileset into FileWave Admin.
- Review the included scripts before deployment and update the domain account placeholders for your environment.
- Test with a small group first. Domain-joined renames depend on Active Directory permissions, DNS/domain health, and the reboot completing successfully.
- Associate the Fileset with the Windows devices that should follow their FileWave Client Name.
- Rename the device in FileWave Admin.
- Update Model.
- Wait for the client to check in and run the Fileset.
- The user receives a reboot prompt, and the device reboots after the configured timeout.
- The Windows hostname is changed to the FileWave Client Name after reboot.
- FileWave Client communication is not affected by the rename.
Sync Computer Name
When a client is manually renamed in FileWave Admin, FileWave disables Sync Computer Name for that client. That allows the Fileset to apply the FileWave Client Name to Windows instead of having Windows immediately sync its old computer name back into FileWave.