Contents

# Getting onebox VHD Dynamics 365 finance and operations virtual machine

Contents
• Go to the LCS main page and select Shared asset library or go to Shared Asset Library.

• Find the VHD you are looking for based on the desired Finance and Operation version. The VHD is divided into multiple file parts that you need to download. For example, the asset files that start with “VHD - 10.0.5” are the different files you need in order to install version 10.0.5.

• Download all files (parts) associated with the desired VHD to a local folder.

• After the download is complete, run the executable file that you downloaded, accept the software license agreement, and choose a file path to extract the VHD to.

• This creates a local VHD file that you can use to run a local virtual machine.

• Rename and restart the machine before you start development or connect to Azure DevOps.

• Update the server name in SQL Server

• Run following query

 1 2  sp_dropserver [old_name] sp_addserver [new_name], local 
• Restart SQL service

• Open Reporting Services Configuration Manager for SQL Server 2016, then Select Database, select Change Database, and use the new server name.

• Update the Azure Storage Emulator

• From the Start menu, open Microsoft Azure Storage Emulator - v4.0, and run the following commands.

AzureStorageEmulator.exe start

If you got an error Port conflict with existing application, please check this post.

• This command verifies that the emulator is running.

AzureStorageEmulator.exe status

• Update the server name

AzureStorageEmulator.exe init -server new_name

• Update financial reporting

Open a Microsoft Windows PowerShell command window as an admin, and run the following command. This command contains the default passwords that might have to be updated. Be sure to replace new_name with the new name.

 1 2  cd \MROneBox\Scripts\Update .\ConfigureMRDatabase.ps1 -NewAosDatabaseName AxDB -NewAosDatabaseServerName new_name -NewMRDatabaseName ManagementReporter -NewAxAdminUserPassword AOSWebSite@123 -NewMRAdminUserName MRUser -NewMRAdminUserPassword MRWebSite@123 -NewMRRuntimeUserName MRUSer -NewMRRuntimeUserPassword MRWebSite@123 -NewAxMRRuntimeUserName MRUser -NewAxMRRuntimeUserPassword MRWebSite@123 

On a VM, you can find most of the application configuration by opening the web.config file of AOSWebApplication.

1. Start IIS.

2. Go to Sites > AOSWebApplication.

3. Right-click, and then click Explore to open File Explorer.

4. Open the web.config file in Notepad or another text editor. The following keys are of interest to many developers and administrators:

• Aos.MetadataDirectory – This key points to the location of the packages folder that contains platform and application binaries, and also source code. (Source code is available only in development environments.) Typical values are: c:\packages, c:\AosServicePackagesLocalDirectory, and J:AosServicePackagesLocalDirectory.

• DataAccess.Database – This key holds the name of the database.

• Aos.AppRoot – This key points to the root folder of the Application Object Server (AOS) web application.

To restart the local runtime and redeploy all the packages, follow these steps.

1. Open File Explorer, and go to C:\CustomerServiceUnit.

2. Right-click AOSDeploy.cmd, and then click Run as administrator.

This process might take a while. The process is completed when the cmd.exe window closes. If you just want to restart AOS (without redeploying the runtime), run iisreset from an administrator Command Prompt window, or restart AOSWebApplication from IIS.

That’s it, thank you for reading.