Event ID: 9548
Source:
MSExchangeIS Type: Warning
Description: Disabled user / O = Organization / OU = SiteName / CN = RECIPIENTS / CN = USER not does have a master account SID. Please use Active Directory MMC in September to an active account as this user's master account.
Summary: A disabled user has not configured msExchMasterAccountSid attribute and generates the 9548 event in the Event Viewer.
Resolution: The event indicates that Exchange can not determine the correct SID for a user it is looking for an attribute that is not already configured.
With the ACL permissions in Exchange 2000/2003, there are two possibilities to calculate the permissions, that is, if the account is disabled or not. If the account is enabled, the permissions are calculated with the attribute objects (or sIDHistory), and otherwise calculated msExchMasterAccountSid.
therefore eligible accounts should have never set msExchMasterAccountSid attribute, however the others do.
How do we know if the attribute is not set?
With ADSIEDIT for example, you can see "Not Set".
select a user not found problem, and adsiedit.msc console, deploy the domain portion to reach to a specific user, then open its properties and check that your attribute is not set.
For a user who has this problem, we should see the same until we put the permissions to the SELF user, then check that your attribute is set.
Instead of "Not Set", we should see something like 0x01 0x01 0x00 0x00 ...
as I said, the SELF user must have two licenses that are "Full Mailbox Access" and "Associated External Account", translated into English would be "Full Mailbox Access" and "Associated External Account".
We generate a log that indicates the number of accounts that have been fixed, just what this tool does is add the license. Check
: We can see in some accounts that the SELF user has configured the permissions on the users that gave errors.
Exchange Support Specialist Web: http://www.steve86.com/
Blog: http://esteban86.blogspot.com/
0 comments:
Post a Comment