Scalable Installation Options

NAV 2009 Three-Tiered Environment

You can find more information about installing the three tiers on two computers on MSDN: Walkthrough: Installing the Three Tiers On Two Computers.

The 'Three Tiers on Three Computers' configuration is described here: Walkthrough: Installing the Three Tiers on Three Computers.

 

During the installation you can encounter the configuration problems. The information below will help you to solve them.

 

In case the MS Dynamics NAV 2009 three-tier environment is used with webservices connection and your website is in decentral hosting environment (separate domains for webserver and NAV server) the following is required: VPN connection must be set up between these environments; These domains have to be made trusted. This will allow to delegate user rights (who runs the web application) to the MS Dynamics NAV. Usage of HTTPS without a VPN in the described scenario does not work.

 

• Open the Windows command prompt;
• Fill in the following command:

   setspn -A DynamicsNAV/NAVSERV.yourDomain.yourCompany.com:7046 yourDomain\yourUser
  

  Replace 'yourDomain', 'yourCompany', and 'yourUser' with the appropriate values.
• In order to set up the second service (NAV 2009 Web Service) fill in the following command:

  setspn -A http/NAVSERV.yourDomain.yourCompany.com yourDomain\yourUser
  

  Replace 'NAVSERV' with the name of the computer running Microsoft Dynamics NAV Server, and replace 'yourCompany', 'yourDomain', and 'yourUser' with the actual company, domain, and user account names.

• No SPN is needed for the NAV Service;
• SPN for SQL Service is not needed if SQL is running under NetworkService;
• SPN for SQL Server is needed if SQL Server is running under a Domain account - see 'SQL SPN' at the end of this chapter.

The Delegation tab will only be present after adding the SPN to the domain user account.

• Click 'Start', then click 'Run';
• Type in 'dsa.msc' and click 'OK';
• Expand the 'Domain' and then click on 'Users';
• Locate the domain user account you are using, right click and select 'Properties';
• Under that 'Delegation' tab, select the 'Trust this user for delegation to any service (Kerberos only)', then click 'OK'. (This is not constrained delegation as mentioned in the Walkthrough, but this makes it a little easier to setup delegation. You can always come back after it is setup and working to implement constrained delegation);
• Close the 'Active Directory Users and Computers' window. 

For Constrained delegation, select Trust this user for delegation to specified services only and then select MSSQLSvc.

• Click 'Start', and then click 'Run';
• Type in 'dsa.msc' and click 'OK';
• Expand the 'Domain' and then click on 'Computers';
• Locate the computer name, right click and select 'Properties';
• Under that 'Delegation' tab, select the 'Trust this machine for delegation to any service (Kerberos only)', then click 'OK';
• Close the 'Active Directory Users and Computers' window.

OCL is not required if the NAV Server and SQL Server are on the same machine and the NAV service is running under Network Service account.

• Open Microsoft SQL Server Management Studio;
• Click 'Security' to expand the tree-view, right-click 'Logins', and then select 'New Login'.
  This opens the 'Login - New' dialog box;
• Add the domain user account in the 'Login' name field, using the following format:
  domain\domainUser
• Click 'OK' to exit the 'Login - New' dialog box;
• Click 'Databases', 'Demo Database NAV (6-0)' or other database name, and then click 'Security' to expand the tree view;
• Under 'Security', right-click 'Users', and then select 'New User'.
  This opens the 'Database User - New' dialog box;
• Add the domain user account in the 'User' name and 'Login' name field, using the following format:
  domain\domainUser.

• Click the 'Securables' page;
• Click 'Add', click 'OK', click 'Object Types', check 'Tables' and then click 'OK'. Click 'Browse', check the '[dbo].[Object Tracking]', click 'OK', click 'OK' again.
  In the 'Explicit permissions' check 'Grant' on the 'Select permission';
• Click 'OK' to exit the 'Database User - New' dialog box;
• Close Microsoft SQL Server Management Studio. 

If the NAV server and SQL Server are on different machines and the Network Service account is running the NAV Service, then the Login and OCL must be set up using the same steps but for the machine account rather than the domain user. Use the steps described earlier, but replace the domain account with the machine account with the following form: <domain>\<computername>$.

• Change the 'ClientUserSettings.config' on the computer running the RTC, under the current user's profile, to define that a domain user account is to be used when connecting to the NAV Service tier.
  On Windows Vista or Windows Server 2008, the default location is:
  X:\Users\\AppData\Local\Microsoft\Microsoft Dynamics NAV
  On Windows XP or Windows Server 2003, the default location is:
  X:\Documents and Settings\\Local Settings\Application Data\Microsoft\Microsoft Dynamics NAV
• Add the following key to the file:
  

  <add key="DelegationInfo" value="DomainUser"></add>
  

  There are two possible values: 'NetworkService' and 'DomainUser'. To enable delegation, set the parameter to 'DomainUser'.

 

After confirming all items above and making the necessary changes, be sure to stop and start the NAV Server service before you attempt to re-connect using the RTC. If you still encounter the error message, remember that Kerberos tickets last for ten hours, so if you add/change the SPN, you may either have to wait for any existing tickets to expire or download KerbTray and attempt to expire any existing tickets. This is found in the Windows Server 2003 Resource Kit, which can be downloaded from here.

• ServiceClass: This identifies the general class of service. This is always MSSQLSvc for SQL Server;
• Host: This is the fully qualified domain name DNS of the computer that is running SQL Server;
• Port: This is the port number that the service is listening on;
• yourDomain\yourUser: This is the user which runs the service.

setspn -A MSSQLSvc/SQLSERVER1.yourDomain.yourCompany:1433 yourDomain\yourUser