分类: WINDOWS
2010-02-23 13:50:22
本文主要讲解了任何删除用户的邮箱属性(注意不是邮箱),当你的EX服务器因为意外损坏(比如硬盘挂掉),又没有备份的时候,恢复往往是比较复杂的(有关恢复问题请搜索论坛),在无法恢复的情况下,我们一般是采用删除AD里的组织重新安装,那么这样安装后有一个问题,就是用户的属性里仍保留有EXCHANGE属性,你不能修改这些属性,也不能重新建立邮箱,这是因为用户属性里的MSEXCHHOMESERVERNAME仍指向坏掉的EXCHANGE组织导致的。以前我说过可以手工编辑清除用户的活动目录属性(见论坛),这样操作不仅慢(要一个一个去做),还带有一定的危险性,现在推荐大家使用EX2000 SP2以后版本都有的一个功能–移除EXCHANGE属性。它可以删除所有错误的EXCHANGE属性,重新建立邮箱。
原文地址:
——————————-
SUMMARY
In Exchange 2000 Service Pack 2 (SP2) and later, administrators can use the Remove Exchange Attributes option to remove Exchange attributes from any user or group object. Use this option with caution. You can use this option to reconnect a mailbox after disaster recovery. You can also use this option if you are using the Active Directory Connector (ADC) and you notice that some of your Exchange attributes are being matched improperly with Active Directory user objects.
MORE INFORMATION
To remove Exchange attributes from any user or group object: 1. Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
2. On the View menu, click Advanced Features.
3. Click the appropriate organizational unit.
4. In the organizational unit, click the user object, and then right-click the user object.
5. Click Exchange Tasks, and then click Remove Exchange Attributes.
6. Click Next, read the warning, click Next again, and then click Finish.
After you perform this action, no event is generated in the Application event log.
List of Attributes Removed (from the Source Code, Build 5716.2)
(”altRecipient”),
(”authOrig”),
(”autoReplyMessage”),
(”delivContLength”),
(”deliverAndRedirect”),
(”deliveryMechanism”),
(”delivExtContTypes”),
(”dLMemDefault”),
(”dLMemRejectPerms”),
(”dLMemSubmitPerms”),
(”dnQualifier”),
(”enabledProtocols”),
(”expirationTime”),
(”extensionData”),
(”folderPathname”),
(”formData”),
(”forwardingAddress”),
(”garbageCollPeriod”),
(”homeMTA”),
(”importedFrom”),
(”internetEncoding”),
(”labeledURI”),
(”language”),
(”languageCode”),
(”legacyExchangeDN”),
(”mail”),
(”mailNickname”),
(”mAPIRecipient”),
(”msExchCustomProxyAddresses”),
(”msExchExpansionServerName”),
(”msExchFBURL”),
(”msExchMailboxSecurityDescriptor”),
(”msExchMasterAccountSid”),
(”msExchPoliciesExcluded”),
(”msExchPoliciesIncluded”),
(”msExchPolicyEnabled”),
(”msExchPolicyOptionList”),
(”msExchPreviousAccountSid”),
(”msExchProxyCustomProxy”),
(”msExchRecipLimit”),
(”msExchUserAccountControl”),
(”pOPCharacterSet”),
(”pOPContentFormat”),
(”protocolSettings”),
(”publicDelegates”),
(”replicationSensitivity”),
(”secretary”),
(”securityProtocol”),
(”submissionContLength”),
(”targetAddress”),
(”textEncodedORAddress”),
(”unauthOrig”),
(”heuristics”),
(”msExchADCGlobalNames”),
(”msExchALObjectVersion”),
(”msExchHideFromAddressLists”),
(”msExchInconsistentState”),
(”msExchUnmergedAttsPt”),
(”replicatedObjectVersion”),
(”replicationSignature”),
(”showInAddressBook”),
(”unmergedAtts”),
(”extensionAttribute1″),
(”extensionAttribute10″),
(”extensionAttribute11″),
(”extensionAttribute12″),
(”extensionAttribute13″),
(”extensionAttribute14″),
(”extensionAttribute15″),
(”extensionAttribute2″),
(”extensionAttribute3″),
(”extensionAttribute4″),
(”extensionAttribute5″),
(”extensionAttribute6″),
(”extensionAttribute7″),
(”extensionAttribute8″),
(”extensionAttribute9″),
(”autoReply”),
(”deletedItemFlags”),
(”homeMDB”),
(”mDBOverHardQuotaLimit”),
(”mDBOverQuotaLimit”),
(”mDBStorageQuota”),
(”mDBUseDefaults”),
(”msExchHomeServerName”),
(”msExchMailboxGuid”),
(”msExchMailboxUrl”),
(”msExchPfRootUrl”),
(”msExchUseOAB”),
(”proxyAddresses”)
If you are running the Active Directory Connector between Exchange 2000 and Exchange 5.5, the procedures listed in this article for removing mail attributes from a user on Exchange 2000 will not propagate across the ADC and remove the Custom Recipient object representing the user on the Exchange 5.5 side.
If the client is expecting the changes to migrate from Exchange 2000 to Exchange 5.5, you will have to avoid removing the legacyExchangeDN attribute, and set its value to ADCDisabledMail.
For additional information, search the Exchange 2000 SP2 Help (the Exadmin.chm file) for “remove exchange attributes”.
The following two Exchange attributes are left behind after running “Remove Exchange Attributes” in Exchange 2000 SP2.
deletedItemFlag
displayNamePrintable
The Exchange Attribute publicDelegatesBL is also left behind after running “Remove Exchange Attribute”. This is because the user has been granted delegated access to another user’s mailbox. This behavior is by design so that when the user is mail-enabled again they will have access to that user’s mailbox without the user having to re-delegate access.