Skip to main content
Contact Us

New to Wasp Helpdesk? Register for an account

Need a password reminder?

MobileAsset v6: The passwords for AssetUser and AssetReader do not pass our security requirements - Knowledgebase / Discontinued Products / Mobile Asset v6 and older / Mobile Asset v6 - Wasp Helpdesk

This Article Category Knowledgebase

MobileAsset v6: The passwords for AssetUser and AssetReader do not pass our security requirements

Authors list
  • Last updated: Jan 19, 2023 by Scott Leonard
Some systems, notably military & government, have stronger security requirements for passwords than our default for MobileAsset v6, so we developed a stronger password procedure. Follow the steps below; there are things that need to be run on the server and on each client to allow them to connect.
 
The zip file should contain some batch files, but sometimes our recipients' network security systems strip those out. If they're missing when they get to you, you'll need to find a way to download the file without having the files stripped out. Or we can email the contents of the files in text format, so that you can recreate them on your PC.
 
Applies to Professional and Enterprise edition, but not Standard: If MobileAsset is installed on additional clients later, the Run On Client script needs to be run for them to connect to the server.

Download and extract this file: https://dl.waspbarcode.com/wasp/supportfiles/CreateWaspAccountsMA6SEC.zip

It will create 2 folders, Run on Server and Run on Client. Copy Run on Server to the server machine, then run UpgradeAllMA.bat to update the databases. This will create the AssetUser and AssetReader accounts with passwords Serial#1Serial#1 and ReadOnly@1ReadOnly@1 respectively.*

Copy the Run on Client folder to all machines where the client program will be run, including the server machine if needed. Install the client program normally if it has not already been installed, then from this folder run 32bit - CreateWaspAccountsRegMA+SEC.bat or 64bit - CreateWaspAccountsRegMA+SEC.bat, whichever is appropriate to your version of Windows, to update the registry entries.

The scripts will create 3 log files: UpgradeConfig.log, UpgradeDB.log, and Upgrade_Trial.log. If the scripts fail to run properly for some reason, we will need to see these three log files.

If you are using the Asset Web Module, you will also need to open C:\Program Files (x86)\Wasp Technologies\MobileAsset\Web and edit web.config in Notepad. Search for Serial#1 and double it, so that part of the line will read Password=$$Serial#1Serial#1

*If these passwords still do not fit your requirements, you will need to contact support and provide us with passwords that will pass your security so we can encrypt them and give you updated scripts.

Helpful Unhelpful

9 of 14 people found this page helpful

This Article Category Knowledgebase
Author
Internal User
Date Created
Jun 4, 2013