Month: September 2022

How to In-Place Upgrade Windows Server 2016 to Windows Server 2019 ?

Yusuf Ustundag 4 Comments

What is the in-place upgrade?
In the simplest terms, it is the process of upgrading your Windows operating system without losing your data.

If you are going to do this on a physical server, it is useful to check the hardware compatibility first.
Hardware requirements for Windows Server

You can also see the version transitions of the operating systems in the table below.

If your server is located on a virtual platform, it is useful to take a snapshot/checkpoint before doing the in-place upgrade.

After connecting the “Windows Server 2019” .iso file to your server with the “Windows Server 2016” operating system, "setup.exe" should be run.

On the next screen, we are asked whether to install the updates. The recommended action here is to make updates, and we continue by ticking this option.

Select the windows version.

Select Accept to accept the terms of your licensing agreement

Attention! Since our preference is an in-place upgrade, we continue with the "Keep personal files and apps" option.

Depending on the size of your data, the in-place upgrade process may take an average of 30 minutes to 1 hour.

 

If you have a server with the "Windows Server 2012 R2" operating system, you can’t upgrade directly to “Windows Server 2019”.
You will upgrade  "Windows Server 2016" first, then you can upgrade to "Windows Server 2019".

 

Ps: Disable UAC before starting the in-place upgrade, then enable it again.

Have a nice day!

 

Basic Authentication Deprecation Reminder and Final Update in Exchange Online

Yusuf Ustundag 6 Comments

Starting October 1, Microsoft will begin to randomize tenants and disable basic authentication access for MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS), and Remote PowerShell.
As you know, SMTP AUTH will not be affected by the changes made.

On the day of the change, Microsoft will notify each tenant through the Service Status Dashboard.

Microsoft 365 Admin Center

If you’re not ready to make these changes, You can do a One-Time Re-Enablement one last time as decided by Microsoft.

For all the details; Basic Authentication Deprecation in Exchange Online – September 2022 Update

 

Have a nice day !

Exchange Server 2019 ECP/OWA Not Working

Yusuf Ustundag 2 Comments

Study this article if you can’t access Exchange Server 2019 ECP(Exchange Control Panel) or OWA(Outlook Web Access).

In your Exchange Server Infrastructure, if your ECP/OWA console doesn’t open and you encounter EventID:1309 in the Application Log, the root cause of the problem is the missing SharedWebConfig file.
You can see this in the “Application Virtual Path” – “Application Path” in Event ID 1309.

ECP Not Working

To resolve this issue follow these steps:

  • Access the server with the problem.
  • Generate the missing file:
    • Run cd %ExchangeInstallPath%\bin to change the current directory to the bin folder that’s under the Exchange installation path.
    • Use the DependentAssemblyGenerator.exe tool
    • If the file is missing from C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy, run the following command:
      • DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\FrontEnd\HttpProxy" -configFile "%ExchangeInstallPath%\FrontEnd\HttpProxy\SharedWebConfig.config"

 

  • IISReset

 

You can now access ECP!

P.S: If you encounter EventID:1309, carefully check its contents.
Because in the problem I mentioned above, the issue was related to the ECP.
EventID contents; “Application Virtual Path: /ecp” and “Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp“

If these contents are as follows;

  • Application Virtual Path: /owa
  • Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\

To resolve this issue follow these steps:

  • Access the server with the problem.
  • Generate the missing file:
    • Run cd %ExchangeInstallPath%\bin to change the current directory to the bin folder that’s under the Exchange installation path.
    • Use the DependentAssemblyGenerator.exe tool
    • If the file is missing from C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess, run the following command:
      • DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"
  • IISReset

 

You can now access OWA!

Have a nice day !