1. Type "%ProgramData%" into the path field, then hit Enter

The AirWatch directory will contain AirWatch Agent logs including enrollment, product provisioning and some profiles such as BitLocker.

The AirWatchMDM directory will contain the software distribution cache folder. Once the software packages are download they will appear in this folder.

We will take a look at how to troubleshoot errors with P2P and software distribution in upcoming sections.

Type in "C:\Windows\AdaptivaSetupLogs\Client" then press Enter

You will find the P2P client installation logs here, if anything goes wrong with the install you can review these logs.

1. Click on the Windows logo to open the Start Menu
2. Type and search for "regedit"
3. Click on regedit

1. Click Yes

1. Scroll to the top of the registry
2. Collapse the Microsoft folder
3. Expand to WOW6432Node>Adaptiva>client

Here you can see all of the configuration information about the P2P client, such as the version, server it's connected to, and other granular info. AirWatch handles installing and setting up all of this information.

1. Expand into AirWatchMDM>AppDeploymentAgent>AppManifests
2. Click on the folders under AppManifests and ensure that you have selected the folder with the Name matching 7-Zip 17.01 (x64 edition)
3. Expand S-1-5-18 (Device Context) folder
4. Select the same folder GUID {23170F69-40C1-2702-1701-000001000000} as above for the 7-Zip Application

This is where AirWatch store all information about Windows 10 native apps being installed on the device. AppManifests will contain information regarding all of the settings selected in the console. ContentManifests will contain where the device can download the software, such as Device Services URL, CDN URL, and P2P Content ID. Queue/S-1-5-X folders will contain the install status and logs for each application, where S-1-5-18 will contain apps being pushed to the device and S-1-5-21-X will contain apps being pushed to the user context.

1. Double click LastDeploymentLog
2. Right click on the highlighted Value data
3. Click Copy

1. Click on the Windows logo to open the Start Menu
2. Type and search for "notepad"
3. Click on Notepad

Paste in the data on your clipboard into Notepad.

1. Click Format, then click Word Wrap
2. Scroll to the bottom of the screen

Notice in the logs it takes 28/secs to download 7-Zip to the first device, when we enroll our next device it will leverage P2P and this time should decrease. You will also see a Content ID for 7-Zip, later we will refer to the P2P Database to see these Content IDs, this content ID will also match your folder in the cache directory.

Back in our File Explorer window which is already pulled up:

1. Type "C:\AdaptivaCache"

Notice you have the same content ID listed with the same file size for 7-Zip, thus the next device to enroll or request this application will peer off of our first device. The content is in format: {contentID}.content

This folder is a hidden directory and uses virtual SAN technology so that the space used goes unnoticed to the end user. When the end user needs more disk space Adaptiva's self managing cache will delete content to make room.

1. Click on the Windows logo to open the Start Menu
2. Click on the _ icon on the top toolbar to minimize our Win10-01.corp.local RDP connection

Notice that 7-Zip has been installed on our device. We will now enroll our second device and validate P2P delivery.

Now on Win10-2 desktop, launch Google Chrome by clicking on the shortcut.

We will now enroll our Windows 10 device in AirWatch.  First, we will need to download the AirWatch Agent.

From a new tab in the browser, if not opened already,

1. Enter "https://www.awagent.com" in the navigation bar and press Enter.
2. Click Download.
   NOTE - Please wait while the AirWatch Agent installer finishes downloading.  
3. Click Keep when warned about the AirWatchAgent.msi download.
   NOTE - If you do not see the warning about the AirWatchAgent.msi file, skip this and continue to the next step.

Click the AirWatchAgent.msi file in your download bar.

NOTE - The installer may take a few seconds to launch, please be patient after clicking the AirWatchAgent.msi file.

Due to Firewall restrictions, Windows SmartScreen won't be available in the lab network.  Click Run to continue.

If any required features are missing, you will be prompted that the installer will install them for you.  Click OK to continue.

The additional features that need to be installed will begin, click the flashing installer icon from your bottom toolbar.

Click Yes when asked if you wish to allow the application to make changes.

NOTE - You may see the installer pause while this process completes.  Please be patient, the installer when continue when it is finished.

Leave the default install location and click Next.

1. Select "I accept the terms of the license agreement".
2. Click Next.

Click Install to start the installer.

Click Yes when prompted if you should allow the AirWatch Agent to make changes.

Click Finish to complete the AirWatch Agent installer.

NOTE - After clicking finish, the Native Enrollment application will launch to guide you through enrolling into AirWatch.  If it does not show up immediately, wait a moment for the next prompt to appear.

Click Yes when asked if you want to allow the NativeEnrollment app to make changes.

Back in the AirWatch console, (either in your VESC Server or opening a new AirWatch tab) 

1. To find the Group ID, hover your mouse over the Organization Group tab at the top of the screen. Look for the email address you used to log in to the lab portal.
2. Your Group ID is displayed at the bottom of the Organization Group pop up.

NOTE - The Group ID is required when enrolling your device in the following steps.

1. Enter "v92.airwlab.com" for the Server Name field.
2. Enter Your Group ID for the Group ID field.  If you forgot your Group ID, check the previous steps on how to retrieve it.

1. Enter "testuser" in the Username field.
2. Enter "VMware1!" in the Password field.
3. Click Next

NOTE - Wait while the server checks your enrollment details.

Click Finish to end the Enrollment process.  Your Windows 10 device is now successfully enrolled into AirWatch.

1. Click on the Windows logo to open the Start Menu
2. Type and search for "regedit"
3. Click on regedit

1. Click Yes

1. Scroll up until you see AirWatchMDM
2. Expand into AirWatchMDM>AppDeploymentAgent>AppManifests
3. Click on the folders under AppManifests and ensure that you have selected the folder with the Name matching 7-Zip 17.01 (x64 edition)
4. Expand S-1-5-18 (Device Context) folder
5. Select the same folder GUID {23170F69-40C1-2702-1701-000001000000} as above for the 7-Zip Application

This is where AirWatch store all information about Windows 10 native apps being installed on the device. AppManifests will contain information regarding all of the settings selected in the console. ContentManifests will contain where the device can download the software, such as Device Services URL, CDN URL, and P2P Content ID. Queue/S-1-5-X folders will contain the install status and logs for each application, where S-1-5-18 will contain apps being pushed to the device and S-1-5-21-X will contain apps being pushed to the user context.

1. Double click LastDeploymentLog
2. Right click on the highlighted Value data
3. Click Copy

1. Click on the Windows logo to open the Start Menu
2. Type and search for "notepad"
3. Click on Notepad

Paste in the data on your clipboard into Notepad.

1. Click Format, then click Word Wrap

Notice in the logs it took 28/secs to download 7-Zip to the first device, however now we see that it only took 7/secs for the 2nd device as it used P2P and not CDN.

Note: If this time did not decrease for you, simply try removing 7-Zip from this device via the console, then re-deploying and check the logs again. P2P is meant to be accomplished with many devices, we are scaling it down to simply two devices for this example.

1. Click on the Windows logo to open the Start Menu
2. Click on the _ icon on the top toolbar to minimize our Win10-02.corp.local RDP connection

Notice that 7-Zip has been installed on our device but this time using P2P. Next we will take a look at the Adaptiva database and server logs.