Thanks for the info. That indeed allows us to integrated VSA logon to AD. Too bad they didn't mention that in the help files.
kentschu... HOWEVER, access to Kaseya is now dependent on the AD system providing the authentication being up. Our Kaseya server happens to live on our domain controller (for better or worse), so integration with AD for our admin users probably is fine (because if AD is down, Kaseya is probably down too). But for our customers that are admins, if their Internet connection or AD server is down and they want to research the problem and troubleshoot remotely via Kaseya, they won't be able to get in. We'll need to create a separate local login account that they can use in emergencies and that becomes a pain to maintain...
1) Will you be adding a validation routine when a user changes his/her logon name to use domain cred? Right now, it doesn't validate and it seems like it could end up stranding a user with no way to log back in.
2) Is there a way to assign an existing VSA admin to a domain credential rather than asking them to change their logon name?
3) What are the risks involved with hosting a domain controller on the same machine as Kaseya? Just the usual precautions regarding external access to domain controllers and the risk if they are compromised? Or are there specific aspects of Kaseya that make a domain controller more susceptible or hack-prone?