I am interested in this also..
To try and get some more life out of some older laptops we are looking at a Windows 7 Thin Client. Has anyone had any experience of this? Especially over wireless.
I am interested in this also..
I am interested in this also...
Shameless plug here (Im a Systems Manager before anyone hits Report Post :-p)... doing this at the moment with Windows Thin PC, which is Windows 7 cut down to use as a Thin client. Posts on my blog about setting it up with RDP.
I use XP as thin client as it's lighter on resources. Pretty easy to setup either way, this works for 7 as well. Set your windows thin client up with 1 admin user, no password, off domain so it automatically logs in or some other auto-login method if you prefer to secure it with a password. Make your rdp file and then make this small VBS script:
This script assumes your placing your rdp file default.rdp in C:\, edit as appropriate. Then you need to:Option Explicit
'On Error Resume Next
Set objShell = CreateObject("WScript.Shell")
If (objShell.AppActivate("Remote Desktop") = False) Then
objShell.Run "mstsc.exe c:\default.rdp"
Change shell string to:
wscript <your .VBS path>
Congratulations you have a windows thin client that relaunches on logout/timeout. Only drawback is without the shell you don't have a shutdown button so you have to tap the power button on your PC to shutdown. I use a remote shutdown script for these at the end of the school day which repeats every 2h after. CTRL + ALT + DELETE works if you need to do other stuff, it opens task manager so you can launch regedit again to set shell back to explorer.exe or just launch explorer.exe but this tends to open a My Computer window only.
Bezwick (11th July 2011)
The advantage of having them on domain is that they are GP'd and patched and managed as part of the main system. You can push all RDP Client settings in GP. The user in our case is a restricted network user. Plus... we use SCCM to build, manage and patch across the site. WTPC builds/deploys in the same way as 7. Ive since found that I could have changed the Shell in GP rather than the first build vbs which tattoos some parts of the registry.
How do you manage the autologin for your restricted network user?
I suggest you search for shelaunch.exe it's an executable that reads from an ini file, you can specify up to 5 buttons one of them being shutdown. create and rdp file with all your settings.
here is my shelaunch.ini file:
;See SheLaunch.sam for information regarding this file
param1=c:\[path to rdp file]\connect.rdp
I've attached the whole application, unzip it, copy to somewhere on the thin client HD, then change the shell reg key to the shelaunch exe. I recommend also changing the registry keys for noclose , etc so that users can't mess with things. the keys I set are:
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoBrowserClose"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoFileOpen"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoFindFiles"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoViewSource"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoBrowserSaveAs"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoBrowserContextMenu"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\Restrictions\NoOpenInNewWnd"
"HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\In ternet Explorer\IEDevTools\Disabled"
I wrote a VBS script to change these reg keys and copy the shelaunch to the local computer, that way i can run one vbs script and it's all done for me. I also wrote a script to undo all the changes, but I had to use remote registry to change the shell back to explorer.exe to log on locally to run it. all in all a very good solution.
Would you be kind enough to post your script?
There are currently 1 users browsing this thread. (0 members and 1 guests)