Update for 10.0.24?

[FH-Inway]

The new 10.0.24 VHD template from Microsoft introduced several changes. Some of those have an impact on the d365fo.tools. Most noteably: It seems that the module cannot be installed without the -Clobber option.

I'm proposing to start a collection of changes and potential issues and improvements for the d365fo.tools resulting from them.

Another topic for discussion: Can and should the module support both pre and post 10.0.24 VHD environments? And if yes, how long should the support last?

[FH-Inway]

Collection of issues and solutions:

• Rename-D365ComputerName -NewName failes due to MS SQL missing path #646
  • fix Rename-D365ComputerName #657
• Visual studio extensions are not updated, services are disabled #642
• Does not install on 10.0.24 VHD #640
  • Replace required module "Azure.Storage" with "Az.Storage" ? #361
• Set-D365Admin command is not working on a new cloud hosted dev environment #633
• ✨ improve browser support #587
• https://www.yammer.com/dynamicsaxfeedbackprograms/threads/1682828402622464
• https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=1472552208572416

[Splaxi]

I'm all in for getting things back on track in terms of making it as easy as possible for people to install and run the tools.

As you correctly point out - what do we do about support for PRE / POST 10.0.24 VHD (Onebox / Local)? The general rule has been that we follow the version enforcement of Microsoft and when possible keep things backwards compatible, unless it requires to much effort.

Take the provisioning tool - there was several changes over the course of time, where we had to do mini hacks in the code, to handle PRE / POST specific PU's.

With that statement, we should strive for getting the tools to install and run flawlessly on any CHE / VHD with 10.0.24 - if they are coming with the same set PowerShell modules installed. It should be fairly easy to identify which ones that are conflicting with our current prereq modules. From there we can plan our work, in terms of what cmdlets are using which modules and create specific tasks that needs to be completed.

[FH-Inway]

Sounds like a plan. I was thinking of creating a PowerShell script that would list all components (PowerShell modules, versions of OS, SQL Server, ...) to make it easier to compare the VHDs. Would have to be a stand alone script so that it can be downloaded and executed without installing the d365fo.tools.