Issues getting remote access to a customers network is simply just a "fact of life" you have to deal with.
Every customer will have it's own remote access policy.
I have multiple customer that give access via logme in and I have other customers that provide remote access via a VPN of some sort.
Frankly, if I were a network security tech, I would not allow remote access at all.
Allowing a third party access to my network would drive me nuts as I have no idea what type of security that they would have in place and who has access to it. And what happens to login creds when someone leaves the third party company?
And being one of those that were affected by last weeks major data breech I'm even more sure I wouldn't want anyone in my network.
But, we need to be able to service these systems remotely. If there was a problem with a system then to have to wait for a truck roll is a bad thing.
So compromises need to be made.
I like logme in if only because it can be controlled by the customer. Having them turn on/off the PC is a good way to know who's coming into the system so I have no problem with that.
I also like the security key fobs. With key fobs the password literally changes every 60 seconds.
Of course my favorite, from a service perspective, is still the Cisco VPN. It makes my life a lot easier for some of the heavier service work I do on some of these systems so I'm always grateful when I have this type of access.
But, bottom line is, remote access is going to be based on the security needs of whoever you're connecting to. If if cost you more to service them then your maintenance cost will need to reflect that.
Ralph