This is critical to me! My company is piloting connectwise control to replace LogMeIn. Our application is database driven and runs as a service account and stores its data in a Microsoft LocalDB Database. In order to apply patches, updates, query the data, etc, you have to run as the service account. for example "runas /user:username cmd.exe sqlcmd -S (localdb)\mssqllocaldb enter query here" While this can be done by connecting in to the host session in ConnectWise Control, in LogMeIn I can actually login to the machine as the service account and access a full powershell and command prompt. This would be a major loss of functionality and ability to efficiently support our clients without interrupting their work. I would imagine the same is true for many users.
This is critical to me! My company is piloting connectwise control to replace LogMeIn. Our application is database driven and runs as a service account and stores its data in a Microsoft LocalDB Database. In order to apply patches, updates, query the data, etc, you have to run as the service account. for example "runas /user:username cmd.exe sqlcmd -S (localdb)\mssqllocaldb enter query here" While this can be done by connecting in to the host session in ConnectWise Control, in LogMeIn I can actually login to the machine as the service account and access a full powershell and command prompt. This would be a major loss of functionality and ability to efficiently support our clients without interrupting their work. I would imagine the same is true for many users.