J4sstrom
asked on
How can I, and SHOULD I, change the legacyExchangeDN information?
Our company has had a name change (some of the partners names formerly used in the company name are no longer with company), but the legacyExchangeDN still reflects the old company name. Granted, it shouldn't be an issue as no user should ever see this information, but that has been showing on occasion when people printout emails, and powers-that-be want it corrected.
Obviously, the larger issue is fixing why it is showing the legacyExchangeDN information in the first place, but short of that, how would I go about changing that information? Will it cause mail delivery issues? This is the only Exchange server in the domain.
Particulars:
Exchange 2007 SP3 running on Server 2003
Obviously, the larger issue is fixing why it is showing the legacyExchangeDN information in the first place, but short of that, how would I go about changing that information? Will it cause mail delivery issues? This is the only Exchange server in the domain.
Particulars:
Exchange 2007 SP3 running on Server 2003
ASKER
Adding the LegacyExchangeDN as an X500, would that have to be done to future users also...or just currently existing ones?
Not to new ones just the current ones as we are changing some info on them .... new ones after change should have the new LegacyExchangeDN
- Rancy
- Rancy
ASKER
Can you recommend a whitepaper with info on using admodify.net? As well as properly adding an X500 entry?
Also, in your opinion, how risky is this, or at least how easy/likely is it to REALLY screw something up doing this?
Also, in your opinion, how risky is this, or at least how easy/likely is it to REALLY screw something up doing this?
Look i know doing such things isnt just risky to Exchnage but many a applications if they use this info .... so ideally i wouldnt touch this and ask to take PST and re-create Mailbox if i am pushed too hard ..... i know it will take time but i dont take the heat and people have to try with Pilot and see what issues are faced (I always have a pilot users to test with before going with everyone as when mgmt says they are happy and good to move)
- Rancy
- Rancy
ASKER
Truthfully, I love the idea of making a pst and recreating a mailbox. :-)
One thing I just discovered, I don't know what the cutoff was, but it seems that mailboxes that have been in existence prior to a certain time/event (upgrade from Exchange 2003 to 2007?) all have two X400 entries in the Exchange Management Console under their user properties. Are these the cause of the issue? If so, would making a PST of that users mailbox, deleting the mailbox, making a new mailbox, importing pst...remove those entries and correct this?
Also, what would consequences be of simply deleting those entries from the user profile?
One thing I just discovered, I don't know what the cutoff was, but it seems that mailboxes that have been in existence prior to a certain time/event (upgrade from Exchange 2003 to 2007?) all have two X400 entries in the Exchange Management Console under their user properties. Are these the cause of the issue? If so, would making a PST of that users mailbox, deleting the mailbox, making a new mailbox, importing pst...remove those entries and correct this?
Also, what would consequences be of simply deleting those entries from the user profile?
X400 isnt that much necessary with Exchange 2010 .... it was more used when we used to have Exchange 2000 and 2003 days ..... but causes no harm as all my users in Exchange 2010 SP2 have the X400 migrated from Exchange 2003 and all is well
- Rancy
- Rancy
ASKER
Looking at the header as shown when printed, it looks like...
/O=OLDCOMPANYNAME/OU=BALA/
(bala is old address of firm, bsh is a user)
So it is not the X400 address info being shown in the header when emails are printed. Am I on right track regarding "older" users? There does seem to be a correlation between who is reporting this issue and the age of their mailbox.
/O=OLDCOMPANYNAME/OU=BALA/
(bala is old address of firm, bsh is a user)
So it is not the X400 address info being shown in the header when emails are printed. Am I on right track regarding "older" users? There does seem to be a correlation between who is reporting this issue and the age of their mailbox.
Thats either LegacyExchangeDN or X500 as maybe how its configured
- Rancy
- Rancy
ASKER
Looking at this forum post, it seems you are right about legacyexchangeDN...
/o=DOMAIN/ou=First Administrative Group/cn=Recipients/cn=use
...since we no longer use Exchange 5.5, we should be able to safely remove this, yes? Where would I go to do this?
/o=DOMAIN/ou=First Administrative Group/cn=Recipients/cn=use
...since we no longer use Exchange 5.5, we should be able to safely remove this, yes? Where would I go to do this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, then if making any changes to LegacyDomainDN is not recommended, that leaves the other issue.
LegacyExchangeDN showing when printing emails
I am going to close this one, but I would appreciate if you could take a shot at the visible symptom of this issue. :-)
LegacyExchangeDN showing when printing emails
I am going to close this one, but I would appreciate if you could take a shot at the visible symptom of this issue. :-)
Secondly you will have to add the LegacyExchangeDN as a X500 to all users for not to affect their email flow
- Rancy