>>The reason I asked you, is because the of the Security Context is done by a series of API calls. I was hoping you would be able to help me in that area. Rick's response was that he had tried to figure a way to automate the password but he knew of know way of accomplishing that.
>
>
>Actually no, it's not done via API calls. The stuff goes in the registry. The problem is that there is no API that performs these operations and the password information goes into an offlimits area of the registry (SAM portion) that you can't write to...
>
>I've looked at the way the context is written out into the registry and because the password can't be created there's no way to use a logged in account. You can specify any of the generic accounts in the DCOMCNFGSvr function in WC like SYSTEM, INTERACTIVE USER, GUEST etc.
>
>+++ Rick ---

I was able to pass it the administrator's account in DComCnfgServer. Of course when I went into the DComCnfg the password wan't in there so I add to add the password manually. The problem is that we're trying to create an install for others with as few as possible instructions. So even if they have to enter a password, that's better than having to add the account manually and then put in the password.