Bob Williamson
MCSE
Eisenhower & Carlson,
PLLC
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge de Almeida Pinto
Sent: Monday, March 21, 2005 4:45 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] domain naming
* This posting is provided "AS IS" with no warranties and with no rights!
* Allways test before implementing!
__________________________________________________________________________
From: Brian Desmond [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 00:51
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] domain naming
[EMAIL PROTECTED]
Payton on the web! www.wpcp.org
v - 773.534.0034 x135
f - 773.534.8101
From: [EMAIL PROTECTED] on behalf of O'Brien, Cathy
Sent: Tue 3/15/2005 5:12 PM
To: 'ActiveDir@mail.activedir.org'
Subject: [ActiveDir] domain naming
Our organization is planning an in-place upgrade from NT4 to W2K3. Our current NT domain name is no longer applicable (due to a corporate name change), unwieldy, and just plain ugly, and so we'd like to select a different name during the upgrade realizing of course that our NetBIOS name would remain the same.
We know that a domain rename is now a possibility, but from the stories we've heard we're not in a rush to go that route. We're just wondering how much confusion may be caused for users by having our NetBIOS and our domain DNS name not match. Off the tops of our heads it seems like not much of an issue, particularly since although we'll be a child domain we're planning to use just the forest root suffix for our UPNs. Our current DNS suffix doesn't contain our NT domain name at all, so whatever gets placed there will be a change for users.
Does anyone have any issues to point out that we're not thinking of, or opinion in general on the pros and cons of having the domain DNS and NetBIOS names match?
TIA,
Cathy O'Brien
Cubic Transportation Systems
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
NOTICE: This is a private and confidential communication for the sole viewing and use of the intended recipient. This communication may contain information protected by the attorney/client privilege or work product doctrine. If you are not the intended recipient of this communication, please immediately notify the sender and delete and destroy all copies of this communication. The unauthorized disclosure, distribution, copying, or use of information contained in this communication may violate the Electronic Communications Privacy Act, 18 U.S.C. 2510 et seq., the Washington Privacy Act, RCW 9.73, and Article I, section 7 of the Washington Constitution.