Posted by Jon Sacks on January 16, 2009 at 09:44:18:
In Reply to: Re: Comet As Service uses Local System Account -- any attempt to change this res posted by Alvin Chin on January 15, 2009 at 14:42:50:
I see this issue as a multi layered problem:
1. It’s clear that we did not have an understanding of what the functions of the Services are, if I am now correct they are:
a. Comet Services-This service is responsible for delivering data to and from the file system for the files served from this machine.
b. Comet As a Service-Is effectively the entire run-time enviornement less the UI.
c. Comet when run on Comet As a Service is no more than the UI that talks to Comet as a service.
2. So based on the above…..
a. Comet Services must have and only needs access to the local files. Therefore, it can be configured to run under the Local System Account.
b. Comet As a Service needs all the network rights that are required by a Comet User. So this must be set-up to run under the Domain Server Account.
3. So now to the flaw in the product (and it should be simple to correct). The install shield needs to be updated when Comet As a Service is selected to ask for the Domain Server Account name and register the service to use this name vs. establishing it as Local System Account. If this was done then we would not have seen this issue.
There may be something I am not thinking about in the design, but I assume I am correct.
JSACKS<<
If you're not the lead dog, the view never changes!
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.