Disjoined Namespace after upgrade

8 months ago, I upgraded our first NT 4.0 PDC to Windows 2000 server.  The upgrade went fine and the other 2 NT 4.0 BDC's on our network cominucated fine with it.

I just placed a new Windows 2000 server on our network and was triing to add it to the domain as an additional (bdc) domain controller for an existing domain.  I kept getting error messages saying the domain I was triing to join was non-existant.  After a little research, I releatized that when I initially upgraded the first NT 4.0 machine (old PDC) there was an error that took place that caused a disjoined namespace.  My domain is local.company.com.  My server name is DC1.  If I look at Networt ID, my computer name is showing as DC1.company.com with a domain of local.company.com.  You see my dilema..

I found a Microsft article that explains how to fix the problem.  Here is the link: http://support.microsoft.com/default.aspx?scid=kb;en-us;257623.

They recommend running a script that will correct the FQDN of the server.  I am willing to try this just a little concerned about the repercussions.  Looking for advise from anyone that may have done this already.  Will I loose any profile information?  Does anyone see any other issues that may arise by running this script 8 months after I have been running with a 2000 server acting as the "PDC" for this domain??  Any advise or tips appreciated..

Thanks You
Chad