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

    • misleading its one word to describe what M$ have done, windows 10 perform better on older hardware and even on new hardware sometimes, windows 11 its a mess and no one want to use it for many good reasons, until they listen its customers read the feedback hub comments and maybe backoff its forced requiremens, they are having a vista and 8 moment.
    • Media Player Classic - Home Cinema 2.5.0 by Razvan Serea Media Player Classic - Home Cinema (MPC-HC) is a free and open-source video and audio player for Windows. MPC-HC is based on the original Guliverkli project (which is no longer maintained) and contains many additional features and bug fixes. As the continuation of the original Media Player Classic, MPC-HC isn’t flashy but it works with nearly any media format. MPC-HC uses DXVA technology to pass decoding operations to your modern video card, enhancing your viewing experience. And MPC-HC supports both physical and software DVDs with menus, chapter navigation, and subtitles. Overview of features A lot of people seem to be unaware of some of the awesome features that have been added to MPC-HC in the past years. Here is a list of useful options and features that everyone should know about: Dark interface Menu > View > Dark Theme When using dark theme it is also possible to change the height of the seekbar and size of the toolbar buttons. Options > Advanced Video preview on the seekbar Options > Tweaks > Show preview on seek bar Adjust playback speed Menu > Play > Playback rate The buttons in the player that control playback rate take a 2x step by default. This can be customized to smaller values (like 10%): Options > Playback > Speed step Adjusting playback speed works best with the internal audio renderer. This also has automatic pitch correction. Options > Playback > Output > Audio Renderer MPC-HC can remember playback position, so you can resume from that point later Options > Player > History You can quickly seek through a video with Ctrl + Mouse Scrollwheel. You can jump to next/previous file in a folder by pressing PageUp/PageDown. You can perform automatic actions at end of file. For example to go to next file or close player. Options > Playback > After Playback (permanent setting) Menu > Play > After Playback (for current file only) A-B repeat - You can loop a segment of a video. Press [ and ] to set start and stop markers. You can rotate/flip/mirror/stretch/zoom the video Menu > View > Pan&Scan This is also easily done with hotkeys (see below). There are lots of keyboard hotkeys and mouse actions to control the player. They can be customized as well. Options > Player > Keys Tip: there is a search box above the table. You can stream videos directly from Youtube and many other video websites You can stream videos directly from Youtube and many other video websites Put yt-dlp.exe or youtube-dl.exe in the MPC-HC installation folder. Then you can open website URLs in the player: Menu > File > Open File/URL You can even download those videos: Menu > File > Save a copy Tip: to be able to download in best quality with yt-dlp/youtube-dl, it is recommended to also put ffmpeg.exe in the MPC-HC folder. Several YDL configuration options are found here: Options > Advanced This includes an option to specify the location of the .exe in case you don't want to put it in MPC-HC folder. Play HDR video This requires using madVR or MPC Video Renderer. After installation these renderers can be selected here: Options > Playback > Output Ability to search for and download subtitles, either automatically or manually (press D): Options > Subtitles > Misc Besides all these (new) features, there have also been many bugfixes and internal improvements in the player in the past years that give better performance and stability. It also has updated internal codecs. Support was added for CUE sheets, WebVTT subtitles, etc. Media Player Classic - Home Cinema 2.5.0 changelog: Updated LAV Filters to version 0.80-1-gb9116 Updated MPC Video Renderer to version 0.9.9.2400 Several small fixes and improvements. Graphics Designers Wanted for New Toolbar Buttons A new toolbar is planned for implementation in the player, featuring optional extra buttons and fully customizable layouts. As a result, existing custom toolbar designs will no longer be supported in the future. New button designs are needed, and contributions from graphics designers are welcome. Those interested in helping create the new toolbar are encouraged to read the dedicated information page. Download: MPC-HC 2.5.0 (x64) | Standalone | ~20.0 MB (Open Source) Download: MPC-HC 2.5.0 (x86) | Standalone Links: MPC-HC Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Then don't put it on an IoT VLAN but put it on your main, trusted, VLAN. If you put it on a different VLAN you lose printer discovery.
    • For me it isn't usable because I'm a power user. I need Wayland but I also need remote desktop. VNC isn't a thing with Wayland and freeRDP isn't nearly ready enough yet either. If I was less demanding (didn't need remote desktop or ran Xorg) I would probably be fine.
    • From Microsoft to RedHat, escape an American company for an American company, that would be funny
  • Recent Achievements

    • Week One Done
      emptyother earned a badge
      Week One Done
    • Week One Done
      DarkWun earned a badge
      Week One Done
    • Very Popular
      valkyr09 earned a badge
      Very Popular
    • Week One Done
      suprememobiles earned a badge
      Week One Done
    • Week One Done
      Marites earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      571
    2. 2
      ATLien_0
      183
    3. 3
      +FloatingFatMan
      173
    4. 4
      Xenon
      124
    5. 5
      Michael Scrip
      117
  • Tell a friend

    Love Neowin? Tell a friend!