NAV 2017 CU2 on Azure


Microsoft Dynamics NAV 2017 CU2 will be released any minute now (it is being deployed to Microsoft Download Servers while I am writing this post), but for once, the Azure Image made it before the MSDN download pages.

The Image is now available in the classic portal and with http://aka.ms/navdemodeploy. The image will be available in the new portal in a few days.

Note: This blog post doesn’t describe what’s new in NAV 2017CU2, you can read about that on the NAV Team Blog.

This blog post only describes what’s new on the Azure Image.

Windows Server 2012R2 AND Windows Server 2016

The NAV 2017 CU2 public gallery image is available in two versions – one based on Windows Server 2012R2 (as all prior NAV images) and one based on Windows Server 2016.

When you query the image list for the latest NAV 2017 image – you will get the Windows Server 2016 version and http://aka.ms/navdemodeploy will as of today deploy a demo environment based on Windows Server 2016. If you want to deploy the Windows Server 2012R2 version, you will have to go to the classic Azure Portal, locate the image and deploy it (remember the endpoints 80, 443, 7046, 7047, 7048, 49000).

There shouldn’t be a lot of differences to you, everything should still work as earlier. One small thing to note is that when you right-click a PowerShell script for the first time and select Run With PowerShell you will (as usual) be prompted for a change of execution policy:

executionpolicy

In Windows 2016, the default answer is No (which means the script cannot run). For the DEMO scripts, you need to answer Yes to this question (which is the default in Windows Server 2012R2).

There are a lot of other changes to Windows Server 2016, which you can read more about here: https://technet.microsoft.com/en-us/windows-server-docs/get-started/what-s-new-in-windows-server-2016

So, if you are thinking: Why does the image also come as Windows Server 2012R2? The answer is really simple: It never rains when you bring an umbrella:-)

Translations on the SharePoint Portal

When deploying a NAV 2017CU1 demo environment, some languages did have some translation errors, which caused the Financial Performance chart to not be displayed correctly. In NAV 2017CU2 this should be fixed and all charts should display correctly in all 20 country deployments.

Locale and Language on the admin user

When you deploy a German, Danish, French or other non-english versions of the demo environment, then the admin user was sometimes created with the wrong locale and language. In NAV 2017CU2, the initialize script will set the locale and the language for the admin user to the language you have specified. This can of course be changed in the User Settings dialog after installation.

Try it

http://aka.ms/navdemodeploy will deploy your NAV 2017CU2 demo environment in ~20 minutes.

Enjoy

Freddy Kristiansen
Technical Evangelist

 

Comments (13)

  1. Thanks for the info! However nothing is posted on NAV’s team blog yet.

    1. FreddyDK says:

      Not sure what delayed the process, IT doesn’t always do as we want:-)

  2. Gert Lynge says:

    Hi Freddy
    I believe i found a small bug in the Certificate.ps1 regarding the trust-validation of non-self-signed certificates. It seems the certificate is installed in cert:\localMachine\my, but the trust is tested in cert:\currentuser\my which I believe will always fail.
    This causes the script to think the cert is self-signed (so it is also imported as root cert) and is probably related to the MS support not being able to re-create my certificate issues (a case you have also been involved in – REG:117011215166449).
    Feel free to e-mail me for further information.
    Keep up the great work – and thank you for this blog!

    1. FreddyDK says:

      Indeed, I will fix this, thanks Gert.

      1. Xavier Garonnat says:

        Hi Freddy,

        Again great job 😉

        Concerning the certificate issue, is-it a blocking issue for deploying CU2 VM ? if yes, could you tell me when the certificate problem will be fixed ?

        Thanks,
        Xavier.

        1. FreddyDK says:

          It is not a blocking issue. The Azure VM works fine with trusted or self-signed certificates.
          If you however deploy a Windows 2016 server manually and install NAV 2017 you will not be able to use a trusted certificate unless you se the LoadUserProfile Setting in the Application Pool to false (which is done by the Initialize script on the VM).

  3. Xavier Garonnat says:

    Sound strange but I can’t connect my Power BI service to UNSECURE OData : the URL is well recognized but the Basic login failed : “Failed to update data source credentials.”

    Source : https://blogs.msdn.microsoft.com/freddyk/2016/11/19/one-nav-2017-on-azure-loaded-please/#powerbi

    1. Xavier Garonnat says:

      Sorry, it’s OK finally.

  4. Hi Freddy, Still super work – we are using your demoenvironment each day helping us getting new customers on Dynamics NAV 😉
    Do you know if there has been any changes in the PowerBi.com “connection”?? Have a new environment where the “CRM-integration” is running, used (http://aka.ms/navdemodeploy).

    Getting Error Message AFTER successful login (UNSECURE, Basic) during importing data saying: OData: Request failed: The remote server returned an error: (400) Bad Request. (An error occurred when communicating with Microsoft Dynamics CRM.

    Detailed description: Could not load file or assembly ‘Microsoft.IdentityModel.Clients.ActiveDirectory, Version=2.28.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference.

    Any idea??

    1. FreddyDK says:

      I was under the impression that this was solved in NAV 2017 CU2 (update 2).
      If you are using the update 2 (build 15052), then please send me an email to freddyk at microsoft dot com and we will take it from there.

      1. Thanks! Yes, update 2 (build 15052) is what i use.

        1. Jan Jaap Smit says:

          Is this problem with the CRM integration solved in CU3? And will the demo template be updated with that? (I hope so:-)). Because this Azure template is such a BIG BIG help in demo-ing stuff!! Freddy for President (in the US!)!

          1. FreddyDK says:

            Thanks:-)
            It should be solved in CU3 (and the updated CU2), yes. I know Dag is deploying a new version right now (as we write) and when I get confirmation that the problem has disappeared (or still exist) I will update this.

Skip to main content