Microsoft Dynamics Nav Mac Client

Return to site

Microsoft Dynamics Nav Mac Client

-->Microsoft Dynamics Nav 2018The following Dynamics NAV clients interact with the Dynamics NAV database through Microsoft Dynamics NAV Server:
Microsoft Dynamics NAV Windows client
Microsoft Dynamics NAV Web client
Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client
Of these client types, the Microsoft Dynamics NAV Windows client is the only one that you explicitly install and configure with Dynamics NAV Setup.
How to Connect Xbox 360 Controller to Mac: This will show you how to connect Xbox 360 controller to Macintosh. Get Microsoft Wireless Receiver. You will need the wireless receiver if you use a wireless xbox 360 controller. If you have a wired xbox 360. Microsoft 360 wireless receiver mac. Aug 17, 2018  Connect the Xbox 360 Controller to your Mac Now you've installed the driver, the next step is to connect the controller, which is simple and only needs to be done once. Firstly, you need to plug the USB receiver into a free USB port on your Mac.
Quickly access one of these emergency contacts in a time of need with just a button push, by pressing the First Responder icon and then option to whom you need to call, saving precious time by eliminating the need to open your phone and dial. Single click to play an emergency siren sound to. Choose Office for your Mac and PC Create your best work with Office 365, and get 1 TB of OneDrive cloud storage for your photos and files. The Office experience you know and love, built for your Mac, PC, iOS and Android devices. Mar 19, 2020  Welcome to the Office Insider for Mac community! On behalf of the Office Insider team, I'd like to welcome you to the new Office Insider for Mac community! We've put together a short Q&A for those who are new to the program. Install Office for Mac now Office 365 customers get the new Office for Mac first. You'll have Office applications on your Mac or PC, apps on tablets and smartphones for when you're on the go, and Office Online on the web for everywhere in between. Made with Mac in mind, Office 2016 for Mac gives you access to your favorite Office applications - anywhere, anytime and with anyone. Includes new versions of Word, Excel, PowerPoint, Outlook, and OneNote. See what's new in Office 2016. Your school may offer Office 2016 for Mac for free. Search for your school below to claim this academic deal. https://daygradlerso1985.mystrikingly.com/blog/add-a-blog-post-title-7865258c-f094-49f7-9f59-8901c8d85703.
In addition, the following service types also interact with the Dynamics NAV database through Microsoft Dynamics NAV Server:
SOAP web services
OData web services
NAS services
You can configure a server instance for RoleTailored clients, SOAP and OData web services, and NAS connections using either the Microsoft Dynamics NAV Server Administration Tool or Microsoft Dynamics NAV Windows PowerShell Cmdlets.
Is there a way around installing Nav 2015 client onto Mac Book. And probably a way of accesing the server while not on the company LAN from either window client or Mac. Microsoft for mac air download. Administration and Setup Client MacBook Microsoft Dynamics NAV 2015 WAN CONNECTION.
 Microsoft Dynamics NAV Windows clientThe Microsoft Dynamics NAV Windows client is an intuitive and versatile Windows application that developers, partners, administrators, and super users can customize to support the job functions of a full range of work roles in an organization.

Microsoft dynamics nav mac client download

For each role, the Microsoft Certified Partner or developer creates a customizable Role Center that displays key information required for relevant employees and makes their day-to-day tasks easier to complete. Users run the RoleTailored client to find the information and data entry points that their jobs require.
The Microsoft Dynamics NAV Windows client is installed when you select the Demo Option, Client Option, or Developer Option in Dynamics NAV Setup. The Microsoft Dynamics NAV Windows client is available in a 32-bit version and 64-bit version. The 32-bit version of the Microsoft Dynamics NAV Windows client can be run on either a 32-bit or 64-bit version of a Windows operating system. The 64-bit version of the Microsoft Dynamics NAV Windows client can only be run on a 64-bit version of a Windows operating system. On a 64-bit Windows operating system, the 64-bit version of the Microsoft Dynamics NAV Windows client is used by default, but you can to run the 32-bit version as well. For more information, see Running 32-Bit Microsoft Dynamics Windows Client on 64-Bit Windows.
Microsoft Dynamics NAV Web clientThe Microsoft Dynamics NAV Web client is an alternative to the Microsoft Dynamics NAV Windows client that enables you to access Dynamics NAV data over the Internet. From a web browser, you can view and edit data by using an interface that is similar to the Microsoft Dynamics NAV Windows client. Install the Web Server components to get the software that you need to set up a Microsoft Dynamics NAV Web client. For more information, see Microsoft Dynamics NAV Web Client.
Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone clientThe Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client allow users in small and medium sized businesses to access data from a tablet or a phone. Developing for Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client is very similar to developing for the Microsoft Dynamics NAV Web client using the Microsoft Dynamics NAV Development Environment. For more information, see Developing for the Microsoft Dynamics NAV Universal App.
SOAP Web ServicesSOAP web services allow full flexibility for building operation-centric services. This includes industry standard interoperability, as well as channel and host plug-ability. For web services that must interoperate with Java or use channels other than HTTP, SOAP services are the only option. Windows Communication Framework (WCF) has supported SOAP services since its initial release in .NET Framework 3.0, and .NET Framework 4 adds additional support and default bindings to make it easier to build SOAP services using WCF. You define and publish Microsoft Dynamics NAV 2018 SOAP web services in the RoleTailored client, and manage them from the Microsoft Dynamics NAV Server Administration tool. See SOAP Web Services for further information.
OData Web ServicesOData services are recommended for client applications that require a uniform, flexible, general purpose. They are less suited for applications that are primarily method-oriented or in which data operations are constrained to certain prescribed patterns. OData supports Representational State Transfer (REST)-based data services, which enable resources, identified using Uniform Resource Identifiers (URIs), and defined in an abstract data model (EDM), to be published and edited by web clients within corporate networks and across the Internet using simple Hypertext Transfer Protocol (HTTP) messages. OData services are lightweight, with functionality often referenced directly in the URI. You define and publish Microsoft Dynamics NAV 2018 OData web services in the RoleTailored client, and manage them from the Microsoft Dynamics NAV Server Administration tool. See OData Web Services for further information.
NAS ServicesNAS services are a middle-tier server component that executes business logic without a user interface or user interaction. NAS services are intended for task scheduling, client offloading, and specialized integration scenarios. NAS services replace the NAV Application Server (NAS) available in earlier versions of Dynamics NAV. You manage NAS services from the Microsoft Dynamics NAV Server Administration tool. See Configuring NAS Services for further information.
See AlsoProduct and Architecture Overview
Installation Options
Web Service Alternatives: SOAP and OData
Microsoft Dynamics NAV Server Administration Tool
-->

For each role, the Microsoft Certified Partner or developer creates a customizable Role Center that displays key information required for relevant employees and makes their day-to-day tasks easier to complete. Users run the RoleTailored client to find the information and data entry points that their jobs require.
The Microsoft Dynamics NAV Windows client is installed when you select the Demo Option, Client Option, or Developer Option in Dynamics NAV Setup. The Microsoft Dynamics NAV Windows client is available in a 32-bit version and 64-bit version. The 32-bit version of the Microsoft Dynamics NAV Windows client can be run on either a 32-bit or 64-bit version of a Windows operating system. The 64-bit version of the Microsoft Dynamics NAV Windows client can only be run on a 64-bit version of a Windows operating system. On a 64-bit Windows operating system, the 64-bit version of the Microsoft Dynamics NAV Windows client is used by default, but you can to run the 32-bit version as well. For more information, see Running 32-Bit Microsoft Dynamics Windows Client on 64-Bit Windows.
Microsoft Dynamics NAV Web clientThe Microsoft Dynamics NAV Web client is an alternative to the Microsoft Dynamics NAV Windows client that enables you to access Dynamics NAV data over the Internet. From a web browser, you can view and edit data by using an interface that is similar to the Microsoft Dynamics NAV Windows client. Install the Web Server components to get the software that you need to set up a Microsoft Dynamics NAV Web client. For more information, see Microsoft Dynamics NAV Web Client.
Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone clientThe Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client allow users in small and medium sized businesses to access data from a tablet or a phone. Developing for Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client is very similar to developing for the Microsoft Dynamics NAV Web client using the Microsoft Dynamics NAV Development Environment. For more information, see Developing for the Microsoft Dynamics NAV Universal App.
SOAP Web ServicesSOAP web services allow full flexibility for building operation-centric services. This includes industry standard interoperability, as well as channel and host plug-ability. For web services that must interoperate with Java or use channels other than HTTP, SOAP services are the only option. Windows Communication Framework (WCF) has supported SOAP services since its initial release in .NET Framework 3.0, and .NET Framework 4 adds additional support and default bindings to make it easier to build SOAP services using WCF. You define and publish Microsoft Dynamics NAV 2018 SOAP web services in the RoleTailored client, and manage them from the Microsoft Dynamics NAV Server Administration tool. See SOAP Web Services for further information.
OData Web ServicesOData services are recommended for client applications that require a uniform, flexible, general purpose. They are less suited for applications that are primarily method-oriented or in which data operations are constrained to certain prescribed patterns. OData supports Representational State Transfer (REST)-based data services, which enable resources, identified using Uniform Resource Identifiers (URIs), and defined in an abstract data model (EDM), to be published and edited by web clients within corporate networks and across the Internet using simple Hypertext Transfer Protocol (HTTP) messages. OData services are lightweight, with functionality often referenced directly in the URI. You define and publish Microsoft Dynamics NAV 2018 OData web services in the RoleTailored client, and manage them from the Microsoft Dynamics NAV Server Administration tool. See OData Web Services for further information.
NAS ServicesNAS services are a middle-tier server component that executes business logic without a user interface or user interaction. NAS services are intended for task scheduling, client offloading, and specialized integration scenarios. NAS services replace the NAV Application Server (NAS) available in earlier versions of Dynamics NAV. You manage NAS services from the Microsoft Dynamics NAV Server Administration tool. See Configuring NAS Services for further information.
See AlsoProduct and Architecture Overview
Installation Options
Web Service Alternatives: SOAP and OData
Microsoft Dynamics NAV Server Administration Tool
-->When you install the Microsoft Dynamics NAV Windows client, the Specify Parameters page in Dynamics NAV Setup prompts you for configuration information to enable the Microsoft Dynamics NAV Windows client to connect to Microsoft Dynamics NAV Server. This information is then saved in the default ClientUserSettings.config file.
A separate instance of the ClientUserSettings.config file is maintained for each user of the computer. The default location for this file is C:UsersAppDataRoamingMicrosoftMicrosoft Dynamics NAV110, where  is the name of the user. This folder and file are hidden by default. Change your folder options in Windows Explorer to view hidden files before you attempt to modify the ClientUserSettings.config file.
Configuring the Microsoft Dynamics NAV Windows Client in SetupIf you install the Demo Option, you are not prompted for configuration information, because all Dynamics NAV components are automatically installed on the local computer. If you install using any other installation option, you must provide some initial configuration information to enable the Microsoft Dynamics NAV Windows client to establish a connection with an instance of Microsoft Dynamics NAV Server.
In Setup, select one of the following Installation Options to install the Microsoft Dynamics NAV Windows client:
You can also customize your installation and customize the list of components to install. For more information, see How to: Choose Components to Install.
After you specify an installation option or customize your component list, the Specify parameters pane is displayed in Setup. The list of parameters that you see in the Specify parameters pane depends on which components that you have selected for configuration. Setup provides a short description for each parameter. For a description of the most important parameters for the Microsoft Dynamics NAV Windows client, see Client Option.
Choose Apply when you have finished entering values on the Specify parameters page in Setup. If you want to change the configuration after installation, you can modify the ClientUserSettings.config file for each client.
 Configuring the Microsoft Dynamics NAV Windows Client After InstallationMicrosoft 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:ProgramDataMicrosoftMicrosoft Dynamics NAV110. The first time a user runs the Microsoft Dynamics NAV Windows client, a copy of ClientUserSettings.config is copied to C:UsersAppDataRoamingMicrosoftMicrosoft Dynamics NAV110, 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:ProgramDataMicrosoftMicrosoft Dynamics NAV110. You must run your text editor with Administrator permissions when you do this.
Microsoft 2008 for mac product key. This release was created for you, eager to use microsoft office 2008 sp2 12.2 mac full and with without limitations.Our intentions are not to harm microsoft software company but to give the possibility to those who can not pay for any pieceof software out there. Nothing can stop us, we keep fighting for freedomdespite all the difficulties we face each day.Last but not less important is your own contribution to our cause. This should be your intention too, as a user, to fully evaluate microsoft office 2008 sp2 12.2 mac withoutrestrictions and then decide.If you are keeping the software and want to use it longer than its trial time, we strongly encourage you purchasing the license keyfrom microsoft official website. Our releases are to prove that we can!
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:UsersAppDataRoamingMicrosoftMicrosoft Dynamics NAV110 folder. After you modify a user's ClientUserSettings.config file, you must restart the Microsoft Dynamics NAV Windows client for changes to take effect.
Microsoft Dynamics Nav Mac Client SoftwareIn 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 FileThe 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.
Microsoft Dynamics Nav InstallationSettingDescription
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.
UseRegionalSettingsFromPersonalizationSets the value indicating whether to use the time and regional settings for the Microsoft Dynamics NAV Windows client from the UserPersonalization table instead of operation system.
 Each client session uses a time and regional setting. You can use this setting to ensure that the time and regional settings for the Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client are the same, in order to minimize confusion for users that work in both clients. The Microsoft Dynamics NAV Web client gets the settings from the UserPersonalisation table. Users can change this setting from the MySettings page or User Personalization page. However, the Microsoft Dynamics NAV Windows client by default uses the time and regional settings of the operation system (OS) of user's computer.
true specifies to use UserPersonalization; false specifies to use the operating system.
 Default value: false
Microsoft Dynamics Nav ClientSee AlsoConfiguring Microsoft Dynamics NAV Server
Configuring Microsoft Dynamics NAV Help Server
Configuring Microsoft Dynamics NAV

Setting	Description
Server	Specifies 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.
ClientServicesPort	Specifies the listening TCP port for the Microsoft Dynamics NAV Server instance that the client connects to. Default value: 7046
ServerInstance	Specifies 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.
TenantID	Specifies the tenant that the client connects to in a multitenant deployment. For more information, see Multitenant Deployment Architecture. Default value: '
ClientServicesProtectionLevel	Specifies 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
UrlHistory	Specifies 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.
ClientServicesCompressionThreshold	Specifies the threshold in memory consumption at which the Microsoft Dynamics NAV Windows client starts compressing datasets, in kilobytes. Default: 64
ClientServicesChunkSize	Specifies the default size for a chunk, in kilobytes. Default: 28. The range of values is from 4 to 80.
MaxNoOfXMLRecordsToSend	Specifies 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.
MaxImageSize	Specifies the maximum image size (in bytes) allowed by validation. Default: 26214400
ClientServicesCredentialType	Specifies 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
ACSUri	Specifies 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: '
AllowNtlm	Specifies whether NTLM fallback is permitted for authentication. To require Kerberos authentication, set this value to false. Default value: true
ServicePrincipalNameRequired	If 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
ClientServicesCertificateValidationEnabled	Specifies 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
DnsIdentity	Specifies 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.
HelpServer	Specifies the name of the computer than hosts the Dynamics NAV Help Server.
HelpServerPort	Specifies the TCP listening port for the Dynamics NAV Help Server. Default: 49000
UnknownSpnHint	Specifies 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.
EnableLegacyControlAddIn	Specifies 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.
UseRegionalSettingsFromPersonalization	Sets the value indicating whether to use the time and regional settings for the Microsoft Dynamics NAV Windows client from the UserPersonalization table instead of operation system. Each client session uses a time and regional setting. You can use this setting to ensure that the time and regional settings for the Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client are the same, in order to minimize confusion for users that work in both clients. The Microsoft Dynamics NAV Web client gets the settings from the UserPersonalisation table. Users can change this setting from the MySettings page or User Personalization page. However, the Microsoft Dynamics NAV Windows client by default uses the time and regional settings of the operation system (OS) of user's computer. true specifies to use UserPersonalization; false specifies to use the operating system. Default value: false