1 / 38

MCC v5.03

MCC v5.03. MCC v5.03 User Training Module 5. Creating and Sending Software Packages to Devices Release 1.0 April 2008. MCC 5.03. New features have been added to MCC since the previous intermediate release (v4.02). New features discussed in this module are listed below

irma-sharpe
Télécharger la présentation

MCC v5.03

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MCC v5.03 MCC v5.03 User Training Module 5. Creating and Sending Software Packages to Devices Release 1.0 April 2008

  2. MCC 5.03 New features have been added to MCC since the previous intermediate release (v4.02). New features discussed in this module are listed below • Abort File /Package Transfer • Add a Folder in Package Studio Wizard. • Improved device Cloning

  3. Mobile Control Center At the end of this module the student will be able to: Create “Software Packages” to use with MCC. Create “Rules” to deploy packages. Actually “Deploy” Packages to devices from MCC Use MCC to also “Remove” Packages from devices.

  4. MCC Package Studio Overview Please Note: You do not have to create packages in order to be able to copy or transfer files to a remote device. You could do it via remote display control, by using the Explorer window. However this only works for on-line devices, one device at a time on a “send now” basis.

  5. Package Studio To deploy software or data to single, or multiple, mobile devices at specified times (immediately or later) using MCC you will need to package the software or data into a package file using “Package Studio”. Note: A “Package” consists of a set of files, complete with installation instructions, compressed into a single “package” file.

  6. Package Studio Note: Once you have deployed a package to a device the “package” itself will normally also be viewable on the flash, or non-volatile, memory. The software you “packaged” will automatically be un-packaged and installed to the folder you chose when configuring the package itself. The “Package” file (.PCG) will remain on the device as well as the software you packaged, so that MCC may uninstall the software should you choose to do so by disabling, or deleting the deployment rule.

  7. Package Studio You are also advised to read the section titled “Configure Package Studio”, under “Package Studio” in the MCC help tutorial. This gives you the option to select “Auto Execute” file settings for .EXE, .CMD, .CAB and .REG files from this section which you may find useful later when sending packages to devices.

  8. MCC Package Studio Overview In addition to putting regular files into Packages, you may also optionally add “Scripts” to packages, these scripts get automatically executed at pre-defined points in the installation or un-installation of the package. It is also possible to create packages that only contain scripts to perform a specific task, you may then deploy these “Script” packages to devices.

  9. Package Studio and Scripts Basically Scripts may be anything that can be run under a DOS window, for example, if you type “help” at the DOS window of a device whilst in “Remote Control” mode, you will find items such as “reset /w” which will wipe the device, securely deleting data stored on the device , “reset /H” which will Hard Reset the device, and “reset /S” which will shut down the desktop software. All of these commands and more may be run as a script included with a software package. A package may even just have scripts that you wish to run at a scheduled time.

  10. MCC Package Studio Overview Remember, Package Studio also includes options to automatically process or execute certain types of files such as .CAB or .REG files when they are installed. Therefore the next item we will discuss is “Packages” but before we can do anything with packages we need to find out how they are created. Please see the next slide for details.

  11. MCC Package Studio Overview Working with “Packages” usually requires the following steps. • Create a new Package project. • Add files, or scripts to the Package. • Build the Package. • Create a Deployment rule and deploy the Package. Although this may seems a lot of effort it actually isn’t that difficult. MCC does all the hard work for you. You just need to follow the steps as documented.

  12. MCC Package Studio Overview Note: If you are provided with a package file, e.g. PisonInfo.pcg then you only need to create a deployment rule, add the package to it, and deploy it to the required devices. There is no need to create a new package project, add files, or do a build, because this has already been done for you. Please follow the guidelines in this presentation and the MCC built-in “help” file.

  13. MCC Package Studio Overview The first step to creating a package is to create a “package project” which may be found in the help file under “Package Studio/Create Package Project”. When you have finished this section of the tutorial you should return to this presentation to continue. You are however recommended to view the next six informational slides of this training before continuing.

  14. Package Studio These next few slides also discuss additional options when working with “Packages” including: • Adding a file to an already compiled Package • Adding a Script File to a Package • The use of Script Variables. It is suggested you read these sections of the tutorial first although you will probably want to start by sending a small, basic, package to start with.

  15. Package Studio Before building your “Package” you should also read the section entitled “File Properties Dialogs” This gives you options relating to: • Where on the device the file is stored, • Whether it is always copied to the device, • Whether it replaces an older file, • Or whether it is copied over only if there is not already a file of that name in existence.

  16. Package Studio There is also an option to disallow uninstall. This is because normally a file will be uninstalled from a device if its deployment rule is disabled, or deleted. You may also request that the file is executed immediately after transfer. This can be very useful especially when copying over .CAB files etc.

  17. Package Studio You may also allow an operator to refuse the loading of a package if they are in the middle of a task. Please be aware that if you choose to offer the option to accept/refuse the installation of a package that the resulting dialog box will time out after around 10 seconds and install the package anyway.

  18. Package Studio It is assumed that if the operator does not respond within 10 seconds that they cannot have a problem with the installation going ahead. Note: If the operator does refuse to allow the installation of the package at this time, MCC will continue to try to load the package, and offer the operator a choice each time, until the package is successfully loaded.

  19. Package Studio Note: Even after you have created your “Package Project” you may still add more files by to it by following the instructions in the next section of the tutorial called “Add File”. If you also want to run a “Script” upon deploying the package to a device you should read the following section in the tutorial entitled “Add Script”, also the next heading “Script Variables” will be useful.

  20. Package Studio Please note: It is not essential to have a script in a package before deploying it to a device, this is just an extra option you may wish to use, although remember Packages may consist of just Script Files if that is all that is required. The next slide will show various methods of starting the “Package Studio” application.

  21. Package Studio You may start “Package Studio” by clicking on “Tools” from within MCC as shown below, or use the “Launch” button in the MCC tool Bar, or just double- click the “Package Icon” on your desktop. Or from the Start Button: Start->Programs->Psion Teklogix->Mobile Control Center->Mobile Control Center Package Studio

  22. Package Studio When you first start Package Studio you should see a “tip of the day”. There are currently 7 different tips, and if you wish you may read all of them now by clicking “next tip” repeatedly. Tip of the Day is accessible from the “help” Tab within Package Studio.

  23. Package Studio Once “Package Studio” is started you should refer to the section of the on-line tutorial entitled : “Package Studio/Create Package Project”. This will take you through creating your first package, with a file, for example a .txt file that you can open on the device to test that the transfer was successful. When you have finished creating the package you should then move on to the next slide for details of how to actually “build” the package.

  24. Adding Multiple Files to Packages Adding Multiple Files to Packages

  25. Adding multiple files to packages You may also select multiple files or directories to add to a package. This helps make package creation easy and efficient when multiple files are required. Files may be selected and will appear in the format: “File 1” “File 2” etc, as shown in the “File Name” field on the left.

  26. Package Dependencies Package Dependencies

  27. Package Dependency Package Dependencies provide a mechanism to enforce the order in which packages are installed on a device. For example: Packages A and B need to be installed, but it is mandatory that Package A be installed before Package B. This order can be ensured by configuring a dependency for Package B

  28. Package Dependency To add a package dependency simply select the package, or packages, a specific version, (or any version), that the target package is dependent on whilst configuring. For example, when editing the Package Dependencies for Package B, you would select Package A to ensure that Package B is installed only if Package A is installed first. In the example on the left we have chosen to ensure that any version of the “Scanner” package is loaded to the device before the package currently being configured is also loaded onto the device.

  29. Package Dependency For full details about setting up and using Package Dependencies please go to MCC Help and select “Mobile Control Centre Manager\Packages\ Package Dependencies” as shown on the left.

  30. Package Studio After creating the package project you should go to the “Build Package Project” heading in the tutorial to complete the process. After building the “Package” in Package Studio, you should then “Add” that package to the MCC Manager. This is done by following the tutorial menu section entitled “Add Package” which can be found under “Package/Add Package” you should then return here again to continue with the training.

  31. Package Studio Please now ensure you have followed all of the instructions so far and created a “Package”, no matter how basic it may be before continuing. You next need to go back up the tutorial menu to “Rules/Deployment rules” to see how to actually create a “Deployment Rule” which will send the package to a device. Once complete, check the device to ensure you can locate the package, and file, you have just sent.

  32. Package Studio You should also take note of the “Logs” display on the “Rules” tab to see the progress of the rule. This will show when a rule is Compiled, Processed, changed, renamed, or disabled. Note: If a rule is deleted all logs pertaining to that rule will also be removed from the logs section.

  33. Cloning Package Another item which may be of great interest is cloning. Please see the section “Packages/Cloning Package” in the tutorial for more details. Please Note: This feature clones all PTX TekTerm parameters, (except the session name). You will also need to connect via ActiveSync in order to create the cloning package from a device, you cannot do this via the radio at this time. You may instead do cloning by creating and sending a software package using the .par files from a terminal.

  34. MCC Module 5 Post Training Test. You will now be asked to take a short test consisting of 3 questions from the current module. Answers may be viewed after closing the Slide Show, within the notes section, under “Normal View”.

  35. Question 1 of 3 You have built a software package for installation onto a device, but you now realise you missed out a file you wanted to send. What can you do? A) Delete the package and start again B) Send the package anyway and build a new package with the missing file? C) Add the forgotten file to the package before deploying it by using the “Add File” feature. • Please select all that apply.

  36. Question 2 of 3 How can you execute a .CAB file on a device through Package Studio? A) Send a software package containing the .CAB file to the device, open the Explorer window in Remote Display Control and double-click the .CAB file. B) Include a Script file in the package to execute the .CAB file automatically. C) Configure the file properties dialog to automatically execute the .CAB file. • Please select all that apply.

  37. Question 3 of 3 You have built a clone package which includes the Wireless 802.11 settings. What is the best way to deploy this to a device? A) immediately via ActiveSync. B) via radio to the devices memory card C) manually via the Explorer window in remote control. • Please select one item.

  38. MCC Package Studio This ends module 5 of training for MCC. The next Module covers “Creating & Editing Filters”, and “Generating Reports”. “Filters” allow you to select which devices you see in a view, and “Reports” may be generated for Devices, Rules, Servers etc.

More Related