How simple should I keep the CMS name?
Upon creating our CCR E2007 Clustered Mailbox Server in the near future, we will have to give it a name. I'm all for a simple, user-friendly name since I understand it will be seen or used by end users when connecting. A colleague, however, is pushing for it to follow a rather complex server naming standard that will produce a non-friendly 14 character name. I don't believe the naming standard applies as we are talking about a virtual resource name, not a piece of hardware which is what the standard applies to. Am I correct in pushing for the simple name option? If the CMS ended up with a complex name could it be obscured from users via DNS aliases for instance? Could this approach lead to other problems? And is it possible to change the name of a CMS without reinstalling CCR/Exchange? Thanks!
May 13th, 2008 2:32pm

Do you have other clusters with standard naming conventions that you could follow ? In terms of managing your environment if it's a large environment and you will have multiple exchange clusters then it might make sense to follow you server naming convention .,...maybe adding CMS1 to the virtual name to distinguish between physical servername and virtual servername. I'm not sure I see any issues with complex names and DNS.......users shouldn't really have to be concerned about what server their mailbox is on anyways. As for changing the CMS......no real easy way to do this. I believe the best way would be to create another server.......move all mailboxes to that server, then rebuild your cluster and move mailboxes back. hope this helps cheers niamh ------------------------------------------------------------------------------------------------------------------------------------------------------ Please mark this as answered or helpful if it was
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2008 1:46pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics