(App Volumes Series III) Manager configuration and agent installation

In the previous blog, we had a basic understanding of the four logical components of app Volumes, environment configuration requirements and how to install the App Volumes Manager component, and we'll continue our app Volumes tour.

First review the installation of the app Volumes, using the process: Initial configuration, App Volumes Manager component installation, App Volumes Manager component configuration, App Volumes Agent component installation-> ; Apply extract, Apply collection (Appstack) assignment.

App Volumes Manager component configuration and app Volumes Agent component installation is the main content of our blog.

appvolumes Manager Configuration

the APP Volumes Manager must be configured to use it. So we should do the app Volumes manager configuration immediately after installing the app Volumes Manager, which needs to be in the app Volumes Agent finish before installation begins. App Volumes Manager configuration mainly refers to license management,AD configuration information,vCenter Server Configuration link information, and app Storage location for Stack and writable volumes .

The first thing to configure APP Volumesmanager license information, although APPP Volumes was not released after the first official version of VMware acquisition, but the future sales model can be guessed, basically two modes, One is the license model for selling App Volumes separately, and the other is the license model for packaging sales as part of Horizon Enterprise editions and other products, the second The Horizon Enterprise Editions Sales license model is obviously a better price-performance approach. Of course, the specific business information must be released after the official version can be determined.

specific to the steps to install the license, as shown, the user selects the license file and uploads the file to the server to complete the license configuration.

Figure One license configuration

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/53/D4/wKioL1Rx4HfDg3wPAAE9X6fjuHY076.jpg "title=" 1.png " alt= "Wkiol1rx4hfdg3wpaae9x6fjuhy076.jpg"/>

then theADthe configuration of the domain controller. App Volumesmanaged objects are domain controller-based objects, primarily domain computer objects and domain user objects. AlthoughApp Volumes Managerthe computer itself does not have to be joined to the domain, but it needs to have domain control information, including domain name, administrator user, password, and so on. TherebyApp Volumes Managercan be taken out of the domain to take out the corresponding object information, and then theAppstackorwritable Volumesassigned to these objects.

Figure II AD Configuration

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/53/D4/wKioL1Rx4WqjKpYvAANYyEajV_4490.jpg "title=" 2.png " alt= "Wkiol1rx4wqjkpyvaanyyeajv_4490.jpg"/>

followed byVCenterthe link configuration. App Volumesthe simple implementation of the principle is that at the virtual machine level willApp Stackorwritable Volumesthe virtual machine file where it resides (VMDKand the virtual machine file for the target system virtual machine (VMDKformat) is dynamically mounted as a system. And this mounted operation requiresApp VolumeshaveVCenteradministrator rights are not possible. As shown in the three, the administrator needs to enterVCenterthe host name orIPaddress, and then theVCenterThe corresponding administrator user and password are also required. In theApp Volumesprior to the launch of the official version, the originalCloud Volumesversion only supports oneVCenter,in other words,App Volumeswhen doing a program or content distribution, the virtual machine in which it manages the target machine must be in aVCenterunder the management. Of course, I believe that the future of manyVCentersupport should be required.

Figure three VCenter link configuration

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/53/D5/wKioL1Rx44yhqabUAAKkKMi2xWM332.jpg "title=" 3.png " alt= "Wkiol1rx44yhqabuaakkkmi2xwm332.jpg"/>

The last is the configuration of the storage and the template, as shown in four, this configuration refers to the user-generated The storage location of the virtual machine files corresponding to the App Stack and writable Volumes, in principle, should be the location where the administrator wants to manage the virtual machine system. In addition , the application Stack or writable Volume virtual machine files and templates can be stored in the default value without modification, unless the user himself has been in the data Store above manually create a corresponding directory schema and upload the corresponding files, it is necessary to make the corresponding changes here.

Figure Four storage location configuration

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/53/D7/wKiom1Rx4yaA9ieyAAKgWTzNyp4097.jpg "title=" 4.png " alt= "Wkiom1rx4yaa9ieyaakgwtznyp4097.jpg"/>

after several configuration steps, App Volumes Manager The configuration is complete and the user is ready to install the next client .

appvolumes Agent Installation

App Volumes is essentially a C/S architecture system, Appvolumes Manager is the server part, and the app Volumes agent is the client part. The APP Volumes agent needs to be installed on the operating system of each target system that the administrator wants to manage. It needs to have corresponding it planning, 1) if it is a new system, the administrator can create a few virtual machines, and install the operating system inside the virtual machine, such as Win7 or WIN8, and then install the Application Volumes Agent software in the corresponding system, then save the corresponding virtual machine as a template. When users need to apply for a new system, they can create a new system based on the template, and the newly created system contains the installed app Volumes agent software so that the app Volumes Manager can distribute the content to the new system. 2) If the user already has a virtual machine and has already started to use it, then the administrator will have to manually install the app Volumes Agent software on each legacy system before using the app Volumes function.

Here to emphasize, appvolumes agent installed by the target system can be divided into two categories, one is the administrator used to create the application stack of the model machine, the other class is used by ordinary users of the virtual machine system. On both of these systems, the APP Volumes agent is installed exactly the same way.

The installation steps of the app Volumes agent are extremely simple, and the user only needs to enter the correct app Volumes manager's address at the time of installation. As shown, first the user clicks on the installation package inside the installation file to start, accept license Agreement, and then select Install Agent

Figure Five Agent options

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/53/D5/wKioL1Rx95WgyAK3AAEM-X_ZMYI706.jpg "title=" 5.png " alt= "Wkiol1rx95wgyak3aaem-x_zmyi706.jpg"/>

Next, you need to enter the address of the app Volumes manager and the port number, this step of the input information must be accurate, because once the wrong, at least the current cloud Volumes agent version does not provide a configuration interface so that users can modify the app Volumes Configuration information for the manager. So once the error is lost, the user has to uninstall the Cloud Volumes agent again and then reinstall the Cloud Volumes agent to enter the correct information, fortunately the steps are simple enough to install.

Figure six APP Volumes Manager configuration

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/53/D7/wKiom1Rx97TwCE23AAEmNS3ZqRk156.jpg "title=" 6.png " alt= "Wkiom1rx97twce23aaemns3zqrk156.jpg"/>

All that remains is to click Next, accept the default configuration, start the installation, wait a few minutes, and after the system is installed, the user will be asked to restart the operating system. After the restart, the app Volumes agent is OK, the user can proceed to the next application extracted.

In the following blog post, I will focus on how to use app volumes for application management and personalized content management.

This article is from the VMware End User Computing blog, so be sure to keep this source http://vmwareeuc.blog.51cto.com/8606576/1581707

(App Volumes Series III) Manager configuration and agent installation