Vault Localhost to Network

[Anonymous]

Okay, I've tried looking around for an answer and looking through the installation guide/advanced config guide, but I'm having some issues. Basically, I have Vault Server installed on localhost on my computer since IT refused to help me setup Vault on an actual data server. I am wondering if (and how) I can continue to run Vault Server on my PC but have a couple other people in my group access the Vault information through our network.

Is this possible and if so, how do I go about doing this?

[DarrenP]

yea you can do this

you would have to make a backup of your current vault and restore the vault to the other server

but the 2 vaults will not be linked

or if your asking how they can access your vault on the local machine

then they would have to have access to that machine at all times that would probably bring your machines performance to a crawl

[Andy.Spivey]

Hi Matt,

If I understand the situation correctly, you just want to have some co-workers login and use the vault you have installed on your local workstation - correct?

What you will want to do in that scenario is create a few unique users in vault for your co-workers.  Then provide them either the name or IP address of your workstation.  They will use this information to log into the vault being hosted on your workstation.

Depending on the amount of data and network traffic they are generating, you may see a performance hit on your workstation as Darren pointed out.  Your computers hardware will also be a factor on how it performs with other folks utilizing it, etc.

I hope that helps clarify.

-Andy

[Anonymous]

Thanks for the replies. I did manage to get it to work and hopefully this run will segway into getting an actual server for Vault. Thanks again.

[Anonymous]

When You said you got it working...What did you get working?? Were you able to move the vault to your network?? If so how did you do that?

When trying to move the vault I run into an network access error. I have access to the network but the vault doesn't have my correct login name. Vault has me as BobH-PC\AutodeskVault and my name for the network is Bob Holt. I tried changing that in the Advanced settings / Impersonation / user name with no success.

Any insight into to this would be greatly appreciated!!!

Thanks

[Andy.Spivey]

Hi Bob - I am not sure what you are attempting to move.

The userBobH-PC\AutodeskVault is the local impersonation user that Vault is using to manipulate the filestore.  Most of the time, the user will be %VaultServerName%\AutodeskVault, though the impersonation user can be changed.  Some reasons to change it may be to have the filestore or backups go to a network location or following a naming standard.

What is the end objective for you?

[Anonymous]

I am trying to move the vault storage from my local machine to the network server so others can access the vault without going through my computer. From what IT is telling me the server has each person with authorization right and the vault seems to be looking for a machine authorization rights.

IT cannot or is unwilling to grant the Machine authorization so I am looking for away around that.

IT is not my thing so any help here would be appreciated!!!!

I tried changing the Impersonation name and it has an error. "Some or all identity references could not be translated"

Thanks

[Andy.Spivey]

Hi Bob,

If the objective is to have the other users be able to access vault without going through your machine, you will need to install the Vault Server application on a seperate machine completly - moving the filestore will only offload the task of storing the file bits to a different location.

At a high level, you will need to:

1.  Install the Vault Server application on a seperate machine (new hardware or existing supported hardware).

     a).  This includes the required database component (SQL Server) as well as IIS. 

     b).  Validate connectivity.

2.  Perform a backup from the Vault Server Console application on your machine.

3.  Copy the backup to the new machine and perform a restore command.

4.  Direct your users to log into the new machine - will only take an adjustment to their login dialog to change from BobH-PC to the new server name - their ID, password, and vault name will be the same.

Once they are connected and things look good, the application can be removed from your machine, and make sure the new machine is scheudled for backups etc etc.

[Anonymous]

Thanks.

Thought I could just move the vault. Didn't realize that I needed to install the software on the server.

Thanks for your help.

[Anonymous]

Interestingly enough, I have come across another odd issue in lieu of Vault. I have my computer set up as the Vault Server and I have populated the vault with assets, however, others cannot see any of the assets that I've placed inside of the vault. 

It states that there are "X" amount of objects in that folder (lower left of the Vault GUI) and all of the folders/sub folders show up in the Vault tree, but nothing populates in the main window nor will it show any information if you perform a search for an existing part. Anyone have any ideas of what's going on?

[Andy.Spivey · Accepted solution]

If I had to guess, I would say you are running Vault 2014 RTM and have .NET.5 (I think with SP1 installed).

There was a known issue regarding the grid population which was resolved with Sp1 for 2014. I would check the other clients - my guess is that you client has Sp1 or newer installed and the others are still RTM.

If thats no it, can you post what version of the client(s) and server are being used?

[Anonymous]

Right now we are running Server/Client 2013 Update 1 (since we are waiting for the release of 2016 before updating again) and .Net Framwork v4.0.

[Anonymous]

Applying the service pack and a hotfix got rid of the issue.

[Andy.Spivey]

Awesome! Thanks for the followup - glad it is squared away.