Now Available in Community - New TechTalk Videos for 2020
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Every time we re-deploy an environment (Tier 1 sandbox), the machine name remains the same. This behaviour causes issue with the workspace mapping. Removing the old / existing workspace for each dev VM is not a solution as it will result in pending changes loss and inability to work simultaneously for all developers.
Do you know how can we change the VM name? Is it a special request? Or we are not following the best practices, because we assign different developers to the same environments. We should deploy environment in our Azure subscription and thus we will be able to change the VM name.
What is your recommendations?
Your developer should not keep changes pending for long duration , in that way you can just delete workspace and give it to someone else Or you can use shelve change set and delete workspace , in that way you don't loose pending changesets.
Ideally you should have VM/developer and you should be able to name it properly while deploying VM.
Thanks you for your response.
We are already following your best practices by assigning a dev environment to a single developer, however sometimes we deprovision / provision an environment and sometimes the developer is not the same. In this scenario the workspace mapping happen.
How should you be able to name it properly? Are you talking about the VM name?
Can you explain scenario in detail ? Removing workspace it not helping ?
Thank you for this comprehensive explanation.
I do remember when we were running 7.3, we were able to name the machine during provisioning wizard. However, now we are no more able to specify the name of the VM during the redeployment wizard:
Business Applications communities