I am messing around with Windows Services for the very first time - I'm
getting to the installation part, and when I install, it asks for a username
and password.
Is this absolutely necessary?
Also - is there any way to get around it, so that it just runs?
Michael C - 30 Oct 2007 01:22 GMT
> I am messing around with Windows Services for the very first time - I'm
> getting to the installation part, and when I install, it asks for a
> username and password.
>
> Is this absolutely necessary?
No, mine doesn't ask for a username/password. Did you specify to use the
system account (I can't remember the exact details).
> Also - is there any way to get around it, so that it just runs?
You always need to install a service. BTW, I don't use the dot net installer
but just called the API to install the service.
rsine - 30 Oct 2007 12:11 GMT
> I am messing around with Windows Services for the very first time - I'm
> getting to the installation part, and when I install, it asks for a username
> and password.
>
> Is this absolutely necessary?
> Also - is there any way to get around it, so that it just runs?
Elmo,
Michael is correct in that unless you need to, you should not install
the service using the "User" account property (set in the
ServiceProcessInstaller). Instead, use the LocalService,
NetworkService, or LocalSystem account types. Using one of these
account types will install you service without any prompting for
username and password. The only time I have used the "User" account
is when I wanted to install the service with the priviledges of a
specific account.