Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated VM Application readme. #108

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions articles/virtual-machines/vm-applications.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,9 @@ The VM application packages use multiple resource types:

- **No more than 3 replicas per region**: When you're creating a VM Application version, the maximum number of replicas per region is three.

- **Storage with public access or SAS URI with read privilege:** The storage account needs to has public level access or use an SAS URI with read privilege, as other restriction levels fail deployments.
- **Storage with public access and SAS URI with read privilege:** The storage account needs to have public level access and use a SAS URI with read privilege, as other restriction levels fail deployments. _SAS Tokens can be by-passed by publishing the artifact on the storage account by allowing anonymous access._

- **System Assigned Managed identity:** The compute galleries system managed assigned identity cannot be used to access a blob in the storage account.

- **Retrying failed installations**: Currently, the only way to retry a failed installation is to remove the application from the profile, then add it back.

Expand Down Expand Up @@ -452,7 +454,7 @@ start /wait %windir%\\system32\\msiexec.exe /i myapp /quiet /forcerestart /log m
Example remove command:

```terminal
start /wait %windir%\\system32\\msiexec.exe /x $appname /quiet /forcerestart /log ${appname}_uninstall.log
start /wait %windir%\\system32\\msiexec.exe /x myapp /quiet /forcerestart /log myapp_uninstall.log
```

Typically, the `start` command would be called within a batch script. If used with the `/wait` parameter, the calling script will be paused until the called process terminates. Once complete, the batch script would check for the `errorlevel` variable set by the `start` command and exit as follows:
Expand Down