General discussion

  • Creator
    Topic
  • #2074759

    Time to upgrade, where is my hammer?

    Locked

    by aaron_wurthmann ·

    Time for me to upgrade my NT 4 servers to 2000. My clients are either 98 or 2000. What I am looking for here are experiences that you have had, articles I should read fist, what I should look out for based on my server description below and roughly what time frame should I expect. (Am I going to have to spend the weekend here?) All servers are Dells with at least 400mhz PIIs, 256 mb ram, 6 gigs of disk SCSI hard drives with a Adaptec 2930 built in on the mother board. I ran the Windows 2000 Readiness Analyzer and didn’t get an problems other than a warning on making sure that I am on SP3 for Exchange and it also told me to upgrade the PDC first. I also dloaded the How to Upgrade from Windows NT Server 3.51 or 4.0 doc from MS, I am reading now.

    Name and main function / Other Purposes and software installed
    PDC / DHCP, Data Server, Diskeeper 5, NAI NetShield, DHCP Manager
    BDC / Exchange 5.5 Sp3, IIS, NT option pack, OWA / NAI GroupSheild
    WEB / Stand-alone server, WINS server, IntrAnet web ser

All Comments

  • Author
    Replies
    • #3894460

      Time to upgrade, where is my hammer?

      by bizaro_aaron_wurthmann ·

      In reply to Time to upgrade, where is my hammer?

      JUST THE SERVER INFO:
      Name and main function / Other Purposes and software installed
      PDC / DHCP, Data Server, Diskeeper 5, NAI NetShield, DHCP Manager
      BDC / Exchange 5.5 Sp3, IIS, NT option pack, OWA / NAI GroupSheild
      WEB / Stand-alone server, WINS server, IntrAnet web server, Backup Exec 8, Exchange Administrator, NAI NetShield, Diskeeper 5, IIS, NT option pack, WINS Manager

    • #3776419

      Time to upgrade, where is my hammer?

      by plantogo2000 ·

      In reply to Time to upgrade, where is my hammer?

      A technical answer is not the correct answer. The cacophony of equipment/software by itself illustrates a problem.
      1. Identify your top ten problems, plan to solve the top two (the hardest) and the other eight will automatically go away.
      2. Develop a budget of the effort required to convert to 2K including down time and training and education. Plan for 40% additional funding for unknown 2K glitches. Add schedule durations for high risk activities = to 40% baseline labor costs.
      3. Develop a top down plan that your boss and h/sr peers understand.
      4. Status the project on a backward pass basis every week and only deal with managers with accountability for master plan deliverable objectives.
      5. Build a small war room displaying master plan and budget status.
      6. Let your people do everything else and fill the gaps.

      • #3776191

        Time to upgrade, where is my hammer?

        by aaron_wurthmann ·

        In reply to Time to upgrade, where is my hammer?

        Okay, I may be a really bad mood right now, but your answer puts me in a worse one… Did you actually think that I was junior enough to not have already done this. Please, stick to the question ask, I asked for experiences not managerial procedures. I wish that I could deduct points from you instead, for wasting my time. Did I post this in the CIO forum NOOO! I posted in a tech forum and I want tech answers THANKS!.

    • #3776378

      Time to upgrade, where is my hammer?

      by mikeaussie ·

      In reply to Time to upgrade, where is my hammer?

      Backup! Backup! Backup!
      Plan for the “weekend” and if sucessful in less time great!. As per reply two, identify the major/critical components and concentrate on those items first. Give DUE CONSIDERATION to Active Directory Installation / Usage / Data Replication etc. You require contingency plans if the upgrade goes wrong eg Do I need to reinstall
      Exchange etc. Again….. BACKUP / EXPORT your critical files/data/account info First. Better to go back to original than have nothing come Monday morning.

    • #3776309

      Time to upgrade, where is my hammer?

      by dennis@l ·

      In reply to Time to upgrade, where is my hammer?

      What???? I don’t believe it. First thing is to backup the Data files on the PDC. Then backup the Exchange data files. Move them off of the PDC/BDC’s and put them on a members server.
      The Domain controllers primary function is to authenicate useraccess, if you get targeted by a hacker you are exposing all of you data directly to a hacker. Find you 2 more systems with atleast 128mb ram and a 6-12gb SCSI hard drives and make them the PDC/BDC. Migrate your Data service and Exchange service to2 separate members service. Consider what it would cost your company if all of there data files where lost vs acquiring additional resources to help nprotect them.

      • #3776193

        Time to upgrade, where is my hammer?

        by aaron_wurthmann ·

        In reply to Time to upgrade, where is my hammer?

        LOL
        Have you ever been hacked? I have (NOT MY FAULT, THE UNIX GUYS OWNED THE FIREWALL THEN). Either way any of those machines are vulnerable. If the PDC gets hacked the hacker will be able to find the location of the home directories and then the data server, where of course the home directories are. A better argument for separating the two is bandwidth and disk use. Which I am totally for, but at this time it isn’t an option. Besides that you didn’t address my Windows 2000 migration concerns just my server layout. Thanks any way. The problem with making Exchange a Member Server instead of a DC is that it will put some undue stress on my users for OWA they’ll have to log in with the domain name. My users are pretty stupid, I’ll take the security risk. Thanks again.

    • #3776282

      Time to upgrade, where is my hammer?

      by inspectorclave ·

      In reply to Time to upgrade, where is my hammer?

      Upgrading to Win2000 is a big task. It can be much worse, though, if you don’t have a decent grip on how Active Directory plays into the whole mess. Setting up an AD forest is more or less a one shot effort. If you don’t look ahead and forecast the items that you will be adding to your forest and prepare up front, you will have to start from scratch. It stinks.. I know. This link is a “must read”:

      http://www.microsoft.com/technet/showcase/w2kacdir.asp

      Also, as usual, start with the PDC, then move to the BDC’s, then conclude with any member servers.

      This link is to Microsoft Win2000 AD Migration Tool:

      http://www.microsoft.com/windows2000/downloads/deployment/admt/default.asp

      • #3776194

        Time to upgrade, where is my hammer?

        by aaron_wurthmann ·

        In reply to Time to upgrade, where is my hammer?

        Yes, this is exactly the info that I am looking for. Actually I forgot to mention in the original posting that I am familiar with AD I use it at home in my 5 machine network, but 5 machines hardly compares to 100 at two sites and growing.

    • #3776233

      Time to upgrade, where is my hammer?

      by aaron v ·

      In reply to Time to upgrade, where is my hammer?

      There are many good suggestions here –
      I would start with the backups. Also we ran into trouble with Virus scanners under Win2k. Verify and re-verify that these work under Win2k (load up a workstation and install the software to test it). We ended up changing Virus scanners when upgrading. (You will most like incure licensing costs for this).

      Diskeeper may interfere with the one built in to Win2k, you may need to re-install.

      If I may be so bold, IMHO, I would convince management tosplit functionality out on your server. I would build a dedicated Exchange Server, in addition to your PDC.

      • #3776195

        Time to upgrade, where is my hammer?

        by aaron_wurthmann ·

        In reply to Time to upgrade, where is my hammer?

        Thanks, if I had anymore points to give they would be yours. And yes I read that Diskeeper should be uninstalled and then reinstalled after the upgrade. The problem with making Exchange a Member Server instaed of a DC is that it will put some undue stress on my users for OWA they’ll have to log in with the domain name. My users are pretty stupid, I’ll take the secuirty risk.

Viewing 5 reply threads