Sql Server 2008 R2 To 2016 Upgrade

[Analisa Wack]

Theprocess of upgrading to a newer version of Windows Server can vary greatly, depending on whichoperating system you are starting with and the pathway you take. We use the following terms todistinguish between different actions, any of which could be involved in a new Windows Serverdeployment.

Upgrade. Also known as an "in-place upgrade". You move from an older version of the operatingsystem to a newer version, while staying on the same physical hardware. This is the method wewill be covering in this section.

In-place upgrades might also be supported by public or private cloud companies; however, youmust check with your cloud provider for the details. Additionally, you'll be unable to performan in-place upgrade on any Windows Server configured to Boot from VHD. An in-place upgradefrom Windows Storage Server Editions is not supported. You can perform either a Migrationor Installation instead.

Cluster OS Rolling Upgrade. You upgrade the operating system of your cluster nodes withoutstopping the Hyper-V or the Scale-Out File Server workloads. This feature allows you to avoiddowntime which could impact Service Level Agreements. For more information, seeCluster OS Rolling Upgrade

License conversion. Convert a particular edition of the release to another edition of the samerelease in a single step with a simple command and the appropriate license key. We call this"license conversion". For example, if your server is running Standard edition, you can convert itto Datacenter.

With Windows Server 2022 and earlier, you can upgrade to a newer version of Windows Server by upto two versions at a time. For example, Windows Server 2016 can be upgraded to Windows Server 2019or Windows Server 2022. If you are using theCluster OS Rolling Upgrade featureyou can only one version at at time.

You can also upgrade from an evaluation version of the operating system to a retail version, from anolder retail version to a newer version, or, in some cases, from a volume-licensed edition of theoperating system to an ordinary retail edition. For more information about upgrade options otherthan in-place upgrade, seeUpgrade and conversion options for Windows Server.

Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.

Support for Windows Server 2008 andWindows Server 2008 R2 has ended. We recommend youupdate your version of Windows Server to a more recent version as soon as possible. Learn moreabout Extended Security Updates (ESU) as a last resort.

We upgraded our GIS Enterprise from 10.9 to 11.0. We have a single site install with Portal on the same ArcGIS Server. The portal and web adaptor upgrades went well. However, after installing the ArcGIS Server upgrade to 11.0, when presented with the server manager page to finish the install, an error occurred after continuing.

I have a case open and was told they have seen this error and are waiting for an 11.1 patch. What?? We looked at logs and ensured permissions on folders for the Windows Server service account. No luck. Maybe somebody has some ideas. Thanks.

I have two cases open for the same issue. I am beyond frustrated as we have been down for two weeks because of the failure to complete the ArcGIS Server 10.9 to 11.0 update. Below are the case #s. It may be I have to uninstall and reinstall ArcGIS Server. I usually create a snapshot on the VM, but not this time. I did perform a full backup using the webgisdr tool for our ArcGIS Datastore, Portal for ArcGIS, and ArcGIS Servers.

Unfortunately, after two weeks of being down, we decided to revert to 10.9. We run VMs, and I did not take a snapshot but did create a full webgisdr backup of our data store, portal, and server. Without the VM snapshot, we had to uninstall the server and reinstall, followed by the portal and reinstall (I did not update the data store to 11.0 because we did not get that far). This was a hot mess! Next time, I will take snapshots as I usually do (much easier to go back).

This just happened to me going from 10.9.1 to 11 on a multi machine site with a separate image server. Had the issue on the first server in the multi machine site as well as image server. I was able to revert back to a snap shot on all machines luckily. The weird thing is that we have a mirrored site for DR that i tested the v11 upgrade on and it had no issues whatsoever so not sure why this would occur on just the production side. Any updates?

I need to upgrade my Alteryx server and designer. And in order to do so, I have the Alteryx documentation with me, but if someone already had done server upgrade and maintained a TO-DO list/task , will be of great help as I don't want to miss any step.

Can you please assist , if we just need to upgrade to Alteryx Admin designer new version , as we do not have any server with us , just an Alteryx Admin designer license. What are the steps involved, do we require any backup or not in this case .

In the case of upgrading only Alteryx Designer, you do not need to make any backups, just install the new version.

If you want to be conservative, and if you have python or R packages installed, it would be worth making a list with what packages you have and after the upgrade install them again.

If you want to have two versions, one more current and another version, in your case, you would need to download NON-ADMIN, as @JosephSerpis said in the other post you will have two versions installed at the same time on the machine.

No, your license key will only work on a single machine, in the case of two versions on the same machine as mentioned above the license will work on both (they are on the same machine). If the installations are on separate machines (dev and prod environments) you will need two licenses, one for each machine.

Doing some searches on the web, it's not clear if there is an upgrade path from 2012R2 to 2022 Windows Server. From the link, I was wondering if there is an upgraded diagram, or if Microsoft has a recommendation on the path forward for this route? Is this upgrade not supported, and we should opt to then do a clean install?

@Harm_Veenstra I appreciate the responses. My concern is that is there a official recommendation from Microsoft? Does Microsoft 'standby' that this upgrade path should work, or what I'm reading from other responses is that, it's better to do a clean install, or perform both routes just in case...

Actually migrating to Windows 11 needs much planning and considerations due to heavy changes to the underlying hardware security stack (TPM 2.0, UEFI, Secure Boot, VBS etc.).

Same is true for Windows Server 2022.

Just because it "works" doesn't mean it is properly configured, secured and optimized.

You certainly doesn't want your brand new Windows Server 2022 relying BIOS/MBR model by example.

This is very difficult to do when the DC has hundreds of users and computers and other roles running, especially when you are a new sys admin with no connection to the prior sys admin of anything else the DC vm may be doing that is critical that you can't migrate by doing a fresh install.

@Chrisntpsfor new domain controllers it's better just to spin up a new server 2022 and join it to the domain then make it a domain controller (DNS Server) I've removed all other roles from my domain controllers such as (DHCP, CERT, KMS, other roles) this way it's easier to upgrade domain controllers by adding a new DC already running the latest OS. if you haven't move the roles out of your DC I recommend you to first work on moving DHCP, KMS, Certificate of Authority or any roles you may be running on that DC aside from (DNS only) this role must stay in the DC imho.

@cespiritu @Zach_B635 it depends on the workloads and antivirus apps.

If this is a correctly setup server like "no Domain Controller + Certificate Authority at the same Server or VM it is a simple as

Pardon me, I wasn't aware at the time of writing I am necroing a thread from 2021, yet as the topic is still hot and the guidance given can be used universally now, allow me to add the last one from my end.

The iiq upgrade command creates a local log file which should be in your Tomcat 9.0\webapps\identityiq\WEB-INF\bin folder. Also, the issue appears to be a TLS negotiation error trying to connect to your DB from the host - most likely a certificate issue.

found the file for the logs, looks to be the same as command prompt errors so nothing extra. I will keep reviewing my cert items and see if I can get someone internal to validate it looks right to them.

Ideally you want to actually fix the TLS issue as you really should have the connection between IIQ and the IIQ DB encrypted, but your update of disabling TLS via the iiq.properties file will suffice as a hot-fix since that does seem to work.

Note that many production DBs have policies set to require all traffic to be encrypted, so there was a chance simply changing the iiq.properties JDBC connection string to ignore encryption might not have worked.

The 1253 is a line number reference in the sailpoint.server.upgrade.Upgrader class. This is in the core IIQ code, presumably this portion is opening a JDBC connection pool to the DB so that the upgrader can modify IIQ config/objects in the database.

Finally, yes - all your searching on that error actually did return the correct answer in that the issue is cert-related (see above). Your work-around was disabling TLS encryption (which takes certs out of the picture), but you will see that same error again most likely - especially when trying to enable TLS for AD/LDAP and public web services like Salesforce if your IIQ goes through a proxy server to reach the public internet.

We have a lot of our workflows scheduled, and what we noticed was that post-upgrade our workflows were running one hour earlier than they are scheduled. There is a discrepancy between what the Gallery UI shows as the scheduled time (when the workflow should run) and when the workflow actually runs.

We suspect it has something to do with DST, but there was no issue with our schedules earlier this week after clocks moved an hour back over the past weekend up until the Server Upgrade.

3a8082e126