Allow Vault installation/configuration to connect to an Instance not named AUTODESKVAULT
We have several separate vault servers (Professional) all connected to remate databases on an SQL cluster. The SQL people claim that they can only have one single instance called AUTODESKVAULT in their complete environment AND that instance names MUST follow their naming conventions
Actually, vault is the only software that I know of that requires a specific instance name
the goal is to run the job processor on many files that are spread accross several replicated servers.
the hurdle is that if you have the job processor logged into one server and it attempts to process a file that is currently owned by a different server, the task cannot be completed successfully. "error"...
we need to be able to allow for this in the job processor settings, whether it is to simply choose
1. "skip file that is not owned by your server", or
2. "run jobs on tasks with preference to one server over another". the job processor would be able to batch together a few hundred jobs for example, to complete on the local replicated server, then reboot itself (or log out and log into a different server) to run a few hundred files that are owned by the other server(s).
3. allow the job processor to run on files regardless of whether they are owned by another server, or
4. allow the option to choose: "if files are owned by a different server, then just run (several topions may be available here).
there may be easier ways to manage this but the job processor is going to be of much more use with some enhancement. (to be read in consideration with the several other requests for job processor improvements currently on the ideas station and discussion forumns).
There should be a relatively simple option in ADMS to truncate data from the vault, or to backup just the configuration.
Doing an implementation at a publicly traded company means going to a multi-stage process (dev, test, UAT, Prod) with multiple vault environments to verify the configuration before go-live. It would be very convenient to be able to either remove all of the files from the vault to provide a clean starting point for a new environment.
Alternately, the option to backup JUST the configuration would be a huge help as well.
If you've attempted to use the Refrence Repair Utility you'll quickly become frustrated it could really use some enhancements
In the settings I should be able to browse and select the Inventor Project File. The slash is opposite "/" to all other pathing in the settings and caused me some grief the first time I used this
I shouldn't have to close the utility when its done processing a folder. I should be able to pick a new folder and continue
I should be able to select multiple folders to process
It would be nice to be able to browse for folders to process
It can error and stop. As a script / batch processing utility it should just log the error and continue. There should be 0-interaction by the user until it is done
When it errors, it says to look at the log, but when you look at the log there is absolutely nothing about the error or what caused it to stop
I would assume that most people run the scan not on the server, apply the changes to the .xml not on the server, but then need to go to the server to import the fixes. It would be nice to be able to "push" the fixes from the same system used to scan and fix.
I use the command line to import the fixes but then need to use the ADMS Console logs to see any errors.... huh? The import needs to have its own GUI that writes its own log / error report