vurpos.blogg.se

To understand how the script works, please read Sitaram's article. Write-Host "$computer : Failed to enabled RDP" "$Computer : Failed to enable RDP" | Out-File -FilePath $FailedComps -Append Write-Host "$Computer : Failed to enabled RDP" "$Computer : RDP Enabled Successfully" | Out-File -FilePath $SuccessComps -Append Write-Host "$Computer : Enabled RDP Successfully" $result = $RDP.SetAllowTsConnections(1,1) "$Computer : RDP Already Enabled" | Out-File -FilePath $SuccessComps -Append Write-Host "$Computer : RDP Already Enabled" "$Computer : WMIQueryFailed" | Out-File -FilePath $FailedComps -Append $RDP = Get-WmiObject -Class Win32_TerminalServiceSetting ` $FailedComps = Join-Path $OutFolder "FailedComps.txt" $SuccessComps = Join-Path $OutFolder "Successcomps.txt" I removed the part of the script that first checks via Test-Connection if the computer is online because this would require an additional firewall setting to make the script work. This allows you to manage computers remotely without PowerShell remoting. Sitaram wrote a PowerShell script that uses the Get-WmiObject cmdlet.

This can be useful if you need to enable RDP on multiple machines or if this task is part of a larger automation problem and your organization's security guidelines don't allow PowerShell remoting. If PowerShell remoting is not enabled on the remote machine, you can still use PowerShell via WMI for the task. We are using PowerShell remoting again to execute Enable-NetFirewallRule remotely. If so, you can simply enable Remote Desktop by modifying a registry key on the remote machine: Invoke-Command -Computername -ScriptBlock Let's assume first that PowerShell remoting is enabled on the remote machine. Which method you use mostly depends on your Windows Firewall configuration. I know of two methods to enable Remote Desktop remotely via PowerShell. Windows Firewall might get in your way, and if PowerShell remoting is not enabled on the machine, things can get a bit tricky. By contrast, on a PowerShell console, you can essentially get the job done with a single command. The only problem is that Group Policy is sluggish, and if you want to log in quickly to a remote machine, it is often not an option. Allow inbound Remote Desktop connections via Group Policy