Reason This happens because you haven’t yet logged on locally on the server and you are launching a gpresult command in a PSSession. Solution Just logon once interactively in a RDP session on the target computer and you will be able to launch the gpresult command in a PSSession without this error.
You probably know the very good and very popular module of Michal GADJA named PSWindowsUpdate. At the time of this writing, the latest version is 2.0.0.0 and can be downloaded from the Powershell Gallery here. I just wanted to add an undocumented behavior of the Get-WUInstall cmdlet. If your computer is not configured to install […]
Disclaimer This is for advanced users only. If Microsoft has hidden this registry key and removed permissions for administrators, it’s probably for a good reason. Thus, the following script is provided as is. Don’t use it or modify it if you don’t understand what you are doing, or if you are not aware of the […]
No need to bother with the syntax of SetSPN anymore (despite it still works). There is now a native function built into the Get-ADComputer and Set-ADComputer cmdlets. View all SPN for a given computer Use the Get-ADComputer cmdlet and specify the ServicePrincipalNames parameter. It returns an array of values you can easily expand with the […]
On recent versions of Windows, neither the telnet client nor the telnet service is installed by default, but they are still available as features. Years ago, they were used as a terminal service system to manage remote hosts. Currently, a lot of people are still using the telnet client to test if a TCP port […]
itluke.online 
You must be logged in to post a comment.