02-Ax 2012 Admin Wkshp-Installation and Configuration

Microsoft Dynamics AX 2012
Administration and
troubleshooting WorkshopPLUS
Chapter 2: Installation and Configuration
Student Lab Manual
Conditions and Terms of Use
Microsoft Confidential - For Internal Use Only
This training package is proprietary and confidential, and is intended only for uses described in the
training materials. Content and software is provided to you under a Non-Disclosure Agreement and
cannot be distributed. Copying or disclosing all or any portion of the content and/or software included
in such packages is strictly prohibited.
The contents of this package are for informational and training purposes only and are provided "as is"
without warranty of any kind, whether express or implied, including but not limited to the implied
warranties of merchantability, fitness for a particular purpose, and non-infringement.
Training package content, including URLs and other Internet Web site references, is subject to change
without notice. Because Microsoft must respond to changing market conditions, the content should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the
accuracy of any information presented after the date of publication. Unless otherwise noted, the
companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events
depicted herein are fictitious, and no association with any real company, organization, product, domain
name, e-mail address, logo, person, place, or event is intended or should be inferred.
© 2015 Microsoft Corporation. All rights reserved.

Copyright and Trademarks
© 2015 Microsoft Corporation. All rights reserved.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property
rights covering subject matter in this document. Except as expressly provided in written license
agreement from Microsoft, the furnishing of this document does not give you any license to these
patents, trademarks, copyrights, or other intellectual property.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights
under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
For more information, see Use of Microsoft Copyrighted Content at

http://www.microsoft.com/en-us/legal/intellectualproperty/Permissions/default.aspx
Active Directory, Bing, Microsoft, Microsoft Dynamics, SQL Server, Visual studio, Windows PowerShell,
Windows Server, and Windows are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries. Other Microsoft products mentioned herein may be either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries. All other trademarks are property of their respective owners.
© 2015 Microsoft Corporation

Microsoft Confidential
Contents
CHAPTER 2: INSTALLATION AND CONFIGURATION.................................................................................1
OBJECTIVES............................................................................................................................................ 1
INTRODUCTION........................................................................................................................................1
OVERVIEW..............................................................................................................................................2
Installation Types......................................................................................................................... 2
Servers in a Minimum Installation of Microsoft Dynamics AX......................................................3
Servers in a Complete Installation of Microsoft Dynamics AX.......................................................4
Other Servers in the Environment................................................................................................. 4
TROUBLESHOOTING..................................................................................................................................4
Install Preparation........................................................................................................................ 5
Install Microsoft Dynamics AX Databases..................................................................................... 9
Install AOS Server(s)................................................................................................................... 12
Install Clients.............................................................................................................................. 16
Initialization Checklist................................................................................................................. 19
Version Numbers........................................................................................................................ 25
Server and Client Configuration.................................................................................................. 25
MICROSOFT DYNAMICS AX 2012 SERVER CONFIGURATION..........................................................................26
Microsoft Dynamics AX 2012 Server Configuration Utility Settings.............................................27
AX 2012 Server Configuration Utility Settings: Best Practices.....................................................30
MICROSOFT DYNAMICS AX 2012 (CLIENT) CONFIGURATION.........................................................................32
Microsoft Dynamics AX 2012 (client) Configuration Utility Settings............................................33
Microsoft Dynamics AX 2012 (client) Configuration Utility Settings: Best Practices....................35
Registry or File............................................................................................................................ 36
SERVICE PACKS AND UPDATES..................................................................................................................38
Hotfixes...................................................................................................................................... 38

6 Installation and configuration
Cumulative Updates................................................................................................................... 39
Service Packs.............................................................................................................................. 39
Deployment Process for Updates................................................................................................ 39
Naming Convention for Update Packages..................................................................................39
Update Package Structure.......................................................................................................... 40
Process for Installing Updates.................................................................................................... 41
Install Updates to Database, AOS, and Clients...........................................................................43
TEST YOUR KNOWLEDGE.........................................................................................................................47
Installation and configuration 1
Chapter 2: Installation and Configuration
Objectives
The objectives are:
 Review the various installation types and servers required.
 Install the database, Application Object Server (AOS), and client.
 Complete the initialization checklist after installing
 Review how to check and interpret the build numbers.
 Review and use the client and server configuration utilities.
 Review the process for installing service packs and updates.
Introduction
Successfully installing Microsoft Dynamics AX requires more than running the Setup
program. It is important to complete all the required tasks to prepare the Microsoft
Dynamics AX environment, in addition to all post-installation tasks. A solid
installation is important to a successful implementation.
Scenario
Contoso is a mid-sized manufacturer of various audio products. Although their
customer base spans multiple countries, their target is mainly North America. They
plan to use much of the functionality within Microsoft Dynamics AX 2012 plus many
of the additional modules.
After a successful fiscal year, Contoso wants to broaden its market share by:
 Focusing their sales efforts on their best customers.
 Extending their product availability through an external website.
 Reducing their cost of sales through reduced production costs.

Challenge
The implementation consultant leading the implementation completed the needs
analysis, the necessary hardware and infrastructure is ready for the installation, and
Contoso is ready to start the installation of Microsoft Dynamics AX 2012.
Goal
The implementation consultant will install Microsoft Dynamics AX 2012 on Microsoft
Windows Server 2008 R2 with 25 clients. The implementation consultant must create
a database, AOS, and clients, each on their own computer.
Solution
The implementation consultant must follow these steps:
1. Start the Microsoft Dynamics AX 2012 Setup Wizard.
2. Complete the setup steps for each Microsoft Dynamics AX
components.
3. Use information that is collected from the planning steps to setup
the necessary information in the setup fields.
4. After finishing all the setup steps, make sure Microsoft Dynamics
AX will successfully start.
Overview
Installation Types
Two types of installation are available from the Setup wizard:
1. Custom installation.
5. Single-computer installation.
Custom installation
Select Custom installation to install specific Microsoft Dynamics AX components on
multiple computers. Use this type of installation in a production environment.
Single-computer installation
Select Single-computer installation to install a complete Microsoft Dynamics AX
system on one computer. Setup uses default settings to configure all components,
and new Microsoft Dynamics AX databases are created. User names and passwords
are the only input that is required. If you want to connect to an existing database or
specify other custom settings, you must perform a custom installation.
A single-computer installation includes the following components:
 Databases
 AOS
 Enterprise Portal
 Help server
 Reporting Services extensions
 Analysis Services configuration
 Client
 Microsoft Office add-ins
 Remote Desktop Services integration
 Debugger
 Visual Studio Tools
 Trace Parser
 .NET Business Connector
 Management utilities
Considerations for Installing Multiple Instances on One Computer

In a single set of servers you can install multiple instances of the Microsoft Dynamics
AX AOS and the database. You can install multiple instances of Microsoft Dynamics
AX components on separate computers, or on the same computer. The AOS
instances and databases cannot be shared among instances of Microsoft Dynamics
AX.
The primary use for multiple Microsoft Dynamics AX instances is in development
environments to support multiple phases of a project such as development, test, and
user acceptance testing.
Caution: It is not recommended or supported installing multiple versions of

Microsoft Dynamics AX components on the same computer in a production
environment.

The following table lists considerations when installing a second instance of a

component.
Component Considerations
AOS Each AOS instance is automatically assigned a number between 01
and 99. That number is displayed in the Programs and Features
control panel.
It is recommended that you create a group in Active Directory to
manage AOS account permissions.
Database During initialization, you can import existing data into the
database.
Components You can install only one instance of the .NET Business Connector
that require the on a computer. In an environment with multiple AOS instances, use
.NET Business the Microsoft Dynamics AX Configuration utility to make sure that
Connector the .NET Business Connector on the local computer connects to
the intended AOS instance for the component you are installing.
In the Configuration Target list in the utility, select Business
Connector (non-interactive use only). On the Connection tab,
verify that the correct AOS instance is displayed.
For more information about using the Microsoft Dynamics AX
Configuration utility, click the Help button in the utility.
Servers in a Minimum Installation of Microsoft Dynamics AX

Minimum server components include the database and the AOS. Single-server
installations are typically used for development or testing only.
Application Object Server

You can install the AOS on a single computer, or you can create a server cluster for
load balancing.
Database server
A Microsoft SQL Server database server hosts the database that stores Microsoft
Dynamics AX transaction data and application elements. These application elements
include customizations.
Servers in a Complete Installation of Microsoft Dynamics AX

For some Microsoft Dynamics AX functionality, you must have one or more of the
following additional servers.
Report server
A report server is a server that runs Microsoft SQL Server Reporting Services (SSRS).
Analysis server
An analysis server enhances the reporting functionality in Microsoft Dynamics AX by
linking to Microsoft SQL Server Analysis Services (SSAS).
Web server
A web server hosts the websites that are required for some Microsoft Dynamics AX
features. These features include Enterprise Portal for Microsoft Dynamics AX, Help
server, Enterprise Search, and web services on Internet Information Services (IIS).
Other Servers in the Environment

The following servers are typically found in infrastructures that run Microsoft
Dynamics AX.
Domain controller
A domain controller in an Active Directory network manages user logons and access
to network and shared resources.
Messaging server
A messaging server enables email messages and instant messages to be sent and
received. The Microsoft Dynamics AX can use an email to send alerts to users. The
Microsoft Dynamics AX requires that the messaging server support SMTP.
Troubleshooting
In Microsoft Dynamics AX 2012, it is easier to troubleshoot problems with installation,
because log files and reports are easier to find. Because log files and reports are
saved to a single location, you do not spend time searching in multiple places.
In addition, a new Setup summary report is added. This report lists the components
that you installed, their installation status, and next steps, if applicable. You can
access the Setup log files and reports from links in the Setup wizard, or you can
navigate to the Setup Logs location in the folder where you installed Microsoft
Dynamics AX 2012.
Install Preparation
This section describes the preparation for installing Microsoft Dynamics AX.
Before you begin

Before you install Microsoft Dynamics AX, you must complete the following tasks:
 Create service accounts (http://technet.microsoft.com/en-

us/library/dd362055.aspx).
 Create a shared directory for installation (http://technet.microsoft.com/en-

us/library/dd362101.aspx)

 Configure SQL Server and storage settings (http://technet.microsoft.com/en-

us/library/dd309734.aspx)
 Include service packs and updates in a new installation (slipstreaming).

(http://technet.microsoft.com/en-
us/library/hh378076.aspx)
 Make sure the appropriate firewall ports are opened

(http://technet.microsoft.com/en-us/library/gg731780.aspx)
 Verify that you have the required permissions for installation

(http://technet.microsoft.com/en-us/library/aa496457.aspx)
 Check prerequisites (http://technet.microsoft.com/en-us/library/gg731884.aspx)
Procedure: Create a shared directory for installation

6. Create a directory that is named AX2012DVD.
7. Share the AX2012DVD directory.
a. Give the Administrator group full control, or owner access.

b. Give the Everyone group read access.
Note: As a security best practice, we recommend that you prevent users from
making changes to this directory. Only read access is required to perform an
installation from the directory.
8. Copy the contents of the Microsoft Dynamics AX DVD to the AX2012DVD

directory.
Procedure: Include Cumulative Update2 as part of the New Installation

(slipstreaming)
9. Create a CU2 folder under C:\AX2012DVD\Updates
10. Copy the DynamicsAX2012-KB2709934 file from the AX2012CU3 folder to the
C:\AX2012DVD\Updates\CU3 folder.
11. From within the C:\AX2012DVD\Updates\CU3 folder double-click the
DynamicsAX2012-KB2709934 to extract.
Note: Only Cumulative Updates for Microsoft Dynamics AX 2012 are supported
for slipstream, other type of hotfixes will need to be installed manually as per the
fix instructions.
Check Prerequisites
Run the prerequisite validation utility for Microsoft Dynamics AX to determine
whether a computer meets the requirements to install a Microsoft Dynamics AX
component. You can run the utility before you install any components in your
environment. If requirements are not met, the utility helps you to install or configure
most prerequisites.
Prerequisite validation is also built into Setup. Therefore, the same prerequisites are
validated when you install a component by using the Setup wizard.
Note: The prerequisite validation utility validates the software prerequisites that
Microsoft Dynamics AX depends upon. However, the utility does not verify
whether Microsoft Dynamics AX components that are also required are installed
or configured. For example, the utility verifies whether a supported version of
Windows is installed, but does not verify whether an AOS is running in the
environment. Prerequisite Microsoft Dynamics AX components are validated
when you run Setup.
Figure 1: Prerequisite Validation

Scenario: Check prerequisites

Before Gary installs the components, he runs the prerequisite checker to validate
which additional components are to be installed.
Procedure: Check prerequisites

Use the following procedure to run the prerequisite validation utility.
1. Start Microsoft Dynamics AX Setup.
12. Under Prepare, click Validate system requirements.
13. The Prerequisite validation page is displayed.
14. At this time we are only going to install the database, AOS, and client, so select
the following components, and then click Validate:
a. Databases
b. Application Object Server (AOS)
c. Client
Figure 2: Component selection
15. The Prerequisite validation results page is displayed. Each prerequisite is

assigned one of the following statuses:
Status Description
Success The local computer meets the prerequisite.
Error The local computer does not meet the

prerequisite. You cannot install the
component until this prerequisite is installed
or configured.
Warning The local computer does not meet the
prerequisite, but you can still install the
Microsoft Dynamics AX component.
16. For information about all the prerequisites that were validated, click View report
to display the Microsoft Dynamics AX Prerequisite check report.
17. Resolve prerequisite issues. For many errors and warnings, the prerequisite
validation utility can attempt to resolve the issue for you:
a. If a link is available in the Download column, click it to download and install

the missing prerequisite. Internet access is required to download some
prerequisites that are not included in the installation media. In some cases,
the download starts immediately when you click the link. In other cases, a
download page is displayed when you click the link.
b. If network or computer security prevents a prerequisite from being
downloaded from the utility, you must download the prerequisite by using
another method. Click the Error link on the prerequisite validation page to
obtain the download URL.
c. If a check box is available in the Configure column, select it, and then click
the Configure button to resolve the issue.
Note: Some prerequisites depend on other prerequisites. In these cases, the

prerequisites must be installed or configured in a specific order. For example, the
Windows Search Service must be installed before it can be started.
18. After you have resolved the prerequisite issues, click Revalidate to run the
prerequisite validation again.
19. When you have finished validating prerequisites, click Close.
Important: Prerequisite software that is installed or configured by the

prerequisite validation utility may not include the latest updates. We strongly

recommend that you run Windows Update to identify and install the latest
updates before you continue with the installation of Microsoft Dynamics AX.
Install Microsoft Dynamics AX Databases

The following topic describes installing the Microsoft Dynamics AX databases.
Before you install the Microsoft Dynamics AX database

Verify that the following steps are completed before you install the Microsoft
Dynamics AX databases.
 Configure SQL Server

For more information on Configure SQL Server and
storage settings, see: https://technet.microsoft.com/en-
us/library/dd309734.aspx
 On the computer where you plan to install the databases, run the prerequisite
validation utility to verify that system requirements have been met.
 For more information on how to run the prerequisite validation utility, see:
https://technet.microsoft.com/en-us/library/gg731884.aspx
 Create an account that is used to run the SQL Server service.

For more information, on Create service accounts, see:
https://technet.microsoft.com/en-
 Make sure that you have the required permissions to install the database.
For more information on Verify that you have the
required permissions for installation, see:
us/library/aa496457.aspx
 Make sure that TCP / IP is enabled in SQL Server, and that you can connect to the
server.
Include additional models in the installation (optional)

During installation, Setup imports models from the <installation
path>\Models\Standard folder. This folder contains the axsys.axmodel file that is
used to import the SYS layer.
However, it is possible to include your own models during the installation. Use the
following steps to include your models during the installation.
Procedure: Add Your Own Models (optional)

1. Browse to the <installation path>Models>folder.
20. Create a folder within the Models folder.
21. Copy your .axmodel model files to the folder that you created.
Best Practice: It is recommended that you create a different folder to store the
models received from different sources. For example, create a folder for each
independent software vendor (ISV) or each value-added reseller (VAR). Store the
model files received from the ISVs and VARs in their respective subfolders.
If models must be installed in a specific order, modify the

ModelFileInstallOrder.xml file that is located in the Models folder. Models are
installed in the order in which they appear in this file.
Warning: Do not copy your model files to the Standard folder. The Standard
folder must be used for models that are mandatory such as the axsys.axmodel
file.
Scenario: Install the Microsoft Dynamics AX Databases

In order to complete a base install of Microsoft Dynamics AX 2012, Gary needs to
install the Microsoft Dynamics AX 2012 databases.
Procedure: Install the Microsoft Dynamics AX Databases

Use this procedure to install the Microsoft Dynamics AX database. If you are
installing other Microsoft Dynamics AX components at the same time, the installation
pages will vary based on the components that you are installing.
1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics
AX components.
22. Step through the initial wizard pages. If the Setup Support files have not yet been
installed on this computer, then Select a file location page is displayed. The Setup
Support files are required for installation. Provide a file location or accept the
default location and then click Next. On the Ready to install page, click Install.
23. On the Select installation type page, click Custom installation, and then click
Next.
24. On the Select components page, select Databases, and then click Next.
25. On the Prerequisite Validation page, resolve any errors. When all errors are
resolved, click Next.
26. On the Select database page, select Create new databases and click Next.

27. Select the name of the computer that is running SQL Server from the Server
name list.
a. Accept the default database name of MicrosoftDynamicsAX, and then click
Next.
b. Accept the default baseline database name of MicrosoftDynamicsAXBaseline
and then click Next.
Important: Setup will create a new database using the name that you provide on
this page. Setup will display an error message if the database name that you
provided already exists.
28. On the Select additional models page, select the following models from the
Available Models grid and then click Next:
a. Foundation
b. Foundation Labels
Note: Setup lists all the models in the Model folder and all its subfolders. Setup
automatically selects the models from the Standard folder, such as the
Foundation model, and you cannot clear the selection. Select additional models
that need to be installed, if any.
By default, the models in the following table are available:

Model Description
Foundation The base Microsoft Dynamics AX model, which contains the
application framework and the application foundation. This
model also contains functionality for the discrete
manufacturing industry. This model is required.
Foundation This is application labels for the foundation model. This
Labels model includes labels for the following languages:
 Danish (Denmark)
 German (Germany, Austria, and
Switzerland)
 French (France, Canada,
Belgium, and Switzerland)
 Dutch (Netherlands and
Belgium)
 English (Canada, Ireland,
Malaysia, New Zealand,
Singapore, Great Britain, United
States, Australia, and South
Africa)
 Spanish (Spain, Mexico)
 Italian (Italy and Switzerland)

Foundation The model that is used to upgrade from Microsoft
Upgrade Dynamics AX 2009 or Microsoft Dynamics AX 4.0.
Process The model that contains features for Process manufacturing
Manufacturing production and logistics for Microsoft Dynamics AX. You
can use these features to manage production, inventory,
and costs in a process-controlled environment, such as in
the food, chemical, and pharmaceutical industries.
Process The model that is used to upgrade Process manufacturing
Manufacturing production and logistics from Microsoft Dynamics AX 2009
Upgrade or Microsoft Dynamics AX 4.0.
Public Sector This is Public Sector model for Microsoft Dynamics AX. This
model addresses special controls, rules, and regulations of
Public Sector organizations.
Project The model that contains additional project-related features
Management for Microsoft Dynamics AX. You can use these features to
invoice customers for various billing scenarios, such as
billing per unit of delivery and billing when a milestone is
completed. You can also use these features to create
customer and vendor retentions, and to manage workers on
projects.
Project The model that is used to upgrade Project Management
Management from Microsoft Dynamics AX 2009 or Microsoft Dynamics
Upgrade AX 4.0.

Warning: It is possible to have models, or the .axmodel files, that are not
electronically signed. The Setup program cannot verify the publisher of an
unsigned model file. Importing an unsigned model file to the model store is a
security risk. Setup will display an error message if a selected model files does
not have a digital signature. Carefully review the models that you have selected
before you decide to continue with or cancel the installation.
30. On the Ready to install page, click Install.
31. Confirm that the Setup installed the Microsoft Dynamics AX database
successfully. In case of errors, click View log file and review the installation log
for the Microsoft Dynamics AX database. Click Finish to close Setup.
32. Review the Setup Summary Report
Install AOS Server(s)

This topic describes installation of the Microsoft Dynamics AX 2012 AOS.
Before you install the AOS instance
 On the computer where you will install the AOS instance, run the prerequisite
For more information on how to run the prerequisite
validation utility, see Prerequisites article:
us/library/gg731884.aspx
For more information on Microsoft Dynamics System Requirements, see:

http://www.microsoft.com/en-us/download/details.aspx?id=11094
 Verify that you have the appropriate permissions to install the AOS instance.
For more information on Verify that you have the
required permissions for installation, see:
us/library/aa496457.aspx
 Select a service account for the AOS service. Before you install an AOS instance,
you must determine which account you want the AOS service to run as. The AOS
service can run as a domain account, as a managed service account, or as the

Network Service account of the computer that you install the AOS service on.
For more information on how to set up an account for the AOS service, see
Create service accounts article: https://technet.microsoft.com/en-
 Choose a name for the AOS instance. We recommend that you use a uniform
naming convention for all aspects of the installation, such as the database name
and the name of the AOS instance. Because Microsoft Dynamics AX installations
typically include one database and multiple AOS instances, make sure that the
name of each AOS instance is unique but consistent with the naming convention.
For example, you can use a name such as CONTOSO_AX6_Live_AOS1, which
includes a shortened form of your business name, the Microsoft Dynamics AX
version, a code that describes the purpose of the installation, and an identifier for
the AOS instance.
Note: The instance name must not include any blank characters or any of the
following characters: ampersand (&), backslash (\), slash (/), colon (:), brackets ([]),
parentheses (()), angle brackets (<>), quotation marks (“”), question mark (?),
exclamation point (!), asterisk (*), percent (%), caret (^), or pipe (|).
 You must install an initial AOS instance and complete the Initialization checklist
on that instance before you install additional AOS instances. If you install
additional AOS instances before you have completed the Initialization checklist,
those AOS instances will not start.
For more information on how to install additional AOS
instances, see Install multiple AOS instances article:
us/library/ee355067.aspx
Scenario: Install an AOS Instance

In order to complete a base install of Microsoft Dynamics AX 2012, Gary installs an
AOS instance.
Procedure: Install an AOS Instance

Use this procedure to install a single or initial instance of the AOS on a server. If you
are installing other Microsoft Dynamics AX components at the same time, the
installation screens will vary based on the components you are installing.
1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics
AX components.
33. Step through the initial wizard pages.

34. If the Setup Support files have not yet been installed on this computer, then
Select a file location page is displayed. The Setup Support files are required for
installation. Provide a file location or accept the default location and then click
Next. On the Ready to install page, click Install.
35. On the Select installation type page, click Custom installation, and then click
Next.
36. On the Select components page, select Application Object Server, and then
click Next.
38. On the Select a file location page, select the location where 32-bit versions of
Microsoft Dynamics AX files should be installed.
39. On the Connect to a Microsoft SQL Server database page, in the Server name
box, type or select the name of the SQL Server computer. In the Database name
box, type or select the name of the Microsoft Dynamics AX database.
40. On the Configure an AOS instance page, assign a name to the AOS instance.
Optionally, you can specify the following ports:
Port Purpose Default
TCP / IP port Used by other Microsoft Dynamics AX 2712
components to communicate with the AOS.
Services Web Used by external applications to access the 8101
Services WSDL for AOS-based Microsoft Dynamics AX
Description web services.
Language
(WSDL) port
Services Used by external applications to access AOS- 8202
endpoint port based Microsoft Dynamics AX web services.
41. If you are installing a second AOS instance on a server, you must specify unique
port numbers. By default, each time that you install an additional AOS instance
on a computer, the port numbers increment by one. For example, the second
AOS instance on a computer would be assigned to TCP / IP port 2713 by default.
Port conflicts can cause one AOS to stop.
Note: It is recommended that you use a uniform naming convention for all
aspects of the installation, including the database name, the AOS name, and the
application file instance name. Because Microsoft Dynamics AX installations
typically include one database, one set of application files, and multiple AOS
instances, make sure that AOS instance names are consistent with the naming
convention, yet unique. For example, you might use a name like
CONTOSO_DYNAX6_Live_AOS1, which includes a shortened form of your
business name, the Microsoft Dynamics AX version, a code for the purpose of the
installation, and an identifier for the AOS instance.
42. On the Specify an AOS account page, select either the Network Service account
of the local computer or a domain account for the AOS service. If you select to
use a managed service account, make sure to specify the account in the format
Domain\AccountName$.
43. On the Prerequisite validation results page, resolve any errors. When there are
no errors, click Next.
45. The AOS Windows service might take several minutes to start the first time after
it is installed. To determine whether it has started, open Administrative tools>
Services, and review the status of the Microsoft Dynamics AX Object Server
service.
46. Setup grants the following permissions to the AOS account:
a. Adds the AOS account to the Microsoft Dynamics AX database as a user,
makes it a member of the db_ddladmin, db_datareader, and db_datawriter
database roles.
b. Grants the AOS account execute permissions to the stored procedures in the
Microsoft Dynamics AX database.
c. Adds the AOS account to the TempDB database as a user and makes it a
member of the db_ddladmin, db_datareader, and db_datawriter database
roles.
Note: If you change the AOS service account later, permissions will need to be
granted manually.
Start the AOS Windows Service

By default, if a Windows service takes longer than 30 seconds to start, the system
warns you that the service did not respond to a start command. The AOS Windows
service can take longer than 30 seconds to start and the lack of a response within 30
seconds can cause the service to stop.
If an AOS repeatedly does not start, you might want to configure the registry to give
Windows services more time, such as 120 seconds, to start before prompting with an
error that a service did not respond to a start command.
Warning: This section contains steps that tell you how to modify the registry. Be
aware that serious problems might occur if you modify the registry incorrectly. It
is recommended that you back up the registry before you modify it. If a problem
occurs, you can restore it.

Procedure: Modify the Registry

Use the following procedure to configure the registry so that the AOS Windows
service has ample time to start before Windows prompts with an error.
1. Click Start, click Run, type regedit, and then click OK.
47. Locate and then click the following registry subkey:
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
48. Right-click Control, click New>DWORD (32-Bit) Value.
49. Right-click the new key and then click Rename. Enter the name
ServicePipeTimeout.
50. Right-click the key again and then click Modify.
51. In the Value data text box, enter 120000 and then click OK. The value 120000
provides the AOS Windows service 120 seconds to start before the system
prompts with a warning.
Figure 3: Registry
If the AOS fails to start after you implement this registry key, verify in the Microsoft
Dynamics AX Server Configuration utility that the AOS is using a unique port. Port
conflicts prevent the AOS from starting.
Note: You can install up to 99 AOS instances in your environment, though

licenses that are required for each AOS instance.
Note: For most production environments, you will install multiple AOS instances,
each on a different server. You can use multiple AOS instances to support batch
processing and load balancing. If you plan to install multiple AOS on the same
computer, you must specify a unique port for each AOS otherwise port conflicts
will cause one or more AOS to stop.
Install Clients
This topic describes installation of the Microsoft Dynamics AX 2012 client.
When you install a Microsoft Dynamics AX client, the following components are
included:
 The Microsoft Dynamics AX interface that connects to an instance of AOS.
 The Microsoft Dynamics AX Configuration utility (unless specified to use

Configuration file)
You can access the Microsoft Dynamics AX Configuration utility from the
Administrative Tools menu. On computers that run Windows 7, Administrative
Tools is an item in Control Panel.
If you are installing many clients, we recommend that you install them from a file
server and create a shared configuration file.
For more information on Mass deployment of the Microsoft Dynamics AX Windows
client, see: https://technet.microsoft.com/en-us/library/dd309709.aspx
Before you install a client

Complete the following tasks before you install a Microsoft Dynamics AX client.
 For more information on deployment best practices that can help secure the
Microsoft Dynamics AX client, see: https://technet.microsoft.com/en-
us/library/hh202063.aspx
 On the computer where you plan to install the client, run the prerequisite
For more information on how to run the prerequisite
validation utility, see:
us/library/gg731884.aspx
 Install the Microsoft Dynamics AX databases and AOS in the environment.

Installation Types
There are three different client installation types:
1. Business user
52. Developer
53. Administrator
 Business user: The basic client is installed. This type of client installation is
appropriate for most users.
 Developer: The client, the developer workspace, and additional files that are
required for development tasks such as compiling the application are installed.
Also, the debug settings are enabled by default for this type of install.
 Administrator: The client, the developer workspace, and additional files that are
required for development tasks such as compiling the application are installed.
Scenario: Install a Client

Gary wants to install a client so that he can initialize and configure the application.
Procedure: Install a Client

Use this procedure to install a Microsoft Dynamics AX client using the Setup wizard. If
you are installing other Microsoft Dynamics AX components at the same time, the
installation pages will vary based on the components that you are installing.
1. Start Microsoft Dynamics AX Setup.
54. Select to install Microsoft Dynamics AX components.
55. If the Setup Support files have not yet been installed on this computer, then
Select a file location page is displayed. Provide a file location or accept the
default location and then click Next. On the Ready to install page, click Install.
Figure 4: Setup support files
56. On the Modify Microsoft Dynamics AX installation page, click Add or modify
components, and then click Next.
57. On the Select components page, select Client and then click Next.
58. On the Prerequisite Validation results page, resolve any errors. When all errors
are resolved, click Next.
59. On the Select client preferences page, select the display language that is used
in the client, and specify whether you want Setup to create a desktop shortcut for
the client as well as the installation type and click Next.
a. Select English as the language

b. Select to Create a desktop shortcuts
c. Select Business user as the installation type
60. On the Specify a location for configuration settings page, specify whether the
client will use configurations from the registry or a shared configuration file and
click Next.
a. Select Save configuration in the registry
Note: If you choose the Use a shared configuration file option, client
configuration settings will not be stored locally, and the Microsoft Dynamics AX
Configuration utility will not be installed on the client computer. If a
configuration file does not exist at the network location that you specify, a new
configuration file will be created.

Note: A configuration file includes the location of the client application. If the
Microsoft Dynamics AX client location differs between the computer generating
the configuration file and the computer using the configuration file, the client
using the file will not start. It is recommended that you create multiple
configuration files if the client is installed in different locations on different
computers. For example, the default location of the Microsoft Dynamics AX client
application differs between 32-bit and 64-bit operating systems. On a 64-bit
system, the default path is \Program files (x86)\Microsoft Dynamics AX. On a 32-
bit system, the default path is \Program Files\Microsoft Dynamics AX. If you have
clients on both operating systems, it is recommended that you create a
configuration file for each version of the operating system, and then specify the
appropriate file when installing clients.
For more information on using a shared configuration file, refer: "Procedure:

Deploy Multiple Clients".
61. On the Connect to an AOS instance page enter the following information and
choose Next.
a. The name of the computer running the AOS instance to connect to.
b. Accept the default TCP / IP port number
c. Accept the default Services WSDL port number
62. On the Prerequisite validation results page, resolve any errors.
63. When there are no errors, click Next.
65. After the installation is completed, click Finish to close the wizard.
Best Practice: If you are installing a large number of clients, it is recommended

that you install them from a file server and create a shared configuration file.
Initialization Checklist
When users launch the Microsoft Dynamics AX client after a new installation, the
client will detect if this is a brand new installation or an upgrade by checking the
SYSSETUPLOG table and determine if it should display the initialization checklist or
the upgrade checklist.
The initialization checklist is intended for environments that are brand new to
Microsoft Dynamics AX when users have no data stored in the system.
Figure 5:
Initialization checklist
Note: If the goal were to install the software into a new environment such as a
test system using a restored copy of the production database, then the steps
would be different and may not require the initialization checklist.
The checklist will be displayed as soon as the client opens Microsoft Dynamics AX
client. To access the checklists manually click System
administration>Setup>Checklists>Initialization checklist. As each task is
completed, it is checked off by the system. Many of the tasks are one-time setup
options.
Users must be a member of the SYSADMIN role in Microsoft Dynamics AX to use the
initialization checklist. The person who installed Microsoft Dynamics AX automatically
becomes a member of the SYSADMIN role.
The initialization checklist has three main sections:
1. Prepare initialization
66. Synchronize database
67. Initialize system.
Some tasks are required and others are optional. If users would like to skip an
optional task, click the Mark as complete link and the step will change to a green
check mark.
For a new installation of a production environment, users might not want to skip any
of the optional tasks. However, if the installation is for demonstration or
development, skipping a task might save time.

Prepare Initialization
 Compile application: Checks the layers and models installed, updates the
references, and makes sure that the application has no code conflicts and is ready
for use. This task is optional if users only have the SYS layer installed, but it must
be completed if there is more than one layer in your system. When the
application is compiled, the application source code is translated into binary code
that can be interpreted by the kernel. The binary code is stored in the database.
 Generate Common Intermediate Language (CIL): Creates common intermediate

language in .NET framework from X++ code to increase performance of some
objects and creates assemblies on the AOS server.
 Provide license information: Opens the form to import the Microsoft

Dynamics AX licenses that were purchased. Licenses activate configuration keys
that are used to enable modules and functions. Some navigation icons may not
be available until a license is imported.
Note: If users do not have a license, they can set up Microsoft Dynamics AX in
demonstration mode. Demonstration mode provides all the functionality of
Microsoft Dynamics AX, and enables all configuration keys by default, but the
keys will expire. Always use customer license codes for production, User
Acceptance Testing (UAT), or a test environment.
 Configure application functionality: Review the functionality associated with

each key, and then enable or disable configuration keys as appropriate for your
installation. Disabled functionality does not appear on Microsoft Dynamics AX
menus.
Note: When a configuration key is disabled, the feature is removed from the user
interface. Unlike previous versions, the underlying tables are not removed.
 Customer feedback options: Join the Customer Experience Improvement

program to help Microsoft improve Microsoft Dynamics AX.
 Modify data types: Change the properties for data types without accessing the
Application Object Tree (AOT). You must be an administrator to make these
changes. All changes must be made before data is entered into the system. A
common example might be to change the number of decimal places on the
Amount data type, other changes are to the length of the Extended Data Type
(EDT) and the justification, which by default is left, justified.
Synchronize Database
Synchronize database (Required): Modifies the database
schema to match the most recent version of the
application code from the AOT.
The synchronization process creates all the tables and indexes Microsoft
Dynamics AX needs to operate. Since most SQL Server objects do not exist until
this task is complete, this is required in the new installation, when users do not
intend to restore an existing database. If errors are encountered during the
synchronization process, review the application event logs on the AOS server the
current client is connected to.
Initialize System
The Initialize system tasks cannot be accessed until the Synchronize database task is
complete.
 Create legal entities: Identify the legal entities that must be represented in
Microsoft Dynamics AX database. This can be a single company or multiple
companies in your organization.
 Set up system parameters: Specify shared system settings, including the system
language. The system language is the default language that is used by the
application for text translations of the menus, reports, and other content using
labels information.
 Configure system accounts: Enables users to setup the Business Connector

proxy account, the Workflow account, the synchronization service account, and
the Bing Maps account to be used throughout the system.
o Business Connector proxy account: Used for communication between

Microsoft Dynamics AX and other applications and integrations.
o Workflow execution account: Used for running application business logic and
accessing Microsoft Dynamics AX data.
o The synchronization service account: Used for communication between

Microsoft Dynamics AX, Windows Message Queuing, and Microsoft Project
Server.
 Import data: Enables users to import demonstration data or data that was
originally exported from Microsoft Dynamics AX (*.dat files). If users will be
working with a restored database this step is not required.

 Initialize user profiles: Select the default user profiles to enable for Role Centers.
Role Centers are customizable home pages that deliver content relevant to your
role. This step can be completed outside of the checklist once the Role Centers
are installed.
Default user profiles are available for various roles in the organization, such as
chief financial officer and accounting manager. These profiles contain role specific
information, and determine the content that is displayed on Role Center pages.
Users must select the profiles that they want to use in their Microsoft Dynamics
AX system.
To complete this task outside of the checklist click Organization administration,
click Setup, click Role Center, and then click Initialize role center profiles.
 Set up an Application Integration Framework: Services and Application

Integration Framework (AIF) require that you register new adapters, services, and
basic ports any time that you change the AOT. Click this checklist item before you
configure integration ports for the first time. Additionally, click this checklist item
any time that you change the AOT, if the change affects the configuration of a
port. For example, if you add a new service to the AOT because you want to use
the service together with an inbound port, you must click this checklist item.
Registration of new adapters, services, and basic ports can take a while.
Scenario: Complete Initialization Checklist

Gary has just finished installing the database, AOS, and client components and needs
to initialize the application for use.
Procedure: Compile application

Use this procedure to compile the application for the first time:
1. Launch Microsoft Dynamics AX.
68. If this is the first time that you have launched the client, the Initialization
checklist will appear.
69. Click Prepare initialization>Compile application.
70. This process might take a few hours to complete.
Procedure: Compile into .NET Framework CIL

Use this procedure to compile into .NET Framework CIL:
73. Click Prepare initialization > Compile into .NET Framework CIL
74. This process might take a few hours to complete.
Procedure: Provide license information

Use this procedure to provide the license information for Microsoft Dynamics AX:

76. Click Prepare initialization > Provide license information
77. The License information form appears.
78. Click Load license file
79. Browse to the license file and click OK
80. Review the Infolog and Close
81. Close the License information form.
Procedure: Mark Remaining ‘Prepare initialization’ Tasks as Complete

Use this procedure to mark the remaining tasks as complete:
83. Expand Prepare initialization.
84. Click the Mark as complete link next to each of the following tasks:
a. Configure application functionality
b. Customer feedback options
c. Modify data types
Procedure: Synchronize database

Use this procedure to synchronize the database:
86. Click Synchronize database > Synchronize database (required)
87. The Synchronize table process will begin.
88. This process might take up to an hour to complete.
Procedure: Mark Remaining ‘Initialize system’ Tasks as Complete

Use this procedure to mark the remaining tasks complete:
90. Expand Initialize system.
91. Click the Mark as complete link next to each of the following tasks:
a. Create legal entities.

b. Setup system parameters.
c. Configure system accounts.
d. Import data.

e. Initialize user profiles.

f. Set up Application Integration Framework.
92. Close Microsoft Dynamics AX application.
After you complete the checklist

After users complete the initialization checklist, they must restart the Microsoft
Dynamics AX client for any configuration changes to take effect such as display
language.
If all tasks are complete, the checklist will not appear when the client is reopened and
it should not be necessary to mark the prevent startup of the checklist.
Next steps
Install additional components or setup module specific parameters. See help for
those modules you are licensed for and which you plan to implement first. In this
course, additional components will be installed in later chapters.
Version Numbers
How to check the build numbers
There are a few ways to check the build numbers of your Microsoft Dynamics AX
2012 system:
 Help>About Microsoft Dynamics AX.
 Check version of AX32.exe and AX32Serv.exe.
How to interpret the build numbers

There are two version numbers to check:
1. Kernel version.
93. Application version.
 The Kernel is the component executing the X++ Application code. So the Kernel
version is the version of the executable (Client, Server, and Business Connector).
 The Application version is the version of the Microsoft Dynamics AX “Business

Logic” (the X++ Application code, Forms, Repots – everything in the AOT)
For more information on Overview of Dynamics AX build numbers, see:
http://blogs.msdn.com/b/emeadaxsupport/archive/2011/07/18/9810501.aspx
Best practice
 Kernel and application versions should be at the same service pack level.
 Microsoft Dynamics AX Client and AOS Kernel Version should be the same build
Server and Client Configuration

A configuration is a group of startup and tracing settings for an AOS instance or
client that can be stored one of two ways:
1. Microsoft Windows registry
94. Configuration file
Administrators might want to create new configurations and configuration files, save
or load configurations to support:
 Having multiple environments, one instance for the live environment, one
instance for development, and one instance for testing.
 Moving from a development environment to a production environment.
 Change the application directory that an AOS instance points to, the database,
and whether a system allows for debugging.
 Tuning Microsoft Dynamics AX 2012, save a configuration with the defaults, and
then change compression, database tuning, and tracing settings one at a time,
and save them as different configurations. Run Microsoft Dynamics AX 2012 with
each different configuration, and evaluate how it performs.
Note: The computer that is running the AOS, only members of the local
Microsoft Windows Power User group or Administrators group can change
configuration settings. Restrict membership in these groups, to reduce the
potential for malicious mischief.
Microsoft Dynamics AX 2012 Server Configuration

The Microsoft Dynamics AX Server Configuration Utility is used to control settings on
an AOS including:
 Database
 Connection ports
 Breakpoint and printer configuration
 Database tuning settings

Figure 6: Microsoft Dynamics AX Server Configuration Utility
Note: After you make changes in the server configuration utility, the system
prompts you to restart the AOS instance. The restart affects all client and
database connections to the AOS instance. If you perform one or more of these
procedures on a production server, we recommend that you perform the
procedures during off-peak hours to prevent dropped connections for clients
and databases.
Scenario: Create new configuration file

Gary Greathouse, the Systems Implementer, has been given instructions to create a
new server configuration file.
Procedure: Create new configuration file

Use the Microsoft Dynamics AX Server Configuration utility to create a new server
configuration file:
1. Open the Server Configuration utility (Start>Administrative Tools>Microsoft
Dynamics AX Server Configuration).
95. Click Manage, and click Create configuration.
96. In Configuration name, type a name for the configuration: “TEST”
97. In Copy Configuration from, select either Active configuration or Original
configuration, and then click OK to exit.
98. On the Application Object Server tab, in the TCP/IP port field, note which port
the AOS is running on. This information is needed to connect to the AOS.
99. On the Application Object Server tab, in the Services WSDL port field, note
which port is used for Services and Web Services in IIS.
100. On the Database Connection tab, validate that the AOS is connected to the
correct database. If not, change it.
101. Click OK to exit the configuration utility.
102. Click Yes on the dialog asking "The data for the AOS service has changed. Do
you want to restart the service?"
Microsoft Dynamics AX 2012 Server Configuration Utility Settings

Field Description
AOS instance Select the AOS instance that you want to configure. You
cannot change settings for the original configuration. If you
want to change any settings, you must create a new
configuration.
Configuration Specify the name of the current group of settings for the AOS
instance.
Manage Select the task that you want to perform:
Open configuration file: Open a file that contains configuration
settings.
Close configuration file: Close a configuration file after you have
finished reviewing or changing settings.
Save configuration file: Save the changes that you have made to
the active configuration file.
Save configuration as file: Save the current configuration to a file.
Use this command to store an offline copy of the settings that you
have been using.
Import configuration from file: Import configurations from a stored
file into the registry.
Export configuration to file: Export the configuration that is
currently active to a file. Use this command when you want to copy
the configuration to an AOS instance on another computer.
Export all: Export all configurations to a file. You can then copy all
configurations from one AOS instance to another computer.
Create configuration: Create a new configuration by using the
Create Configuration dialog box. The new configuration can be
based on either the configuration that is currently selected or the
default configuration.
Delete configuration: Delete the current configuration.
Rename configuration: Rename the current configuration.
Tabs
Tab Description
AOS Specify startup, port, and development options for an AOS
instance.
Database Specify information about server and database connections.
Connection

Database Tuning Specify database settings to adjust performance.

Performance Specify settings for compression and processor affinity to
adjust performance.
Fields
Field Description
Alternate bin Specify the location of a directory that contains an alternate
directory kernel text data file. This file is one of the Microsoft
Dynamics AX label files.
Configuration Enter the configuration commands that are run when the
command to run at AOS instance starts.
kernel startup For more information on Execute configuration commands, see:
https://technet.microsoft.com/en-us/library/aa569627.aspx
TCP / IP port Specify the TCP / IP port that the AOS instance uses to
connect to clients.
Services WSDL port The port that is used by AOS services. You cannot change
the services port. If you want to specify different services
ports, you must install a new instance of AOS and specify
the port numbers of the services ports in Setup.
Enables clients to Select this option to enable client computers to print from
connect to printers the active AOS instance. The print option in the Microsoft
on this server Dynamics AX 2012 Configuration utility must also be
enabled.
For more information on Configure an AOS instance to print,
see: https://technet.microsoft.com/en-us/library/aa569633.aspx
Enable breakpoints Select this option to enable clients to trace their interactions
to debug X++ code with the AOS instance.
running on this For more information on how Microsoft Dynamics AX Debugger,
server see: https://technet.microsoft.com/en-us/library/aa569668.aspx
Enable global Select this option to debug X++ code that is invoked by
breakpoints using Query Services. Query Services use Query Builder,
which is a set of X++ classes that are invoked by services.
Query Services and Query Builder use the interpreted mode
for remote procedure call (RPC). All other Microsoft
Dynamics AX services use the CIL. The infrastructure of SSRS
is the largest consumer of Query Builder's X++ classes. The
Reporting Services Report Data Provider (RDP) is based on
Query Builder and requires that this option be enabled.
Otherwise, debugging cannot be performed.
Enable the hot- Select this option if you want to deploy assemblies to the
swapping of server without restarting the AOS instance.
assemblies for each For more information, on How to: Enable Hot Swapping of
development Assemblies, see: https://technet.microsoft.com/en-
session us/library/gg889279.aspx
Server name Specify the computer that is running an instance of SQL Server.
Specify a connection in the format Servername\instancename.
Database name Specify the name of the database that the AOS instance
connects to.
Baseline database Specify the baseline model database. The baseline database
name was either specified during installation or created manually.
The baseline database is used to perform code analysis.
Statement cache Specify the size of the statement cache. The recommended
size is less than 256 kilobytes (KB). A value that is larger
than 256 KB can cause memory issues on the server. If you
increase the value in this field, validate that the value is
appropriate, based on your data composition and query
patterns.
For more information on Tune data access settings, see:
Maximum buffer Specify the maximum size of the buffer. The recommended
size size is less than 24 KB. A value that is larger than 24 KB can
cause memory issues on the server. If you increase the value
in this field, validate that the value is appropriate, based on
your data composition and query patterns.
For more information on Tune data access settings, see:
Local Microsoft Specify the location of the ODBC log file.
Open database
Connectivity (ODBC)
log file location
Number of Specify the number of times that the AOS instance tries to
connection retries connect to the database before the connection fails.
Connection retry Specify the interval between attempts to connect to the
interval (in seconds) database.
Limit the number of Select this option if you want the AOS instance to limit the
inactive connections number of inactive connections to the database.
Maximum number The maximum number of inactive connections to the
of inactive database that the AOS instance retains. The default value is
connections 20.
Generate ORDER BY Select this option to override the order of columns that is
clauses from specified by the index on the data source. Instead, the order of
WHERE clauses columns that is specified in the WHERE clause is used.
Minimum packet Specify the minimum size of the data packets when data
size to compress (in that is sent between the AOS instance and its clients is
KB) compressed. Data compression accelerates client-server
communications. Use this field in low-bandwidth or high-
latency network environments. Specify the smallest packet
size that is useful. The amount of acceleration that you
achieve decreases as the size of the packets increases.
Default Select this option if you want Microsoft Windows to
determine the processor that hosts the AOS instance.
Custom Select this option if you want to specify the processor that
hosts the AOS instance.
AX 2012 Server Configuration Utility Settings: Best Practices

Field Description
Configuration For the purposes of tracing or debugging, create new

configurations for each of these and switch to these

configurations when necessary.
Enable breakpoints We recommend Breakpoints Enabled not be activated on
to debug X++ code production Microsoft Dynamics AX AOS instances as this
running on this adds unnecessary overhead. This functionality should only
server be used in non-production Microsoft Dynamics AX
environments.
Enable global
breakpoints
Statement cache Do not increase this value unless specifically instructed to. A
value that is larger than the default one can cause memory
issues on the server.
Maximum buffer Do not increase this value unless specially instructed to.
size The recommended size is less than 24 KB. A value that is
larger than 24 KB can cause memory issues on the server.
Processor Affinity Default: select this option if you have only one instance of the
AOS on this machine.
Custom: Select this option if you have more than one
instance of the AOS on this machine. For example, if you
have 4 CPUs on the box give Instance1 CPU0 and CPU1 and
give Instance2 CPU2 and CPU3.
Scenario: Increase Maximum Buffer Size

Gary Greathouse, the Systems Implementer, has been given instructions to increase
the maximum buffer size setting by 8 KB on the AOS servers to accommodate a
custom process.
Procedure: Increase Maximum Buffer Size

Use the Microsoft Dynamics AX Server Configuration utility to increase the maximum
buffer size:
1. Open the Server Configuration utility (Start > Administrative Tools > Microsoft
103. In the Configuration field, scroll down and select TEST configuration.
104. On the Database Tuning tab, change the existing value to 30 in the
Maximum buffer size field.
105. On the Application Object Server tab, in the TCP/IP port field, note which
port the AOS is running on. This information is needed to connect to the AOS.
109. Click Yes on the dialog asking "The data for the AOS service has changed. Do
you want to restart the service?"
Scenario: Enable Breakpoints

Gary, the Systems Implementer, needs to enable breakpoints to debug a process in
Microsoft Dynamics AX.
Procedure: Enable Breakpoints

Use the Microsoft Dynamics AX Server Configuration utility to enable breakpoints:
1. Open the Server Configuration utility (Start > Administrative Tools > Microsoft
2. In the Configuration field, scroll down and select TEST configuration.
3. On the Application Object Server tab, select Enable breakpoints to debug X++
code running on the server.
4. On the Application Object Server tab, in the TCP/IP port field, note which port
the AOS is running on. This information is needed to connect to the AOS.
8. Click Yes on the dialog asking "The data for the AOS service has changed. Do you
want to restart the service?"
Note: The registration information for the server configuration is stored in the
following location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\Dynamics
Server\6.0\01\<configuration>

Microsoft Dynamics AX 2012 (client) Configuration

The Microsoft Dynamics AX (client) Configuration Utility is used to control how a
client connects to an AOS. The settings available for configuration include:
 Logon company
 Startup message
 Startup commands
 Connection information to an AOS including failover AOS servers
 Debugging settings
 Layer
 Performance settings
Figure 7: Microsoft Dynamics AX Configuration Utility
Note: Only members of the Administrator or Power User group on the computer
can use the Microsoft Dynamics AX Configuration utility.

Microsoft Dynamics AX 2012 (client) Configuration Utility Settings

Field Description
Active Configurations are stored either in the registry on the local computer
configuration store or in a configuration file. You cannot change the configuration store
for the original configuration. To change the active configuration
store for the original configuration, you must create a new
configuration. For new configurations, you can change the
configuration store by clicking Set Configuration Store on the
Manage menu.
Configuration Specify whether you want to configure the local client or the
target proxy for .NET Business Connector.
Configuration Select the configuration that you want to use.
Manage Select the task that you want to perform:
Open configuration file: Open a file that contains configuration
settings.
Note: Although you can use the Open command to view a saved
configuration, Microsoft Dynamics AX does not store the
settings from the file that you open in the registry. To save the
settings from a configuration file to the registry, you must use
the Import command.
Close configuration file: Close a configuration file after you have

finished reviewing or changing settings.
Save configuration file: Save the changes that you have made to the
active configuration file.
Save configuration as file: Save the current configuration to a file.
Use this command to store an offline copy of the settings that you
have been using.
Import configuration from file: Import configurations from a stored
file into the registry.
Export configuration to file: Export the configuration that is
currently active to a file.
Export all: Export all configurations to a file. You can then copy the
configurations from one client instance to another computer.
Create configuration: Create a new configuration by using the Create
Configuration dialog box. The new configuration can be based on
either the configuration that is currently selected or the original
configuration.
Delete configuration: Delete the current configuration.
Rename configuration: Rename the current configuration.
Set Configuration Store: Specify a configuration file. Configuration
information is then read from the file instead of the registry.
Microsoft Dynamics AX administrators can specify a configuration file
on a network share to reduce administrative overhead. If you have
previously specified a file, you can reset the configuration store so
that the registry is used. Click Set Configuration Store, delete the
path in the Configuration File Path text box, and then click OK.
Tabs
Tab Description
General Set startup options for a client. The options specify the location of
the log directory, the company that opens, the commands that
run on startup, and the messages that are displayed.
Connection Specify the AOS instance that the client connects to, and set
connection options for that AOS instance.
Developer Set development options. The options specify whether
debugging is enabled in the client or .NET Business Connector,
the default application layer that opens for the developer, and
license information for development.
Performance Specify cache settings to adjust Microsoft Dynamics AX
performance.
Buttons
Button Description
Add Open the Add Application Object Server instance dialog box,
where you can add an AOS instance to the list of available
instances.
Edit Edit an AOS instance.
Delete Delete an AOS instance from the list of available instances.
Configure Open the Windows Communication Foundation (WCF)
Services Configuration Editor tool, SvcConfigEditor.exe, if the tool is
installed. This tool is installed as a component of some
versions of the Windows SDK. This tool is also installed by
Microsoft Visual Studio 2010. The tool provides a graphical
user interface (GUI) that you can use to create and modify
configuration settings for services that are based on WCF.
For more information on Configuration Editor Tool, see:
https://msdn.microsoft.com/en-us/library/ms732009.aspx
If the WCF Configuration Editor tool is not installed, the WCF

configuration file opens in Notepad when you click this
button. You can then modify the XML code to change the
information about the WCF configuration, and then save the
file.
For more information on Configuring Services Using Configuration
Files, see: https://msdn.microsoft.com/en-
us/library/ms733932.aspx
Refresh Use this button to make sure that the local configuration is
automatically updated when a change is made on the server.
Up Move the selected instance higher in the list.
Down Move the selected instance lower in the list.
Fields
Field Description

Log directory Specify a directory for log files.

Company Specify the company that opens when a user starts the
Microsoft Dynamics AX client.
Command to run Enter the SysStartupCmd method that runs when the client
at application application starts.
startup For more information on startup commands, see: Run client
commands at startup and Client configuration commands.
Configuration Enter the configuration command that runs when the client
command to run at kernel starts.
kernel startup For more information on configuration commands, see: Client
configuration commands.
Startup message Enter the text of the message that is displayed when Microsoft
Dynamics AX starts. For example, if a configuration connects to
a production environment, you can inform developers by
entering the message, "Connecting to production environment."
Server name The name of computer that runs AOS.
Instance name The name of the AOS instance.
TCP / IP port The TCP / IP port that the AOS instance communicates on.
WSDL Port The port that is used by services.
Connect to printers Select this option to enable clients to connect to printers that
on the server are connected to the computer that runs AOS. The print option
must also be enabled on the AOS instance.
For more information on Configure an AOS instance to print, see:
Encrypt client to Encrypt all data that is sent between the client and the AOS
server instance.
communication
Enable user Select this option to enable X++ code that runs in .NET Business
breakpoints to Connector to be interrupted by breakpoints. This option applies
debug code in the to individual sessions.
Business
Connector
Enable global Select this option to enable the X++ code that runs in .NET Business
breakpoints to Connector or the client to be interrupted by global breakpoints. This
debug code option applies to all sessions. To debug .NET Business Connector, you
running in the must set both this option and the Enable user breakpoints to debug
Business code in the Business Connector option. To debug the client, set only
Connector or client this option.
Application object Select the layer that opens by default in the AOT.
layer to open
Development Enter the code for a development license so that you can access
license code the AOT by using the current configuration.
Confirm license Retype the code for the development license.
code
Microsoft Dynamics AX 2012 (client) Configuration Utility Settings:

Best Practices
Field Description
Configuration For the purposes of tracing or debugging, create
new configurations for each of these and switch to
these configurations when necessary.
Company Empty by default
Command to run at Empty
application startup
Configuration command to Empty
run at kernel startup
Startup message Empty
Server names Only available AOS’s
TCP/IP 2712
WDSL Port 8201
Connect to printers on the Disabled
servers
Encrypt client to server Enabled
communication
Enable user breakpoints to Disabled
debug code in the Business
Connector
Enable global breakpoints Disabled
to debug code running in
the Business Connector or
client
Cache settings Least Memory for RDP
Registry or File
By default, the Microsoft Dynamics AX client reads configuration information from
the registry on the local computer. If you deploy many Microsoft Dynamics AX
clients, it can be difficult to maintain or troubleshoot configurations.
To enhance security and simplify client administration, we recommend that large
deployments must run the Microsoft Dynamics AX client as a remote application,
which means to use a common configuration file.
Note: If your business or organization runs Microsoft Dynamics AX 2012 clients

on both 32-bit and 64-bit versions of the Windows operating system, you must
create multiple configuration files.

Microsoft Dynamics AX clients that run on a 32-bit version of Windows must

connect to a client configuration file that was created on a 32-bit version of
Windows.
Similarly, Microsoft Dynamics AX clients that run on a 64-bit version of Windows

must connect to a client configuration file that was created on a 64-bit version of
Windows.
Note: The registration information for the client configuration is stored in the
following location:
HKEY_CURRENT_USER\Software\Microsoft\Dynamics\6.0\Configuration\<configu
ration>
Scenario: Create Configuration File

Gary, the Systems Implementer, would like to create a new configuration file based
on the original configuration, pointing to the " Contoso Entertainment Systems
(West)." company with a startup message 'Test environment.' He would also like to
review the rest of the client configuration settings.
Procedure: Create Configuration File

Use the Microsoft Dynamics AX 2012 Client Configuration utility to create a new
configuration file based on the original configuration, pointing to the "Contoso
Entertainment Systems (West)." company with a startup message "Test environment".
He would also like to review the rest of the client configuration settings.
1. Open the Microsoft Dynamics AX Client Configuration utility (Start>
Administrative Tools>Microsoft Dynamics AX Configuration).
2. In the Configuration target list, select Local client.
3. Click Manage, and click Create configuration.
4. In Configuration name, type a name for the configuration as New
Configuration.
5. In Copy Configuration from, select either Active configuration or Original
configuration, and then click OK.
6. On the General tab, select Company and type "CEU” for Contoso
Entertainment Systems (West)
7. On the General tab, select Startup message and type "Test environment."
8. On the Connection tab, validate the connection settings to the AOS.
9. On the Developer tab, validate the settings for breakpoints and the
application layer.
10. On the Performance tab, validate the settings for client performance.
11. Click Manage, and then click Export Configuration to File.

12. Save the configuration file as “NewConfiguration.axc”
Procedure: Create a shared configuration file

1. On a file server or the server that hosts AOS, create the directory that the clients
share. In this procedure, create a directory called C:\ClientShare.
110. Configure the directory (C:\ClientShare) so that all users of the Microsoft
Dynamics AX client have read access.
111. Copy the configuration file that you created in the previous procedure to the
share that you created in step 1.
112. Double-click the configuration file to launch into Microsoft Dynamics AX
2012.
Scenario: Modify Configuration File

Simon, the Systems Implementer, needs to modify the TCP / IP port to the AOS
Server 2713 that is used by Microsoft Dynamics AX users.
Procedure: Modify Configuration File

1. Browse to the Configuration file you saved in the previous procedures.
113. Right-click Properties on the file.
114. Click the Change button next to Opens with.
115. Click More options, select Notepad, and then click OK.
116. Double-click NewConfiguration.axc to open.
117. Change the line aos2,Text,MicrosoftDynamicsAX@DAX2012:2712 to
aos2,Text,MicrosoftDynamicsAX@DAX2012:2713.
118. Save file.
119. Right-click Properties on the file.
120. Click the Change button next to Opens with.
121. Select Microsoft Dynamics AX Client and Click OK.
Service Packs and Updates

This section describes the types of updates that are available for Microsoft Dynamics
AX 2012 and the deployment process for updates. The section also describes the
naming convention that is used for updates and the structure of update packages.
Hotfixes
A hotfix is code that resolves selected bugs that affect key features or a significant
number of Microsoft Dynamics AX installations. A hotfix can address either a single
issue or a cumulative set of issues.

Microsoft publishes a corresponding Knowledge Base (KB) article for every hotfix that
is released for every Microsoft product. These KB articles describe the changes that
the hotfix makes to objects, database tables, or files, or other code.
Microsoft Dynamics AX has the following standard types of hotfix:
Binary hotfixes (also known as Kernel hotfixes)

Objects and components that are installed by using standard Windows installer (MSI)
files are patched with Windows Installer Patch (MSP) files and are applied by using
AXUpdate.exe. These updates are cumulative (each binary hotfix contains changes
from all previously released hotfixes).
Application hotfixes
Application hotfixes are those that are provided by using application model
(.axmodel) files to any of the Microsoft application patch layers (SYP, GLP, FPP, SLP).
Unlike binary hotfixes, application hotfixes target a specific fix and are not cumulative
in nature.
Important: All application hotfix model files must be installed by using

AXUpdate.exe. Importing these application models manually is explicitly
unsupported and may result in errors.
Pre-processing hotfixes
Pre-processing hotfixes are applied to data upgrade scripts (for example,
DatabaseUpgrade) that are run on Microsoft Dynamics AX 4.0 and Microsoft
Dynamics AX 2009 systems before upgrading to Microsoft Dynamics AX 2012.
Cumulative Updates
A cumulative update (CU) is an update that contains all previous hotfixes to date.
Additionally, a CU contains fixes for issues that meet the criteria for hotfix
acceptance. These criteria may include the availability of a workaround, the effect on
the customer, the reproducibility of the problem, and the complexity of the code that
must be changed.
Service Packs
A service pack is a tested, cumulative set of all hotfixes and updates. Service packs
may also contain additional fixes for problems that have been found internally since
the release of the product, and a limited number of design changes or features that
were requested by customers.
Deployment Process for Updates

For any update that affects code or the database schema, we recommend that you
first deploy updates, make all required changes to customizations, and compile your
code in a test environment. After your system has been compiled in the test
environment, we recommend that you use the Windows PowerShell Import-
AXModelStore cmdlets to deploy changes to the production environment. This
approach requires the least downtime for your production system.
Naming Convention for Update Packages

The following naming convention is used for packages that service Microsoft
Dynamics AX: <ProductName>-KB<KBNumber>v<PackageVersionNumber>-
<ServicePackLevel>.exe.
For example, a package might be named DynamicsAX2012-KB123456-v2-SP2.exe.
The following table explains the name segments that are used in package names.
Name segment Description
<ProductName> This segment indicates the name of the product
that is being serviced. For packages that service
Microsoft Dynamics AX 2012, this segment is
DynamicsAX2012.
<KBNumber> This segment indicates the KB article that
corresponds to the package, such as KB123456.
<PackageVersionNumber> This segment is not used for the first release of a
package. If the package is recalled or otherwise
re-released, this segment indicates the revision
of the package, such as v2, v3, or v4.
<ServicePackLevel> This segment indicates the service pack level
that the package services. This segment is used
only for packages that must be applied to a
product for which Service Pack 1 or a later
version is installed. This segment is not used for
packages that service the original release
version of a product, for which no service packs
are installed.
Update Package Structure

This section describes the structure of update packages. When you run the self-
extracting executable package, you unpack a folder. The following table describes the
files and folders that this folder contains.
Name T Description
y
p
e

u
p
d
a
t
e
t
h
a
t
t
h
e
f
i
l
e
o
r
f
o
l
d
e
r
i
s
u
s
e
d
f
o
r
AXImpactAnalysis.exe Application The version of the Update wizard that

updates you can run to analyze the effect of the
update on customizations in your
environment.
Although AXImpactAnalysis.exe may be
included in binary update packages,
running it provides no additional
information if you run it.
AXUpdate.exe Binary and The Update wizard that you can run to
application install MSP and model files that are
updates required for the update.
DatabaseUpgrade Updates to pre- A folder that contains updated pre-

processing files processing files that are used to upgrade
that are shipped from Microsoft Dynamics AX 4.0 or
in cumulative Microsoft Dynamics AX 2009 to
updates Microsoft Dynamics AX 2012.
LicenseTerms Binary and A folder that contains the license terms
application that you must agree to before you can
updates install an update. This folder is used by
AXUpdate.exe.
Models Application A folder that contains the models that
updates are being updated. This folder is used by
AXUpdate.exe.
MSI Binary updates A folder that contains subfolders for the
components of Microsoft Dynamics AX
that are being updated. Each subfolder
contains one or more MSP files. This
folder is used by AXUpdate.exe.
Support Binary and A folder that contains support files and
application subfolders that are called by
updates AXUpdate.exe. The files and subfolders
include language-specific files for
AXUpdate.exe. This folder is used by
AXUpdate.exe.
Process for Installing Updates

It is important that day-to-day operation of your business be disrupted as little as
possible when you install hotfixes.
Evaluate the hotfix

Each hotfix is created to address a specific issue, problem, or customer scenario.
Hotfixes are distributed only to those customers, partners, and organizations that
Microsoft technical support personnel determine can benefit from the changes that
are made to the code. Each hotfix includes documentation that indicates what files,
tables, code, or functions are changed by the hotfix.
Before you install a hotfix, review the knowledge base (KB) article that is released
together with the hotfix. The KB article helps you determine whether the hotfix
applies to your environment, and how the hotfix affects your environment.
Note: If you have customized your environment before you received a hotfix,
thoroughly review the KB article that describes the hotfix. Investigate any objects
that are affected by the hotfix to determine whether the changes that are
implemented by the hotfix should be merged with customizations in a higher
layer, such as BUS, VAR, USR, or CUS.

Test the hotfix in a test environment

After you have decided to install a hotfix, we recommend that you install the hotfix in
a test or backup environment. Then validate the hotfix against the implementation,
customizations, data, and processes that are currently used in your organization.
After the hotfix has been tested, you can roll the code changes forward to the
production environment. Use the methodology that is described in the following
White paper: Deploying Customizations Across Microsoft Dynamics AX 2012
Environments: https://technet.microsoft.com/en-us/library/hh292604.aspx and How
to: Export and Import a Model Store: https://technet.microsoft.com/en-
Install the hotfix

To install a hotfix, follow the instructions in the associated KB article, and in the
articles in the following article, Installing updates and hotfixes:
https://technet.microsoft.com/en-us/library/hh538447.aspx
Additionally, make sure that business processes or operations can be restored to
their original state if problems occur during or after installation.
 Back up the database that is being updated. By backing up the database, you can
roll back to a known, reliable version if you have to. In this manner, you can
reduce downtime if an unexpected error occurs.
 Schedule a time when the fewest system users, or no users, are affected. As a best
practice, announce the time of the update in advance, to make sure that users are
aware of the pending update and the expected downtime. By notifying all users
of the time of the update, you can minimize data loss, data corruption, and loss
of productivity.
 Make sure that the system runs in single-user mode while the hotfix is installed,
and that only the administrator is designated to perform the update. Because
changes to the code can affect AOS, the changes can affect users who are
currently on the system.
Note: Changes to the application may require a compilation or synchronization

of the application. These operations increase downtime.
Validate the hotfix in test and production environments

After the hotfix has been successfully installed, check the install log to make sure that
there are no error messages and warnings that can affect the operation of the
system. Test the system for the following conditions:
 The change that was implemented by the hotfix is working as expected.
 The change has not affected other areas of the system.
 The Microsoft Dynamics AX application as a whole is working as expected.
Troubleshooting
If errors or issues occur during or after installation of a hotfix, the hotfix must be
uninstalled, and the system must be rolled back. Follow these steps to restore your
system to the last known, reliable version:
1. If the hotfix installed any binary files, uninstall the hotfix by using the Add or
Remove Programs item in Control Panel.
122. Restore the database backups.
123. Synchronize the database, if synchronization is required, to return the
implementation to pre-update conditions.
124. Optional: If you require help troubleshooting the installation errors or issues,
open a support request by contacting your partner or VAR. Alternatively, if you
are enrolled in a support plan directly with Microsoft, you can log on to
CustomerSource and submit a new support request.
Install Updates to Database, AOS, and Clients

This section describes how to install updates on Microsoft Dynamics AX 2012. We
recommend that you perform updates in a test environment, and resolve all code
changes there.
You can then roll the code changes forward to the production environment by using
the methodology that is described in the following article: Deploying Customizations
Across Microsoft Dynamics AX 2012 Environments (White paper):
https://technet.microsoft.com/en-us/library/hh292604.aspx and How to: Export and
Import a Model Store: https://technet.microsoft.com/en-us/library/hh433530.aspx
By exporting and importing the model store, you can avoid having to compile an
environment more than one time.
Different updates can affect different components of Microsoft Dynamics AX. When
you install an update, the update installer indicates which components of Microsoft
Dynamics AX are affected by the update.
If an update affects multiple components, we recommend that you follow these steps
to apply the update:
1. Apply the database updates to a single database, apply the AOS updates to a
single local AOS instance that is associated with the updated database, and apply
the client updates to a single local client. Then get the environment running.
Note: Because the Microsoft Dynamics AX 2012 model store is part of the
Microsoft Dynamics AX database, when you update the database, you also
import all code updates.

125. Apply the database updates to any additional databases by exporting and
importing the model store.
126. Apply the AOS updates to any additional AOS instances.
Note: You cannot apply updates to remote AOS instances by using

AXUpdate.exe. You must apply the updates locally.
127. Deploy changes to SSRS, and then to Enterprise Portal for Microsoft
Dynamics AX.
128. Mass deploy the updates to your clients.
For more information on Run AXUpdate in silent mode,
see: https://technet.microsoft.com/en-
Extract the update

Updates for Microsoft Dynamics AX are shipped as self-extracting executable files.
Before you can install an update, you must extract the files that are required to install
it.
1. Download the update from CustomerSource or PartnerSource.
129. Double-click the downloaded file to extract the contents.
130. We recommend that you extract the files to a location that can be accessed
from all servers and clients that you plan to update.
Evaluate the effect of an update on your environment

Microsoft Dynamics AX updates are shipped together with the Impact Analysis tool,
AXImpactAnalysis.exe. This tool is a version of the update installer that helps you
determine the effect that an update has on your environment before you install the
update.
Important: Before you can run the Impact Analysis tool, you must install
KB974255. If you have installed Cumulative Update 1 for Microsoft Dynamics AX
2012, KB974255 is already installed. Otherwise, you must install KB974255 first.
Run AXImpactAnalysis.exe
1. Browse to the location where you extracted the files for the service pack, right-
click AXImpactAnalysis.exe, and then click Run as Administrator.
131. On the Welcome to Microsoft Dynamics AX Update Setup, Impact Analysis
Mode page, click Next.
132. On the License terms page, review the license terms. Select the option to
accept the license terms, and then click Next.
133. On the Select client configuration page, select a client configuration or a

configuration file to analyze, and then click Next.
134. On the Select model store page, select a model store to analyze, and then
click Next.
a. The model store that you select must be the same model store that is used
by the client configuration that you selected.
135. On the Select baseline model store page, select a baseline model store to
use for the impact analysis, and then click Next.
a. The model store that you select must be the same model store that is used
by the client configuration that you selected.
Note: AXImpactAnalysis.exe deletes the existing contents of the baseline model

store to perform the analysis.
136. A list of affected objects is displayed. Click Impact Analysis to open the
Microsoft Dynamics AX client and view detailed results of the impact analysis.
You can use the Impact Analysis form to view details about the objects that are
affected by the update, and to export the results. You can perform the following
actions:
o Compare code: Click Compare to open the Comparison Results form. From
this form, the changes that were made to an object that was loaded during
the impact analysis can be compared with the same object in two other
layers.
o Review cross-references: The bottom pane of the tool loads the cross-
reference data for the selected object. The data that is presented resembles
the data that is presented in the Cross References Used By view. If cross-
reference data is not available, this pane provides an option to update the
cross-reference data. For new objects that do not exist in the AOT, no cross-
reference data is available.
8. Export the results of the impact analysis, so that you can quickly make changes
after you install the update. The following options are available. We recommend
that you select Impact Analysis State:
o Summary: Save the information about the objects that are loaded in the
form to an XML file that you select. Also save information about the layers
where the objects exist, and the number of cross-references.

o Cross Reference Data: Save more detailed information about the cross-
references of the objects by using Resource Description Format (RDF).
For more information on RDF, see:
http://www.w3.org/RDF/.
o Impact Analysis State (IAS): Save the objects that are loaded in the form to
an XML file. This file has an .ias file extension. After you save the objects to an
.ias file, you can load the same list of objects into the Impact Analysis form
later. This capability is helpful when you install a hotfix, because you might
want to save the list of objects before you start the installation. After the
installation is completed, you can reload the objects for additional analysis.
Install updates to Microsoft Dynamics AX

1. Browse to the location where you extracted the files for the service pack, and
then double-click AxUpdate.exe.
137. On the Welcome to Microsoft Dynamics AX Update Setup page, click Next.
138. On the License terms page, review the license terms. Select the option to
accept the license terms, and then click Next.
139. On the Select components page, in the list of components that can be
updated, select the components to update, and click Next.
If you update a database instance, you can select the name of the instance to
update the local instance. Alternatively, you can select Other to select a remote
instance to update. In this case, a Database instance page is displayed, where
you can select the remote instance.
140. On the Ready to install page, review the summary of the components that
are being updated, and then click Install.
141. When the update is completed, click Finish to close the wizard.
142. After the installation is completed, examine the log files that were created by
AXUpdate.exe. By default, log files are saved to a subfolder of the
%ALLUSERSPROFILE%\Microsoft\Dynamics AX\Dynamics AX Setup Logs
folder.
143. Restart the AOS service for the instance.
Complete the software update checklist

Before the changes to the model store that were included in the update can be fully
implemented, you must complete additional tasks. The software update checklist
helps you complete these tasks.
The checklist is available in application hotfixes and cumulative updates that have a
version number of 6.0.947.339 or later. When you start the client, if you do not see
the Start the software update checklist option that is mentioned in the following
procedure, install hotfix KB2616405.
1. Start the Microsoft Dynamics AX client. When you launch the client, you receive
the following message: "The model store has been modified."
144. Click Start the software update checklist.
145. Complete the items on the checklist, in the order in which they are listed.
Checklist section Option and description
Upgrade Restart Application Object Server
preparation We recommend that you restart the AOS instance before you
start the client. However, if you did not restart the AOS
instance, restart it now by using this option.
Code upgrade Compile application
This option compiles X++ code for the application.
Compilation might require an hour or longer.
Detect code upgrade conflicts
This option creates upgrade projects that contain conflicting
model elements.
Compile into .NET CIL
After you have resolved any conflicts for the code upgrade,
you can use this option to compile the application into CIL
code for the Microsoft .NET Framework.
Data upgrade Detect update scripts (Required)
This option finds and registers update scripts that require
additional processing.
The appearance of the checklist varies, depending on
whether update scripts are detected.
Presynchronize
This option only appears if upgrade scripts were detected.
Synchronize database
This option is required even if update scripts were not
detected.
Launch data upgrade (required)
This option only appears if upgrade scripts were detected.
This option opens the data upgrade checklist.
Upgrade additional features
This option only appears if upgrade scripts were detected. This
option opens the Data upgrade cockpit form.
For more information on see Data upgrade cockpit (form), see:
Test Your Knowledge

Test your knowledge with the following questions.
1. Which of the following initialization checklist steps are required? (Select all that
apply)
( ) Compile application
( ) Generate CIL
( ) Import data
( ) Create legal entities

2. What is the purpose of default ports?
_____ 1. 2712 Services endpoint port

_____ 2. 8101 Services WSDL port
_____ 3. 8201 TCP/IP port
3. When should a single-computer deployment be used?

( ) Production system
( ) Test system
( ) When using an existing database
( ) When a custom port is desired
4. Which users can manage the Configuration Utility? (Select all that apply)
( ) All users
( ) Power users
( ) Administrators
( ) Guests
5. Categorize the following items by determining which configuration utility is used
to complete each task.
Categories (Configuration Utilities):
a. Only the Microsoft Dynamics AX 2012 Server Configuration Utility
b. Only the Microsoft Dynamics AX 2012 Configuration Utility
c. Both Configuration Utilities Configuration Utility
d. Neither Configuration Utility
_____ Item 1: Determine which AOS the client should connect to.
_____ Item 2: Determine which database the AOS should connect to.
_____ Item 3: Determine where the installation files are stored.
_____ Item 4: Determine where the application file system is located.
_____ Item 5: Determine which company the client should open on startup.
_____ Item 6: Determine the database tuning

02-Ax 2012 Admin Wkshp-Installation and Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02-Ax 2012 Admin Wkshp-Installation and Configuration

Uploaded by

Copyright:

Available Formats

Microsoft Dynamics AX 2012

© 2015 Microsoft Corporation. All rights reserved.

For more information, see Use of Microsoft Copyrighted Content at

© 2015 Microsoft Corporation

Servers in a Minimum Installation of Microsoft Dynamics AX......................................................3

Servers in a Complete Installation of Microsoft Dynamics AX.......................................................4

Other Servers in the Environment................................................................................................. 4

Install Microsoft Dynamics AX Databases..................................................................................... 9

Install AOS Server(s)................................................................................................................... 12

Server and Client Configuration.................................................................................................. 25

MICROSOFT DYNAMICS AX 2012 SERVER CONFIGURATION..........................................................................26

Microsoft Dynamics AX 2012 Server Configuration Utility Settings.............................................27

AX 2012 Server Configuration Utility Settings: Best Practices.....................................................30

MICROSOFT DYNAMICS AX 2012 (CLIENT) CONFIGURATION.........................................................................32

Microsoft Dynamics AX 2012 (client) Configuration Utility Settings............................................33

Microsoft Dynamics AX 2012 (client) Configuration Utility Settings: Best Practices....................35

SERVICE PACKS AND UPDATES..................................................................................................................38

© 2015 Microsoft Corporation

Deployment Process for Updates................................................................................................ 39

Naming Convention for Update Packages..................................................................................39

Update Package Structure.......................................................................................................... 40

Process for Installing Updates.................................................................................................... 41

Install Updates to Database, AOS, and Clients...........................................................................43

TEST YOUR KNOWLEDGE.........................................................................................................................47

© 2015 Microsoft Corporation

Chapter 2: Installation and Configuration

 Review the various installation types and servers required.

 Install the database, Application Object Server (AOS), and client.

 Complete the initialization checklist after installing

 Review how to check and interpret the build numbers.

 Review and use the client and server configuration utilities.

 Review the process for installing service packs and updates.

 Focusing their sales efforts on their best customers.

 Extending their product availability through an external website.

 Reducing their cost of sales through reduced production costs.

© 2015 Microsoft Corporation

© 2015 Microsoft Corporation

 Reporting Services extensions

 Analysis Services configuration

 Microsoft Office add-ins

 Remote Desktop Services integration

 Visual Studio Tools

 .NET Business Connector

Considerations for Installing Multiple Instances on One Computer

Caution: It is not recommended or supported installing multiple versions of

© 2015 Microsoft Corporation

The following table lists considerations when installing a second instance of a

Servers in a Minimum Installation of Microsoft Dynamics AX

Application Object Server

Servers in a Complete Installation of Microsoft Dynamics AX

© 2015 Microsoft Corporation

Other Servers in the Environment

Before you begin

 Create service accounts (http://technet.microsoft.com/en-

 Create a shared directory for installation (http://technet.microsoft.com/en-

© 2015 Microsoft Corporation

 Configure SQL Server and storage settings (http://technet.microsoft.com/en-

 Include service packs and updates in a new installation (slipstreaming).

 Make sure the appropriate firewall ports are opened

 Verify that you have the required permissions for installation

 Check prerequisites (http://technet.microsoft.com/en-us/library/gg731884.aspx)

Procedure: Create a shared directory for installation

a. Give the Administrator group full control, or owner access.

8. Copy the contents of the Microsoft Dynamics AX DVD to the AX2012DVD