The Gears Inside My Head

Have you ever needed to programmatically set the KMS keys on a bunch of systems?  This PowerShell script allows you to do that. Feed the script with the name of the KMS server, or you can hard-code it if you prefer.   The script detects the OS version and sets the appropriate GVLK (generic) KMS key.  It then sets the  location of the KMS server itself and attempts to activate the system.  Lastly it pops up the result.  Everything is done by leveraging the existing SLMGR VB script on every Windows system. Place the script on a common server and call it from the system to be activated.  That can be from a one-time run key, manually, or from a remote PowerShell session. I also included the full list of GVLK keys and Windows OS version numbers at the end for reference.  Remember that by themselves these keys will not activate systems, you need to use them in conjunction with a fully licensed KMS server. #================================...

I just ran into a case where I needed to remove the PC side client from BMC TrackIt! from an entire domain.  I created a little script to do it for me.  It happily ran through and removed it from every workstation.  It's quick and dirty but it does work. clear-host function Run-RemoteCMD {     param (     [Parameter(Mandatory = $true ,valuefrompipeline = $true )]     [ string ] $computer ,     [ string ] $command     )     begin {     #$computer         #$command = "ipconfig /registerdns" #Read-Host " Enter command to run"         [ string ] $cmd = "CMD.EXE /C " + $command                         }     process {    ...