Is it safe to clear the legacyExchangeDN = ADCDisabledMail attribute on an Exchange admin?
- From: Alan <bruguy@xxxxxxxxx>
- Date: Fri, 25 Jul 2008 00:10:20 -0700 (PDT)
Hello,
We have an E2K/E2K3 Exchange Organisation which is still running in
mixed-mode. We removed our original Ex5.5 server after installing the
E2K server and uninstalled the ADC before installing the first E2K3
server. We share the SMTP address-space with a third-party e-mail
system.
One of our users, whose Window account is a domain/full exchange
administrator, used to have a mailbox on the Ex5.5 server. That
mailbox was deleted over a year ago and the account is not mail- or
mailbox-enabled. However, it's still holding onto the e-mail address
(only visible by doing a custom search on proxyaddresses) so we can't
assign that address to another account. It's also causing some
delivery problems. It seems that legacyExchangeDN is set to
ADCDisabledMail on the account.
To fix the problem, should we :
- right-click on the account in ADUC, select Establish email address,
give it the problem address and then use Delete e-mail address when it
becomes visible in ADUC?
- right-click on the account in ADUC and select Remove Exchange
attributes?
- or use ADSIedit to clear the legacyExchangeDN?
Given that the account is a domain/exchange admin, could those
modifications cause other problems to the whole Exhange installation?
We want to avoid deleting and recreating the Windows account.
Thanks,
- Alan.
.
- Follow-Ups:
- Re: Is it safe to clear the legacyExchangeDN = ADCDisabledMail attribute on an Exchange admin?
- From: Rich Matheisen [MVP]
- Re: Is it safe to clear the legacyExchangeDN = ADCDisabledMail attribute on an Exchange admin?
- Prev by Date: Re: Strange behavior. Any explanation?
- Next by Date: Simil Migration from 2003 to 2007
- Previous by thread: Strange behavior. Any explanation?
- Next by thread: Re: Is it safe to clear the legacyExchangeDN = ADCDisabledMail attribute on an Exchange admin?
- Index(es):
Relevant Pages
|
