Yet again we hit a frustrating snag with the Wavelink Enabler and I have taken it upon myself to add a new section to my blog for Wavelink Enabler Bugs. It’s not that I am frustrated with Wavelink support personnel. They have been more than attentive to my issues and have responded to my calls almost immediately.

The frustration comes with the core of the issue. I am having the same problems in the PPT-8846 Enabler (Released December 2006) as I am having in the MC-55 Beta Enabler (Beta Release this 2009). To Wavelink’s immediate defense, the MC-55 “Beta” Enabler is a “Beta” for a reason. But having an Enabler that has been revised more than once since the release of the 3.50-56 Enabler with the same fundamental issues? – hmmm.

Known Issues:

Issue: Handheld Desktop Displays ; No Method to Get Back to the Wavelink Enabler.

Motorola MC-55	Symbol PPT-8846

Above is an image of my case and point for my frustration. The above graphic displays the exact same issue on both Windows Mobile 6.1 (left) and Pocket PC 2003 (right). Same problem 3 years later?

Enabler Config MC-55	Enabler Config PPT-8846

When configuring the Enabler you have the ability to Manage the Taskbar and effectively lock access to the background of the Enabler. While this works most of the time I’ve noticed multiple instances of the Enabler allowing access to the desktop. Additionally, there is no way for the Wavelink Enabler to be accessed again. This is troublesome especially when the Enabler is responsible for Launching Applications (like in my client’s case).

Come on Wavelink; you can do better than this. – I have faith!

Work Around: The only work around for this issue is to restart the handheld. (aka warm boot/soft reset)

Known Versions: 3.50-56, 4-06-13 beta

Bug Status: Reported to Wavelink

Issue: Handheld Freezes in the Locked Full Screen Window; No Method to Get Back to Wavelink Enabler.

	*
Motorola MC-55 (Agent Not Found)	Symbol PPT-8846 (Update Complete)

Both of the devices are frozen at the Update Window Screen. While the PPT-8846 is at a hard lock, the MC-55 will return to the Enabler if touched. * The right image was modified to remove application specific information and agent addresses.

Motorola MC-55	Symbol PPT-8846

The Wavelink Enabler is having issues with the Full Screen Control and Update Window. As shown in the above screens, the Update Windows should be “Hidden” as it’s normal state. For some reason, the Update Window Remains locked and will not automatically unlock itself. The end result is the Enabler is frozen in an Update State. The subsequent updates will not affect the screen locked out state.

Work Around: The only work around for this issue is to restart the handheld or not lock the screen during updates. (aka warm boot/soft reset)

Known Versions: 3.50-56, 4-06-13 beta

Bug Status: Reported to Wavelink

Issue: Software which monitors for state changes of Wireless WILL lock handheld device or cause TCP/IP stack corruption.

Symbol PPT-8846 (Corrupt TCP/IP Stack)	Symbol PPT-8846 (Idle Application Locked)

* The images have been blurred to remove any client specific information.

On the left you will see a corrupt TCP/IP Stack. You also will see that the wireless status indicator is changed to “no connectivity”. In this instance, the application which was sharing the call to the API for the wireless status lost the battle.

On the right, you will see the application (which previously lost the race) is frozen. The wireless feud seems to have caused the login credential boxes (the blank space above the numbers) to disappear.  The handheld is locked and unusable. Please note that the wireless status indicator (next to the battery) is missing from the screen.

Work Around: The only work around for this issue is to restart the handheld (aka warm boot/soft reset)

Known Versions: 3.50-56

Bug Status: Reported to Wavelink

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. **

This is the quick guide for installing Wavelink Avalanche Mobility Center 4.2.X. 

Double-Click on the Wavelink Installer

Select Next >

Custom: Select Individual Components

Site: Install all the functionality for Mobile Handheld Management; no Access Point Management.

Select Custom >

Console: The console is also referred to as the eServer. It enables remote administration of the Wavelink Avalanche Mobility Center.

Server: The server is the core of the application which links the communications between the eServer and DServer.

Database: This is the database engine. Later versions of AMC allow SQL Server Installation.

Site Agent Deployment: This enables software deployments to the individual devices from the server.

Avalanche Site: Avalanche is the software deployment and network profile tool

Mobile Manager Site: Mobile Manager is the access point and non handheld infrastructure management toolkit.

Select the Desired Features >

Select Next >

Select Next >

Select the Destination >

Select Next >

The AMC Product Will Install PostGreSQL if it doesn’t exist on the system.

The software will begin to install….

Enter registration keys if necessary >

Select Finish >

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. **

While this could very easily go into a tangent about software design, this article is going to be focused on Bugs which one may see in the Wavelink Product. — What is the purpose? To provide methods by which one can work around the issue until Wavelink corrects the issues in the product.

So if you find an issue, let me know so I can post it here. Be sure to report these bugs to Wavelink as the issues cannot be corrected unless they are reported to Wavelink..

Wavelink Avalanche Frozen Screen / Loading Freeze / Blank Screen

While running in a RDP (Remote Desktop) connection, it appears that the software is frozen. The Title Bar of Wavelink Avalanche Mobility Center is at the top of the screen, but the core application does not load into view. This has to do with some weird JAVA rendering that happens upon loading of the software.

Work Around: Minimize the Wavelink Avalanche Mobility Center then click on the application in the Task Bar. The screen will come back.

Bug Status: Reported to Wavelink

Wavelink Avalanche Blank Selection Criteria Issue

Selection Criteria Blank = Bad Thing

Not a lot of people understand the “inherent” blank selection criteria. By setting the selection criteria to nothing, it in fact, deploys to everything. This becomes more complicated when you start thinking form the perspective of using != (does not equal) in selection criteria.

E.G. If I were to say only IP != 10.10.10.10 & IP != 10.10.10.11, the software would deploy to every device. Why? Well and IP address can’t be two values at the same time, therefore, the software will deploy will deploy to every device.

Work Around: There currently is no work around for this issue.

Bug Status: Reported to Wavelink

Wavelink Avalanche Selection Criteria Logical Arguments

Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230

This issue has to do with Wavelink’s in ability to parse the statements as we would expect them to… The above statement would be evaluated as:

Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15

OR

IP = 10.10.200.10 – 10.10.11.230

Why? Well Wavelink uses a character sorting algorithm, with reads letter by letter and only evaluates AND and OR via parenthetical statements. This means for the example above, the server will first evaluate if Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15 are true. It then will check to see if IP = 10.10.200.10 – 10.10.11.230 is true.

In reality, you want the package to be deployed ALL of the Model = “Sym50”, and those IP addresses which are between IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230.

If and & and an | (OR) are used in the same statement, Wavelink should force the use of parentheses.

Work Around: Use Parentheses in your selection criteria. So for the example:

Model = “Sym50” & (IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230)

The Wavelink Server will evaluate are the IP addresses between (IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230)? Are the model numbers of those units equal to “Sym50”?

Bug Status: Reported to Wavelink

NEW! Wavelink Avalanche Duplicate Devices

It appears a bug they once upon a day ago fix has re-entered the system. It appears that the software is reporting duplicate handheld entries for devices with the same MAC addresses, Terminal IDs and IP addresses for the handhelds.

Work Around: Manually delete the duplicate devices from the server. Obtain a script from Wavelink to delete these duplicate devices

Bug Status: Reported to Wavelink

NEW! Wavelink Avalanche Group Selection Criteria Issue

Group = "MobileDeviceGroupName”

This issue has to do with the ability to send software out to Mobile Device Groups. The key behind this was to group sets of handhelds into Mobile Device Groups.

E.G. One of my clients created a mobile device group for each individual location they have for controlled deployments (1050 locations). In doing this they wanted to send specific software to groups of stores via Group = "MobileDeviceGroupName”.

The result of the selection criteria is the same as leaving the selection criteria blank; it will deploy the software to EVERY handheld in the system. Architectural flaw, it needs to be corrected.

Work Around: There currently is no work around for this issue.

Bug Status: Reported to Wavelink

UPDATE! Wavelink Avalanche Enabler v3.50-56 Launch Times

There seems to be an inherent bug in the Wavelink Enabler v3.50-56 where it takes 5 seconds for any application to launch from their “Desktop Interface”. It seems to be linked, or ironically similar, to their default auto-launch time of 5 seconds. Any and all applications (including extensions of .exe and .ica) take 5 seconds to launch.

Work Around: There currently is no work around for this issue other than waiting 5 seconds for each application.

Bug Status: A test Enabler has been sent to me for testing. I will provide it here if it appears to fix the issue!

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. **

This section will provide detailed information of an Enabler which was designed for a Symbol Device v3.50-56. While there are different files on different devices, the core of the applications remain the same.

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. **

To most problems, it is recommend most Users should RTFM and STFW. Q: What happens when reading the manual leaves you even more confused than beginning and searching the web results in NO coherent results for the product?!? A: Well you get my BIT Tangents to listen to….

Understanding Packages

There are four types of Wavelink packages which can be created:

Auto Run – Provides the ability to execute multiple commands after the deployment of a package. So what exactly does this mean?

The execution of Auto Run commands don’t actually work as you would expect. The Auto Run commands have to be specified in the “Startup Command”. While you’d think you can specify multiple commands, the commands don’t always parse correctly from the Package Builder for an Auto Run Package. As a result, Wavelink Support, and my recommended methodology is to create a auto execution file within the package named : autoexec.bat

This file .BAT file is only allowed to have 1 command contained in it. This is a result of a bug within the Package Builder Software and the way the mobile devices parse the file. As a result, and more perplexing, the a caveat of the software is that it only accepts the following:

1. Single Line

2. No Triggers

3. No spaces to execute other items.

4. Startup command must read exactly: autoexec.bat

Note: The startup command MUST say only autoexec.bat (NO relative path to the file is required) and the autoexec.bat must be configured in the ‘APPS’ ‘Install Drive’ within the package for proper execution (install path should be left blank). Surprisingly enough, the Enabler is smart enough to know that by saying ‘autoexec.bat’ it needs to look in the \Application\Avalanche\Packages\Files\AVA\APPS\APP_NAME\ directory for the file.

Commands which will NOT work:

Copy \Application\Brent.CPY \Windows\Brent.CPY

<– technically the spaces are considered triggers. –>

Cmd.exe /c brent.bat

<– again the use of triggers –>

Commands which WILL work:

\Application\brent.bat

<– My recommended usage –>

\Program Files\BrentsApplication\brent.bat

<—While there is a space, it is still a singular line. –>

Getting the Auto Run to Work correctly

I always recommend two .BAT files with the use of Auto Run Packages. With the inability of the Enabler to parse multiple lines in the autoexec.bat, I call a secondary .BAT file to execute the commands I need to occur. This provides me with a stronger command base and the ability to run IF EXIST, IF NOT EXIST, DEL, COPY, MKDIR, >, ECHO, or any other command that is supported by Pocket CMD.

#1 Setup the autoexec.bat – Create a new .BAT file named autoexec.bat

#2 Mapping to second .BAT – place in the autoexec.bat a single line that states the location of the new .BAT file. The location MUST be the absolute location of the .BAT file.

E.G.

\Application\brent.bat

or

\Application\Avalanche\Packages\Files\AVA\App_Name\Brent.bat

#3 Create the second .BAT file – Create the secondary .BAT file on the system. Place as many command line parameters in the .BAT file as necessary for the package.

#4 Placing of the files within the package – The Autoexec.bat file MUST be located in the ‘APPS’ ‘Install Drive’. The second .BAT should be located in either ‘C’ ‘Install Drive’ and the ‘\Application\’ ‘Install Path (first example) or the the ‘APPS’ install drive (second example).

** For more information on building this package; read my Creating an Auto Run Wavelink Avalanche Package.

**Also, for those devices that do not natively support .BAT extensions, you will need to add .BAT registry customization by reading my .BAT Execution for Pocket PC 2003 article.

Support – This provides the ability to place files on the device. In short, the Support Package enables a user to place specific files into specific locations.

Note: While Support Packages do not support the autoexec.BAT syntax, the Support Packages do enable the Post Install Scripts. This allows certain registry entries and files to be imported into the system via their scripting engine.

My Recommendation: Use Support Packages when you want to place files onto the device without the requirement of additional commands. If additional commands are required, create an Auto Run Package.

Application – This provides the ability to place files onto the device, and adding a launch-able icon to the Enabler.

My Recommendation: Don’t use this feature. This all goes back to the Software Profiles. I strongly recommend setting up Software Profiles for individual departments for the handheld devices. In this create an enabler confi package to include the Applications which are required. This enables the Users of these devices to have the same icons and same items on their desktops. Software Profiles are much easier to support and the “one offs” will be eliminated.

Config – This is a method to configure or change a specific file. I’ve avoided the use of Config Packages as there are better methodologies to get around using this type of packages.

My Recommendation: Don’t use this feature. If a file need to be configured, redeploy the file as a Support Package or redeploy the entire software package. This a better solution as upon an update of a software package on the Avalanche server will only send the specific files which were updated; not the entire package.

For More Training: 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. **

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. **