Technical Upgrade MSDYN365 On-premise v14 to v15 (Release 2019 Wave 2)

Technical Upgrade MSDYN365 On-premise v14 to v15 (Release 2019 Wave 2)

SCENARIO: “Convert a database and Technical Upgrade from v14 to v15 Release 2019 Wave 2”

NOTE: after the installation on the server of the new release of BC, for the first time, two historical components of Dynamics NAV and Business Central will be missing: “Development Environment” and “Windows Client”. Some operations done with the Development Environment will have to be done via Powershell or Admin Console.

Technical Upgrade to Dynamics 365 Business Central 2019 Wave 2

“Use this scenario if you have a Business Central Spring 2019 (referred to as version 14) application that does not include any code customization. Your solution might include Microsoft (1st party) extensions and custom extensions (3rd party). With this upgrade, you will replace the C/AL base application with the new Business Central 2019 release wave 2 base application extension. The result will be a fully upgraded Business Central 2019 release wave 2 (referred to as version 15) application and platform.”

Microsoft Link about “Technical Upgrade”

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-technical-upgrade-v14-v15

Remember!

• “NO MORE” Development Environment

• “NO MORE” Windows Client!

Technical Upgrade Document

The document above (on link) explains step by step how to do it, I report only the original Microsoft link, All is very clear.

Since, as already mentioned, two historical components have disappeared, I wanted to point out some things that previously could have been done also by the Development Environment and that can now be done only through commands.

COMPONENTS FOR A TECHNICAL UPGRADE TO V15 SCENARIO

You only need to achieve this type of upgrade: DATABASE SERVER, POWERSHELL, NAV SERVER, BROWSER (or Power APP), LICENSE

DATABASE: SQL SERVER\POWERSHELL

SERVER: BUSINESS CENTRAL SERVER

WEB CLIENT: BROWSERS

LICENSE: a License File “.FLF File”

TIPS FOR SOME STEPS

(In MANUAL mode from Consoles or from POWERSHELL, ADMIN CONSOLE)

• RESTORE DATABASE (OR CREATE A NEW ONE)
• CREATE A NEW BUSINESS CENTRAL SERVER
• UPGRADE DATABASE (TECHNICAL UPGRADE)
• UPLOAD THE LICENSE (CUSTOMER LICENSE)
• CREATE A NEW WEB CLIENT

“HOW-TO” RESTORE A DATABASE

Manual way

Via Powershell script

Delete BAD users (if you come from another domain etc.)

Example

“HOW-TO” CREATE A NEW DATABASE

Use NAV-NAVApplicationDatabase 

New-NAVApplicationDatabase –DatabaseServer YOURSERVER –DatabaseName DATABASE_NAME -DatabaseLocation YOUR_DB_FILES_LOCATION_PATH

“HOW-TO” TO CONVERT YOUR DATABASE TO v15 FORMAT

Use Admin Shell to Convert Database in v15 format

Invoke-NAVApplicationDatabaseConversion –DatabaseName DATABASE_NAME –DatabaseServer YOURSERVER

ERRORS in Old Database? Some message during conversion?

• Check your Old version database
• Launch Syncro
• Check Start-NAVDataUpgrade – (something can be pending…)
• Check Database version…

Example of errors Minimal version for database application

Or errors on..

..Or open Development Environment for V14 and Launch Sync from here or from powershell

However, at the end… Conversion is DONE!

Check versione on SQL Server, version “15.0.36649.0”

Check for $systemID in tables

“HOW-TO” CREATE A NEW BUSINESS CENTRAL SERVER

Manual way (console)

Create a New Server via Powershell Script

Import-Module ‘C:\Program Files\Microsoft Dynamics 365 Business Central\150\Service\NavAdminTool.ps1’

New-NAVServerInstance -ManagementServicesPort 8401 -ServerInstance BCITA-V15 -ClientServicesCredentialType Windows -ClientServicesPort 8402 -DeveloperServicesPort 8403 -ODataServicesPort 8404 -SOAPServicesPort 8405

Start Service

Manual way or by cmd

• Start-NAVServerInstance –ServerInstance BCITA-V15

SERVER IS RUNNING! DONE!

“HOW-TO” UPLOAD CUSTOMER LICENSE (or another license, ex Development)

Remember: No more: Tool|License Information|Change\Upload

Import-NAVServerLicense ‘NAVSERVER’ –LicenseData ([Byte[]]$(Get-Content -Path “c:\YourLicenseFolder\CustomerLicenseFile.flf” -Encoding Byte))

Example

Import-NAVServerLicense ‘BC15W2TEST’ -LicenseData ([Byte[]]$(Get-Content -Path “c:\Licenza\BC_5318216.flf” -Encoding Byte))

DONE, Restart BC Server!

“HOW-TO” CREATE PERMISSIONS TO LOGIN

Create User, assign permission set USER

import-module “C:\Program Files\Microsoft Dynamics NAV\90\Service\NavAdminTool.ps1”

Create user (domain user in this case)

New-NAVServerUser ServiceInstanceName –WindowsAccount DOMAIN\UserName

Assign a SUPER PermissionSet

New-NAVServerUserPermissionSet ServiceInstanceName -WindowsAccount DOMAIN\UserName -PermissionSetId SUPER

“How-to” add your currently logged on Windows user

New-NAVServerUser ServiceInstanceName -WindowsAccount $(whoami)

New-NAVServerUserPermissionSet ServiceInstanceName -WindowsAccount $(whoami) -PermissionSetId SUPER

“HOW-TO” CREATE A NEW WEB ISTANCE

You can create a new web instance using the already available script NAVAdminTools.ps1 in “Microsoft Dynamics 365 Business Central\150\Service\” folder.

Import-Module ‘C:\Program Files\Microsoft Dynamics 365 Business Central\150\Service\NavAdminTool.ps1’

Example

New-NAVWebServerInstance –Server localhost –ServerInstance BCT0150WAVE2 –WebServerInstance BCT0150WAVE2 –AddFirewallException -ClientServicesCredentialType Windows -ClientServicesPort 15061 -ManagementServicesPort 15062 -SiteDeploymentType SubSite

THE NEW WEB SITE IS RUNNING!

HOW-TO UPGRADE TO MICROSOFT AL BASE APP

C/AL objects are no longer available, so you need to convert old C/AL objects to a new Microsoft AL BaseApp.

Run Cmdlet Sync-NAVApp -Mode BaseAppUpgrade , this cmdlet renames tables conforming to Microsoft AL Language naming convention. This cmdlet  rename tables adding the Microsoft AL extension’s AppID as a part of table names.

BUSINESS CENTRAL IS READY!

DONE!