Vault does not install in non-default directory

vrapp · Post by **vrapp** » Thu Mar 17, 2005 2:53 pm

I saw an article that was describing how Vault can't coexist with Sharepoint on the same web. The article advised to create separate web for Vault.

I had exactly this scenario, so I followed the article. I created separate directory c:\vault, created new web with that directory as home, and specified it during the installation.

After the installation, however, I found that virtual directories VaultService and VaultShadowFolder were still created under inetpub/wwwroot, i.e. inside the default directory, where the sharepoint lives. In IIS, they appear under the web Vault, which directory is c:\vault, but obviously, the purpose was not achieved.

Did I do something wrong, or it's oversight of the installation?

mskrobul · Post by **mskrobul** » Thu Mar 17, 2005 3:21 pm

When you install the Vault Server you can specify the directory on disk where the VaultService files go. By default this location is c:\inetpub\wwwroot.

On the Select Feature screen of the Server installer, select the Server component and browse to your c:\vault directory for the install directory.

I update the article with this information.

vrapp · Post by **vrapp** » Thu Mar 17, 2005 8:16 pm

Thanks, I see now.

Another question about the installation: I download the server package, which also includes client and admin tool. On the client machine, I want to install only client component. On the same Select Feature dialog, I can make Admin Tool unavailable, but I can't make the server unavailable - only advertised, i.e. "installed when required". I think it should be possible to make it unavailable as well. (I wonder, when would it be "required"?)

gmagana · Post by **gmagana** » Thu Mar 17, 2005 8:36 pm

There are separate downloads for the client and the admin tool in the download section...

mlippert · Post by **mlippert** » Thu Mar 17, 2005 11:20 pm

On your client machine get or run the client installer by browsing to your installed vault server, ie http://servermachine/VaultService

There is a link on that page to the client installer (there is also a link to the admin installer).

Mike

vrapp · Post by **vrapp** » Fri Mar 18, 2005 12:38 am

> There are separate downloads for the client and the admin tool in the download section...

server downlload includes client installation, why downloading two packages?

> On your client machine get or run the client installer by browsing to your installed vault server

Thanks; I meant that the installation package might be improved.

GregM · Post by **GregM** » Fri Mar 18, 2005 8:24 am

You don't need to download two packages. The client installer is placed on the server for clients to use, and is available by accessing the server with a web browser as listed in Mike's post.

Guest · Post by **Guest** » Fri Mar 18, 2005 8:30 am

Yes, but besides that, it is also possible to install it from the server package. If it's not a supported option, then it should not be there. If it is supported option, then server component should be possible to specify as "never install". I don't think the administrator has to remember to ignore the installation in one place because there it's wrong, and install from elsewhere.

mskrobul · Post by **mskrobul** » Fri Mar 18, 2005 8:45 am

The client installer is included with the Server installer for convenience for users who want to install the client on the server machine. If you choose to install the client during the server install, the client will be installed on the server machine along with the server.

If you are installing only the client on a machine, we recommend using the stand alone client installer.

Guest · Post by **Guest** » Fri Mar 18, 2005 9:38 am

OK, putting aside the best way to install the client, is there a reason to not allow "never installed" option for the server component in the installation?