By: Brenton Blawat

Wavelink’s Avalanche Mobility Center (AMC) does not have an intuitive interface for importing packages into the application. I’ve decided to provide step-by-step instructions on how to import ‘New Packages’ (also creating a ‘Software Profile’) into AMC application.

Note: This document has been created utilizing Avalanche Mobility Center 4.2. While the newest version is well above this, the core program is the same.

1. Log into the AMC (default credentials are: U:amcadmin | P:admin)

2. Select Software Profiles

3. Select Add Profile

4. Enter a Name (TestCampusA) for the Software Profile.

Note: Software Profiles

There are two methods by which software profiles can be setup. The first method, and most commonly used method, is creating a new Software Profile for each individual package. While this is an acceptable methodology for setting up packages, it isn’t the method by which the feature was intended.

The second methodology, and typically my recommended solution, is creating Software Profiles per each device role (or location the device will be). For our example, I use “TestCampusA” to describe devices in CampusA that are in test (I could have used “LibraryPDAs” to describe the devices in the Library rather than Campus). This will enable a network administrator to logically segment all packages that should be sent to the set of devices in “TestCampusA”.

While the major disadvantage of the second topology is that a deployment of a single software package to an individual device is not possible, it is typically the organization goal to get all devices configured uniformly. This is why the second methodology is the best methodology as all devices must adhere to the template created in the Software Profile. Likewise, if testing needs to be conducted on several devices, a new software profile, such as “TestCampusA” can be created to deploy new test packages. – and the BIT Tangent ends.

5. Select the New Software Profile

Note: A bug / “undocumented feature” in AMC is that doesn’t auto-select the new Software Profile which was created. This step will not be necessary in future releases.

6. Select the Software Packages Tab — > Select Install

7. Select … — > Browse to the .AVA file you want to import — > Select Next

8. Select YES, I agree – > Select Next >

9. Select Finish

10. Select the New Package — > Select Enable

Note: A bug / “undocumented feature” in AMC is that doesn’t auto-select the new Software Package which was created. This step will not be necessary in future releases.

11. Select Selection Criteria – > Enter Selection Criteria for the Software Profile (E.G. IP = 10.10.10.10)

This will set the Selection Criteria for the entire Software Profile of “TestCampusA”. So now, the question –

Q: How can I tell a specific software package to ONLY install on a specific set of devices in this group?

A: This can be done when creating the Software Package. Typically the Selection Criteria of ModelName = “SYM8800” or ModelName = “SYMMC50” should be used on the Selection Criteria of a package (to filter the package to a specific Model Type or device). As I will describe in a different post, DO NOT filter by ‘IP Address ranges’ in Selection Criteria for the Software Package; only the Software Profiles.

12. Select the General Settings Tab — > Select Enabled

13. Select Save – > Select Yes to Save Changes

Assigning New Software Profile to a New Location

Now that the Avalanche Software Profile is populated with a Software Package, it needs to be assigned to a Server Region, or specific deployment server (dserver). To do this following steps can be performed:

1. Expand My Enterprise – > Expand Your Server Region (Arlington Heights) — > Select the dServer (Salt Creek)

Note: AMC provides the ability to deploy the Software Profile to a granular set of locations. This strictly adheres to the hierarchy scheme of the system. If you deploy the software profile to the “My Enterprise”, the software will propagate to all of the Regions and their dServers. Likewise, if it is deployed to a specific Region, it will propagate to all of the respective Region’s dServers. BE CERTAIN to select the right location when deploying the package, as upon Universal Deployment, the AMC will configure the respective handhelds for deployment of that package.

2. Select Software Profile Tab — > Select Add

3. Select the New Software Profile (TestCampusA) — > Select OK

4. Select Save — > Select Yes to Save Changes

5. Select Tools — > Select Task Schedule

6. Select Add…

7. Select Universal Deployment as Task Type — > Select Next >

8. Select My Enterprise or Select Region or Select dServer — > Select Next >

9. Select Perform the task now. — > Select Next >

10. Select Next >

11. Select Finish >

12. Select Close.

The Enterprise / Region(s) / dServer(s) will now be populated with the Software Profiles (and thus the Software Packages contained in the Software Profiles).

For More Free Training by BIT Tangents: Go to Wavelink Training (Click Here)

Info on Author: Brenton Blawat is a Wavelink Consultant who has worked closely with the Avalanche product for over 5 years. He has integrated Wavelink AMC (and variants) into a multitude of corporations including but not limited to: Seneca Foods Corporation, American Eagle Outfitters, and Alexian Brothers Health System.

** BIT Tangents nor any of its contributors are liable for damages as a result of following these instructions. These instructions are intended as guidelines for best practices and are to be used at the executioners own risk! All re-productions / digital copies of this content must be approved in writing by an authorized representative of BIT Tangents. **