Bring back ConnectWise Control
Yeah, it’s absolutely not worth that. It’s a nice to have, not a must have.
Bring back ConnectWise Control
We just signed up for ConnectWise control, so I'm interested in seeing what this integration brings.
Added VPN connection to RDP session settings, now RDP session attempts logon with wrong account
I found my problem... turns out when I added the VPN connection settings, I also checked the box for Remote Credential Guard in the advanced tab of the RDP session properties. Reverting that returned the expected behavior.
Added VPN connection to RDP session settings, now RDP session attempts logon with wrong account
I recently modified an existing RDP Session entry in Remote Desktop Manager, setting it to connect a Microsoft VPN connection if unable to ping the server. Since adding the VPN connection info, this RDP Session is not using the specified credentials for the RDP connection. Instead, it seems to attempt logon using my windows user account, which doesn't have rights to RDP to the target computer. That logon fails, showing me the target computer's lock screen with an error message on it. If I click through the message, I can manually enter the correct username and password at that logon screen to successfully access the target machine.
The windows user account is also the account used to authenticate to the VPN connection, so I don't know whether the account info is coming from the VPN connection or the windows session that RDM is running in. Because the VPN connection uses certificate based auth, the VPN settings in that RDP session are very simple, as shown below.
Why is the the RDP session not using the credentials specified for the RDP Connection?
Login Using LAPS Credentials
Assuming you have rights to the attribute, you can get it with:
get-adcomputer COMPUTERNAME -server DOMAINCONTROLLER -properties ms-MCS-AdmPwd
Login Using LAPS Credentials
This custom credential only works when used from a domain joined computer. I believe this may actually be a limitation in the LAPS powershell module 'admpwd.ps' which this custom credential uses. As we've started moving some computers to native AzureAD joined, this is a problem for our IT staff that still need to be able to manage hybrid joined computers. Could this custom credential be updated to support use from a computer that is not domain joined?