In the default installation just one NAV Server Service and one NAV Business Web Service is created.

I have found that in real life you need more NAV Server Services, and then you can spread users across them. In one case I created 7 different instances.

Often the documentation suggests names like NAV2, NAV3.. I found it more useful to use names that identify the group of users.
This also makes it easier for users to know which Instance they are using.

Here is the syntax I use.

Create Service NAVAdmin

sc \\pandora-nav create MicrosoftDynamicsNAVServer$NAVAdmin binpath= "F:\Program Files\Microsoft Dynamics NAV\60\ServiceAdmin_WS\Microsoft.Dynamics.Nav.Server.exe $NAVAdmin" DisplayName= "Microsoft Dynamics NAV Server Admin" start= auto type= own depend= NetTcpPortSharing

Set the description of the service (otherwise it will be blank)

sc description MicrosoftDynamicsNAVServer$NAVAdmin "NAV Service used by Admin"

Create a Web Service

SC \\pandora-nav CREATE MicrosoftDynamicsNAVWS$Admin binpath= "F:\Program Files\Microsoft Dynamics NAV\60\ServiceAdmin_WS\Microsoft.Dynamics.Nav.Server.exe $Admin" DisplayName= "Microsoft Dynamics NAV Business WS" type= share

Set the description of the web service

sc description MicrosoftDynamicsNAVWS$Admin "NAV Web Service used by WS"

Cutom.config changes

<add key="ServerInstance" value="DynamicsNAVAdmin"></add>

See http://msdn.microsoft.com/en-us/library/dd301437.aspx for full details, particularly on setting up TCP Port Sharing