I haven’t loaded E12 yet to play with it but if this is true… thank you! Much better than that horrendous dare I say, yes I dare, moronic naming in place now…
Err let me start at the beginning…
The EHLO blog mentions that since they reorganized things internally and Administrative Groups don’t need to be exposed so they came up with a secret name for the AG for E12 which is EXCHANGE12ROCKS.
I tried to leave a comment but the EHLO blog comments didn’t seem to be working… So here is the comment
Thanks!
Other acceptable alternatives
o NotNotes
o E124EVER
o _A1
o .A1
o _
o .
o .e12.
o _e12_
o e1975
o joeware.netrocks
o $
The default Exchange RDNs in E2K and E2K3 are the worst ever for people who use the command line to do work. It is the only app that was able to force me to use LDP on a semi-regular basis because I couldn’t stand typing all of that crap over and over again at the command line. 🙂
I mean seriously… here is a homemdb value where I have purposely made the DB and SG as short as possible but still end up with a ridiculous sized DN…
>homeMDB: CN=DB1,CN=SG1,CN=InformationStore,CN=2K3EXC01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=joeware,CN=Microsoft Exchange,CN=Services,CN=Configurat
ion,DC=test,DC=loc
I would have posted the full default homeMDB value but the internet bit quota police stopped by and said I would have blown my quota for the month… Â
The spaces suck, the length sucks.
InformationStore could easily have been, and should have been IS.
Servers could have been SRVs,
First Administration Group could have been many things but I don’t recommend the first thing that pops out and I don’t recommend 3 words with spaces either, whoever came up with that, find them and slap them.
Administrative groups could have been AGs.
Microsoft Exchange could have been MSEXCH.
The Org doesn’t even need to be there unless you guys are planning on allowing us to host multiple orgs from a single forest which doesn’t look like it is happening anytime soon so it could be an attribute on MSEXCH.
This DN could have looked something like
>homeMDB: CN=DB1,CN=SG1,CN=IS,CN=2K3EXC01,CN=SRVs,CN=AG1,CN=AGs, CN=MSExch,CN=Services,CN=Configuration,DC=joe,DC=com
Still not the greatest but certainly it won’t give you cramps while typing…
Â
The only question it brings up is did all of the Exchange admins always want to do things only in the GUI or were they forced to because they could actually open a slow gui that has to pull every piece of info back for every intermediate object and fish down through the structure faster than they could type one DN?
Don’t take it too hard, I’m only being serious. 🙂
  joe
