IIS Process Model Windows 7

[kdonn]

The install needs to know the IIS Process Model Identity and gives choices of Machine, System, or Custom. But since IIS on Win7 uses ApplicationPoolIdentity for the Process Model, it seems I must change it in order to get SourceGear to work. This seems undesirable since it's likely to just break something else that depends on IIS running as ApplicationPoolIdentity. Is there any way to get Vault to use ApplicationPoolIdentity?

Kevin

[lbauer]

Have you tried install Vault using the Machine account? On my Windows 7 machine, I installed Vault Server using the Machine account. Vault is running under IIS APPPOOL\VaultAppPool and the App Pool is using ApplicationPoolIdentity.

[kdonn]

I haven't tried anything yet. The installer is sitting on the dialog where it wants to know the login. I had Vault all happily installed on my old Vista machine (which died on me), so I'm trying to get it up and going on Win7 now. I don't remember having to change the Process Model Identity last time (although I may have, just don't remember).

Let me get a better handle on your proposal. When you say, "I installed Vault Server using the Machine account", do you mean that on the Vault install dialog where it asks for "which login is used by the IIS Process Model", you chose "Machine"?

I think I may not understand what you're saying exactly, because the next thing you say seems at odds with this: "Vault is running under IIS APPPOOL\VaultAppPool and the App Pool is using ApplicationPoolIdentity." By this do you mean that you set up an App Pool specially for Vault, or does the Vault installer do that automatically? I'm confused.

Can you give me a little more detail about what you told the installer and then what you actually configured manually in IIS?

Thanks!
kd

[lbauer]

This is my experience: I recently did a clean install of Windows 7 Professional 64-bit on my machine. I installed the Vault 64-bit Server installer. For the IIS Process Model I chose Network Service.

I did no other configuration and made no changes to IIS.

After the installation, Network Service was DB Owner in SQL Server, but was not used for the Vault server process or the App Pool.

If I look in my server log, Vault is running under IIS APPPOOL\VaultAppPool and in IIS, the App Pool is using ApplicationPoolIdentity.

If you've ever looked at a Vault installation log, the installer tries to give permissions to a number of different built-in accounts. The installer may use one of those accounts for the Vault service and app pool rather the one explicitly chosen in the installer if there are issues with the chosen account.

Your experience may be different, but I would suggest to first try running the installation without making any changes in IIS.

Make sure to run the appropriate installer for your machine, such as the 64-bit installer for a 64-bit OS.

[kdonn]

That did it. I should have just been more trusting.

[lbauer]

Glad that worked for you. We do try to get things right, but we don't have a problem with you asking about it first.