Recently I needed to do this for our PRTG alerting account which was failing to send notifications as the O365 password had expired. I did this from Powershell within Windows 10 as follows: Launch powershell…
First connect to the remote server with powershell
|
1 |
[cc lang="powershell"]Enter-PSSession -ComputerName contoso\hv01[/cc] |
Next run the command to add the group:
|
1 |
[cc lang="powershell"]Add-LocalGroupMember -Group "Administrators" -Member "CONTOSO\Hyper-V Admins"[/cc] |
If you’re paranoid (like me) and want to check this worked you can use:
|
1 |
[cc lang="powershell"]Get-LocalGroupMember "Administrators"[/cc] |
If you’ve tried to add a powershell script to a registry run key, you’ve probably discovered that it doesn’t run with powershell. Instead, Windows just opens the script in Notepad and leaves it sitting there…
I required a script that would run automatically for a user from a RunOnce key. This powershell script gives the user a message box asking if they would like to restart now or later. If…
Here’s a little script I created that was useful to check the amount of physical RAM installed on a Hyper-V server running core. It reports the amount of physical RAM in the host as well…
To calculate the cost of licensing for Server 2016, it’s necessary to know how many cores each CPU of your server is running. This WMI query is useful in identifying that.
|
1 2 |
[cc lang="powershell"]$property = "systemname", "deviceid", "name", "maxclockspeed","addressWidth", "numberOfCores", "NumberOfLogicalProcessors" Get-WmiObject -class win32_processor -Property $property | Select-Object -Property $property[/cc] |