This topic explains about Upgrading AX 2012 by using Upgrade Analyzer Tool to Microsoft Dynamics 365 for the Finance and Operations. This Upgrade analyzer tool is run against an AX 2012 environment and identifies data that you should clean up in Microsoft Dynamics AX 2012 to help reduce the subscription cost for Finance and Operations. The Upgrade analyzer tool also suggests SQL configuration optimizations that can help speed up the AX F&O upgrade processes. Additionally, the Upgrade analyzer tool warns you if any features that you use in Dynamics AX 2012 are obsolete in Finance and Operations. The upgrade is currently supported from either Dynamics AX 2012 R2 or AX 2012 R3 only. Therefore, you can plan ways to replace those features.
Microsoft Dynamics Axapta 2012 implementations that are running some deprecated features cannot be upgraded to Finance and Operations. For example, the upgrade is not possible from systems that are using either virtual companies or data partitions. If you aren’t that much sure whether your system can be upgraded, run the Upgrade analyzer tool.
Upgrade analyzer gathers data from your Microsoft Dynamics AX 2012 environment as part of the regular System diagnostic service in Microsoft Dynamics Lifecycle Services (LCS). It provides the environment and set of regularly updated services that can support you manage the app lifecycle of your D365 for Finance and Operations implementations. For the overview of the System diagnostic service, and for data about how data is collected and pushed back into the cloud so that you can consume it through LCS, see System diagnostics (Microsoft Dynamics AX 2012).
To perform the Analyze activities before you purchase the Finance and Operations, you need to sign up for an LCS trial or partner project. This lets you to deploy your own Finance and Operations environments. It also provides you access to the tools in Microsoft Dynamics Lifecycle Services (LCS) that are used to evaluate your AX 2012 environment and your existing custom code.
You can see the results of the System diagnostic service in the Microsoft Power BI report in LCS. The report presents a list of tasks that you should complete in the Microsoft Dynamics AX 2012 environment.
The below illustration shows an overview of the procedure for using Upgrade analyzer.
The upgrade analyzer tool runs for AX F&O upgrade against your AX 2012 environment and identifies tasks that you should do to prepare the AX 2012 environment, to help make the AX F&O upgrade experience smoother and less expensive:
- Data cleanup – This process supports you identify data that you can remove without causing loss of functionality. The tool identifies various types of information that you can reduce by running a cleanup process. For each type of information, an explanation is given about the impact of the cleanup. You decide then whether to run the cleanup process. Therefore, by reducing the size, you reduce that component of the subscription cost and also help reduce the time that is required for the AX F&O upgrade go-live process. A smaller database helps guarantee a faster AX F&O upgrade.
- SQL configuration – This process will review the SQL configuration and recommends optimizations. By making sure that the SQL performs optimally, this process supports to reduce the time that is required for the upgrade go-live process.
- Deprecated features – This process identifies features that you’re currently using, but that isn’t available in Finance and Operations. Therefore, the process supports you discover gaps in functionality early. It also provides suggestions for alternatives.
Additionally, as part of this step, you must install the pre-upgrade checklist in your Axapta 2012 environment. You can use this checklist to enter data that will be required for the AX F&O upgrade procedure. For example, in one pre-upgrade checklist task, you can provide the Microsoft Azure Active Directory sign-in data for each current Axapta 2012 user, so that each user will be able to sign in to the Finance and Operations.
- If upgrading from Axapta 2012 R3, install KB 4035163
- if upgrading from Axapta 2012 R2, install KB 4048614
The output of the upgrade analyzer tool becomes the workstream in the AX F&O upgrade project plan for your AX 2012 system administrators. Complete the tasks that the upgrade analyzer tool discovered, and that is documented in your AX F&O upgrade project plan. Your Microsoft Dynamics Axapta system administrator and the database administrator (DBA) must complete these tasks.
If you already use the System diagnostic service in your Microsoft Dynamics AX 2012 environment, you must configure a new instance of the service on a machine that differs from the existing machine.
In Microsoft Dynamics Lifecycle Services, System diagnostics add the on-premises component that must be installed before you can use the service to discover Dynamics Axapta environments and collect information.
To install the System diagnostics on-premises component, the below is required:
- A service account with specific permissions on the local computer and Microsoft Dynamics Axapta business database.
- An X509 certificate. You can either use the existing certificate or have the installer create one for you. Each of the X509 certificates is associated with a single project. Diagnostics from the environment can be uploaded to only one project.
- Microsoft .NET 4.5 or 4.5.1
On each of the server in your environment that hosts the AOS instance or Dynamics AX SQL Server business database, you must grant read access to a registry key in the HKEY_LOCAL_MACHINE hive to the service account for System diagnostics. You must make the services of an AOS remotely accessible in the Group Policy. The service account must be able to read the Windows event logs on each server in an environment and must be able to monitor the remote Windows Management Instrumentation connections. On each server in your environment that hosts an AOS instance or Microsoft Dynamics AX SQL Server business database, ensure that you secure the remote Windows Management Instrumentation (WMI) connection.
The service account must be able to read the information in the Dynamics AX business database and must have access to the default dynamic management views in SQL Server. The Business Connector service must be running on the host where Lifecycle Services Diagnostic Service is installed. If more than 1 environment is to be discovered, the Net Business Connector proxy account must be the same for each of the servers that is running the Dynamics AX Application Object Server (AOS) instance.
You can collect the information on demand from the Environment Discovery window. We recommend that you schedule the job to collect information regularly. Data collection takes between 5 and 15 minutes. Errors that are encountered during data collection are logged in the Windows Application event log, as well as in a log file in the location that you specified during installation.
Within a few minutes, after you configure the System diagnostic service, the Axapta 2012 environment will appear in your LCS project.