How to In-Place Upgrade Windows Server 2008 R2 to Windows Server 2019
As you know the Windows Server 2008 and Windows Server 2008 R2 are out of support on January 14th, 2020. Customer will need to upgrade their Windows Server 2008 and Windows Server 2008 R2 to a newer version of Windows Server or migrate these servers to Microsoft Azure.Ignite 2024: Are you ready for Office 2016/2019 end of support?
At this year’s Ignite conference, I had the pleasure of teaming up with Microsoft 365 deployment expert Eric Wayne to dig into the details of how to prepare your organization for the end of support for Office 2016, Office 2019, and their related servers and standalone apps, coming up on October 14, 2025. Missed Ignite? Watch the full session recording to help kickstart your upgrade today. You will learn: The best upgrade paths for Office suites, servers, and standalones facing end of support, How to identify and remove older versions of Office and make a smooth transition to Microsoft 365, and Where to turn if you need more help. October 2025 is just around the corner, and now is the time to act. If your organization is still using 2016 or 2019 versions of Office, Exchange Server, Skype for Business Server, Project, or Visio, now is the time to start your migration to a supported solution. Starting your move to Microsoft 365 as soon as possible will help keep your organization secure, compliant, and productive through 2025 and beyond. Over the coming months, we’ll continue to provide additional resources and guidance to help you and your organization smoothly navigate next year’s end of support milestones. After you’ve watched the Ignite session, here are a few great places to go next: Prepare your organization for October 2025 end of support events (Microsoft Ignite Learning Collection) Products reaching end of support on October 14, 2025 (Microsoft Lifecycle site) Plan an upgrade from older versions of Office to Microsoft 365 Apps (Microsoft Learn) Need more personalized guidance? Consider requesting migration assistance from FastTrack, reach out to your Microsoft account team, or fill out this form to get in touch with sales and have a specialist demonstrate how Microsoft 365 can benefit your organization.
SQL Server 2019 SKU Upgrade for Entra
I am looking to upgrade our 2019 instance to 2022 with in place upgrade. The database and server was created using a Template in Azure for "SQL Server Standard 2019 on Windows Server 2022". We would like to enable Entra Authentication. Currently the SQL Server Virtual Machine, Security Blade in Azure says: "Microsoft Entra authentication is not available for SQL virtual machine offer SQL2019 and sku Standard. Microsoft Entra authentication is available starting SQL Server 2022." Does anyone know if I upgrade in place will the option be available or will I have to build a new machine?
Failed to upgrade Windows Server 2016 to Windows Server 2019
I have an issue when I try to do an in-place upgrade from Windows Server 2016 to Windows Server 2019. Installation keep fails at 5% The server is Domain joined I used Local admin & Domain admin same error According to Upgrade logs i found these errors: PidGenX function failed on this product key. (hr = 0x8a010001) ProductKey: Failed to report Host OS channel to telemetry ERROR,OrphanFileFinder::GetEvidence,98,onecore\base\appcompat\inventory\software\inv\lib\file.cpp(1881)\AEINV.dll!00007FFD2AC46D01 DoExecute: Cannot extract file \Windows\System32\Recovery\winre.wim from C:$WINDOWS.~BT\Sources\Install.wim. Error 0x80070522[gle=0x00000522] ExecuteOperations: Failed execution phase Downlevel. Error: 0x80070522 ExecuteCurrentOperations reported failure! Using action error code: [0x80070522] CDlpActionImageDeploy::ExecuteRoutine(487): Result = 0x80070522 ExecuteInstallMode(883): Result = 0x80070522 ExecuteDownlevelMode(390): Result = 0x80070522Key End of Support dates for Office 2016, 2019 Apps & Productivity Servers
Important Notice for Users of Office 2016 and 2019: As we approach the end of support date on October 14, 2025, it is critical for businesses to consider upgrading to Microsoft 365 to maintain security, management, and productivity standards. For those with specialized requirements, Office LTSC and Exchange Server remain available. We encourage utilizing Microsoft's upgrade resources to ensure a smooth transition to ongoing support. Prompt action is recommended.
Problems after upgrade to CU14
Hi, I'm in the process of migrating from Exchange 2013 CU23 to Exchange 2019. I installed Exchange 2019 CU13 on Win2022 Server, in coexistence with our 2013 and everything was looking good. Before starting with the testing to route emails through 2019, I checked that CU14 was released recently, so I download/install the CU14 in upgrade mode (with the no EP flag) to have the last build, and now I'm having problems with virtual directories, mailboxes, and so ON. Already run the healtchecker powershell scripts and nothing out of the ordinary. Some of the problems I'm having: 1. When I clic on the 'authentication' tab in any Virtual Directory (ECP, OWA, EWS) I got this error: "The task wasn't able to connect to IIS on the server <FQDN>. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable." The other tabs don't throw me any errors, but almost all options are greyed-out. 2. In SERVERS > DATABASES, when entering the properties of any Database that are on the new EX2019, I got this error: 'Exchange can't connect to the Information Store service on server <FQDN>. Make sure that the service is running and that there is network connectivity to the server.' I cannot create a new Database neither and the status of the currents 2019 Mailbox databases says Uknown and BadCopyCount = 1. 3. SERVERS > CERTIFICATES: Cannot see any Cert here for the EX2019. The error I get: "Cannot connect to the remote procedure call service on the server named <servername>. Verify that a valid computer name was used and the Microsoft Exchange Service Host service is started." Already check: - Binding of the Certificate 'Microsoft Exchange 'on the BackEnd and our Public Certificate on the Frontend Server. - All Exchange Services are up and running. - Restart of IIS. It appears that is something with permissions and/or with IIS that breakdown after the installation, but still don't know what it is. Al things related to the 2013 environment appears to be normal and functioning. according. Something I noticed, on the Certificate error it says the name of the server, and in the other errors, it says the FQDN of the server. Please guide me here, what could be the problem and what to check/confirm. Thanks in advance.Upgrade from Exchange 2013 CU23 to Exchange 2019 CU14
Hi all, I'm in the process of upgrading or Exchange infrastructure from 2013 CU23 (Hybrid) to 2019 CU 14. A really long time without making Exchange Upgrades... so just want to confirm some things. Doing just the initial Setup/installing of Exchange Server 2019 on our AD does not break anything with the current Exchange 2013 config and connections from users right? to that point there are no changes for the users and it's safe? just confirming. I'm using the 'Exchange Deployment Assistant' for this upgrade, and I assume that installing exchange 2019 doesn't brake anything of the current config because everything will still be pointing out to EX2013 until I change it, but want to make sure. Any additional tips, is welcomed for the upgrade process. Thanks in advance.
E3 to E5 EEA upgrade
Hi team, If a customer has en E3 subscription purchased before October 1st, and then decides to make a partial upgrade to regular E5 after October 1st, is this possible? Or, will the customer need to make a partial upgrade to E5 EEA instead, and then buy Teams on the side? Br, NisImportant Office end of support reminders
Urgent Action Required. If you have Office 2016/2019 clients connecting to Microsoft 365 services or if you are running Office for Mac 2019, you need to act now. Review the crucial end-of-support actions you need to take to keep your environment running smoothly!
