I don't think your users will have much confusion over the matter. Just have them use upn to login when a domain is required. It's bene a logn time since I did an NT4 -> AD inplace upgrade, but I want to say you can edit the netbios name during the upgrade. --Brian Desmond [EMAIL PROTECTED] Payton on the web! www.wpcp.org v - 773.534.0034 x135 f - 773.534.8101 c - 312.731.3132
________________________________ From: [EMAIL PROTECTED] on behalf of O'Brien, Cathy Sent: Tue 3/15/2005 5:12 PM To: '[email protected]' 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
<<attachment: winmail.dat>>
