Task Force 'GummyBear'
Looking for a script or program that will accomplish this:
We are using RDP currently, our application (GummyBear) (based on NASA worldwind), does not render the 3D globe unless the RDP session is first started on the console.
We need to be able to run the tscon command as an administrator on a Windows2008R2 server. We would like a domain user to able to perform this action after they have connected to a session using RDP client. I believe that a service (DisconnectService), running as Administrator, could listen on a local port (or named pipe) for information that the client can send it. I imagine that the client would need to pass the service it's session name (%sessionname%) and perhaps its own login credentials (based on testing). Then, the windows service would execute this as Administrator:
tscon %sessionname% /DEST:Console /PASSWORD:%password%
This would effectively transfer the RDP session away from the client, which is needed.. The session would remain running and the user would be able to reconnect shortly after being disconnected. The client could use a local socket to connect to the service and ideally would pass the information in a secure manner. Nothing from outside the 2008R2 server should be able to interact with the DisconnectService. After this takes place, the client script/program would then launch the 3D application.
There may be third party applications that would accomplish this but I would like to stick with what is outlined above.
We are using RDP currently, our application (GummyBear) (based on NASA worldwind), does not render the 3D globe unless the RDP session is first started on the console.
We need to be able to run the tscon command as an administrator on a Windows2008R2 server. We would like a domain user to able to perform this action after they have connected to a session using RDP client. I believe that a service (DisconnectService), running as Administrator, could listen on a local port (or named pipe) for information that the client can send it. I imagine that the client would need to pass the service it's session name (%sessionname%) and perhaps its own login credentials (based on testing). Then, the windows service would execute this as Administrator:
tscon %sessionname% /DEST:Console /PASSWORD:%password%
This would effectively transfer the RDP session away from the client, which is needed.. The session would remain running and the user would be able to reconnect shortly after being disconnected. The client could use a local socket to connect to the service and ideally would pass the information in a secure manner. Nothing from outside the 2008R2 server should be able to interact with the DisconnectService. After this takes place, the client script/program would then launch the 3D application.
There may be third party applications that would accomplish this but I would like to stick with what is outlined above.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Qlemo
Why not configure auomatic logon on that machine? That would start a console session after reboot.