And have forced a major operator banc de binary to cease operations in the us and pay back all custo


This topic walks you through the steps for using the command line to apply either a binary update or an application AOT deployable package that was created in your development or build environment. For most types of environments, you can apply a deployable package to an environment directly from Microsoft Dynamics Lifecycle Services LCS. For more information, see Apply a deployable package on a system. Therefore, this topic applies primarily to environment types that don't support the application of updates via LCS.

However, you can also use this topic any time that you want to install deployable packages by using the command line instead of LCS. An AOT deployable package is a package that contains customizations and extensions to your application.

If you want to use the command line just to install an AOT deployable package on a development or demo environment, follow the instructions in this section. You can then skip the rest of this topic. On the virtual machine VMdownload the zip file for the deployable package. Make sure that the zip file is stored in a non-user folder. After you download the zip file, right-click it, and then select Properties. Then, in the Properties dialog box, on the General tab, select Unblock to unlock the files.

As of Microsoft Dynamics for Finance and Operations, Enterprise edition with platform update 12, the devinstall option doesn't require that you be an administrator on the VM.

This command doesn't run database synchronization. You must run database synchronization from Microsoft Visual Studio after you install the deployable package. In the folder where you extracted the deployable package, find and open the file that is named DefaultTopologyData.

You must specify the VM name and the installed components in this file. Go to the extracted folder, and run the following command to see a list of all the components that are installed on the computer.

Repeat steps 1 through 4 for every other VM that is listed on the Environment page. Based on the topology information in the DefaultTopologyData. The runbook provides the sequence of steps that must be run to update the environment. The following illustration shows an example of a runbook file.

Each step in a runbook is associated with an ID, a machine name, and step execution details. The runbook also logs information about each step.

For manual steps, follow the instructions, and then run the following command to mark the step as completed in the runbook. If errors occur during any step, debug the script or the instructions in the step, and update accordingly. Repeat step 1 on every other VM that is listed in the runbook file. For one-box environments, such as development, build, and demo environments, there is only one VM.

View the runbook to see the completed steps. Here is an example of a runbook file where the steps have been completed. After all the steps in the runbook are completed and you've exported the runbook, save the file outside the computer for future reference. For example, you might have to use the runbook file in these situations:. To prevent version mismatch or downgrade, or installation of the same deployable package, run the following command.

The feedback system for this content will be changing soon. Old comments will not be carried over. If content within a comment thread is important to you, please save a copy. For more information on the upcoming change, we invite you to read our blog post. Important For most types of environments, you can apply a deployable package to an environment directly from Microsoft Dynamics Lifecycle Services LCS. Note After you download the zip file, right-click it, and then select Properties.

Note This command doesn't run database synchronization. Note The feedback system for this content will be changing soon.