With the Microsoft Dynamics NAV 2013 Set up function you can now easily install different components on different computers.
When you run the Microsoft Dynamics NAV 2013 Set Up you have the choice to install a predefined component package or modify the component contents of an existing package prior to deployment.
With the Developer installation you can also add in components from the full range of Microsoft Dynamics NAV components.
Running the Set Up.exe application provided as part of Microsoft Dynamics NAV 2013 and selecting the Install option displays the Installation Options (component packages) as a tree view.
If you have chosen the ‘Choose an Installation Option’ (rather than ‘Install Demo’), then the ‘Choose an Installation Option’ page appears where you have the choice of the following options to install:
· Client option
· Server option
· Developer option
Select the components that you wish to deploy.
Next, preconfigure the parameters for the installation which will have been defaulted as part of the process.
If the ‘Custom Option’ was selected on the ‘Choose and Installation option’ page, then at this point it is possible to configure the following components dependent on the choice of installation:
· Microsoft Dynamics NAV Server
· Microsoft Dynamics NAV Server Administration tool
· Windows Client
· SQL Server Database components
· Microsoft Dynamics NAV Portal Framework for Sharepoint
· Web Server components
· Microsoft Office Outlook Add-In
· Automatic Data Capture Systems
· ClickOnce Installer Tools
Before applying the parameters defined above, you can save the SetUp configuration which can then be reloaded on the ‘Choose an Installation Option’ page during future installations when choosing ‘Custom Components’
This allows you to create custom deployments that you can distribute to different Users within a company.
ClickOnce Client Deployment
ClickOnce is a component of the Microsoft .NET framework which allows users to install the Windows Client from a URL (Network Share or Web).
· Centralised Configuration of Client Settings (via the ClientUserSettings.config file), e.g. Server Address, Authentication Type.
· Centralised Management of Binary Patches enabling automatic verification of new versions each time the user clicks on the URL.
· Ability to centralise Configuration file Upgrades, e.g. moving users to connect to an alternative server.
· Ability to distribute additional 3rd party assembly components to a user’s desktop.