Useful when RDP won’t connect because NLA is an issue, or domain trust issues are present. If the remote OS is still accessible via PowerShell and your current user is also an administrator on the remote OS, try:
|
1 2 |
$ComputerName = "remotehostname" (Get-WmiObject -class Win32_TSGeneralSetting -Namespace root\cimv2\terminalservices -ComputerName $ComputerName -Filter "TerminalName='RDP-tcp'").SetUserAuthenticationRequired(0) |
Change the 0 to a 1 to re-enable.
Very useful one-liner. Run from CMD, rather than PS:
Schedule once:
|
1 |
schtasks /create /tn "reboot" /sc once /sd dd/MM/yyyy /st HH:mm /rl highest /ru username /tr "shutdown -r -t 0" /f |
Schedule daily:
|
1 |
schtasks /create /tn "reboot" /sc daily /sd dd/MM/yyyy /st HH:mm /rl highest /ru username /tr 'powershell C:\folder\script.ps1' /f |
To change which logon connections are required to use Duo after installation, use the Registry Editor (regedit.exe) with administrator privileges to create or update the following registry value in
HKEY_LOCAL_MACHINE\SOFTWARE\Duo Security\DuoCredProv:
|
Registry Value
|
Type
|
Description
|
|
RdpOnly
|
DWORD
|
Set to 1 to protect RDP logons only or 0 to protect both RDP and local console logons.
|
When modifying the RdpOnly registry value on a Windows 2003 or XP system a reboot may be required to make the change effective.