Posted by Justin Reynolds on January 14, 2009 at 10:57:15:
In Reply to: Re: Comet As Service uses Local System Account -- any attempt to change this res posted by Barbara Brazil on January 14, 2009 at 10:44:06:
"Anyone else out there using Active Directories and running Comet as a service?"
Yes.
On our server, "CometAsService" and "CometServices" both run as "Local System" without problems. This is a dedicated Comet server, so all files are hosted locally -- not on a network drive.
From the screenshot, I'm guessing that there are data files on the network somewhere other than the server. This won't work with "Local System" access rights, if I remember correctly.
Running as system/domain admin is a bad idea in general, but it should work. It sounds like the admin account you setup in services doesn't have rights to local files -- can probably just login as that account and try it out.
If I were forced into this situation, I'd create a new "Comet" domain user, give them appropriate rights to the network files/folders & make them a local machine admin. Login as that account, install Comet, etc, etc.
...
As an aside, Active Directory isn't new by any stretch. If Signature doesn't know how AD works, I'd suggest you don't understand your clients very well. Making your product play well in a standard business environment (Windows servers, Active Directory, the whole nine yards) should be higher on your priority list. Keep up or get left behind - that's just the way it works.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.