exchange 2013 ExchangelegacyDN garbled

This wont affect the OAB as its now more on Web-based .... and Exchange 2013 with Windows2012 isnt supported as far as i know in production as of yet

- Rancy

http://technet.microsoft.com/en-us/library/bb691354.aspx

server 2012 is listed

Is this still RTM can you share its Version ..

- Rancy

All i can give u at the minute is that it is Exchange 2013 Std from the MS Partner site...

wonder does exchange not understand the '/' character at the beginning of the DN?  Only one way to find out

i am putting together a server 2008 r2 / exchange 2010 env at the minute....just gonna make sure that my memory isn't failing me

In DN if your applying some symbol\character at the starting your incorrect

- Rancy

Exchange 2013 can only be installed\Supported on Windows Server 2008 R2 Sp1 or Windows Server 2012.

I followed the same article to set the CreateDialog attribute to %<sn>.%<givenName> and below are the output.. Can you help me to know the issue here ?

[PS] C:\Windows\system32>get-mailbox rajkumar | fl *legacy*


ServerLegacyDN   : /o=First Organization/ou=Exchange Administrative Group
                   (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CHENNAI-EX-01
LegacyExchangeDN : /o=First Organization/ou=Exchange Administrative Group
                   (FYDIBOHF23SPDLT)/cn=Recipients/cn=a6c2a018253c4129bc73787a8a7e2b06-Rajku


[PS] C:\Windows\system32>adsiedit.msc
[PS] C:\Windows\system32>dsa.msc
[PS] C:\Windows\system32>Enable-Mailbox -Identity kumar1.raj1

Name                      Alias                ServerName       ProhibitSendQuota
----                      -----                ----------       -----------------
Kumar1.Raj1               rajkumar1            chennai-ex-01    Unlimited


[PS] C:\Windows\system32>get-mailbox rajkumar1 | fl *legacy*, distin*


ServerLegacyDN   : /o=First Organization/ou=Exchange Administrative Group
                   (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CHENNAI-EX-01
LegacyExchangeDN : /o=First Organization/ou=Exchange Administrative Group
                   (FYDIBOHF23SPDLT)/cn=Recipients/cn=9b9d12b6d44a442c93918bd5df51951e-Kumar
DistinguishedName : CN=Kumar1.Raj1,CN=Users,DC=CHENNAI,DC=COM

it does this automatically when u follow the technet article for changing display names in AD..

So when i go to ADSI edit i see DN=\Bloggs, Joe

can you please share some screenshot of it if possible

- Rancy

hi raj,

I am installing Exchange 2010 in another test environment.  I am going to change the display name and check the results....i can remember that this was an issue when exchange 2010 was first released...it took an update rollup to fix it....

so i will apply sp2 to the exxchange install and report back

Ok we will wait for your update on exchange 2010. I tested the same in Exchange 2013 with Windows 2012, but I cannot reproduce it.

Tried to create two other AD accounts and mailboxes, but the dn value is normal without \

I could actually go through the process of applying each rollup for 2010 at a time, but i dont have that time

So, in Exchange 2010 the DN is correct

but in SP2 update rollup 6, it changes

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/8b4181c3-2fa2-4311-a245-3e81e9659f4b
Capture.JPG

The LegacyDN is correct after changing the display name in Server 2008 R2 with exchange 2010 sp1.

More investigation will have to be done to understand why the LegacyDN is all random characters with Server 2012 and Exchange 2013.
Capture2.JPG
Capture3.JPG
Capture4.JPG

See attached Exchange 2013 with Server 2012

I am installing Server 2008 R2 SP1 with Exchange 2013
Capture.JPG

See attached LegacyExchangeDN name using a combination of Server 2008 R2 with Exchange 2013
2008R2-EXCH2013.JPG

this is obviously an issue with Exchange 2013

My tests have been..

Server 2012 Domain Controllers and Exchange 2013
Server 2008 R2 Domain Controllers and Exchange 2013
Server 2008 R2 Domain Controllers and Exchange 2010

looks like the issue isn't an issue at all.  This is now by design.