Announcement

Collapse
No announcement yet.

Windows Server 2003 Questions

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows Server 2003 Questions

    Hello, I've recently added a Windows 2003 Server AD to an existing Windows 2000 Domain. I plan on removing the Windows 2000 Server, and letting the Windows 2003 Server run all by itself. I am having trouble with replication of the server. I have replication taking place on the Global Catalogue, Licenses, and for Exchange 2000 to Exchange 2003.

    My big question is, how long does this process take? It seems that whether or not its replicating, I have no way to tell if its working, or when it will be done. Is there any easy way to do this? Why can't i just copy the information over?

    In the end we will be demoting the Windows 2000 Server, and killing its AD. When we took the Windows 2000 Server offline to see if the Windows 2003 Server could function on its own, and it seemed that it needed the Global Catalogues and Licenses to function properly. Any help would be apprectiated, as well as additional suggestions that I may have overlooked. This is my first time doing this.

  • #2
    Re: Windows Server 2003 Questions

    Please review:

    http://support.microsoft.com/default...b;en-us;555040

    There no real reason to remove the Win 2000 for now in SMB org.
    However, you should know that Exchange 2000 doesnt support on Win 2003 and its recommanded to plan to move to Win 2003 Native and Exchange 2003 Native in the future.

    A few extra tips:

    You may need to move the FSMO to the Win 2003.

    There no option (supported) to make Exchange 2003 server DC (You can install the DC and the the Exchange but not the opposite).

    You may need to move the site license server data to the new DC.

    Regards,

    Yuval
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Windows Server 2003 Questions

      Thank you for your advice. After trying a few things, I have more questions!

      For some reason the old server is still a primary global catalogue server, how can I move this to my new Windows 2003 Server? Because the global catalogue is stuck on the other server, it won't let me transfer the FSMO roles.

      Don't worry about Exchange 2003, we aren't going to worry about merging the data after all from Exchange 2000, we decided to go for a fresh start.

      If you could get those answered, I think the server would be good to go. Thanks! Also is there anything I'm overlooking? This is my first time doing this so any additional advice would be appreciated.

      Comment


      • #4
        Re: Windows Server 2003 Questions

        In Win 2000/2003 there no Primary global catalog. To remove the current GC (asfter you configure a new one, reboot it and backup the system) you use
        the instructions in:

        http://www.petri.com/configure_a_new_global_catalog.htm

        To find out how to remvoe exiting GC (you should reboot it twice after the changes).
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: Windows Server 2003 Questions

          Originally posted by yuval14
          In Win 2000/2003 there no Primary global catalog. To remove the current GC (asfter you configure a new one, reboot it and backup the system) you use
          the instructions in:

          http://www.petri.com/configure_a_new_global_catalog.htm

          To find out how to remvoe exiting GC (you should reboot it twice after the changes).
          You do not need to reboot after you configure a DC as GC or remove the GC role from a DC. All you need to do is wait about 15 minutes (in W2K3 it greatly depends on the size of the DIT and the amount of objects that need to be replicated to GC. In W2K the DC will be announced as GC after 15 minutes even if the GC replication has not finished) and make sure the corrrect SRV records got registered (restarting netlogon service should fix that).
          Guy Teverovsky
          "Smith & Wesson - the original point and click interface"

          Comment


          • #6
            Re: Windows Server 2003 Questions

            Ahhhh more problems!

            It seems that after we shutdown the old primary server (a Win2K Server) and leave the new primary server (a win2k3 server) running by itself, users cannot login, cannot find the domain, and even the active directory can't find the domain, yet the gobal catalogue has been replicated, and I've transferred all 5 FSMO roles.

            I'm about to start using the NTDSUTIL to force the roles over, but I'm not sure if thats my problem.

            I'd like to solve this quickly as this is costing me a lot of time, more than planned anyway!

            Comment


            • #7
              Re: Windows Server 2003 Questions

              Your Last Post indicates of DNS Problems.
              it seems that your clients are not configured with your new (2003) server as a dns server, and when your old (2000) server is down, the cannot locate any domain resources because they don't have any DNS server to turn to.

              Check for client defenitions, and if so, then redefine your settings in DHCP to include the 2003 server as the first DNS server.
              Yaniv Feldman
              Microsoft Security Regional Director
              Microsoft Management Expert
              MCSA, MCSE, MCT

              Comment


              • #8
                Re: Windows Server 2003 Questions

                After making your suggested changes, the entire network has slowed down to a crawl. The server requires constant restarts to keep things running smoothly.

                Something that is very bizarre is taht when I shutdown the old server, no one can access the new server, even though all DHCP and DNS settings do not have any referral to the Old Server.

                If I shutdown both servers and only restart the new server, it cannot see the companies domain, and there is no active directory. What would cause this? I think once we get this problem sorted out, things much just start working.
                Last edited by Theldon; 5th December 2005, 17:26.

                Comment

                Working...
                X