Net localgroup administrators /remove userĬ:\mstsc\shutdown.exe -r -t 5 -f -c "Now rebooting" Add the RDP file "DisableChangePassword"="1" Create a file named “UserRunOnce.cmd” regedit.exe /s C:\mstsc\mstsc-2.reg "Shell"="wscript C:\\mstsc\\launchmstsc.vbs"
Windows 7 Thin Pc X64 Download windows#
"UserRunOnce"="C:\\mstsc\\UserRunOnce.cmd" Create a file named “mstsc-2.reg” Windows Registry Editor Version 5.00 Set WshShell = Nothing Create a file named “mstsc-1.reg” Windows Registry Editor Version 5.00 WshShell.Run chr(34) & "C:\mstsc\launchmstsc.cmd" & Chr(34), 0 Goto RDS create a file named “LaunchMSTSC.vbs” Set WshShell = CreateObject("WScript.Shell") Log in as local Administrator by holding the Shift key when logging Reboot the system to modify the user account shell.Ĭ:\mstsc\shutdown.exe -r -t 5 Create the file name “Launchmstsc.cmd” off Regedit /s This allows the user account to auto login. Net localgroup administrators /add Add the following registry key changes: Net user user user /ADD /PASSWORDCHG:NO /FULLNAME:"RDS User"
Windows 7 Thin Pc X64 Download password#
You will need to create a number of files in a folder stored on the root directory C:\MSTSC\ Name the first file “Installmstsc.cmd”Īdd the following content Add a user called "user" with the password "user" Creating a Windows Thin PC Client – MSTSC Client Redirection would be great for organisations that have one template but for organisations that wish to use multiple VDI pools, i would recommend using RDP files. You can use redirection using a Connection Broker but there are limitations: you can only redirect to one VDI pool if you have a Highly Available Connection Broker configuration. My RDS environment has multiple VDI pools so i needed to use a RDP file to load VDI sessions.
My self and a colleague Chris Shaw came up with a solution that loads a RDP file from the root directory (C:\>). I have spent some time researching windows Thin PC Thin Clients.
0 kommentar(er)
