7
We recently had an issue with our newly-build V10 dev VMs. Our setup path was:
1. Download VHD from LCS.
2. Patch Windows.
3. Patch D365FO (upgrade to newer platform update, apply ISV packages, apply local packages).
4. For each developer, copy VHD and create new VM.
5. Rename, attach to local domain, restart.
6. Get on with developing!
The above process can take a couple of days due to the amount of patching and restarting required.
We had an issue in the copied VMs that was not present in the originally built VM. When we asked Microsoft support for assistance in resolving the issue and were told that copying the VHD was not an approved approach, which leaves us in the situation of having to run through the whole patching process for each and every developer VM.
There has to be a less resource-intensive approach! More frequent (and better patched) VHDs on LCS (probably one for each platform update)? Support for copying and renaming VMs to shortcut the effort?
1. Download VHD from LCS.
2. Patch Windows.
3. Patch D365FO (upgrade to newer platform update, apply ISV packages, apply local packages).
4. For each developer, copy VHD and create new VM.
5. Rename, attach to local domain, restart.
6. Get on with developing!
The above process can take a couple of days due to the amount of patching and restarting required.
We had an issue in the copied VMs that was not present in the originally built VM. When we asked Microsoft support for assistance in resolving the issue and were told that copying the VHD was not an approved approach, which leaves us in the situation of having to run through the whole patching process for each and every developer VM.
There has to be a less resource-intensive approach! More frequent (and better patched) VHDs on LCS (probably one for each platform update)? Support for copying and renaming VMs to shortcut the effort?
STATUS DETAILS
Needs Votes