It is time to share with you the scripts that I am using to install and update the NAV application in the company network. In the attached ZIP packages you will find a lot of files.
In the root folder I keep the settings files. These files must be customized. The folders are as follows;
- Edge3-Internet – my internet facing server. Here I install ClickOnce, WebClient and NAV Service.
- Fjarvinna-Domain – my remote desktop server. Here I install KB updates remotely.
- Localhost-Domain – my intranet server. Here I install NAV Service for the domain.
- NAVCmdLets – my collection of PowerShell scripts for NAV. Some a copied from the NAV DVD.
- Install-KBLocally – scripts to install a KB package to the local computer.
If we first look at the Edge3-Internet folder, here I have scripts to remotely install NAV on a server. I usually create a ClickOnce container in the folder ‘c:\inebpub\ClickOnce’ and keep all my ClickOnce subfolders in there. In the Set-MachineSettings.ps1 file I set the machine name.
Next, in Fjarvinna-Domain folder I only have scripts to upload and install a KB package. Also in here I have the Set-MachineSettings.ps1 to define the machine name.
The Localhost-Domain folder includes scripts to install NAV Service and NAV Users to the localhost.
Then there are the functions that I use in the above scripts. In the NAVCmdLets folder I have a collection of scripts to handle ClickOnce, KB install and some SQL administration tasks.
Finally the Install-KBLocally folder. As the name suggest, the contained scripts are used to install a KB package on the localhost. I usually create a folder that contains this folder, the NAVCmdLets folder and for example the KB2955941 folder. The KB2955941 can be downloaded from Microsoft. I usually delete all sub folders except ADCS, NST, OUTLOOK, RTC and WEB CLIENT after I add this folder to the update package.
Also, in my KB package I have two CMD files. One to install to a 64bit machine (default) and the other to a 32bit machine. If you put this package on your network and modify the CMD files to point to the correct file share you should be able to use this for all the computers on the domain. The KB package without the Microsoft binaries is attached below. Make sure to right-click on the install CMD file and run as administrator for a succesful install.
With your network administration tools you should be able to use some of these scripts to install a KB package on all your domain computers to make sure that everyone is running the latest version recommended by Microsoft.