Deploying packages is a time-consuming thing. MS has improved the speed, but we partner can also help. This helping is by merging the packages. Good merged combinations are Binary updates and x++ updates, but your own code can also be combined with your customizations on your Retail (SDK) part.
Till now I was not able to merge ISV packages, so those must be deployed separately. However, there is quick dirty trick for local VM.
the tick
You must download the ISV packages and extract them all into the same map. Don’t bother messages like this file is already there, just override it.
On the end your ISV extracted content will look like this.
Next open the DOS prompt (just press file button in the file explorer and select DOS, your also directly on the right spot. Finally run the next 3 commands.
- AXUpdateInstaller.exe generate -runbookid=”runbook” -topologyfile=”DefaultTopologyData.xml” -servicemodelfile=”DefaultServiceModelData.xml” -runbookfile=”runbook.xml”
- AXUpdateInstaller.exe import -runbookfile=”runbook.xml”
- AXUpdateInstaller.exe execute -runbookid=”runbook”
Most of the time you get an error telling you the runbook is empty, that’s correct look at the file DefaultTopologyData.xml
| <string>AOSService</string> <string>MRApplicationService</string> <string>RetailServer</string> <string>CortanaAnalyticsService</string> <string>PayrollTaxModule</string> <string>DIXFService</string> <string>DocumentRoutingAgent</string> <string>SCMSelfService</string> <string>BIService</string> <string>RetailSelfService</string> <string>AOSService</string> <string>PowerBIService</string> <string>RetailHQConfiguration</string> <string>RetailCloudPos</string> |
So, on the end the file will look like
The post Dynamics 365 LCS Tricks – mass install packages appeared first on Kaya Consulting.