Upgrading thru all version of Windows......server and domain controller


Recommended Posts

Ive seen a couple of videos of people that upgrade client versions of Windows (even DOS) to Windows 8.1 or 10.

Im gonna try to do the same with the Windows servers........and take it a step up with domain controllers and active directory.

This is just for fun and learning purposes. Nothing at the end of the day and of course, this should never be used in a real life scenario.

My scenario is:

- VMWare Workstation

- Ill make a virtual network only for this

- 1 domain controller, 1 domain client

- Start from the oldest possible server/domain controller (Windows NT 3.1 Advanced Server) and upgrade to the latest possible server/domain controller ("Windows Server 10 Technical Preview")

- Start from oldest possible client that can join a domain (Windows NT 3.1) and upgrade* to the latest possible client that can join a domain (Windows 10).

* Upgrades will ONLY be done when the client cannot logon to the domain. What I mean by this is that Ill first install Windows NT 3.1 and Windows NT 3.1 Advanced Server. Ill upgrade Advance Server to the next version and check if I can logon. If I cant, Ill upgrade the client and recheck again. Meaning I want to upgrade the client as less as possible. If Windows NT 3.1 can logon to Windows Server 10 Technical Preview, awesome.

- On the server side, minimum features/changes will be installed/configured to check if they go thru the upgrade: Server name, admin user name/pass, client user name/pass, etc...

- Later versions of server/DC/AC, require some things that weren't available/needed. Windows NT 3.1 obviously doesn't need PDC Emulator but later versions of Active Directory, do. Those will be added/enabled STRICTLY as required. Also compatibility layers for previous clients will always be enabled to ensure that our oldest clients can logon/join.

- Server list:

Windows NT 3.1 Advance Server (All continuous operating systems will be the server version, first server and domain controller that will be installed)

Windows NT 3.5

Windows NT 3.51

Windows NT 4.0

Windows 2000 (first time Active Directory will be implemented)

Windows 2003 (or R2, I dont think there is MUCH differences in domain services between non R2 and R2 right?)

Windows 2008 R2

Windows 2012 R2

"Windows Server 10 Technical Preview"

- Client list:

Windows NT 3.1 (My goal is to stay on this version till Windows Server 10 Technical Preview)

Windows NT 3.5

Windows NT 3.51

Windows NT 4.0

Windows ME/Windows 2000 (Sadly, Im not sure if it is possible to upgrade from NT 3.51 to Windows ME so we would have to upgrade first to Windows 2000. If I have to go to Windows 2000, I am hoping that Windows 2000 is compatible with all future servers)

Windows XP (I really hope avoid having to reach this)

Windows Vista (I should NEVER reach this point)

If for some ODD reason, I have to upgrade past Vista, Ill take a step further as "bonus trial" and switch to a Linux distribution with Samba support. Again, I should NEVER even pass 2000 or at most XP)

- The procedure would go:

1: Install first server

2: Configure first server/DC/AD/etc,

3: Make a color scheme change on server to see if it passes thru upgrades

4: Make one domain admin account and make one domain user account

5: Install first client

6: Join client to domain using domain admin account

7: Logon using domain user

8: Leave/modify a file on the domain user's desktop to see if it passes thru

9: Upgrade to next server

10: Configure any changes that are absolutely needed

11: Apply fixes needed on server so oldest client can log on

12: Logon with domain user

13: If impossible to logon, upgrade client

14: Repeat from 9

For now, that is the idea. Am I on the right track?

I do need some points though as I've never done anything like this and AD is new to me as well.

What things am I missing that I should take in consideration?

Is my upgrade path correct? Maybe I'm missing that some arch are not compatible or not available

What are the minimum domain services I should have? As far as I know, barebones I have to have the PDC emulator, RID master, infrastructure master, schema master, and domain naming master. Once I hit Windows 2000, I think I should also enable a DHCP and DNS servers.

Not only will this take a while, but I also have to see how I can get and install all these operating systems!

there is no direct upgrade for windows server until windows server 2008 to 2012.

 

there is no direct upgrade for dos to the windows nt platform (windows 2000, windows xp, windows 7, windows 8, windows 10). 

 

I wish you the best of luck, but being that there are no direct upgrades you are pretty much on your own.

"should never be used in a real life scenario."

 

I don't know about you, but this is a real life scenario. 100% chance that there is a company out there somewhere that upgraded their server from 3.1 all the way up to 2012 R2, just not in 1 day, but a couple of years. This is a real life scenario, just in turbo speed.

  On 29/03/2015 at 20:18, sc302 said:

there is no direct upgrade for windows server until windows server 2008 to 2012.

 

there is no direct upgrade for dos to the windows nt platform (windows 2000, windows xp, windows 7, windows 8, windows 10). 

 

I wish you the best of luck, but being that there are no direct upgrades you are pretty much on your own.

I thought the same thing but I saw this article: http://support.microsoft.com/en-us/kb/298107 and I thought it applied.

Does that article only apply to terminal services?

  On 29/03/2015 at 20:37, Studio384 said:

"should never be used in a real life scenario."

 

I don't know about you, but this is a real life scenario. 100% chance that there is a company out there somewhere that upgraded their server from 3.1 all the way up to 2012 R2, just not in 1 day, but a couple of years. This is a real life scenario, just in turbo speed.

In a real life scenario, I think most companies in the situation you stated, would go from NT to a clean Windows Server install...
  On 29/03/2015 at 20:37, Studio384 said:

I don't know about you, but this is a real life scenario. 100% chance that there is a company out there somewhere that upgraded their server from 3.1 all the way up to 2012 R2, just not in 1 day, but a couple of years. This is a real life scenario, just in turbo speed.

In a real life scenario, I don't see 2012R2 running on a machine that's approximately 20 years old from the Windows for Workgroups 3.1 era, where the minimum requirements were what, a 386SX with 4MB memory?  Think NT 3.1 was an SX with 12MB? That's not a "couple of years" worth of upgrades, that's a couple of decades.

  On 29/03/2015 at 21:54, opo said:

I thought the same thing but I saw this article: http://support.microsoft.com/en-us/kb/298107 and I thought it applied. Does that article only apply to terminal services?In a real life scenario, I think most companies in the situation you stated, would go from NT to a clean Windows Server install...

The article states you have to perform a full install if the os doesn't support upgrade. I don't remember any server os having the ability to upgrade..god knows I have tried.

I'd just start at Windows 2000 - I did an NT4 to AD migration every few months at my old job years back, you just migrate objects (build a new forest\setup a trust\move objects to new forest).

 

It isn't very exciting lol, I don't miss LAN\User Manager, or batch login scripts.

  • 2 weeks later...
  • 2 months later...
  On 29/03/2015 at 22:02, Max Norris said:

In a real life scenario, I don't see 2012R2 running on a machine that's approximately 20 years old from the Windows for Workgroups 3.1 era, where the minimum requirements were what, a 386SX with 4MB memory?  Think NT 3.1 was an SX with 12MB? That's not a "couple of years" worth of upgrades, that's a couple of decades.

 

Idea is this company like Bank of America (just an example here) probably had a 1994 era domain controller on a dual core 486 with no active director. Upgraded to NT 4.0 in 1998 merged with a smaller bank in 2000 with Windows 2000 with their own ad. Upgraded to 2003 with forests and bought another company with another 2003 forest with a 2000 era AD ... etc.

 

Long story have a freaking huge global catalog. No biggie

  • 2 months later...

LOL! This was a stupid idea. You do realise that you usually migrate to new servers, than upgrade an existing one. 

Not once have I ever ran an in place upgrade on a domain controller, always built new servers and promoted them to DCs, let replication happen, move FSMO roles, rah rah, decommission old boxes. 

Edited by Jared-
  On 29/03/2015 at 20:37, Studio384 said:

"should never be used in a real life scenario."

 

I don't know about you, but this is a real life scenario. 100% chance that there is a company out there somewhere that upgraded their server from 3.1 all the way up to 2012 R2, just not in 1 day, but a couple of years. This is a real life scenario, just in turbo speed.

 

No, it's not... 20 year old hardware doesn't run Server 2012 R2. AD didn't exist till Server 2000.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • WinToUSB 9.9 by Razvan Serea WinToUSB allows you to install and run a fully-functional Windows on external hard drive, USB flash drive or Thunderbolt drive. It is so easy and efficient, with just 3 steps and a few minutes, you can create your first portable Windows 11/10/8/7 or Windows Server directly from an ISO, WIM, ESD, SWM, VHD, VHDX file or CD/DVD drive, or you can clone currently running Windows installation to USB or Thunderbolt drive as portable Windows. WinToUSB also supports creating Windows installation USB drive from Windows 11/10/8/7 and Windows Server installation ISO, with it you can install Windows from the USB drive easily. Note: The WinToUSB Free Edition is solely intended for non-commercial, private, and personal use on home computers. It should be noted that technical support is not available for the free edition. Use of WinToUSB Free Edition within any organization or for commercial purpose is strictly prohibited. WinToUSB key features include: Creation of Windows To Go from ISO, WIM, ESD, SWM, VHD(X) or DVD drive.Improved Clone Windows 11/10/8/7 to USB/Thunderbolt drive as portable Windows. Creation of Windows To Go on Non-Certified Windows To Go USB drive. Encrypt Windows To Go with BitLocker to keep your data safe. Creation of Windows installation and bootable WinPE USB drive with BIOS & UEFI support. Download Official Windows 11/10/8.1 ISO file from Microsoft. Use any edition of Windows 11/10/8/7 and Windows Server 2022/2019/2016/2012/2010 to create Windows To Go USB drive. Windows To Go (Portable Windows) Creator WinToUSB allows you to install & run fully-functional Windows on an external HDD/SSD, USB flash drive or Thunderbolt drive, which means you can carry the portable Windows drive to anywhere and use it on any computer. Faster installation and cloning speed compared to competing products Support any edition of Windows 11/10/8/7 and Windows Server Creation of Windows To Go from ISO, WIM, ESD, SWM, VHD(X) or CD/DVD drive Clone currently running Windows to USB/Thunderbolt drive Creation of Windows To Go on Non-Certified Windows To Go drive Create BitLocker encrypted Windows To Go Workspace Create portable Windows for Intel-based Mac computers Support for creating VHD(X)-based Windows To Go Windows Installation USB Creator WinToUSB releases a feature called "Windows Installation USB Creator" which allows you to create a Windows installation USB drive from a Windows 11/10/8/7/vista/2022/2019/2016/2012/2008 installation ISO file with a few simple steps, with this feature you can create a bootable Windows installation USB drive to install Windows on both Traditional BIOS and UEFI computers by using the same USB drive. Bypass Windows 11 system requirements (TPM 2.0, Secure Boot, Minimum hardware and Microsoft account) Install Windows on both BIOS and UEFI computers by using the same USB drive Windows PE Bootable USB Creator This feature allows you to create a bootable Windows PE USB drive, it can help you transfer the contents of a Windows PE ISO file to a USB drive and make the USB drive bootable, and this feature supports the creation of a bootable WinPE USB driver that supports both Traditional BIOS and UEFI computers. WinToUSB 9.9 changelog: Added option to disable BitLocker automatic drive encryption when creating Windows installation USBs Fixed bug: setup.exe cannot bypass the Windows 11 system requirements Fixed bug: Cloned Windows ARM64 cannot start properly Fix other minor bugs Download: WinToUSB 9.9.0 | 28.7 MB (Freeware) Links: Home Page | Free vs Pro Comparison | Screnshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Maybe you don't realize this...but everything you said agreed with me. Yes, many tech outlets reported on Ryzen 9000 issues prior to 24H2, which I already addressed, and as I already said, that issue only existed for a few short months. Ryzen 9000 was released the same quarter of 2024 as 24H2. So again...months, not years. I also already said 24H2 showed some minor improvements on older Ryzen CPU. The article you posted agrees with me, and even says the improvements were only 3-5%, which is even more harsh a statement than what I said. If you want to fuss on the 3-5% numbers, then yes, I will grant you that was an issue for an extended amount of time. In my opinion, that is such a small amount it isn't worth fussing over, but you are welcome to a different option. However, if that was your point, then you didn't make that point in good faith, because you highlighted Ryzen 9000 so much, which had a FAR bigger and FAR shorter issue, it's really a very different conversation.
    • The vast majority of users do not care which iOS version they're using. They don't even know or bother updating to the latest version, unless they see the prompt. The version numbers is more for the power users and I don't think Apple renamed their OS for them.
    • No operating system works well with programs that modify its interface. There will always be bugs, whether it's MacOS or Linux. Windows too, you'll only suffer from bugs using this crap software.
  • Recent Achievements

    • Week One Done
      abortretryfail earned a badge
      Week One Done
    • First Post
      Mr bot earned a badge
      First Post
    • First Post
      Bkl211 earned a badge
      First Post
    • One Year In
      Mido gaber earned a badge
      One Year In
    • One Year In
      Vladimir Migunov earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      snowy owl
      251
    3. 3
      +FloatingFatMan
      251
    4. 4
      ATLien_0
      228
    5. 5
      +Edouard
      191
  • Tell a friend

    Love Neowin? Tell a friend!