Re: Vault 2.0.1 install on Domain Controller

luke:

i've answered in-line.

*********** REPLY SEPARATOR  ***********

On 4/2/2004 at 10:06 AM Luke T. Gatchell wrote:

>Before I go through all the steps listed on the support page for 
>creating an ASPNET account, assigning directory permissions, etc.,
>could someone explain why this is all necessary when I don't 
>recall doing any of this for Vault 1.1 (when I was evaluating it)?

if you don't mind me asking, why are you trying to create a separate account?  it is possible, but not really necessary to create a custom account / use identity impersonation unless you are :
- installing vault server on a primary domain controller (PDC) - something I would not recommend (.net does not create the local asp.net process account on a PDC without tweaking)
- configuring shadow folders for network access or on windows 2003 server (the local asp.net process account does not have the ability to access a network resource)
- sql server is hosted on a different machine than the vault server, and it is configured to use windows authentication



>I presume you guys would concur with MS that using the SYSTEM
>account in machine.config is the wrong way to go. Rather, creating
>an ASPNET account as a User, assigning directory permissions, etc.
>is better?

from a security standpoint, yes.



>And is it true, as mentioned in one of your forums, that this is
>really an installer error and that it should install just fine
>under the first radio button choice when choosing the ISS Process
>Model? Will this be fixed, or is there really no way around it?

i see your point, and it is valid, but i think the vault server installer should probably stay just that - a vault server installer.  the installer would be opening a huge pandora's box (for support), if an installer started mucking with a systems .net settings as well as creating accounts on people's domains.


>Thanks.
>
>As an aside...
>
>I found it interesting in reading up on this (after my install
>failed), that the ASP.NET framework doesn't run by default under
>a Windows 2003 Server? I had installed Visual Studio .NET on 
>there awhile ago and had run through some web app tutorials, and
>they seemed to run fine. But I did notice that there is no 
>aspnet_wp.exe that shows up in Task Manager, even when running a
>web app. Does it use a different name? How is the web app working
>if it's not running?

i'm uncertain what you mean by this statement? do you mean that you must install the asp.net components from the windows setup -> application server components?  did you have to enable the handling of asp.net pages from within iis?  under iis 6.0, you will see the asp.net process is named w3wp.exe.