Lab 06: Configuring App Volumes for physical Windows endpoints (AV Agent - Managed & Shared Storage modes)
Objective and Tasks
This is a two-part series in which the task in this lab is to simulate a physical Windows endpoint and install the App Volumes Agent with the required parameters.
- Install the App Volumes Agent on a physical Windows endpoint
- Configure the App Volumes Agent for a physical Windows endpoint
Once this lab is completed, move on to the next lab to configure a computer-based assignment of an App Volumes application targeting this physical Windows endpoint and validate a successful delivery of the package
In this section, we will use the Appvolprov-01a VM as a physical Windows endpoint. Install the App Volumes Agent, adding the parameters that would be configured on a physical Windows endpoint
- Navigate to vCenter, identify, and Power ON the packaging machine
- Log in to the ControlCenter VM
- Username: administrator
- Password: Pa$$w0rd
- Open the Google Chrome browser from the desktop
- Click on vCenter-01 link from the bookmark bar to connect to the vCenter https://vcenter01.omnissatraining.com
- Login using the following credentials
- Username: [email protected]
- Password: Pa$$w0rd
- Within the vCenter web console, identify, revert the App Volumes packaging virtual machine to the 'baseline' snapshot and Power ON the VM
- Navigate to vcenter01 > DC1 > Cluster1
- Right-click on the appvolprov-01a VM
- Select Snapshots click on Manage snapshots
- Select the snapshot to install App Volumes Agent for a physical Windows endpoint
- Snapshots tab select the 'baseline' snapshot
- Click the 'REVERT' option from the toolbar above
- Confirm by clicking on 'REVERT'
- Confirmation message received in the 'Recent Tasks' section with Status: Completed
- Power ON the Appvolprov-01a VM
- Right-click on the appvolprov-01a VM
- Select Power Power On
- In the center panel, click on the Summary tab
- Under the Summary tab > click on the LAUNCH WEB CONSOLE button
- This opens up a new browser tab to the virtual machine, login and initiates the application installation
- Username: Administrator
- Password: Pa$$w0rd
- Install the App Volumes Agent
- Open the File Explore
- Navigate to the file path: \\labfiler\resources\software\appvolumes\appvol2603
- Go to the installation folder
- Initiate the App Volumes Agent installation
- Double-click on Setup.msi
- Acknowledge the start of the setup wizard, click on Next
- Choose 'Install App Volumes Agent'
- Click on Install
- If presented with a User Account Control pop-up, acknowledge and click on Yes
- Continue the setup wizard, click on Next
- Management Mode screen, select 'Managed (Connects to App Volumes Manager)'
- Click on Next
- Package Access Mode screen, select 'Local Copy'
Management Mode: Standalone
This setting is used in a scenario which requires the delivery of the App Volumes Package (VHD or MSI) to be carried out by a software delivery tool like Workspace ONE UEM or other 3rd party tools.
This where an App Volumes Manager infrastructure is not in the environment.
Package Access Modes: Local Copy
Physical Windows endpoints such a laptops are mobile devices and might not always be connected to the corporate network.
This scenario allows for the delivery and management of the App Volumes application when the device is connected to the corporate network (even over VPN - needing line of sight and reporting into the App Volumes Manager).
Local Copy Mode - allows for the Agent Polling to take place based on a predefined interval set on the App Volumes Manager. This allows for the Agent to check-in to see if entitlements have changed and carry out action.
Which is why the Management Mode is set to Managed and the Package Access Mode is set to Local Copy. This ensure management when connected, but the package once delivered can be used offline.
- Click on Next
- At the Server Configuration screen
- App Volumes Manager: appvol-02a.omnissatraining.com
We used a Windows endpoint VM within vCenter, to simulate a physical endpoint, we configured the App Volumes Agent with persistence and delivering the package as a local copy.
- Click on Next
- Click Install
- Click on Finish
Configuring the App Volumes svservice enables the App Volumes Administrator to provide user notifications when an application is about to be changed/updated or removed, providing the user with time to save changes if they have the application open at the time of an upgrade or removal.
https://docs.omnissa.com/bundle/AppVolumesAdminGuideV2606/page/Configurationofsvservice.html
Parameters: EnableAppChangeNotification, EnableAppChangeTimer, EnableAppChangeAutoClose and EnableAppChangeTimerDuration
- Run the batch file to enable the four 'Notification' parameters mentioned above, referenced from the product documentation.
- Run the script from the following path C:\Scripts\AppVolumesNotification.bat
- It is also available as a Desktop shortcut
- Acknowledge the confirmation dialog box by clicking on OK
- Use Regedit to validate the four entries are listed within the Registry Editor location shown below.
- Run the script from the following path C:\Scripts\AppVolumesNotification.bat
- Shutdown the Appvolprov-01a virtual machine and close the browser tab
- At the vCenter tab, take a snapshot of the current state of the Appvolprov-01a VM
- Click on the Appvolprov-01a VM
- Navigate to the Summary tab and confirm the VM is in the powered OFF state
- Click on the Snapshots tab
- Select the 'baseline' snapshot
- Click on the TAKE SNAPSHOT button
- Name: Physical_Windows_Endpoint
- Click on CREATE
- Observe the 'Recent Tasks' to get a 'Completed' status next to 'Create virtual machine snapshot' is displayed
This concludes the steps required to complete this lab. The next lab will have you target this Physical Windows Endpoint, configure a Computer assignment of an application and validate the delivery.
0 Comments
Add your comment