Comet As Service uses Local System Account -- any attempt to change this results

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Alvin Chin on January 09, 2009 at 09:30:26: Uploaded files: 1

In an Active Directory environment, we have discovered network folders/files permissions problems when Comet is installed as a "service".

The services "COMET As Service" and "COMET Services" by default are configured to use the LOCAL SYSTEM account. However, Active Directory will not recognize these "local" accounts.

If I change the logon account for these services to a domain administrator or Active Direct user account (that has administrative rights to the server or workstation), COMET generates several errors -- it cannot locate nor access the local COMET folders (eg C:\COMET, C:\COMET\TMP, etc). Attached is a screen shot of the error code in COMET.



Follow Ups:


Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]