KNOWN ISSUE: Collection membership cache change monitoring is not functioning due to inability to run as service account. This is okay during installation
|Article:TECH196163|||||Created: 2012-09-05|||||Updated: 2013-05-09|||||Article URL http://www.symantec.com/docs/TECH196163|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
"Warnings","9/5/2012 2:54:13 PM","Collection membership cache change monitoring is not functioning due to inability to run as service account. This is okay during installation.","Altiris.NS.ItemManagement.CollectionMembershipCache.ImpersonateMonitoringThread","AeXSVC.exe","*"
Symantec Management Platform 7.1 SP2, 7.1 SP2 MP1
This issue has multiple causes:
- Casing of the domain portion of the application identity's credential does not match the case returned by the .NET security API.
- Multi-part domain name used to set up the app id credential. For example: typing "domain.local\Altiris" during setup. The .NET security API only returns the NETBIOS domain name as "domain"
- When the DNS domain name does not match the NETBIOS domain name. For example: using corpdom\Altiris during setup, when the NETBIOS domain name is just corp. The .NET security API we use returns the NETBIOS domain name, which must match the domain used during setup or impersonation will fail.
As a workaround, you can run AeXConfig.exe [/svcid user:<user name> password:<password>] and use the NETBIOS domain name in the domain portion of the domain\username pair, and use the same casing for the domain as returned by running "whoami" at a command prompt.
These issues are resolved in ITMS 7.1 SP2 MP1 Rollup v3. See HOWTO81832
|Value||2833532, 2973760, 2904875|
Article URL http://www.symantec.com/docs/TECH196163