+1 This is how you truly get rid of "crud".
From: Jon Harris [mailto:[email protected]] Sent: Thursday, September 03, 2009 4:33 AM To: NT System Admin Issues Subject: Re: Changing a NetBIOS name considerations You might depending on the number and complexity of the situation want to just setup a 2003 domain and migrate everything to it if you don't want to just do the 2008 and have done with it. A 2000 to 2003 move is pretty painless as is the 2003 to 2008 but you need to watch the details. Linux and Mac's don't play well in a "pure" native 2003 domain you will have to make changes to the domain to allow them to play well. Jon On Wed, Sep 2, 2009 at 11:01 PM, Michael Leone <[email protected]<mailto:[email protected]>> wrote: On Wed, Sep 2, 2009 at 4:00 PM, Ben Scott<[email protected]<mailto:[email protected]>> wrote: > On Wed, Sep 2, 2009 at 2:49 PM, Michael > Leone<[email protected]<mailto:[email protected]>> wrote: >> Thanks to everyone for setting me straight about NetBIOS support in >> Win2000 Native mode. So, since I'm planning on slapping my AD into >> shape, I'd like to change the NetBIOS name. > > You said Win 2000, right? Correct. Currently at Win2000; thinking of changing the NetBIOS name before upgrading to Win2003 later in the year. > Win 2000 won't let you change the name of the domain (DNS or > NetBIOS). That was introduced in 2003, IIRC. Ratz! I was hoping to do cleanups and changes prior to the upgrade, if possible, so that the upgrade would be as clean as possible, free of any leftover crud. Ah, well. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
