Windows Logo Certification for Microsoft Dynamics AX 2012 Setup

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic provides information for the Windows Server Logo certification for the Microsoft Dynamics AX 2012 installer.

Application Verifier Stop Codes

As documented in the Microsoft Dynamics AX 2012 Installation Guide, only elevated administrators may run Setup. Because the Setup and Microsoft Installer processes are running as administrators, several 331B stop codes are generated. Since Setup cannot be run as a standard, untrusted user, these errors can safely be ignored.

Valid File Versions

All files that are delivered with Microsoft Dynamics AX 2012 have valid file version information, with the following exceptions.

Interop Files

These files are generated for interop, and necessarily do not have file version information.

• Interop.NetFwTypeLib.dll

• Interop.WUApiLib.dll

• Interop.COMAdmin.dll

• AxInterop.WMPLib.dll

Third-Party Files

The following files are generated by SQL Server Reporting Services and are not controlled by Microsoft Dynamics AX.

• %PROGRAMFILES%\Microsoft SQL Server\%SQLINSTANCE%\ReportingServices\ReportManager\Bin\ReportingServicesCDOInterop.dll

• %PROGRAMFILES%\Microsoft SQL Server\%SQLINSTANCE\Reporting Services\ReportServer\bin\ReportingServicesCDOInterop.dll

• c:\Program Files (x86)\Microsoft Visual Studio 10.0\common7\IDE\PrivateAssemblies\WMPLib.dll

• c:\Program Files (x86)\Microsoft Visual Studio 10.0\common7\Tools\Deployment\VsdProjects\vsibinver.dll

Generated Files

These files are not installed by Microsoft Dynamics AX 2012 Setup. Rather, during its normal operation, Microsoft Dynamics AX 2012 generates files in the following locations:

• %PROGRAMFILES%\Microsoft Dynamics AX\60\Server\%AXINSTANCENAME%\bin\XppIL\

• %PROGRAMFILES%\Microsoft SQL Server\%INSTANCENAME%\Reporting Services\bin

• %PROGRAMFILES%\Microsoft SQL Server\%INSTANCENAME%\Reporting Services\RSTempFiles\

These files are generated directly from the Microsoft Dynamics AX layered application metadata. This metadata can be customized by third-party vendors, ISVs, and customers. Because of this, these files can be regenerated at any time. It would be technically and legally incorrect for Microsoft to version these files.

Executable files requiring elevation

It is normal for the following executable files in Microsoft Dynamics AX 2012 to request UAC elevation:

• AxSearchSetup.exe – This executable configures the Windows Search Service and Windows Search Server for use with Microsoft Dynamics AX 2012, which requires elevated administrative privileges.

• AxUpdatePortal.exe – This executable configures SharePoint for use with Microsoft Dynamics AX 2012, which requires elevated administrative privileges.

• Microsoft.Dynamics.AX.Tracing.TraceParser.exe - Trace Parser is a developer tool that creates new SQL Server databases for analyzing Microsoft Dynamics AX traces, requiring full permissions on the databases that it operates on. The most common user scenario is that developers connect the Trace Parser to their local SQL server instances, requiring administrative privileges.

Files without valid file signatures

All files that are delivered with Microsoft Dynamics AX have valid file signatures. However, during its normal operation, Microsoft Dynamics AX 2012 generates files in the following locations that are not signed.

Generated files

• %PROGRAMFILES%\Microsoft Dynamics AX\60\Server\%AXINSTANCENAME%\bin\XppIL\

• %PROGRAMFILES%\Microsoft SQL Server\%INSTANCENAME%\Reporting Services\bin

• %PROGRAMFILES%\Microsoft SQL Server\%INSTANCENAME%\Reporting Services\RSTempFiles\

These files are generated directly from the Microsoft Dynamics AX layered application metadata. This metadata can be customized by third-party vendors, ISVs, and customers. Because of this, these files can be regenerated at any time. It would be technically and legally incorrect to sign these files, as they are not fully owned by Microsoft.

Third-Party Files

• %Program Files (x86) %\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies\

Custom Actions performed during Setup

During the installation of Microsoft Dynamics AX 2012, several .msi files perform custom actions.

Custom actions not owned by Microsoft Dynamics AX 2012

The following .msi files, though redistributed by Microsoft Dynamics AX 2012, are not part of the product, and should be ignored. Custom actions for these .msi files should have been documented by the teams producing the redistributables.

• OpenXMLSDKTool.msi

• OpenXMLSDKv2.msi

• sqlncli.msi

• sqlncli_X64.msi

• SQLSERVER2008_ASADOMD10.msi

Custom actions owned by Microsoft Dynamics AX 2012

The following custom actions are performed in .msi files owned by Microsoft Dynamics AX 2012. Note that some custom actions are included by default in the WiX framework. Documentation for this framework can be found at http://wix.sourceforge.net/.

Artifacts remaining after uninstallation

The following artifacts are not removed when Microsoft Dynamics AX is uninstalled.

Files and Folders

• %INETPUB%\wwwroot\wss\VirtualDirectories\80\App_Code

  Items in this folder are from ASP.NET. However, other applications may have dependencies on files in the app_code folders. If this were the case, deleting this folder with Microsoft Dynamics AX would break other functionality.

• %INETPUB%\wwwroot\wss\VirtualDirectories\80\App_Code\Proxies

  The Proxies folder is created by Enterprise Portal but left after uninstallation, because it could be used by other pages that get data from Microsoft Dynamics AX. Removing this folder would also require modifying the web.config file, which is against generally accepted uninstallation practices. It is not possible to differentiate between changes to the web.config file performed by Setup and those performed by an administrator. Were Setup to remove this folder, it could break web configurations not related to Microsoft Dynamics AX.

• Setup logs - We do not remove the Setup logs as these may be needed for system diagnostic purposes. If desired, these folders may be deleted manually.

  • %PROGRAMFILES%\Microsoft Dynamics AX

  • %PROGRAMFILES%\Microsoft Dynamics AX\60

  • %PROGRAMFILES%\Microsoft Dynamics AX\60\Setup Logs

• SharePoint and Enterprise Search files – These files are not directly created by Microsoft Dynamics AX.

  • %PROGRAMFILES%\Microsoft Office Servers

  • %PROGRAMFILES%\Microsoft Office Servers\14.0\Data\Applications\

• SQL Server Reporting Services generated content - Some of this content may be user-generated.

  • %PROGRAMFILES%\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services

Registry entries

A number of registry keys may be left over following the uninstallation of Microsoft Dynamics AX 2012.

1. Client Registry keys – The Microsoft Dynamics AX Client creates a number of registry keys in the following nodes. These registry keys are used by the Client.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\

   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes

2. Outlook Integration keys - Keys in this registry hive are used for integration with Microsoft Outlook.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\CLSID

   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\COM3\SelfReg\CLSID

3. Setup registry keys - This registry hive tracks the location where Microsoft Dynamics AX components are installed, which can be used by component .msi files. Because Setup can be uninstalled before other components, this information persists outside Setup.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\6.0\Setup

   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Dynamics\6.0\Setup

4. SharePoint keys - Keys in this registry hive are automatically generated by SharePoint Server and cannot be controlled by Microsoft Dynamics AX.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeServer

5. Windows Event Tracing keys - These registry keys are generated by Crimson tracing registration, and are needed after uninstallation to view tracing events.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

6. Windows Installer keys - Keys in this registry hive are maintained by Windows Installer and cannot be controlled by Microsoft Dynamics AX.

   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders

7. Control set keys - These registry hives contain information about the current and last-known good control sets for Windows. They should be automatically cleaned up when the system is restarted.

   • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\LanmanServer\Shares

   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Shares