I'm trying to rename the ADMS Impersonation account from "computername\AutodeskVault" to something differnt. Is there a way to do this?
I can't seem to find a solid answer on this.
Thanks
Hi,
This can be done from ADMS console:
Tools -> Administration -> Advanced Settings tab -> Advanced Configuration settings
You will need to rename the windows user itself - then this is where you would then change the user info used by Vault.
Paul Gunn
Thanks Paul,
I guess that's not what I was looking for because it didn't solve my problem. Here's what I want to do: I have Vault Basic 2014 running on a local machine and our clients are connected via our company network by IP address. When attempting to backup the Vault, I want to change the destination for the backup to a network location. The problem is that the user "AutodeskVault" does not have permissions to write to that directory. I thought that if I changed the impersonation account to my name, the server would allow it seeing as though I have permission.
I think I'm on the right track but I'm not able to successfully change all parameters to allow access. Any ideas? Maybe there's a more straight forward way to accomplish what I'm trying to do. I should also mention that our IT department doesn't want to add the user (for one reason or another).
Thanks again.
Hi,
The advanced configuration guide has a section on this (Setting up a remote backup location 😞
http://download.autodesk.com/us/vault/2014/2014_Advanced_Config_Guide-2014.pdf
That said, it looks like the instructions recommend using a domain user (both impersonating user and SQL server user need access). It is possible to use a non-domain user, however you would need to set up a mirror account on the remote machine with the same username and password. Certainly using a domain account is probably simpler overall.
Paul
I have a problem not sure how to solve. We have ADMS Console for Vault 2014 (SP2) running on my SQL Server. When I try to change the Impersonation account to a domain acct, do I can do remote FileStore Backups, every single time I try to change the Impersonation acct, the ADMS Console hangs (Not Responding). I have to manually force close the app, run it again, and the original local acct is still there. So everything works fine, but it hangs every time I try to change the Impersonation acct to the Domain acct I created for remote FileStore backups. (Domain\AutodeskRemote)
Any advice on how to solve?
TIA...
I have the same problem.
Was there any solution to thhis?
This time it is ADMS 2017.
It takes a very long time for some reason. Like 5 minutes. I had the same reaction - ADMS (2018 Pro) seeming to hang, killing it, restarting it, lather - rinse - repeat.
I had notes somewhere that the first time I changed it, it took a long time. So this time I waited a long time and it changed successfully.
Hope this helps
I believe that when the impersonation account is changed it goes through the sometimes very lengthy procedure of setting the acl security on the vault filestore for the newly assigned account. If the filestore is very large it will take a while.
I have exactly the same problem on the Vault ADMS 2019. When I try to change the Impersonation User Name, the Advance Config form becomes the Not Responding state and grays out. I waited a few hours, but it never completed. Maybe I need to wait longer? or is there another way to do change it such as Windows Registry??? We evaluated the server and domain account, but nothing is wrong, and the Vault functions on the users side, but the backup doesn't, which I believe due to the Impersonation account. We have not been able to backup over 2 weeks and desperately need a help.
As someone mentions above, this operation can take a long time (easily hours) depending on the size of your file store. Basically the new impersonating user needs to be given permissions to all of the files which take a good deal of time in Windows. I would suggest waiting over-night to see if the operation completes.
If the problem persists, you may want to open a support ticket - I can understand the concern about not having a recent backup.
Paul
Hi,
That should not be necessary. The system will not actually change the impersonating user in configuration until the file system security changes have all been made.
Paul