Hey everyone, I’m curious if anyone else has been making use of the BYOV activity logon account type. I followed the below Netwrix guidance to connect to the Netwrix DB as a BYOV in order to checkout credentials without disabling the accounts; however I am seeing some odd behavior that might be a misunderstanding on my part of how the BYOV accounts are supposed to work.
(for reference Netwrix Documentation)
I have a pretty basic activity that checks out an account using a BYOV, and strips the domain section of the logon, in order to use to access a server. Everything works completely fine until the activity is de-provisioned at which point it looks like the “disable user script” is trying to run, and then fails because it can’t actually “manage” this server as you would normally expect. I was under the impression that the BYOV login account type would remove the steps of “enabling” and “disabling” an account and that it would instead simply use the BYOV connector to check in and check out the credential. Does anyone have experience with this working for them?
I haven’t reached out to support yet, as I am not sure if this is a bug or a misunderstanding on my part for what the functionality is. Would love to hear from anyone who has made use of the BYOV connectors a bit more than me. Below is the activity in question. It’s blurred but the login account template is filled out to be the correct account for the BYOV checkout script to find it 
