When an environment is first deployed, only one user account is enabled as a developer on the virtual machine (VM). This article explains how to enable another user account as a developer on a development VM.
When an environment is first deployed, only one user account is enabled as a developer on the virtual machine (VM). This user is preconfigured by Microsoft Dynamics Lifecycle Services (LCS) or is the local administrator account on downloaded virtual hard disks (VHDs). However, you can enable a new user account to develop on the VM. Even after you enable a new account, only one developer can develop at a time on the same VM/application.
To enable a new user account to develop on the VM, the user account must be an administrator on the VM. Additionally, you must log on to the VM by using the credentials of the default developer account. If the VM is a Microsoft Azure VM, the account information is available on the environment page in LCS. If the VM is a local VM that runs on the downloaded VHD, use the local administrator account. For more information, see Access Instances.
- Download the following script: ProvisionAxDeveloper.ps1, the script is available at https://github.com/Microsoft/Dynamics-AX-Scripts.
- Open a Microsoft Windows PowerShell Command Prompt window as an administrator.
Run the ProvisionAxDeveloper.ps1 script. Specify the following parameters:
- DatabaseServerName – Typically, this is the machine name.
- Users – Use the following format: <domain or machine name>\user1, … <domain or machine name>\user n
> ProvisionAxDeveloper.ps1 RDXP00DB20RAINM RDXP00DB20RAINM\username1 > ProvisionAxDeveloper.ps1 -databaseservername RDXP00DB20RAINM -users RDXP00DB20RAINM\username1,RDXP00DB20RAINM\username2
If more than one user account will be developing on the same version control workspace, you need to make the workspace public.