Обновление windows server 2003 до 2019

Posted by JasonMatt 2019-11-18T15:39:30Z

• I’d just leave it alone and block off access as much as you can, that version of Note is unlikely to cope with Server2019 anyway

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  You’d have to make a lot of stops along the way, probably 2003 > 2008 > 2012 > 2019.  And if 2003 is 32-bit, it’s a non-starter.  I’d isolate it and nuke the others.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• What data have you got there? Can it be migrated to other systems? Is it still being used?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• You have no idea if Lotus Notes gets botched if you try.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Why not test it? This is the real helpfulness of having VMs. Take snapshots. Make copies to another test environment. Rollback if something goes wrong?

  This is too specific of a one-off issue. So, you need to do your due diligence and test, test, test.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Does the version of Notes even support running on a new OS? There may be issues with it running on newer Windows versions. There are a lot of changes between 2003 and even server 2008, let alone 2016 or 2019.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• If those VMs are running 2003 32-bit, Server 2008 is the highest you would be able to upgrade to because Microsoft phased out 32-bit server platforms after that.

  
  1 found this helpful
  thumb_up
  thumb_down
  

• I don’t have Lotus Notes, but we do use Lotus Approach.  I was able to successfully install and run Approach after some finagling on an RDS Server 2019 install (migrated from 2008R2).

  If you do decide to move the information, and reckon that Notes is similar enough to Approach, I would consider myself a minor expert on the application and can assist you as required.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Thanks so much for all the assistance!

  It looks like with the setup we have, I should be able to copy the Lotus Notes databases and access them from the clients without having to use the server, so that really helps!

  The other 2003 servers are only 32 bit so it looks like I will be building new servers and trying to get the old software to run on them.

  And like Fessor said, I will be testing my face off!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Burt0s

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  jalapeno

  Hi Jason

  We had a similar issue, but in our case the certificate expired (admin account credentials weren’t supplied before former IT user left) plus the server was on server 2003, so we couldn’t access any of the DB’S.

  So installed lotus notes on a new 2012 server than copied over the DB’S, we than access the data by double clicking the DB’S themselves and than get access to the data within. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• In my experience, looking at software that was made to run on Server 03 (especially if it was pre-server 2008), you will probably find that most any old software that was ever made to run on Windows Server of some variety works alright on Server 2019, although as everyone else has suggested, do your due diligence testing to be as certain as you can! The fundamental methodology of how Windows (Server and Desktop) run applications within the OS has not changed substantially since Server 2003/XP besides the addition of X64 support. There are of course more options supported over time, but Microsoft has overwhelmingly just added options to ways software can be run. Besides, most old programs are typically pretty simple/stupid, and don’t care what they are running on unless the developing organization was particularly greedy or the software was especially finicky to begin with (not that the software can’t be fooled, but tricking/hijacking old software into thinking it’s running on something it isn’t is where problems tend to arise in my experience). 

  I’m with the others that for Server 03, I would recommend just trying to build clean instances of the desired Server OS, and install applications rather than migrating unknown levels of garbage multiple times if possible. If you can just migrate the databases, so much the better! I’m all for migrating versus clean install and rebuilding where feasible.. but there is a legitimate architectural difference between Server 03, and everything after it. Even Server 2019 still fundamentally shares a LOT of the same basic guts with Server 08, so that upgrade is not remotely as disruptive as attempting to go from 03 to anything newer to be frank. Your major architectural changes are with Server 08 (Vista), and Server 2012 (Windows 8). The Windows 8/Server 2012 changes were predominantly at the very low levels of the OS, and how it interfaces with hardware, drivers, and services.. but the way programs run within the OS didn’t fundamentally change much between Server 08 and 2012 the same way that it didn’t really change between Windows Vista/7 and Windows 8/8.1. Server 2016 and 2019 are still fundamentally Windows 8 with a variety of new toys and features built in, but the core hasn’t really changed substantially, much as Windows 7 was literally Vista with some tweaks and no changes of any real substance (resulting in Server 08 with two revisions, since it really didn’t change substantially at all besides some tweaks). 

  So with all that background out of the way, I’m comfortable recommending that folks consider in-place upgrades from 08 to 2012, and 2012 to 2016/2019, but there’s just too much different between Server 03 and everything newer to expect a very consistent or reliable end result of upgrading versus just building new from scratch and migrating manually.

  
  Was this post helpful?
  thumb_up
  thumb_down