MOBILE LIFECYCLE MANAGEMENT SUITE: BEST PRACTICES BY: CHAD J. SANDERS

MOBILE LIFECYCLE MANAGEMENT SUITE: BEST PRACTICES BY: CHAD J. SANDERS PURPOSE OF THIS DOCUMENT The purpose of the Mobile Lifecycle Management Suite Best Practices document is to address some of the most common issues and tasks within the Mobile Automation software. Through this document, you will find many bits of information that may be helpful when applied to your environment. You will also find information on Best Practices to help manage your Mobile Automation environment. TABLE OF CONTENTS This Table of Contents is a set of hyperlinks designed to allow you to navigate to a particular section of this document. The following list contains all of the main topics covered in this document. Server Related Information o Microsoft Data Access Components (MDAC) Installation o Database Setup and Configuration o Backup Procedures Agent Related Information o Appearance of the Agent o Locking Down the Agent o Manually Uninstalling the Agent Package Creation and Management o Naming Schema for Packages o Package Storage and Management o Creating and Importing Packages o Reboots, Packages, and the Client Machines Mobile Lifecycle Management Suite (MLMS) Tips o Migration Information o Other Options and Uses for MLMS Other Tools and Tips o Customizing the Context Menu o Command Line Options o Mobile Automation Download Center o Final Note SERVER RELATED INFORMATION This section of the document will cover information regarding the Mobile Automation Primary Command Server and Secondary Command Server. There are several tasks you need to accomplish before installing your Command Server. The Microsoft Data Access Component (MDAC) drivers must be installed depending on the database you are using in conjunction with the Command Servers. Once the correct version of the MDAC drivers have been installed, you must configure the database to be used with the Mobile Automation software. 1

Furthermore, once your Mobile Automation environment has been implemented, you will want to begin backing up the data you collect from your client machines as well as any data stored for use with the Command Servers. 1. INSTALLING THE APPROPRIATE VERSION OF THE MDAC DRIVERS: Prior to installing your Command Server, you will need to install the appropriate version of the MDAC drivers. The version of MDAC drivers you install depends what enterprise database you are using in conjunction with the Primary Command Server. If the Primary Command Server will reside on the same physical computer hardware as the database technology, there is no need to update or install a version of the MDAC drivers. The Primary Command Server and the enterprise database technology may reside on the same physical computer hardware if the environment you are supporting contains no more than 2500 client machines. If you are using Microsoft SQL 6.5 or SQL 7.0, you will need to install the MDAC 2.5 drivers. The install is located in the root of the Mobile Automation CD delivered to you upon purchasing the software. If you downloaded the Mobile Automation software from the Internet, the MDAC drivers are located where you stored the downloaded files. The Microsoft Windows 2000 Server/Advanced Server operating system contains the MDAC 2.5 drivers inherently, so there is no need to install them. If you have chosen to use the Microsoft SQL 2000 database technology, it will be necessary to update your MDAC drivers to version 2.7. The installation can be found in the root of the Mobile Automation CD that was delivered to you upon purchase of the software. If you downloaded the software from the Internet, the install will be located where you stored the downloaded files. 2. CONFIGURING THE DATABASE FOR USE WITH MOBILE AUTOMATION Once you have the appropriate MDAC drivers installed, you need to configure a database instance for use with the Mobile Automation software. The database will be connected only to the Primary Command Server. This document will demonstrate what you need to configure in Microsoft SQL Server to use the Mobile Automation software. First, you will need to open the Microsoft SQL Enterprise Manager (Figure 2-1). The Enterprise Manager allows you to configure and manage databases. 2

Right click on the Databases option and select New Database Figure 2-1 When the Enterprise Manager opens, expand the view on the left hand side of the window so that you can see the various options available for configuration. Locate the Databases option and right-click. From the resulting menu, select the New Database option. A new dialog box will appear allowing you to configure a new database (Figure 2-2). Note the configuration tabs here Specify the name of your new database here Figure 2-2 There are three tabs available for configuration. The first tab, General, allows you to name the new database. You may type in any name you like. However, it is recommended that the database be named ma2000 as in Figure 2-2, above. Since the Mobile Automation 3

software is the only application that will be using the database, it should be named something that relates to the Mobile Automation software. Whatever you choose to name you database, make sure you have the name written down for later use with the installation of the Mobile Automation software. When you have entered the name of your database, you may select the next tab, Data Files (Figure 2-3, top of next page). The Data Files tab allows you to specify the options for the data files that will be associated with the new database you are creating. In most cases, the options for the location of the files can be left at the default. However, if you are storing your database on a separate hard disk or a different location, specify the correct location here. Within this dialog box, the options to specify the size and the type of growth you would like to associate with the database file are available. To determine how large the database file should be in relation to the Mobile Automation software, you will need to know how many client machines you will be supporting in your environment. Each client machine requires at least 50k (kilobytes) of database space. For example, if you have 500 client machines you will need at least a 250MB database file to retain all of the information. It is also recommended that you set the database option to Automatically Grow the database file. Enabling this option allows you to specify how to grow the file (in Megabytes or in Percentage). The Mobile Automation software will work with either of the available growth options. Select the option that suits you. Furthermore, this dialog box allows you to restrict the growth of the file, if needed. If the hard disk where you are storing the database file has a limited amount of space, you may need to restrict the growth of the database file. Once you have selected the options, click the last tab, Transaction Log. Specify the growth options here Specify the location and size of the database here Figure 2-3 The Transaction Log tab (Figure 2-4) allows you to specify the options for the Transaction Log file used in conjunction with the database you are creating. Microsoft recommends that the Transaction Log file be at least twenty percent (20%) of the overall size of the database you are creating. 4

Specify the growth options here Specify the location and size here Figure 2-4 For example, if your database has been configured (using the Data Files Tab) to be 250MB in size, then your Transaction Log file must be no smaller than 50MB (or 20% of 250MB). Again, specify the options for growth in the lower half of the dialog box. It is recommended that you specify the same settings for the Transaction Log file as you did for the Data File in relation to growth. Once you have specified all of the necessary options, click the OK button to create the database. The creation of the database may take several minutes depending on the hardware resources available on the server where the database is installed as well as the overall size of the database you have created. Now that you have created the database to be used with the Mobile Automation software, it is recommended that you create a Login ID to be associated with the database. Since the Mobile Automation software will be the only application accessing the database, it is recommended that you create a Login ID specifically for use with the implementation. To create a Login ID you will need to return to the Enterprise Manager and expand the Security folder on the left side of the screen (Figure 2-5, top of next page). 5

Expand Security to create a new Login ID Figure 2-5 When the Security folder expands, select the Login menu item and right-click. Select the New Login option. A new dialog box will appear prompting you to enter information about the new login (Figure 2-6, top of next page). There are three tabs present at the top of this dialog box. For creating a Login ID to be used with the Mobile Automation software, only two of these tabs will be used. The first tab, General, allows you to specify the name for the login, the type of authentication you would like to use, and the default database to which the login will be connected. It is recommended that you name the database login ma2000. Naming the login ma2000 allows you to easily associate the Mobile Automation software with the login being used. Furthermore, since the Mobile Automation software will be the only application using this login, this name is perfect. Once you have specified the name of the login, select the type of security you would like to use. 6

Enter the login name here Select the type of security here Select the default database here Figure 2-6 The security that you choose depends on your environment. However, for most installations and environments, using the SQL Server Authentication method for security will work fine. Whichever security method you choose, enter the necessary information (username/password) in the text boxes provided. After you have selected the type of security to use with the database, select the default database with which the new login name will be associated. Since the database was created earlier in this section of the document, you will be able to see the ma2000 database listed in the drop-down menu. Select the ma2000 database from the list. The next tab that needs configuration is the Database Access tab (Figure 2-7, top of next page). This tab allows you to select the permissions the new login name will have to the database. In the upper half of this dialog box, select the database which you would like the Login ID to have access to. In this case, select the ma2000 entry. Once you have selected the database, the second half of the dialog box will appear. This portion of the dialog box allows you to define a role for this Login ID. Select the Public role (if it is not already selected) and select the db_owner role. The db_owner role allows the Mobile Automation software to create the database tables, links, and fields automatically during the setup of the software. This concludes setting up the database and the login associated with the Mobile Automation software. You may now close the Enterprise Manager. It is recommended that you reboot your computer after the database and login have been created. 7

Select the database to permit access to Select the database role to assign to the login Figure 2-7 3. BACKUP PROCEDURES RELATING TO MOBILE AUTOMATION The Mobile Automation software collects a plethora of information from the client machines and stores this information in the Mobile Automation database. Furthermore, the packages that have been created for use in the Mobile Automation environment are stored on the Primary Command Server installed in your environment. There are several occasions in which you may need to restore data into your Mobile Automation environment. A serious failure within the server operating system on your Primary Command Server, a failure within the database server associated with Mobile Automation, or even an error within the Mobile Automation software may be cause to rebuild your environment. Once your new environment has been implemented, you may want to restore the previous data collected to refresh the implementation to the state that it was in prior to the rebuild. To properly backup your Mobile Automation environment, there are several items that need to be addressed. These items are listed below: The database associated with the Mobile Automation environment The Archive directory located on the Primary Command Server The datamap.ini file located on the Primary Command Server To restore information residing in the database, you will need to have a backup copy. The information a database backup will restore is related to client machine inventory, server information, extensive logging information, and any other information that is viewable from within the Mobile Automation Console. To backup the database associated with the Mobile Automation environment you will need only to select the backup software of your choice and setup a backup job to backup the database. No special procedures are necessary to complete a backup of the Mobile Automation database. Depending on how accurate and up-to-date you want the information stored in the Mobile Automation database when it is restored is a direct reflection of how often a backup of the Mobile Automation database should be completed. Regardless of the 8

age of the information stored in the Mobile Automation environment, when the client machines make the next scheduled connection to the Primary Command Server, the Agents will update the database with the latest information. The next item that should be backed up is the Archive directory. The Archive directory is the location in which all packages for the Mobile Automation environment are stored. The location of the Archive directory is \Program Files\Mobile Automation\Archive on the Primary Command Server. There may be many directory structures beneath the Archive directory so make sure you backup not only the Archive directory, but the subdirectories as well. Backing this data up allows you to have an accurate copy of the packages being utilized within the Mobile Automation environment. The last piece of information to backup on your Primary Command Server is the datamap.ini file. Backing up this file is an optional task. However, if the database and inventory information have been customized, you will want to back this file up to retain the customizations that have been made. The location of this file is the \Program Files\Mobile Automation directory on the Primary Command Server. AGENT RELATED INFORMATION The Mobile Automation Agent is the client portion of the Mobile Automation software. There are many settings within the Mobile Automation Agent which allow for easy configuration and communication in a variety of enterprise environments. This section of the document will address information concerning the visibility of the Mobile Automation Agent, locking down the settings for the Agent, and the procedure for uninstalling the Agent manually from a client machine. 1. APPEARANCE OF THE MOBILE AUTOMATION AGENT Installing the Mobile Automation Agent on your client machines allows them to be managed from the Mobile Automation Console. There are many different options available when configuring your Agent installations from the Deploy Agent Wizard within the Mobile Automation Console. One of the most commonly adjusted Agent options is the Appearance of the Agent on the client machines. When the Deploy Agent Wizard is initialized, select the button Modify PC Agent Settings (Figure 3-1). To configure the PC Agent options, select this button Figure 3-1 9

Clicking on the Modify PC Agent Settings button opens a new dialog box with a series of tabs across the top (Figure 3-2). Select the Advanced Tab of the dialog box. Select the appearance of the Agent here Figure 3-2 Once you have the Advanced Tab selected, the top of the dialog box allows you to specify how the Agent will appear on the client machines when it is installed. There are three options for the appearance of the Agent and each one is described below. MINIMIZED ON THE TASKBAR DEFAULT SELECTION: The Minimized on the Taskbar option is the default selection when configuring the Agent options. When this option is selected, the Agent will appear on the client machine (in the taskbar) as a small computer icon in front of a globe. The appearance is shown in Figure 3-3. Mobile Automation Agent icon on taskbar Figure 3-3 SHOW AGENT WINDOW: The Show Agent Window option displays the status window for the Mobile Automation Agent. The status window is shown in Figure 3-4 (top of next page). 10

Figure 3-4 This is the window that will be displayed (when the client machine boots up) for the Mobile Automation Agent in the event that you select the Show Agent Window option. HIDDEN: The Hidden option within the Agent Appearance settings allows you to completely hide the Mobile Automation Agent from the eyes of the user. This means there will not be any appearance in the taskbar or display of the status window when the client machine boots up. This is the most commonly used appearance setting in enterprise environments. It is important to note, however, that when hiding the Agent on the client machines you may need to specify an additional option related to the Mobile Automation Live Support (remote control) feature. If you have chosen to use the Attended Mode Live Support functionality in your environment, the users will need to initialize and accept the incoming remote control connection request. To do this, by default, the user will need to right-click on the Agent in the taskbar (on the client machine) and select the Start Live Support option from the pop-up menu. If you hide the Agent on the client machines, there is no way for the user to initialize the Live Support connection. To allow the user to initialize and accept the incoming connection request, you will need to add a Live Support icon to the Start Menu of the client machine. To do this, select the Live Support Tab within the PC Agent Settings of the Deploy Agent Wizard. The Live SupporTab is shown in Figure 3-5 (top of next page). The Live Support Tab contains options relating to the remote control functionality of the Mobile Automation software. At the bottom of the dialog box, you will see an option to Add the Live Support Icon to the Start Menu. If you would like to add the icon for Live Support automatically, place a checkbox next to this option. It is recommended that if you are hiding the Mobile Automation Agent on the client machines and are using the Attended Mode Live Support (meaning that a user must initialize and accept the incoming connection request at the client machine) that you select this option available on the Live Support tab (see Figure 3-5, top of next page). 11

Select this checkbox to add the Live Support icon to the Start Menu Figure 3-5 2. LOCKING DOWN THE MOBILE AUTOMATION AGENT: When configuring the Mobile Automation Agent for installation on the client machines, you can select options to lockdown the Agent to prevent the users from changing configuration settings. The options are available on the Advanced Tab of the PC Agent Settings dialog box (Figure 3-6). Lockdown options for the Agent Figure 3-6 The checkboxes that allow you to lockdown the Agent are located in the bottom section of the Advanced Tab. Each option, and a description of what the option does, is listed below: 12

PREVENT USER FROM CHANGING CONFIGURATION SETTINGS: This option allows you to prevent the user from changing the configuration settings of the Mobile Automation Agent. When this option is selected, the Settings button within the Mobile Automation Agent will be grayed out and inaccessible (Figure 3-7) Options button is unavailable Figure 3-7 DISABLE THE UNLOAD OPTION: This option prevents the user from unloading the Mobile Automation Agent. When this option is selected, the Unload button will be grayed out and inaccessible (Figure 3-8). Unload option is unavailable Figure 3-8 3. MANUALLY UNINSTALLING THE MOBILE AUTOMATION AGENT: There may be some instances where you will want to uninstall the Mobile Automation Agent manually from a client machine. For example, if the client machine does not have network connectivity (cannot receive the default Agent Uninstall Package from the Primary Command Server) and you want to uninstall the Agent, you will need to remove it manually. To uninstall the Agent manually follow these simple instructions: If the Agent is installed on a Windows NT-Based operating system (Windows NT, 2000, XP), open the administrative object Services. Among the services listed in the dialog box, select the Mobile Automation Agent service and the Live Support Host service (the Live Support Host option may not be listed depending on your environment s Agent configuration). Each of these services must be stopped. Open the Task Manager (Windows NT, 2000, XP) or the Task List (Windows 9x) and select the following running tasks and kill (or end) them if any of them are running: o Marchost.exe o Rsstatus.exe o Rstate.exe 13

Ending the processes will allow you to remove the files and registry keys associated with the Agent. Open the Windows Registry Editor and navigate to the registry key HKLM\SOFTWARE\Mobile Automation. Once you have located this registry key, delete it. Close the Registry Editor Open Windows Explorer and navigate to where the Agent is installed. The default location is the \Program Files\Mobile Automation directory. When you locate this directory, delete it. Close Windows Explorer If you are running an operating system that is based on Windows 9x, you will need to locate the autoexec.bat file on the local C: drive. Once located, select to Edit the file. Remove the line (or REM it out) that refers to the \Program Files\Mobile Automation directory (may be shown as \Progr~1/Mobile~1). Save and close the file Reboot the client machine PACKAGE CREATION AND MANAGEMENT When using the Mobile Automation software in your environment you will generate many new packages through the process of ongoing management of the client machines. There are several key points of information to make note of when creating and managing packages for your environment. This section of the document will address naming schemas for packages, importing packages, the storage of packages, and rebooting the client machines from packages. It is important to note that all packages must be located in the Mobile Automation directory on the Primary Command Server under the Archive directory. The default location is \Program Files\Mobile Automation\Archive. Packages can be stored directly beneath the Archive directory or under subdirectories. 1. NAMING SCHEMAS FOR PACKAGES: When creating packages, you will need to save them to use them in your Mobile Automation environment. When you save packages, you should name them in a manner that is easily recognizable, yet detailed enough to distinguish them from others. A couple of examples/scenarios are listed here and a naming schema is suggested. It is important to remember that when you save your packages, they will show up exactly as they were saved inside the Console under the Packages Views. Scenario 1: Acrobat 5.0 Upgrade for the Sales Force You are creating a package that you will be delivering to Sales Force users only. This package has been designed to update Adobe Acrobat from version 4.0 to version 5.0. A possible name for this package is: Sales Force Acrobat 4.0 to 5.0 Upgrade.pkg By naming the package in this manner, it is very easy to determine what this package has been designed to do as well as the group of machines the package is to be sent to. Scenario 2: Service Pack 3 Upgrade for Windows 2000 with Forced Reboot You are creating a package that will be sent only to Windows 2000 client machines. The package is going to install Service Pack 3 into the operating system. The package is also going to force a reboot after the installation of the Service Pack. A possible name for this package is: Windows 2000 Service Pack 3 Install (Forced Reboot).pkg 14

Remember, the way you save the package is how it will show up in the Mobile Automation Console. 2. PACKAGE STORAGE AND MANAGEMENT: As stated in previous information, all packages must be located under the Archive directory on the Primary Command Server. The location of the Archive directory is \Program Files\Mobile Automation\Archive. Packages may be stored directly beneath the Archive directory or in subdirectories. When storing packages, if you store them beneath subdirectories of the Archive directory, the folder structure will be viewable inside the Mobile Automation Console (Figure 4-1). Subdirectory structure of Archive displayed here Figure 4-1 For example, if you have packages that will be sent to Sales Force users, you can save the packages in \Archive\Sales Force and the Sales Force directory (with the packages listed beneath it) will be displayed in the Console. If you create a directory with no packages inside, the directory will not show up in the Mobile Automation Console. This feature is available in the 5.1 version of the Mobile Lifecycle Management Suite. 3. CREATING AND IMPORTING PACKAGES: Packages can be created using the Mobile Automation Package Editor located on the Primary Command Server or on a stand alone workstation that has the Package Editor installed. When creating packages locally on the Primary Command Server, the packages will immediately show up in the Console. However, when creating packages on a stand alone workstation (which has the Package Editor installed), the packages will need to be imported into the Mobile Automation Console. To import a package into the Console, save your package in the Archive directory of the Primary Command Server (if it is not already saved 15

there). Remember, you can save in subdirectories as well. Once it is saved, open the Console and from the toolbar, select the Packages menu item. From the drop down menu, select Import Package. A dialog box will appear with the Archive directory selected and the subdirectories listed in the window. Select the location of the package (to select multiple packages, hold the CTRL key on your keyboard) and click the Open button. If you do not see your package(s) show up in the Console Views, press the F5 key on your keyboard to refresh the view. 4. REBOOTS, PACKAGES, AND THE CLIENT MACHINES: When creating packages for use in your Mobile Automation environment, you will undoubtedly create packages that require reboots after the package has executed (for example, when installing a new application) or any time you wish a reboot to occur. First of all, when creating third-party package files (such as Wise InstallMaster, InstallShield, MSI packages, etc) that will be included inside Mobile Automation Packages, if the installation requires a reboot, suppress it in the third-party package you are creating. By suppressing (or skipping) the reboot inside the third-party package that will be inside of a Mobile Automation Package, you allow the Mobile Automation software to handle the reboot process. For example, if you install a Microsoft Service Pack, a reboot is often required. Instead of allowing the Service Pack Install application to reboot the computer, skip this step. You can then add a Restart Windows command into the package which contains the Service Pack Install application. When this Restart Windows command is used, the client machine will reboot, but continue doing other management tasks (within the same Mobile Automation Package) after the reboot has occurred. This will allow you to complete further verification testing (or many other tasks) after rebooting the client machine. MOBILE LIFECYCLE MANAGEMENT SUITE (MLMS) TIPS The Mobile Lifecycle Management Suite (MLMS) allows administrators to discover and inventory technology assets, manage these assets, provide support, and migrate the assets from out-dated equipment to new machines. This section of the document will discuss information concerning the migration functionality available in the MLMS software and the tools used in the migration process. 1. MIGRATION INFORMATION: When using the Mobile Automation software, you may decide to use the migration functionality available. Depending on whether you have purchased this capability, you may need to contact your Mobile Automation Sales Representative. When preparing to do an operating system migration, there are several steps you may want to take before beginning. Below is a high-level example migration plan: Determine what operating system you will be migrating to on your client machines. You will need to build a Master-Client machine (that will be setup in the way you want all client machines to be setup after migrating to the new operating system). The Master-Client machine will need to have the Mobile Automation Agent installed. You will use this client machine to build your master image which will be applied to all of your target client machines. Determine the system requirements for the new operating system on the client machine. For example, determine the required processor speed, amount of physical memory, hard disk space, etc.) 16

Determine the overall size of the new image being created from the Master-Client. You will need to know this information to ensure there is enough hard disk space available on the client machines to receive the new operating system image Determine the amount of data on the client machines that will be migrated. To do this, use a Mobile Automation Package. Build the package to locate all of the file types you want to migrate (*.doc, *.xls, *.pst, *.ppt, etc). Once these files are located, you can use the Arithmetic Command to add up the sizes of the found files on the client machine. This information can be stored as inventory information (which is the recommended option). To include this info as inventory, you will need to customize your inventory. Contact Mobile Automation Tech Support for assistance in this matter Build a Dynamic Group in the Mobile Automation Console based on the system requirements you collected above (or system requirements you feel are necessary for the new operating system on the client machines). Be sure to include the amount of disk space (approximately) needed for migrating user data. Furthermore, be sure to include the necessary hard disk space to receive the new image file. To calculate this, take the size of the master image and multiply by two. This is because when the package is received, it will be stored in the staging directory for the Mobile Automation Agent. When executed, the master image will be extracted into the separate partition on the hard drive and the original package will be deleted from the staging directory On the existing client machines in your environment, conduct an environment-wide inventory collection for both hardware and software Once the inventory collection process is complete (this may take some time depending on how often your client machines attempt to scan the Primary Command Server for new packages) your Dynamic Group will only contain machines that meet the requirements specified when creating this group Create the packages associated with the migration process. There are four steps for the migration process: o Step 1: Create the Master-Image (discussed the first bullet point listed on Page 15) this step is only done on one client machine (Master-Client machine) o Step 2: Prepare the Client Machines to Receive the New Image: this step creates a partition on the client machine (you can make the partition hidden) to store the new operating system image file and the user data during the migration o Step 3: Deploy the New Image to the Client Machines: this step creates the package that contains the new operating system image and delivers it to the o client machines new partition Step 4: Commit the New Image to the Client Machines: this step captures the user data and settings, applies the new operating system image delivered in the previous step, and then applies the user data and settings into the new operating system Determine how you want to complete the entire migration process. The migration packages (Steps 2 ~ 4) are created as separate packages by default. However, you may nest all four packages into a single package, allowing you to send one package to all client machines to complete the entire migration process. The recommended strategy is to send the package corresponding to each Step as separate packages. For instance, on Day I of your migration plan, send the Prepare package to the client machines. Once you have verified that the clients have successfully executed this package, send the Deploy Package, and so on. 17

2. OTHER OPTIONS AND USES FOR MLMS: The migration functionality within the Mobile Automation software is built upon a number of tools that are available with the installation of the software. The tools the migration process is built upon are the following: Virtual Floppy technology User Data and Configuration Setting capture tools Hard Disk Configuration and Partitioning tools Imaging technology These tools can be used a number of different ways. Some examples of other uses of the available technology (and a high-level description of what is needed to accomplish them) are listed below: Capture an Image of the existing Operating System on a Client Machine: a Mobile Automation Package can be created to capture an image of the existing operating system on a client machine. To do this, you would need to create a Virtual Floppy that contains the necessary drivers and configuration files to image a client machine (and probably store this image on a network drive). Then, create a Mobile Automation Package that contains the Virtual Floppy needed to image the client machine and the ability to initialize the Virtual Floppy environment Capture the User Data and Configuration Settings from a Client Machine: a Mobile Automation Package can be created to capture the user data and configuration settings from the client machines. To accomplish this, you will need to create the necessary command files associated with the capture of these settings. Then, create a Mobile Automation Package that will execute the application which captures these settings. You can then have the package store the captured data and settings locally or on a network share or mapped drive Image a Client Machine from a Network Drive: the default process for the migration functionality is to deliver the new operating system (and store it locally) to the target client machine. In some instances, this may not be possible (there may not be sufficient hard disk space). If you would like to install a new operating system from a network share or mapped drive, you will need to create a Virtual Floppy that contains the necessary drivers and configuration files to image a client machine from a network drive. This Virtual Floppy could then be included in a Mobile Automation Package containing the necessary commands to initialize the Virtual Floppy environment and delivered to the client machines Adjust Hard Disk Partitions on the Client Machines: the hard disk management tools available allow you to adjust partitions on the client machines. This can be accomplished by building a Virtual Floppy which contains the hard disk partitioning application and configuration files. This Virtual Floppy can then be included into a Mobile Automation Package along with the command to initialize it, and delivered to the client machines Adjusting the Default Migration Process: the default migration process (discussed earlier in this section) can be adjusted at any time. In the event that you want to make changes or include additional commands (custom log entries are a good example), you can open and edit the packages you create using the Migration Wizard from within the Mobile Automation Console. Any of the command files located in these packages can be extracted, edited, and re-inserted into the package. This capability allows administrators to easily create migration packages using the Migration Wizard process, while enabling them to customize and tweak these packages to fine-tune any type of package or migration process they plan to use 18

OTHER TOOLS AND TIPS There are several other bits of information that may be helpful when managing your Mobile Automation implementation. This section will discuss adding menu items to the Context Menus of the Mobile Automation Console, command line options available for the Command Server and the Agent, the Mobile Automation Download Center, and a final note concerning the Mobile Automation software. 1. CUSTOMIZING THE CONTEXT MENUS: The Context Menus within the Mobile Automation Console can be customized to include packages and menu items that can execute external processes. The Context Menu can be seen if you select any client machine within your Mobile Automation Console and right-click with your mouse. A small menu will appear on the screen and this is called the Context Menu. You may want to customize the Context Menu if there is a package that you regularly send to the client machines. By including this package on your Context Menu, you can send it to a client machine with fewer steps. To add a package to the Context Menu, locate the package you want to include (from within the Mobile Automation Console) and right-click with your mouse. From the menu that appears, select the Properties item. A dialog box (Figure 5-1) will appear allowing you to adjust the properties of the selected package. Locate the Advanced Tab in the dialog box. Select this option if you want the package to show up in the Context Menu Figure 5-1 Near the bottom of the dialog box, you will see Add to Machine Context Menu during Package Import. Selecting this checkbox will force the package to appear on the Context Menu when right-clicking on a client machine. You can also place commands into the Context Menu that will execute any external command. This type of configuration is done through the DeviceMenuTable within the Mobile Automation database. This is a detailed process and will not be covered in this document. If you would like more information of this process, please contact the Mobile Automation Tech Support Department. 19

2. COMMAND LINE OPTIONS: There are command line options available for use with the Mobile Automation software on both the Command Server and the Agent. These command line options (and a short description) are listed below: Mobile Automation Agent: o Launch the Agent Status Window: in the event that the Agent on the client machine is hidden and you need to access the status window, type the following command at the command prompt on the client machine: rsstatus.exe /manual o Launch the Mobile Automation Download Center: in the event you want to launch the Download Center from a command line, type the following command at the command prompt on the client machine: rstate.exe /downloadcenter o Force the Agent to Scan the Primary Command Server Immediately: if you want to force the Mobile Automation Agent to scan the Primary Command Server for new packages immediately, at the command prompt, type the following: rstate.exe /scannow o Force the Agent to Reload the Settings from the Registry: if you make changes to the Agent on a client machine (through the registry or by adjusting the settings from the Agent dialog box) and want to update the changes, open the command prompt and type: rstate.exe /reloadsettings o Force the Agent to Scan for Incoming Live Support Connections: if you want to force the Agent to scan for an incoming Attended Live Support connection, open the command prompt and type the following: rstate.exe /livesupport Mobile Automation Command Server: o View Cache Information on the Server: to view cache information on the Command Server, open a web browser and type the following into the address box: http://<servername >/ma2000/maext.dll?debug o View the Number of Installed Nodes (Agents): to view numbers related to the Mobile Automation environment (number of Command Servers, PC Agents, Handheld Agents, etc.), open a web browser and type the following in the address bar: http://<servername>/ma2000/maext.dll?nodestatus Please note that these command line options probably won t be needed unless asked by the Mobile Automation Technical Support Department. 3. MOBILE AUTOMATION DOWNLOAD CENTER: Another feature of the Mobile Automation software is the Download Center. The Download Center allows packages to be published to a web page automatically and made available to the client machines. The user can then access this web page (through the Agent or from the Start Menu) and select packages to download. For example, if you have some applications within your environment that not every client machine needs to have, but you would like the users to be able to install it if they want it (while still supporting the installation and retaining administrative control), you can place the package (or installation) on the Download Center. To do this, select the package you would like to include on the Download Center from your Console and right-click. From the pop-up menu, select the Properties item. A new dialog box will appear allowing you to adjust the properties of the selected package. From the tabs across the top of the dialog box, select the Advanced Tab (Figure 5-2, top of next page). 20

Select this option to publish the package to the Download Center Enter the text you want displayed in the Download Center in relation to the package Figure 5-2 Selecting the checkbox that says Publish to Download Center will add the package to the Download Center. The Description text box allows you to type what you want displayed in the Download Center in relation to the package being published. In the above figure (Figure 5-2), the Download Center will display the link to the package as Agent Configuration Change. There are a couple of items to note when using the Mobile Automation Download Center. When Agents access the Download Center, all of the functionality of the Mobile Automation is utilized. For example, the Mobile Automation Agent downloads the package from the Command Server/Relay Server, the Bandwidth Throttling and Checkpoint Restart functionality are used in the delivery of the package to the client machine, and the extensive logging capability is also retained. Furthermore, if you decide to use the Download Center and the Agent has been hidden from view of the user (Page 11), you will need to provide a way to access it. By default, the Download Center is accessed by right-clicking on the Agent icon on the client machine and selecting the Goto Download Center item. This will launch a web browser with the Download Center loaded inside. If you hide the Mobile Automation Agent, there is no way for the user to access the Download Center. To provide a way to access the Download Center from the client machines, open the Agent settings and select the Advanced Tab, as seen in Figure 5-3 at the top of the next page (Agent settings can be adjusted by double-clicking on an individual Agent at the client, by reconfiguring the Deploy Agent Wizard, or by creating an Agent Configuration Change Package). 21

Select this option to add the Download Center icon to the Start Menu Figure 5-3 Once the Advanced Tab is selected, locate the Add Download Center Shortcut to the Start Menu option near the bottom of the dialog box. Select this option and a Start Menu shortcut will be automatically added to access the Download Center. 4. FINAL NOTE: When managing your client machines and your Mobile Automation environment, the most important thing to remember is that anything that can be done locally on the client machine (as if you are sitting at the machine with administrative rights), the Mobile Automation software can be used to accomplish the same task remotely. The reasons for this are the use of the local system account in relation to the Agent, the ability to impersonate a local (or domain) user to accomplish external tasks without elevating the currently logged in user s permissions, and the ability to execute any external command (from executables within Windows or from a command line interface). These capabilities allow for extreme flexibility when managing the client machines as well as unprecedented management control from a remote location. 22