amedexitt
asked on
Best solution for preventing users from connecting to Terminal Server?
We have an application that will need to be updated nightly, and everyone uses this application (10-15 users per Terminal Server) What is the best method for kicking out users from the application and preventing them from connecting to the system while the update is performed?
Is there an application that exists that could automate the process of kicking users out to take the new install (which is an MSI file)
I remember in Solaris you would copy a file to a certain directory would prevent anyone from telnetting in until that file was removed.
Is there an application that exists that could automate the process of kicking users out to take the new install (which is an MSI file)
I remember in Solaris you would copy a file to a certain directory would prevent anyone from telnetting in until that file was removed.
ASKER
That won't work as its not every night that a release will occur, and we are talking about 8-9 Terminal Servers and 15-20 users a piece.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might want to add in to this batch file
net stop "terminal services"
This will prevent users from logging back on to the server. and then another batch file that does
net start "terminal servives" after the back has completed.
net stop "terminal services"
This will prevent users from logging back on to the server. and then another batch file that does
net start "terminal servives" after the back has completed.
sorry typo I ment:
net start "terminal services"
net start "terminal services"
ASKER
But if you stop the Terminal Services service it would kick me out too! These changes will have to be done manually until we get an idea of timeframes with upgrades at which point I think we can implement it automatically.
ASKER
Does anyone else have any suggestions? We have 8-9 Terminal Servers and over the weekend I tried to update some and it was quite the nightmare.
1. Deny their logon hours in their user profile in Active Direcotry Users and Computers.
2. If you have a good amount of users, it would be easier to create a GPO.