Saturday, May 12, 2018

Configuring the Microsoft Dynamics NAV Windows Client After Installation

Source: https://docs.microsoft.com/en-us/dynamics-nav/Configuring-the-Windows-Client

Microsoft Dynamics NAV 2018 Setup installs ClientUserSettings.config, the default configuration file, with the values that you provided as you ran Setup. This file is stored in C:\ProgramData\Microsoft\Microsoft Dynamics NAV\110. The first time a user runs the Microsoft Dynamics NAV Windows client, a copy of ClientUserSettings.config is copied to C:\Users\\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\110, where is the name of the user. This folder and file are hidden by default.
If you want to change default Microsoft Dynamics NAV Windows client settings for all future users on this computer, edit the default ClientUserSettings.config file in C:\ProgramData\Microsoft\Microsoft Dynamics NAV\110. You must run your text editor with Administrator permissions when you do this.
If you want to change Microsoft Dynamics NAV Windows client settings for an existing user, edit the ClientUserSettings.config file in that user’s C:\Users\\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\110 folder. After you modify a user’s ClientUserSettings.config file, you must restart the Microsoft Dynamics NAV Windows client for changes to take effect.
In addition to the settings that you can configure in Setup, the ClientUserSettings.config file contains other settings for the Microsoft Dynamics NAV Windows client.

Settings in the ClientUserSettings.config File

The ClientUserSettings.config file is an .xml file that you can edit with any text editor. Quotation marks are required for all values.
The following settings are available.
SettingDescription
ServerSpecifies the name of the computer that is running Microsoft Dynamics NAV Server for this client.

Default value: Empty string if you installed by using the Client installation option, or localhost if you installed by using the Developer Environment installation option or a custom installation.
ClientServicesPortSpecifies the listening TCP port for the Microsoft Dynamics NAV Server instance that the client connects to.

Default value: 7046
ServerInstanceSpecifies the name of the Microsoft Dynamics NAV Server instance that the client connects to.

Default value: DynamicsNAV110

For more information, see Managing Microsoft Dynamics NAV Server Instances.
TenantIDSpecifies the tenant that the client connects to in a multitenant deployment. For more information, see Multitenant Deployment Architecture.

Default value: ""
ClientServicesProtectionLevelSpecifies the security services for protecting the client/server data stream. This value must match the value that is specified in the Microsoft Dynamics NAV Server configuration file. For more information, see Configuring Microsoft Dynamics NAV Server.

Default: EncryptAndSign

Values: EncryptAndSign, Sign, None
UrlHistorySpecifies a comma-delimited list of Microsoft Dynamics NAV Server connections that is displayed in the Select Server window when you choose the drop-down arrow in the Server name field.

This parameter is not available after you install the Microsoft Dynamics NAV Windows client, but it is created and populated after the user enters a server name in the field.

You can create and populate this field after you install the Microsoft Dynamics NAV Windows client. This gives the user a list of servers from which to choose.

Example:



Each value must contain a computer name and can optionally also include a port number and a Microsoft Dynamics NAV Server instance. Defaults are assumed if either value is missing.
ClientServicesCompressionThresholdSpecifies the threshold in memory consumption at which the Microsoft Dynamics NAV Windows client starts compressing datasets, in kilobytes.

Default: 64
ClientServicesChunkSizeSpecifies the default size for a chunk, in kilobytes.

Default: 28.

The range of values is from 4 to 80.
MaxNoOfXMLRecordsToSendSpecifies the maximum number of data rows that can be sent as XML during export to Word or Excel.

Default: 5000

Note: This setting does not pertain to data in lists. The limit for list type pages is configured on the Microsoft Dynamics NAV Server instance. For more information, see Configuring Microsoft Dynamics NAV Server.
MaxImageSizeSpecifies the maximum image size (in bytes) allowed by validation.

Default: 26214400
ClientServicesCredentialTypeSpecifies how Microsoft Dynamics NAV Windows client users are authenticated when they connect to Microsoft Dynamics NAV Server.

For more information, see Users and Credential Types.

This parameter value must be the same as the Credential Type setting for the Microsoft Dynamics NAV Server instance that the client is configured to connect to. For more information, see Configuring Microsoft Dynamics NAV Server.

Default value: Windows
ACSUriSpecifies the web location where the Microsoft Dynamics NAV Windows client goes to authenticate the client user.

This parameter is only relevant if the ClientServicesCredentialType is set to ACS.

Default value: ""
AllowNtlmSpecifies whether NTLM fallback is permitted for authentication.

To require Kerberos authentication, set this value to false.

Default value: true
ServicePrincipalNameRequiredIf this parameter is set to true, then the client can only connect to a Microsoft Dynamics NAV Server instance that has been associated with a service principal name (SPN).

If this parameter is set to false, then the client attempts to connect to the configured Microsoft Dynamics NAV Server instance, regardless of whether that instance is associated with an SPN.

Default: false
ClientServicesCertificateValidationEnabledSpecifies whether to enforce validation of the certificate.

In a production environment, setting this parameter to true is strongly recommended.

When validation is enabled, the certificate must be trusted, not revoked, and the CN name should match the URL of your service.

When validation is disabled, you can use a self-signed certificate without a revocation list and no constraint on the CN name.

Default: true
DnsIdentitySpecifies the subject name of the service certificate for Microsoft Dynamics NAV Server. The Microsoft Dynamics NAV Windows client makes sure that the certificate that is provided during the SSL handshake contains a Domain Name System (DNS) or CommonName (CN) attribute that is equal to the DNS identity of the client. This check is performed in addition to determining the validity of the server certificate.

Default: ""

For more information, see Connecting the Microsoft Dynamics NAV Clients over a Wide Area Network.
HelpServerSpecifies the name of the computer than hosts the Dynamics NAV Help Server.
HelpServerPortSpecifies the TCP listening port for the Dynamics NAV Help Server.

Default: 49000
UnknownSpnHintSpecifies whether to use server principal name when establishing the connection between the Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Server. This setting is used to authenticate the Microsoft Dynamics NAV Server. You set the values that are based on the value of the ServicePrincipalNameRequired key.

Value: The value has the following format.

* (net.tcp://NavServer:Port/ServerInstance/Service)=NoSpn|SPN

* NavServer is the name of the computer that is running the Microsoft Dynamics NAV Server.

* Port is the port number on which the Microsoft Dynamics NAV Server is running.

* ServerInstance is the name of the Microsoft Dynamics NAV Server instance.

* NoSpn|SPN specifies whether to use an SPN. If the ServicePrincipalNameRequired key is set to false, then set this value to NoSpn. If the ServicePrincipalNameRequired key is set to true, then set this value to Spn.

Default value: (net.tcp://localhost:7046/DynamicsNAV110/Service)=NoSpn

This setting is updated automatically.
EnableLegacyControlAddInSpecifies that control add-ins run in IE7 mode instead of IE11 mode. Important: With this parameter you enable IE7 mode for all control add-ins and this means that if you also have newer control add-ins, these will not run.

No comments:

Post a Comment

Business Central SaaS Extension Design: Implementing Plant Tracking with AL Event Subscribers

  Extending Business Central SaaS: Plant Tracking Using AL Extensions  1️⃣ Problem Statement In many manufacturing and service-oriented or...