That alone is at least an entire day of work, so can you think of anything else I should know or look into before banging my head against that wall? It looks like I would have to manually recreate every single connection profile and all of it's settings. Will read up, and see about switching over, but assuming I can get it rewired for VNC, are all of these issues then resolved, or some remain?ĮDIT: Apparently, switching to VNC is possilbe, but a major undertaking as there appears to be no mechanism to convert the existing connection profiles. It's a plugin based system, so I'm currently using the RDP plugin, but I believe I could switch over and use VNC (which is also supported by provider). I'm using Royal TSX as my connection client. It never occurred to me that my scripts would stop working just because I disconnected the client. So this may even be a much bigger issue than I thought. However, you may be at the mercy of your provider if you are using a cloud service and may need them to do something their end at the physical server to make this possible. What people usually do to get around this is simply ditch Remote Desktop and use a different product such as VMWare/VSphere instead, or some version of VNC. I can't vouch for whether this still works or not - I wouldn't be surprised if Microsoft "plugged" this a long time ago. There was a way to make RDP *not* disconnect when you close it, but leave it sat at the desktop:
ROYAL TSX SORT CONNECTIONS WINDOWS
Macro Scheduler requires a user console to automate a UI and a UI does not exist until a session is connected - until Windows is logged in. Only once you've connected via RDP will it log in.
ROYAL TSX SORT CONNECTIONS PASSWORD
Just as if you power on your local server it will sit waiting at the log on prompt - until you type the password it will do nothing - equally with a remote server you need to connect to RDP to log in but then the issue is it will log out when you close the RDP client. Just starting your server does NOT log it in. Even when you simply minimize RDP the remote session is locked.
Microsoft, (in their infinite wisdom ) made RDP so that when you close it the session is logged out. I'm afraid this is all down to how RDP works, and how it is designed to work. I have been reading up about task scheduler and the "Run whether user is logged in or not" option, but this raises new questions:ġ) Am I on the wrong track here? Is there no way to do this without using the Task Manager?Ģ) Some reading has revealed issues that pop up if the item being run via Task Scheduler with "Run whether user is logged in or not" checked is interactive in any way (like can pop up dialogs) It would seem that a MS script would fall under this category, no? I came across the following statement in a discussion about unattended excel automation: Troubleshooting: I have tried running shell:Common Startup to make startup item universal.
Even if I could somehow get the RDP client to constantly try to reconnect, I have too many vps to connect to all simultaneously, so solution needs to be on the Windows server side allowing the script to run regardless of login. RDP client will disconnect automatically every time connection is lost (like during a reboot), so there is a built in issue where despite rebooting, machine will not run script until I manually intervene. Problem: I have compiled exe shortcut in Startup folder, but vps sits there and does nothing after reboot until I connect via RDP client (Administrator login happens automatically upon connection). Goal: Have compiled script launch, and include> additional scripts upon startup regardless of user login.
0 kommentar(er)
