GPUG Summit 2018 Phoenix Arizona–October 15-18th

If you are into Dynamics GP, Power BI, then head over to GPUG Summit summit this October in Arizona – even better, bring your “IT crowd” too!

 GPUG Summit Site Phoenix, October 15-18, 2018

This event has over 215 GP –specific sessions and a separate parallel conferences going on “under the same roof” for business central and Power BI. There will be lots of ISVs and networking opportunities in the expo hall and corridors.

Session listing can be found here for the four conferences:

(Power BI) PowerBIUG Power Summit

(D365UG) AXUG Summit

(Business Central) BCUG Summit

(Dynamics GP) GPUG Summit

CRMUG Summit

 

It is difficult to emphasise enough the value that can be found in attending this nature of event, with a world class concentration of expertise in the Microsoft Dynamics products housed in the same place for a week. There is a strong sense of community and endless opportunities to get the answers to long held questions, or discover new products and features that you never realised existed. This knowledge could be priceless when brought back to the workplace after the event.

Lots of practical sessions are available on how to better utilise the investment you have in your company systems. This includes discovering the tools you didn’t even realise you already had at your fingertips. Notably, this year there is a real growth in the developer and IT pro tracks – so not only will the accounting, purchasing, warehousing, sales, admin employees find value in attending, now the IT crowd can come along and there will be lots for them to get their teeth into too.

Have you ever considered how much more could be achieved in your company by growing a better understanding of the financial systems that drive the business,  by getting buy in and understanding from your IT support staff and developers? Trust me, once they see the kind of things that are possible from the exhibiting companies and from the technical sessions, they will return enthused and ready to help facilitate change, perhaps brining in improvements (great and small) for everyone! –my message is simple, BRING YOUR IT CROWD TO SUMMIT 2018!

  • Newly released Microsoft Dynamics G 2018 R2 (October 1st) will be in action on stage and within sessions
  • Meet new peers, reunite with existing friends and mentors within the GPUG community
  • GPUG Medics will be onsite and available all week to talk you through your unique GP challenges
  • BI track for Power BI you can attend Power Summit sessions at NO additional cost

See my write up of the 2016 Summit in Tampa for an example of what to expect.

As a bonus I will be presenting two sessions, so see you there!

Docker build and UilttiuyVM: The parameter is incorrect - Failed to regis error

The following error can occur when doing a Docker build.

Docker image

Docker . failed to register layer: re-exec error: exit status 1: output: processUtilityWImage

\\?\C:\ProgramData\docker\windowsfilter \UtilityVM: The parameter is incorrect.

At line: 2 char: 1

+ Docker build - -tag tw/gp2018 .

+ CategoryInfo :NotSpecified: (failed to regis…r is incorrect.:String) []. Remote Exception

+FullyQualifiedErrorId : NativeCommnadError

 

On a windows build, this is often due to the base image not being compatible with operating system of the Docker host machine.

For example, I moved my dockerfile and build directory from Windows 10 to Windows Server 2016 and experienced this error.

Turns out that the windowscore I was attempting to use was not compatible.

See here https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility for the guide on the windows container versions compatible with different hosts.

dockercompat

I was attempting to use microsoft/windowsservercore:1803, but the only version that is compatible on Server 2016, from the above table, without using Hyper-V isolation (where a small Linux machine is used to host container), is build 14393.

Thus in my dockerfile, changing the base image instruction to

FROM microsoft/windowsservercore:ltsc2016

solved the above error on the server host.

The reason is obvious really, Docker works by sharing the underlying kernel from the host with the containers, overlaying layers of files until you reach the image. Changes to the host operating system will adversely affect this layering, as expected components may not be present that were there when the image was created. The container my start but fail later.

Using Hyper-V isolation works, as the Hyper-V isolation introduces its own kernel instead of the host’s thus isolating the container from the host operating system. This still gives us benefits if multiple containers are ran, and the benefits of portability are still present, but less efficient on disk storage. Use the switch parameter –isolation=hyperv to enable this isolation.

Installing Docker onto Windows Server 2016

 

https://docs.docker.com/install/windows/docker-ee/

Docker comes in two editions, free community edition and enterprise edition.

The company Docker and Microsoft entered into a commercial agreement to bring Docker to windows server as a commercially supported container enterprise product.

Docker running containers on Windows is the result of a two-year collaboration between Microsoft that involved the Windows kernel growing containerization primitives, Docker and Microsoft collaborating on porting the Docker Engine and CLI to Windows to take advantage of those new primitives and Docker adding multi-arch image support to Docker Hub. (https://blog.docker.com/2016/09/dockerforws2016/)

 

 

As a result of the agreement Docker Enterprise is already licenced as part of Windows Server 2016. So you just need to install and use it!

 

There are two types of containers, Linux and Windows. To run Windows OS containers, you must install the windows provider. Choose the appropriate container type below and issue the relevant commands.

For Install for Windows containers:

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force

Install-Package -Name docker -ProviderName DockerMsftProvider

For Install for Linux Containers:

Install-Module DockerProvider –Force

Install-Package Docker -ProviderName DockerProvider –Force

 

When installed there will be a Docker Service on the machine:

Docker Service

When the command has finished executing (can take some time), then powershell should be aware of Docker commands. Thus issuing the following command:

Docker version

will return information about the Docker version.

Docker Version

 

Uninstall docker from Windows Server 2016

Uninstall-Module dockerprovider

Uninstall-package docker

or for windows container:

Uninstall-Module DockerMsftProvider

Uninstall-package docker

Dynamics GP 2018 wrong version of GP2018 Power Shell included

Be aware of an issue with the GP2018 installation media

GP2018 Power Shell Additional Product is version 2016

You can see above that the installation media MDGP2018_RTM_DVD_ENUS has under the Additional Products the GP2016 installer for Power Shell.

The correct installer has been provided by Microsoft under Customer Source here: https://mbs.microsoft.com/customersource/northamerica/GP/downloads/service-packs/mdgp2018_dexterityreleases

It is not obvious that a administration module should be under something as specific as Dexterity Development System – buy hey at least it IS available!


Dynamics GP 2018 Power Shell installer found under Dexterity Development System Releases for Dynamics GP 2018