Posted August 5, 200816 yr Good morning! We have a WIN2003 R2 member server running Terminal Services about ready to go into production but my testing has unfortunately provided a little surprise: I can not run any scripts on this box. Specifically, I have a .vbs script for all of the users (logon.vbs) and it will not run. I can log on as me to the other TS and logon.vbs works (I get all of the mapped network drivers). However, when I log on as me to this one I get nada! We also have management software on all of the machines that we manage and my "Managed Services" colleague can not run any of his scripts. So, something is preventing this from happening on this "new box". I did not load the OS. In fact, I *believe* that my colleagues did not do a wipe and load (Dell PowerEdge 2950). They took it to the co-lo as-is. I do have a GPO that locks down this box (Loopback processing - replace mode) -BUT- that same GPO applies to the other TS as well (both boxes are in the same OU and the GPO is linked only to that specific OU). And, there is nothing in the GPO about allowing only approved software to run.... Any ideas? Thanks, Cary
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.