Versions Compared

Old Version 3

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Add_docset_workflow
APPRJIDSYM-20390
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'}
DEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
LDEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'}
SVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c9, userName='null'}
LSVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c078f, userName='null'}
AUTHJIDSYM-20389

Info

Before ASM Virtual Machines can be managed and operated via WebUI options, the VM instances must be created on the ASM using Microsoft Hyper-V. See Prerequisites - – Managing the VM.

Overview

The ASM is able to host one or more Virtual Machine (VM) instances. A VM hosts 3rd party software or runs the Cloud Connector Edition developed by Microsoft. A VM instance is created by logging into the ASM via Remote Desktop Connection and running the Microsoft Hyper-V management platform. Each VM is operated and configured through ASM WebUI options and Hyper-V.

...