Re: rename AD user account creates problem with autocomplete in Ou
- From: Rebecca <Rebecca@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Feb 2007 11:35:01 -0800
BurningSpleen: Wow, thank you for the excellent and complete compilation, I
think many people can benefit from using your post as a resource. I'm saving
your information for the next time that I have a real user with a name
change, or the next time that I have an opportunity to try your steps on a
test account. In the meantime, if anyone else sees and tries these steps,
let all of us know if you experience success, trouble or adverse and
unexpected results.
"BurningSpleen" wrote:
I posted.
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?&query=legacydn&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.exchange2000.admin&p=1&tid=a258f7c7-ba6f-44e0-bec6-7dc88b1d2723&mid=a258f7c7-ba6f-44e0-bec6-7dc88b1d2723
based in part on this thread. Did I miss a step that would negatively affect
my mailbox?
"Dave Goldman [MSFT]" wrote:
Most people I know recommend to add another proxy address (smtp or x500 -
make sure the legacyExchageDN is the same, just the RDN changes /cn=davegold
to /cn=dgoldman). This way everything can stay the same and your users can
continue to get email to the old account address and new one. You can also
change the display name so this way the gal will refelect the new name
change. I dont really see the point to changing the RDN portion as this
really affects the login account name and will break mailflow. If you wanted
to change the way the user logs in you could do this.
With any proxy changes you need to make sure that the mail attribute and the
primary proxy address (the one denoted in capitals SMTP) are the same as the
below example
dgoldman
dgoldman@xxxxxxxxxxxxxx
If both of these are different the user will get skipped from the generation
process. Typically when you change the mail attribute or proxy it should
also change the other one to match.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Dgoldman
http://blogs.msdn.com/dgoldman
"Rebecca" <Rebecca@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2ED76108-0939-4375-A309-4814F1169829@xxxxxxxxxxxxxxxx
Eventually, after we fix jwalter <jgoulding> I guess what I really need is
the answer to this question: if user Mary Zielinksi (mzielinski) gets
married and changes her name to Mary Smith (msmith) then EXACTLY what
steps
am I supposed to take?
I would expect to be able to rename her account in Active Directory and
rename her Exchange mailbox and email address without losing all of the
and contacts that she received as Mary Zielinski. And then I would expect
that when logs on to her own cleint computer after the wedding, her old
Mary
Zielinski desktop should still be there with everything correct?
I wouldn't expect that I should need to go through such a complicated
process.
"Dave Goldman [MSFT]" wrote:
I would hold off a bit more to make sure that your replication between
domain controllers is working as fast as it should. You can use a tool
called repadmin /showmeta "dn of object" and then get ldp dumps of the
user
object from both domain controllers to ensure that it is the same on both
sides. For that object OABInteg is showing that in the active directory
that
users rnd portion has not been changed yet, so trying to email via legDN
or
by using the nicknames cache will fail.
I am not sure if you know how to use the DS Servers key on your Outlook
client for testing purposes but if you do you can look at the OABInteg
log
to see what domain controller the first test connected too. Set the DS
Servers key on your client in HKLM\Software\Microsoft\Exchange\Exchange
Provider, add a Value type: REG_SZ Value: servername of your other domain
controller and run OABInteg again. This registry key will force your
client
to connect to and only that domain controller specified. Once this is
done
you can remove the registry key and compare the OABInteg results to see
if
the objects are the same or different.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Dgoldman
http://blogs.msdn.com/dgoldman
"Rebecca" <Rebecca@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6456D57F-D168-4CFB-8E31-E40B10D4F6F2@xxxxxxxxxxxxxxxx
Dave, I just discovered something that MIGHT mean that one of my
previous
steps had already solved the problem, but maybe I had not waited long
enough
for the changes to replicate from the server to the client. Not sure.
We have two AD user accounts that have/had the same problem, and all of
the
various steps that I already did by myself before I contacted you were
done
for the account that was in the AutoComplete as dpritchard
<amazzarisi>.
No
matter what I did, it was still appearing incorrectly which is what led
me
to
contact you. However, as of today that account is showing up correctly
as
dpritchard <dpritchard>. Everywhere!
However, we still have jwalter <jgoulding>. I really don't want to
re-do
EVERY step that I tried with dpritchard because I did A LOT and I don't
know
which one was the trick. So, what do you recommend as my next step for
jwalter <jgoulding>?
- References:
- Re: rename AD user account creates problem with autocomplete in Ou
- From: BurningSpleen
- Re: rename AD user account creates problem with autocomplete in Ou
- Prev by Date: Re: Reporting on NDRs
- Next by Date: Re: How do I setup a Calendar that is readable by all, but updatedable by only a few?
- Previous by thread: Re: rename AD user account creates problem with autocomplete in Ou
- Next by thread: Re: Logs unexpectdedly filling fast
- Index(es):
Relevant Pages
|
