asked on RDP - Need Change to change response when a 2nd user tries to login to windows 7
We have a Win 7 Pro workstation that has software that several people within our network need to use from time to time. We use RDP to access this workstation. The problem is that when a second user logs into this machine, the person already logged in is kicked out. Once in a while the second person gets a message about someone already logged in, but not always. This has caused data corruption if the person is in the wrong part of the program.
What we need is to change the response from the host machine when the second person tries to log in. It (ideally) needs to inform them that someone else is in, but must prevent the 2nd person from logging in until the first person disconnects / logs out.
Any ideas how I can do this?
Thanks!
Deon
What we need is to change the response from the host machine when the second person tries to log in. It (ideally) needs to inform them that someone else is in, but must prevent the 2nd person from logging in until the first person disconnects / logs out.
Any ideas how I can do this?
Thanks!
Deon
Microsoft Legacy OSMicrosoft Applications
Last Comment
dosdet2
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Actually, he doesn't get an option to accept, or even know what happened. His RDP session just closes. Each person logs in to this workstation as the same user or the program being accessed does not work, We tried to login as a different user and it still knocks off the user, but that wouldn't help us anyway.
I am testing some VNCs to see if they have the options I'm looking for. It would help if someone knew of one that does. We are NOT assessing via the web, it is local within our network.
I am testing some VNCs to see if they have the options I'm looking for. It would help if someone knew of one that does. We are NOT assessing via the web, it is local within our network.
If you take different users, as I said before, it disconnects, it never kicks. Take different users.
I have a great deal of experience doing this, you can believe me that it does not "knock them off", that was with xp, stopped with vista (and stayed the same with win7).
I have a great deal of experience doing this, you can believe me that it does not "knock them off", that was with xp, stopped with vista (and stayed the same with win7).
ASKER
The software being accessed only works with the user name it was licensed for. We are only using an Remote Desktop type connection so that users do not have to leave their desks and go to the physical computer to access this software, which software is this machine's only purpose. Logging in with different user names defeats it's purpose.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
That sounds promising. I'm not familiar with RSAT or the terminal services plug-ins. Let me check into that and test it. I'll post the results after that. Thanks!
Please respond or finalize it, this question is growing old :)
ASKER
Nothing mentioned has worked the way we had envisioned. We have limited the people who have access to the workstation's IP and they are asking via email if anybody is on. I don't know if there is a really good answer at this time but this manual solution is working for now. Thanks!
But he will never get logged off unless the "new" user decides to reboot the computer - this is of course possible.
So to mitigate it, I only see the possibility to change the shutdown-privilege assignment to administrators only.