White Paper Vodafone Mobile Connect IT...

White Paper

Issue: August 2007

Version: 004

Vodafone Mobile Connect IT Administrator’s Guide

White Paper Issue: August 2007 Vodafone Mobile Connect / 62

Contents

IT Administrator’s Guide 3 Installation of the Vodafone Mobile Connect Software 3

Introduction 3 Operating Systems 3 Software Requirements 3 Launch Conditions 3 Installing the Vodafone Mobile Connect Software 4 Installation Sequence 4 Installing the Devices 8 First-time Device Installation Sequence 8

Installation and Customization from Command Line 11 Introduction 11 Command Line Parameter for msiexec.exe 11 Command Line Parameter for setup_vmc.exe 14 Examples for silent installations 15

Embedded Customization using Network Operator file 16 Introduction 16 Authoring a Network Operator file 16

Embedded Customization using a modified User Profile file 17 Introduction 17 Creating and Authoring a customized User Profile 17

Using Transforms for Customization 18 Introduction 18 Creating Transforms 18 Authoring Transform files 20 Applying Transform files with setup_vmc.exe 27

Scenarios for IT Administrators 31 A. Installation of VMC9 on a computer 31 B. VMC 9 and Limited Users 31

Frequently Asked Questions (FAQ) 32 How to display hidden files and folders in Windows explorer 32 The folder which contains the VMC files that were created on run-time 32 How to create Windows Installer logging files 32 How to find the VMC logging files 33 How to control the logging files 33 How to enable an additional WLAN trace 35 Which items remain on the system after uninstalling VMC 9? 35 Where to find which user data files 35 Which Registry values are used by VMC 9? 35 Which network identifiers are used by VMC 9? 39 Which language identifier codes are used by VMC 9? 39 How to add programs/executables in VMC’s left-hand navigation bar in the “Other Programs” area 40 How to install the .Net Framework 2.0 silently 41 Which devices are supported by VMC 9? 41 How to disable the feature WLAN after a successful installation? 41

Further Information 42 Appendixes 43 Appendix A1 – Network Operator File (Opco file) 44 Appendix A2 – Sample Network Operator File 48 Appendix B1 – Mobile Connect Profile File 50 Appendix B2 – Sample Mobile Connect Profile File 53 Appendix C1 – SMS Profile File 55 Appendix C2 – Sample SMS Profile File 57 Appendix D1 – Settings File 58 Appendix D2 – Sample Settings File 59 Appendix E1 – Conflicting Applications Decisions Fil e 61 Appendix E2 – Sample Conflicting Applications Decisi ons File 62


IT Administrator’s Guide This document covers installating the Vodafone Mobile Connect software on Microsoft® Windows® operating systems.

Installation of the Vodafone Mobile Connect softwar e Introduction This document is based on version 9.2 of the Vodafone Mobile Connect software (VMC 9). The installation of VMC 9 requires certain Microsoft software to be installed on the target computer. This software will be installed from the VMC 9 software media, e.g. a VMC 9 CD, if it is not already present. The VMC 9 installer then checks specific launch conditions before proceeding with the installation.

Operating Systems VMC 9 is available for the following Windows operating systems: � Windows 2000 and Service Pack 4 ¹ � Windows XP and Service Pack 2 � Windows Vista 32 � Windows Vista 64 ¹ (¹ WLAN not supported)

Software Requirements There are four requirements for installing VMC on a computer that is not running Windows Vista. These software requirements will be checked by the setup_vmc.exe program, but are not relevant for Windows Vista: � Microsoft’s Windows Installer 3.1 ² � Microsoft’s .Net Framework 2.0 ² � Microsoft’s Core XML Services (MSXML) 6.0 ³ � Microsoft Wireless LAN API (KB918997) ³ (² already included in the setup_vmc.exe package) (³ only required for Windows XP/SP2, to be downloaded from Microsoft’s on-line download support)

Launch Conditions Once the software requirements have been verified, the setup_vmc.exe program starts the Microsoft Installer with the Vodafone Mobile Connect .msi database file. The database will check for the following launch conditions: � Administrator permissions � Operating System Windows XP with Service Pack 2 or Windows 2000 with Service Pack 4 or Windows Vista � Previous versions of the Vodafone Mobile Connect Software have to be removed � Microsoft’s .Net Framework 2.0


Installing the Vodafone Mobile Connect software Start the file setup_vmc.exe and follow the instructions in the windows presented by the installation process.

Installation Sequence 1. Language Window The language of this window is determined by the system language settings of the computer. The user can choose the language for the installation process from the drop-down menu. The chosen language will be used for the Vodafone Mobile Connect 9 software, too. The following 25 languages are currently supported.

� Arabic (Egypt) � French (Belgium) � Portuguese (Portugal) � Chinese � French (France) � Romanian (Romania) � Croatian (Croatia) � German (Germany) � Russian (Russia) � Czech (Czech Republic) � Greek (Greece) � Slovenian (Slovenia) � Danish (Denmark) � Hungarian (Hungary) � Spanish (Spain) � Dutch (Belgium) � Italian (Italy) � Swedish (Sweden) � Dutch (Netherlands) � Latvian (Latvia) � Turkish (Turkey) � English (United Kingdom) � Lithuanian (Lithuania) � Finnish (Finland) � Norwegian (Norway) 2. Preparation Window The setup_vmc.exe program displays this window while checking the operating system version as well as other system requirements for installing the Vodafone Mobile Connect Software to the target system.

3. Vodafone Network (OPCO) Window This window is the first one which will be displayed after the setup_vmc.exe program (setup launcher) has finished successfully. A network operator must be chosen in order to continue with the Vodafone Mobile Connect Installer. Otherwise the button labelled ‘Next >’ will remain disabled. The installation tries to detect the network operator from the operating system, and pre-select it in the drop-down menu. Otherwise the default text ‘Please select your network operator …’ will be displayed. The following 44 networks are available.


� A1 � SFR � Vodafone Greece � Bite Latvija � Si.mobil-Vodafone � Vodafone Hungary � Bite Lietuva � SmarTone-Vodafone � Vodafone IE � Celcom Malaysia � Swisscom Mobile � Vodafone IT � Cytamobile-Vodafone � TDC Mobil � Vodafone K.K. � DIALOG � TDC Song � Vodafone Malta � Elisa � Telenor Sweden � Vodafone NL � Elisa Estonia � Vipnet � Vodafone NZ � LUXGSM � Vodacom � vodafone P � MobileOne � Vodafone Albania � Vodafone RO � MTC-Vodafone BH � Vodafone Australia � Vodafone Spain � MTC-Vodafone KT � Vodafone CZ � Vodafone TR � M-Tel � Vodafone DE � Vodafone UK � Vodafone Iceland � Vodafone Egypt � XL-Indonesia � Proximus � Vodafone Fiji 4. License Window The installation will proceed only if the user accepts the terms in the license agreement by clicking on the radio button labeled ’I accept the terms in the license agreement‘. Otherwise the ’Next >‘ button will not be enabled. This window can be hidden during installation by setting the element ‘AskEULA’ to ‘False’ in the <opco>.xml file.

5. Reporting Window Reporting can be switched on or off by clicking the respective radio button. This window can be hidden during installation by setting the element ‘AskReports’ to ‘False’ in the <opco>.xml file. The value of the Reporting option is also controlled by an entry in the <opco>.xml file.

6. Account Type Window The Account Type depends on how the customer is paying for using the mobile phone operator’s network. This window can be hidden during installation by setting the element ‘AskAccountType’ to ‘False’ in the <opco>.xml file. The value of the Account Type option is dependent on the option being displayed: hiding this window means that the Account Type is automatically set to ‘Contract’.


7. TCP/IP Settings Window The ’Optimise Settings’ option is used to set some TCP/IP parameters in the Windows Registry. Allowing optimization requires a reboot of the system after installation. This window can be hidden during installation by setting the element ‘AskTcpSettings’ to false in the <opco>.xml file. The value of the TCP/IP Settings option is controlled by an entry in the <opco>.xml file, as are the actual TCP/IP settings to be applied.

8. Setup Type Window For the Vodafone Mobile Connect installation, there are two setup types – ‘Standard’ installation or ‘Custom’ installation.

9. Installation Options Window (only Custom Install ation) The installation options which are handled by this window are the location of the installation folder and whether to create shortcuts for the Vodafone Mobile Connect Software and the Vodafone SMS program on the desktop. This window can be hidden during installation by setting the element ‘AskInstallationPath’ to ‘False’ in the <opco>.xml file. The installation folder path and the desktop shortcut option are also controlled by entries in the <opco>.xml file.

10. Features Window (only Custom Installation) Certain features offered by the network operator (OpCo), but not wanted by the user, can be de-selected by the user (note: WLAN is not de-selectable). This window is customisable by entries in the <opco>.xml file in terms of visibility of the features. Features are WLAN, Optimisation Software, and SMS.


11. Summary Window The Summary window displays the items chosen in the preceding installation windows. Clicking the ‘Install’ button starts the installation of the Vodafone Mobile Connect software on the target computer.

12. Progress Window This window informs the user about the status of the current installation by displaying a progress bar and status text.

13. Final Window After a successful installation of the Vodafone Mobile Connect Software, this window will be displayed. Clicking the ‘Finish’ button exits the installer.

14. Restart Window Some components of the Vodafone Mobile Connect Software require a system reboot after the installation, and will cause this window to be displayed. These components are TCP/IP Optimization, the ByteMobile Optimiser, and the Flash NettGain Optimiser. The installation of Microsoft’s .Net Framework does not require a reboot.


Installing the Devices After the installation has been carried out, devices (e.g. data cards or embedded data cards) can be installed. They can be inserted before starting VMC, or VMC can be started and will then request a device. Start the Vodafone Mobile Connect software (MobileConnect.exe) and follow the instructions in the windows presented by the first-time device installation process.

First-time Device Installation Sequence 1. Welcome Window The Welcome window informs the user about web access with the Vodafone Mobile Connect software and the possibility to use the SMS software included in the package.

2. Searching for Device Window When installing for the first time, the VMC software searches for supported devices by itself.

3. Device Type Window (only when no device has been detected so far) When installing for the first time, and no device is found by the software itself, three options are offered to the user. The user can choose to set up Vodafone Mobile Connect Cards, mobile phones, or just use WLAN for the time being.

3. Phone Connection Type Window (only Mobile Phones) Available connection types for your phone are Bluetooth, USB, infrared, and serial.

4. Add Data Card Window (only when no device has be en detected by VMC 9. Not shown if WLAN Only was selected). This window requests that a data card with a SIM be inserted into the computer’s data card slot. While identifying the device and installing the drivers, a progress bar is shown.


5. Enter PIN Window (not shown for WLAN Only) If a PIN is required by the current SIM, this window appears. If the network operator (OpCo) has allowed the PIN saving option within the <opco>.xml file, the checkbox labelled ’Save PIN‘ is enabled.

6. Confirm Selection Window (Only when no device has been detected. Not shown if WLAN Only was selected) After the device drivers have been installed, this window is displayed. The user can confirm the name of the device which has been added to the device list.

7. Main Window (not connected state) The main window of the Vodafone Mobile Connect software is opened once device setup is complete.


8. New Connection Found Window (only when the Promp t connection behaviour is set) This window will be shown when a network connection is available.

9. Main Window (connected state) The main window of the Vodafone Mobile Connect software looks like this when a connection is open.

10. Mini Window The ‘mini-window’ view of the Vodafone Mobile Connect software.

11. Windows Notification Area Menu A menu is accessible by right-clicking the Vodafone Mobile Connect software icon in the Windows Notification area (sometimes called the ‘systray’).

12. SMS Notification Window The SMS notification window, opened above the Windows Notification area when an SMS has been received.

13. Splash Window The Splash window of the Vodafone Mobile Connect software (here shown for the Danish network operator TDC Mobil).


Installation and Customization from Command Line Introduction The Microsoft Windows Installer - ‘msiexec.exe’ - is an executable program. It installs products and related components that have been included in an installation database file with the suffix .msi - also called an installation package - onto the target system. Every Windows Installer .msi database can be installed from the command line. The Macrovision InstallShield Setup Launcher - ‘setup_vmc.exe’ - is an executable program that checks software requirements, like the Microsoft Installer. It presents a language window in which the language for the installation windows can be selected, as well as the language to be used by the product once it is installed. This program can also be executed from the command line. Using the command line and parameters is useful for performing silent or unattended installations. Note The software requirements are only checked when the setup_vmc.exe Setup Launcher is used for a silent or unattended installation. The msiexec.exe Windows Installer should only be used directly if the software requirements are already on the target system.

Command Line Parameter for msiexec.exe There are the following parameters. Parameter Values Description /i Package|Product Code Installs or configures a

product. /x Package|Product Code Removes a product. /l [i|w|e|a|r|u|c|m|p|v|+|!]Logfile Specifies the log file path and

indicates the flags to be logged. i - Status messages w – Non-fatal warnings e - All error messages a - Startup of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra de-bugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options.

/q n|b|r|f Sets user interface level n - No UI at all - ‘silent install’ b - Basic UI - small progress bars displayed, but not interactive r - Reduced UI - standard windows displayed to report progress, but not interactive f - Full UI (default) - fully interactive

/norestart --- Do not restart and do not show message box for restart request.

OPCO_PROP 23415 for Vodafone UK 26202 for Vodafone DE … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’

Determines the operator network to be installed.

LANG_HEX_PROP 0x0809 for English (United Kingdom) 0x0407 for German (Germany) …

Language identifier (hexadecimal string).


Values are detailed in the FAQ section entitled ‘Which language identifier codes are used by VMC 9?’

OPCOCONFIG_WLAN true (Default) false

Shall WLAN feature be installed?

OPCOCONFIG_SMS true (Default) false

Shall SMS feature be installed?

OPCOCONFIG_OPTIMISERCLIENT None ByteMobile (Default) FlashNettGain

Shall Optimiser Client feature be installed, and if it should, which one?

CREATEDTSHORTCUTS 0 1 (Default)

Create desktop shortcuts? (Yes=0, No=1).

REPORTING_PROP on (Default) off

Shall Reporting be enabled?

ACCOUNT_PROP contract (Default) prepay

Which account type shall be used?

NETWORKRBGROUP_PROP 1 (Default) 2

Should TCP/IP settings be optimized? (Yes=1, No=2).

OPCOCONFIG_TCPWINDOWSIZE 131072 (Default) TCP/IP setting for HSDPA. The TcpWindowSize parameter can be used to set the receive window for each network interface.

OPCOCONFIG_GLOBALMAXTCPWINDOWSIZE 131072 (Default) TCP/IP setting for HSDPA. Sets the maximum TCP receive window size of the computer.

OPCOCONFIG_TCP1323OPTS 3 (Default) TCP/IP setting for HSDPA. Controls RFC1323 time stamps and window-scaling options.

OPCOCONFIG_TCPMAXCONNECTRETRANSMISSIONS 5 (Default) TCP/IP setting for HSDPA. Sets the number of times that TCP re-transmits a connect request (SYNC) before aborting the attempt.

TRANSFORMS <filename>.mst Comma-separated list of Transform files.

INSTALLDIR path string Installation folder. Only if the <InstallationPath> element in the opco file is empty.

ROUTETOMARKET string (default=”1”) Identifier for marketing to show how the installed product was delivered, e.g. download, CD etc.

USEDEFAULTLANGUAGE boolean Should the system language be used for the VMC software? The default for GUI-based installations is ‘False’, whereas the default for silent installations is ‘True’.

CONFLICTINGAPPS SilentAndPrompt SilentAndPromptOnce SilentAndAutomatic SilentAndAutomaticOnce Automatic Manual ManualWLANOnly ManualWWANOnly ManualForFirstRun (default) DisabledCannotBeEnabled DisabledCanBeEnabled

Parameter for controlling conflicting application management. SilentAndPrompt - Silently check for conflicting applications and prompt user if conflicts exist SilentAndPromptOnce - Silently check for conflicting applications and prompt user if conflicts exist, one time only SilentAndAutomatic - Silently check for conflicting applications and automatically resolve all conflicting applications SilentAndAutomaticOnce - Silently check for conflicting applications and automatically resolve all conflicting


applications, one time only Manual - Check for conflicting applications and display window ManualWLANOnly - Check for WLAN conflicting applications only ManualWWANOnly - Check for Mobile (‘WWAN’) conflicting applications only ManualForFirstRun - The conflicting applications window will be shown only in first run. In future runs of the software conflicting applications, the CA window will not be shown, unless requested by the user. DisabledCannotBeEnabled - No check for conflicting applications is ever done, and the check cannot be enabled DisabledCanBeEnabled - No check for conflicting applications is done, but the check can be enabled by the user if wished

DRIVERTYPE all (default) huawei lg motorola nokia novatel option samsung sierra sonyericsson

The drivers that should be installed. Only a single choice is possible.

DRIVERINSTALL yes (default) no

Should any drivers be installed?

OEMID string OEM identifier. FIRSTRUNWIZARD boolean (default=false) Controls the first-run wizard. ACCEPTEDEULA boolean (default=false) EULA pre-accepted? DETECTOPCOAFTERINSTALL boolean (default=true) Detect OPCO after install? DETECTOPCOPRIORINSTALL boolean (default=true) Detect OPCO before install? It

is recommended to set this parameter to ‘False’ if no SIM is present.

MAINTAINSETTINGS boolean (default=false) Preserve settings when an upgrade or update is performed on top of an existing version.

LOCKUPDATING boolean (default=false) Disables the software update function.

LOCKUSAGE boolean (default=false) Locks the usage settings. LOCKINGCODE string (default=””) Defines a locking code for the

Lock Settings window before installation.

WLANSETTINGS On Off UseOpCoSetting DisabledCannotBeEnabled DisabledCanBeEnabled EnabledCannotBeDisabled EnabledCanBeDisabled

Sets how the user can control the WLAN feature. (Only for GUI-based installations).

ALLOWWLANCHANGE boolean (default=true) Allows WLAN state to be changed by the user.

SIMACTIVATIONCHECK boolean (default=true) Allows SIM activation check. UPDATEINTERVAL weekly (default)

monthly daily never

The time after which the software should check for updates.


PIN string Valid ‘Personal Identification Number’ for the SIM.

ADVERTISE list of features delimited by commas

To advertise a feature, use ADVERTISE=<feature> on the command line. Features are WLAN, SMS, ByteMobile, or FlashNettGain.

ADDLOCAL list of features delimited by commas, or ALL

To install a feature, use ADDLOCAL=<feature> on the command line. Features are WLAN, SMS, ByteMobile, or FlashNettGain.

REMOVE list of features delimited by commas

To not install certain features, use REMOVE=<feature> on the command line. Features are WLAN, SMS, ByteMobile, or FlashNettGain.

Example

The following command line example installs the Vodafone Mobile Connect Software silently, for the Vodafone UK network. The chosen language is German. Msiexec.exe /i “Vodafone Mobile Connect.msi” TRANSF ORMS=”1031.mst” OPCO_PROP=”23415” LANG_HEX_PROP=”0x0407” /qn

Command Line Parameter for setup_vmc.exe There are the following parameters. Parameter Values Description /v any string Passing parameters to the .msi file. Please

note command line parameter for msiexec.exe above.

/s Run setup_vmc.exe silently. /L 2057 for English (United Kingdom)

1031 for German (Germany) … Values are detailed in the FAQ section entitled ‘Which language identifier codes are used by VMC 9?’

Language identifier (decimal string).

Example

The following example installs the Vodafone Mobile Connect Software silently for the Vodafone UK network. The chosen language is German. The difference to the example with the installer msiexec.exe is that the software requirements are checked by the setup program. No check is performed by the installer msiexec.exe. It is recommended to use the setup program when performing a silent or unattended installation. setup_vmc.exe /s /L1031 /v”OPCO_PROP=23415 LANG_HEX _PROP=0x0407 /qn”

The command line parameters for the Windows Installer msiexec.exe can also be applied by editing the CmdLine key in the section [Startup] of the file setup.ini.


Examples for silent installations The following are the most important comand line parameters of the setup_vmc.exe Setup Launcher. Description Example Remarks Silent /s /v”/qn” The switch /s controls the setup

launcher and the switch /qn is passed from the setup launcher to the installer.

Silent, and no restart /s /v”/qn /norestart” The switch /norestart ignores any re-start request.

Silent, no restart, and logging /s /v”/l*v c:\temp\vmclog.txt /qn /norestart” The switch /l*v sets the log level of the installer to the maximum.

Silent, no restart, logging, and no SIM available

/s /v”DETECTOPCOPRIORINSTALL=false /l*v c:\temp\vmclog.txt /qn /norestart”

If there is no SIM present in the embedded device, use this parameter to avoid delays.

Silent, no restart, logging, and network operator (OPCO)

/s /v”OPCO_PROP=23415 /l*v c:\temp\vmclog.txt /qn /norestart”

For a list of network operator codes, see the FAQ section.

Silent, no restart, logging, network operator (OPCO), and language

/s /L2057 /v”OPCO_PROP=23415 LANG_HEX_PROP=0x0809 /l*v c:\temp\vmclog.txt /qn /norestart”

For a list of language codes, decimal and hexadecimal, see the FAQ section.

A. Network operator (Opco) not known 1. In this example the Opco and language are unknown at installation time, and the WLAN, ByteMobile and FlashNettGain features will be installed only when required (‘advertised’). Once ByteMobile has been installed, FlashNettGain will not be installed on the same system, and vice versa. The first Opco that is detected determines the Optimizer. If a different Optimizer is subsequently required, the VMC software must be re-installed. Also in this example, no SIM is available at installation time, the installer-logs will be saved to c:\vmclogging.txt, the system will not be restarted automatically, and the installation is silent. setup_vmc.exe /s /v"ADDLOCAL=ALL ADVERTISE=WLAN,Byt eMobile,FlashNettGain DETECTOPCOPRIORINSTALL=false /l*v c:\vmclogging.txt /qn /norestart" 2. The difference to the first example above is that WLAN will not be installed onto the system. This is achieved by setting the REMOVE parameter in the command line, i.e. REMOVE=WLAN. setup_vmc.exe /s /v"ADDLOCAL=ALL ADVERTISE= ByteMobile,FlashNettGain REMOVE=WLAN DETECTOPCOPRIORINSTALL=false /l*v c:\vmclogging.txt /qn /norestart" 3. The difference to the second example above is that the run-time language will be Greek. This is achieved by setting the parameters /L, LANG_HEX_CODE, and USEDEFAULTLANGUAGE in the command line, i.e. /L1032, LANG_HEX_CODE=0x0408, and USEDEFAULTLANGUAGE=false. setup_vmc.exe /s /L1032 /v"ADDLOCAL=ALL ADVERTISE=ByteMobile,FlashNettGain REMOVE=WLAN DETECTOPCOPRIORINSTALL=false LANG_HEX_CODE=0x0408 USEDEFAULTLANGUAGE=false /l*v c:\vmclogging.txt /qn /norestart" B. Network operator (Opco) known 1. In this example, the Opco (OPCO_PROP=23415) and language (/L2057 and LANG_HEX_PROP=0x0809) are known at installation time, the VMC software will not use the operating system language (USEDEFAULTLANGUAGE=false), no SIM will be available for an embedded device (DETECTOPCOPRIORINSTALL=false), and the installer logfiles will be saved to c:\vmclogging.txt. The system will not be restarted automatically after this silent installation. setup_vmc.exe /s /L2057 /v"OPCO_PROP=23415 LANG_HEX _PROP=0x0809 DETECTOPCOPRIORINSTALL=false USEDEFAULTLANGUAGE=false /l*v c:\vmclogging.txt /qn /norestart" 2. The difference to the first example above is that WLAN shall not be installed onto the system. This is achieved by setting the REMOVE parameter in the command line, i.e. REMOVE=WLAN. Also no optimizer will be installed, i.e. REMOVE=ByteMobile,FlashNettGain. setup_vmc.exe /s /L2057 /v"OPCO_PROP=23415 LANG_HEX _PROP=0x0809 DETECTOPCOPRIORINSTALL=false USEDEFAULTLANGUAGE=false REMOVE=WLAN,ByteMobile,FlashNettGain /l*v c:\vmclogging.txt /qn /norestart"


Embedded Customization using Network Operator file Introduction For each network operator included in the installer database, there is an <opco-id>.xml file that controls the installation process. Each OpCo is associated with an identifier (e.g. Vodafone UK: 23415). The complete list of network identifiers is provided in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’ Authoring a Network Operator file These files are located by default in c:\Program Files\Vodafone\Vodafone Mobile Connect\Opco\. The elements in each xml file are detailed in Appendix A1. A sample of a Vodafone UK network operator file is attached in Appendix A2. Modifications to these files are applied using a ‘Transform file’. Please refer to the section Using Transforms for Customization for more details. xml elements in this xml file that are related to installation can be found in the following list. XML element Values Description <WLAN> true

false Show or hide the feature WLAN in the Features window. The WLAN feature is not de-selectable from the feature list.

<SMS> true false

Show or hide the SMS feature in the Features window.

<OptimiserClient> None ByteMobile FlashNettGain

Show or hide the Optimisation Client feature in the Features window and determine the Optimiser software.

<Optimize> true false

Enable or disable the TCP/IP optimization settings for the Windows Registry.

<TcpWindowSize> 131072 TCP/IP setting for HSDPA. The TcpWindowSize parameter can be used to set the TCP Receive Window for each network interface.

<GlobalMaxTcpWindowsSize> 131072 TCP/IP setting for HSDPA. This parameter determines the maximum TCP Receive Window size for the computer.

<Tcp1323Opts> 3 TCP/IP setting for HSDPA. This parameter controls RFC1323 time stamps and window-scaling options.

<TcpMaxConnectRetransmissions> 5 TCP/IP setting for HSDPA. This parameter determines the number of times that TCP re-transmits a connect request (SYNC) before aborting the attempt.

<SaveAndRestoreSettings> * not used * * not used * <AskEULA> true

false Show or hide the License window.

<AskReports> true false

Show or hide the Reporting window.

<ReportingEnabled> true false

Enable or disable the reporting.

<AskAccountType> true false

Show or hide the Account window.

<AskTcpSettings> true false

Show or hide the TCP/IP Settings window.

<AskInstallationPath> true false

Show or hide the Installation Option window.

<CreateDesktopShortcuts> true false

Create shortcuts for the Vodafone Mobile Connect software and the SMS program on the desktop.

<InstallationPath> <drive>:\<path> Set the installation folder.


Embedded Customization using a modified User Profil e file Introduction When the Vodafone Mobile Connect software is started for the very first time after installation, a user profile XML file ‘MobileConnectProfile.xml’ is generated. No specific user input is required. This XML user profile can be used as a template: it can be edited and then replaced in the msi database. Modifications to this file are actioned using a Transform file. Please refer to the section Using Transforms for Customization for more details. The elements in this XML file are detailed in Appendix B1. A sample of a user profile is attached in Appendix B2. Creating and Authoring a customized User Profile 1. Install VMC9 on a test computer.

Install the Vodafone Mobile Connect software as described above. 2. Perform first-time device installation.

See above for details on adding one or more devices. The device details created will be stored into the MobileConnectProfile.xml file. Note First-time device installation overwrites any existing user profile XML files.

3. Save file MobileConnectProfile.xml to be used as a template for further customized installations.

Save the file MobileConnectProfile.xml created by VMC and located in the folder

Windows 2000 and Windows XP <drive>:\Documents and Settings\<username>\Applicat ion Data\Vodafone\Vodafone Connection Manager\UserD ata

Or

Windows Vista <drive>:\Users\<username>\AppData\Roaming\Vodafone\ Vodafone Connection Manager\UserData

Use this file as a template for your customized installations with Transforms.

4. Edit file MobileConnectProfile.xml.

Optional: Modify certain xml elements to match your requirements. 5. Create a Transform file.

Refer to the chapter “Using Transforms for Customization”. 6. Apply your Transform file to the VMC 9 setup pro cedure.

Refer to the chapter “Using Transforms for Customization”.


Using Transforms for Customization Introduction A Windows Installer Transform is a database that contains the differences between two MSI databases. A Transform can only be applied to an MSI database which will be installed, not to a product that is already installed on a target machine. Transforms are useful for system administrators to provide variations of a single product without having to modify the original database. Multi-language installations are also performed by a default language contained in the MSI database and several transform files for the localized strings used by each language. Creating Transforms The following instructions are describing base steps to perform tasks with Microsoft’s ‘Orca’ software to create Transforms. All tasks can actually be put into one single Transform. Task: Replace a File - the file 23415.xml should be replaced by a modified file. Original file <working folder>\program files\Vodafone\Vodafone Mobile Connect\Opco\23415 United Kingdom\23415.xml Modified file 23415.xml For the modified file size, open Windows Explorer, navigate to the modified file, right-click it to display its properties, and then note the file size, e.g. “Size: 4.64 KB (4.756 bytes)”. Keep this number in mind, when later creating the Transform.

1. Start Orca. 2. From the File Menu, select Open. 3. Browse to the folder that contains your working copy of the VMC software. 4. Select ’Vodafone Mobile Connect.msi’. 5. Click Open. 6. From the Transform menu, select ’New Transform’. 7. In the left pane, select the ’File‘ table. 8. In the right pane, select the row which displays the filename ’23415.xml‘ in the third column. 9. Select the column ’FileSize‘ and enter the file size of your modified file ’23415.xml’ 10. From the Transform menu, select ’Generate Transform’. 11. Enter a Transform filename and save the Transform. 12. From the Transform menu, select ’Close Transform’. 13. Exit Orca.

These are the basic steps to replace a file using a Transform. For all Opco files, including 23415.xml, an additional step is necessary to replace this file correctly. 9.1. In the left pane, select the ’ISSetupFile‘ table. 9.2. In the right pane, select the row which displays the filename ’23415.xml‘ in the second column.

9.3. Read the binary stream for file 23415.xml by clicking on to the ’Stream‘ column 9.4. Select the modified file 23415.xml with the browse button

After generating the Transform, the Transform must be applied to the installation setup package.

1. Open the file setup.ini in an editor, e.g. notepad.exe. 2. Find the [Startup] section and complete the ’CmdLine=’ key with the name of your Transform file, e.g.

CmdLine=TRANSFORMS=MyTransform.mst 3. Copy the modified file 23415.xml to the location of the uncompressed setup where the original file was stored. 4. Copy the Transform file to the root directory of the uncompressed setup where the files ’Vodafone Mobile

Connect.msi‘ and ‘setup.ini’ are located. 5. Start the setup, e.g. by double-clicking ‘setup_vmc.exe’.


Task: Change a property - a specific property should be modified.

1. Start Orca. 2. From the File Menu, select Open. 3. Browse to the folder that contains your working copy of the VMC software. 4. Select ‘Vodafone Mobile Connect.msi’. 5. Click Open. 6. From the Transform menu, select ‘New Transform’. 7. In the left pane, select the ‘Property’ table. 8. In the right pane, select the row which displays the file you want to modify. 9. In the right pane, select the column ‘Value’ and enter a new value for the property. 10. From the Transform menu, select ‘Generate Transform’. 11. Enter a Transform filename and save the Transform. 12. From the Transform menu, select ‘Close Transform’. 13. Exit Orca.

Task: Modify a registry key - a specific registry key should be modified.

1. Start Orca. 2. From the File Menu, select Open. 3. Browse to the folder that contains your working copy of the VMC software. 4. Select ‘Vodafone Mobile Connect.msi’. 5. Click Open. 6. From the Transform menu, select ‘New Transform’. 7. In the left pane, select the ‘Registry’ table. 8. In the right pane, select the row which displays in the column ‘Name’ the name of the registry key to be modified. 9. In the right pane, select the column ‘Value’ and enter a new value for the registry key. 10. From the Transform menu, select ‘Generate Transform’. 11. Enter a Transform filename and save the Transform. 12. From the Transform menu, select ‘Close Transform’. 13. Exit Orca.


Authoring Transform files The following example shows how to create a Transform file with the Microsoft ‘Orca’ tool, in order to replace the sample file MobileConnectProfile.xml and the Opco file 23415.xml from the MSI database. If a user Profile file MobileConnectProfile.xml needs to be modified, the start mode of the VMC software must also be changed. This is achieved by changing the MSI property VMCSTARTMODE for the user account that was used to install VMC, and adding two registry keys for new user accounts on the target machine – there are currently two components, each component needs one registry key. For existing user accounts, a workaround must be applied. For the workaround, refer to the section ’5. Conclusion‘ in the chapter ’Applying Transform files with setup_vmc.exe’. Note For VMC versions 9.2.2 or greater, only the MSI property VMCSTARTMODE has to be modified in a Transform to set the VMC start mode when changing the Profile file MobileConnectProfile.xml. This modification of the MSI property is then valid for all user accounts. 1. Install Microsoft’s tool Orca. Microsoft’s tool Orca can be downloaded from the following Web page: http://support.microsoft.com/kb/255905/EN-US 2. Make a copy of the file “Vodafone Mobile Connect .msi” for backup. 3. Open Orca.exe. 4. From the File menu, select Open and browse to th e file “Vodafone Mobile Connect.msi”.

5. From the Transform menu, select New Transform.

6. In the left pane, select the “File” table.


7. In the right pane, select the “MobileConnectProfi le.xml” row.

8. Select the column “FileSize” and enter the file si ze of the new “MobileConnectProfile.xml” file.

9. In the right pane, select the row which displays filename “23415.xml” in the third column.


10. Select the column “FileSize” and enter the file size of the new “23415.xml” file.

11. In the left pane, select the “ISSetupFile” table.

12. In the right pane, select the row which display s the filename “23415.xml” in the second column.


13. Read the binary stream for file 23415.xml by cl icking on to the ‘Stream’ column. Select the modifie d file with the Browse button.

14. In the left pane, select the “Property” table.

15. In the right pane, select the row which display s the property name “VMCSTARTMODE” in the first column .


16. Enter the value 2 (Mini-Window) in the column “Va lue”, or 1 (Main window), or 3 (minimized in Window s Notification Area), but not 0 (first-time device installation).

17. In the left pane, select the “Registry” table.

18. Select “Add Row…” from the “Tables” menu.


19. Enter the values for component “VodafoneMobileCon nect”.

20. Enter the values for component “VodafoneMobileCon nect1”.

21. Check the added rows.


22. Generate a Transform file by selecting “Generat e Transform…” from the Transform menu.

23. Save your modifications.

24. Close the Transform file “MyTransform.mst”.


25. Exit Orca.exe.

Applying Transform files with setup_vmc.exe The following steps explain how to apply a Transform file along with an installer database package. 1. Apply the Transform file. Apply the Transform file by editing the ‘setup.ini’ file. Open the setup.ini file in an editor - e.g. notepad.exe. Find the [Startup] section and complete the CmdLine key with the name of your Transform file, e.g. MyTransform.mst as in the following example.

Note


Any Transform file can also be applied by setting the command line parameter TRANSFORMS, either with setup_vmc.exe or with the installer msiexec.exe. 2. Provide the modified file MobileConnectProfile.xml for setup_vmc.exe launcher. Copy the new file MobileConnectProfile.xml, which should replace the existing one, to the related folder of the source media. For example, navigate to the folder “DISK1\program files\Vodafone\Vodafone Connection Man ager\Templates” , and replace the existing file MobileConnectProfile.xml .

3. Provide the modified file 23415.xml for setup_vmc .exe launcher. Copy the modified 23415.xml file, which should replace the existing one, to the related folder of the source media. For example, navigate to the folder “DISK1\program files\Vodafone\Vodafone Connection Mana ger\Opco\23415 United Kingdom” , and replace the existing file 23415.xml .

4. Run Setup_vmc.exe.


Execute setup_vmc.exe, e.g. by double-clicking it in Windows Explorer.

5. Conclusion The installation process should now use both modified files, MobileConnectProfile.xml and 23415.xml. Also the property VMCSTARTMODE was changed to the value 2 and two registry keys were created to set the start mode of VMC to the value 2 for all users. Note Normally, when VMC has been started for the very first time after installation, no device will have been detected. VMC will therefore start with the mode "First-Time installation" which is equal to "0". But when a transform is used to pre-define one or more devices in the file MobileConnectProfile.xml, then - after installation - the start-mode of VMC should not be "First-Time installation". Therefore, the VMCSTARTMODE property must be set to "2" which is the Mini-View, or "1" (Main-View) or "3" (Notification area icon only). Unfortunately, setting the msi public property VMCSTARTMODE within the Transform only changes the start mode for the current user, who is usually an administrator. All other users - existing and future - are not affected by this setting (see points 14, 15, and 16 in this chapter). For users who will be created after the installation of VMC, there must be a registry entry in the .DEFAULT user hive, also to be done with a Transform and explained in this chapter under points 17, 18, 19, and 20. The following workaround must be used for all existing users in VMC versions lower than 9.2.2. For VMC versions greater or equal to 9.2.2, only the MSI public property VMCSTARTMODE has to set. Workaround First-time installation is controlled by a user-specific database registry entry: HKEY_CURRENT_USER\Software\Vodafone with the value MobileConnectStartMode. To enter the main view of VMC 9 instead of the first-time installation after starting the VMC 9 software MobileConnectStartMode has to be to 1. The VMC 9 software will then be started with the main view and not with the first-time installation. First-time installation has the value 0 and is the default. This database value must be set for every existing user on the system in the specific user hive HKEY_CURRENT_USER (HKCU). A database registry entry must be created for existing users using the following procedure: Create the following key. � HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\<identifier> The term <identifier> should be an unambiguous string, e.g. a GUID string. Under this key there should be at least the following two values. � Version (REG_SZ)


� StubPath (REG_EXPAND_SZ) For the Version value, use a value such as: 1,0,0,0 For the StubPath value, use a value such as: <path>\regedit.exe /s <importfile> Example [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}] "StubPath"="<path>\\regedit.exe /s import.reg" "Version"="1,0,0,0" The content of the <importfile> should create the value MobileConnectStartMode=1 for the current user, e.g. [HKEY_CURRENT_USER\Software\Vodafone] "MobileConnectStartMode"="1" Steps to apply this workaround � Create a batch file which creates the key in “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed

Components”, and be sure that the file <import.reg> is copied to a certain folder on the target machine to which the StubPath value is referring.

� Run this batch file after every installation of VMC 9 for all of your machines. � After the very first start of VMC 9 on the target machines, your device now should be ready to work.


Scenarios for IT Administrators A. Installation of VMC9 on a computer Certain preparations are necessary before installing the Vodafone Mobile Connect software on a computer to be used by all users of that computer. 1. Create a user profile file and/or a network oper ator file.

A user profile file can be created by manually installing the VMC software on a computer, along with the first-time device installation for all the devices the users of the computer should use. The resulting MobileConnectProfile.xml file can be used as a template for all users. Consider the start mode of VMC for your installations – see above.

2. Create a Transform file to replace the user prof ile file and/or the network operator file in the ms i database.

To replace the file MobileConnectProfile.xml from step 1 and/or the network operator file in the MSI database, a Transform database has to be generated. A tool for creating Transform databases is Orca from Microsoft – see above. Any other tool which can deal with Transform files can also be used.

The steps to install the Vodafone Mobile Connect Software are 1. Optional - Unattended installation of Microsoft’ s Windows Installer 3.1.

This is not necessary for a system with the latest Service Packs and Updates from Microsoft. This is also not necessary if you are using the setup_vmc.exe program for your silent installation, instead of using the installer msiexec.exe.

2. Optional - Unattended installation of Microsoft’ s .Net Framework 2.0.

The .Net Framework is not currently part of Windows XP, or Windows 2000, nor is it part of a Service Pack. It therefore has to be installed separately on a Windows XP or 2000 operating system. This is not necessary if you are using the setup.exe program for your silent installation, instead of using the installer msiexec.exe In order to perform this installation using the setup.exe program, a parameter in the setup.ini needs to be modified. Please refer to the FAQ section entitled ’How to install the .Net Framework 2.0 silently’.

3. Unattended installation of the VMC 9 software.

The unattended installation of the VMC software using a Transform file is described in the chapters Command Line Customization and Using Transforms for Customization – see above.

B. VMC 9 and Limited Users The Vodafone Mobile Connect software can be used by limited user accounts (user accounts without administrative privileges). However installation of VMC 9 on a machine requires administrative privileges. There are two cases where the limited user needs to be elevated to administrator rights. Case 1 USB devices must have been detected once under administrative privileges by VMC 9 or a limited user has to accept the execution of a utility application which requires administrative privileges. This utility changes certain database registry keys, usually located in HKEY_LOCAL_MACHINE, during the first installation of a USB device. Case 2 When the VMC software has been installed with the MSI property USEDEFAULTLANGUAGE=true, a utility will also change some database registry keys, which again requires administrative privileges.


Frequently Asked Questions (FAQ) How to display hidden files and folders in Windows explorer Windows 2000 and Windows XP

1. Open Explorer. 2. From the Tools menu, select ‘Folder Options… ‘. 3. Click on the ‘View’ tab. 4. Check ‘Show hidden files and folders’ in the list of

advanced settings. 5. Click on the ‘Apply’ button and if desired click on

the ‘Apply to All Folders’ button.

Windows Vista

1. Open Explorer. 2. From the Organize menu, select ‘Folder and

Search Options’. 3. Click on the ‘View’ tab. 4. Check ‘Show hidden files and folders’ in the list of

advanced settings. 5. Click on the ‘Apply’ button and if desired click on

the ‘Apply to Folders’ button.

In which folder are the VMC files that were created at run-time? The location of <vmc folder> depends on the operating system. This folder will be referenced below several times. Operating system System folder Windows 2000 <drive>:\Documents and Settings\<username>\Application Data Windows XP <drive>:\Documents and Settings\<username>\Application Data Windows Vista <drive>:\Users\<username>\AppData\Roaming

How to create Windows Installer logging files Windows Installer logging can be enabled for a single installation with a command line parameter. Alternatively, logging can be enabled for all installations on the same computer by setting a registry key. 1. There is a command line parameter for the Windows Installer msiexec.exe. This parameter can be set in the command line or in the file setup.ini. The syntax of the parameter is /l<option> <filename>


Example This example creates a file named vmc9install.log in the folder c:\tmp using the option *v to include all possible information. /l*v c:\tmp\vmc9install.log

2. The value data “voicewarmup” in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\ Installer creates logging files for all installations performed on the computer. Value Name Value Type Value Data Description Logging REG_SZ voicewarmup Enables logging.

Where can I find the VMC logging files? The logging files in <vmc folder>\Vodafone\Vodafone Connection Manager\Log are created by the Vodafone Mobile Connect Software. File Name Description Diagnostics.txt Wwan logging file. DiagnosticsBackup.txt Backup of Wwan logging file. iftrace.txt Interface trace file for connection - VMC and WWAN. iftraceBackup.txt Backup of Wwan interface trace file. SendMessageTimeout.txt Interface trace file for connection - VMC and WLAN. SendMessageTimeoutBackup.txt Backup of Wlan interface trace file. MobileConnect-Log1.txt Logging/Backup file of VMC application. MobileConnect-Log2.txt Backup/Logging file of VMC application. SMS-Log1.txt Logging/Backup file of SMS application. SMS-Log2.txt Backup/Logging file of SMS application. ConAppM-Log1.txt Logging/Backup file of ‘conflicting application’ application. ConAppM-Log2.txt Logging/Backup file of ‘conflicting application’ application. DeviceListener-Log1.txt Logging/Backup file of ‘device listener’ application. DeviceListener-Log2.txt Logging/Backup file of ‘device listener’ application. SetLanguage-Log1.txt Logging/Backup file of ‘set language’ application. SetLanguage-Log2.txt Logging/Backup file of ‘set language’ application. Zuhause-Log1.txt Logging/Backup file of ‘zuhause’ application. Zuhause-Log2.txt Logging/Backup file of ‘zuhause’ application.

How to control the logging files The following logging files in <vmc folder>\Vodafone\Vodafone Connection Manager\Lo g are controlled by the user profile file Settings.xml. The size of these files can be set by the xml element LoggingFileSize in the Settings file. Trace File Name Values XML element SendMessageTimeout.txt integer WlanInterfaceTrace iftrace.txt integer WanInterfaceTrace Diagnostics.txt bool IsWanDiagnosticsTrace The following logging files in <vmc folder>\Vodafone\Vodafone Connection Manager\Log are controlled by the related configuration files – with suffix .config. Trace File Name Config File XML element MobileConnect-Log<n>.txt MobileConnect.exe.config system.diagnostics.switches SMS-Log<n>.txt SMS.exe.config system.diagnostics.switches ConAppM-Log<n>.txt ConAppM.exe.config system.diagnostics.switches DeviceListener-Log<n>.txt DeviceListener.exe.config system.diagnostics.switches SetLanguage-Log<n>.txt SetLanguage.exe.config system.diagnostics.switches Zuhause-Log<n>.txt Zuhause.exe.config system.diagnostics.switches The following trace levels are available for all configuration files. Trace Level Description

0 Off: Output no tracing and debugging messages. 1 Error: Output error-handling messages. 2 Warning: Output warnings and error-handling messages. (default) 3 Info: Output informational messages, warnings, and error-handling messages. 4 Verbose: Output all debugging and tracing messages.


To change the trace levels, open the configuration files (*.config) in a text editor e.g. notepad.exe, and modify the value numbers. On Windows Vista (see picture on right), “Run as administrator” must be used to change config files.

If the trace levels should be set in general and not individually, the following registry key in HKEY_CURRENT_USER\SOFTWARE\Vodafone can be used to set all trace levels at once. To re-set this trace level, set the value data to “-1” or delete the key. Value Name Value Type Value Data Description LogLevel REG_SZ -1

0 1 2 3 4

The values for the levels are Inactive (-1), Off (0), Error (1), Warning (2), Info (3), and Verbose (4). This key is effective from VMC version 9.2.2.

Samples of configuration files File Content MobileConnect.exe.config …

<system.diagnostics> <switches> <add name="MobileConnect" value=" 2"/> <add name="ConnectionServices" value=" 2"/> <add name="BaseServices" value=" 2"/> <add name="Tracer" value=" 2"/> <add name="Wlan" value=" 2"/> <add name="SmsContactManager" value=" 2"/> <add name="ManageDevicesControl" value=" 2"/> </switches> <trace autoflush="true" indentsize="2"> </trace> </system.diagnostics>

SMS.exe.config … <system.diagnostics> <switches> <add name="BaseServices" value=" 2"/> <add name="SmsGUI" value=" 2"/> <add name="Tracer" value=" 2"/>

<add name="SmsContactManager" value=" 2"/> </switches>

<trace autoflush="true" indentsize="2"> </trace> </system.diagnostics>

ConAppM.exe.config … <system.diagnostics> <switches> <add name="BaseServices" value=" 2"/> <add name="Conflicting Applications" value=" 2"/> <add name="Tracer" value=" 2"/>

</switches> <trace autoflush="true" indentsize="2"> </trace> </system.diagnostics>

DeviceListener.exe.config, SetLanguage.exe.config, Zuhause.exe.config

… <system.diagnostics> <switches> <add name="BaseServices" value=" 2"/>


<add name="Tracer" value=" 2"/> </switches>

<trace autoflush="true" indentsize="2"> </trace> </system.diagnostics>

How to enable an additional WLAN trace The following registry entry in HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\WLANClient is used to enable the WLAN trace. Value Name Value Type Value Data Description EnableLogging REG_DWORD 0

1 If the value data is zero, logging is switched off.

Which items remain on the system after removing VMC 9? After removing the Vodafone Mobile Connect software, all folders and files in the following folders remain on the system. Folder <vmc folder>\Vodafone\Vodafone Connection Manager\Log <vmc folder>\Vodafone\Vodafone Connection Manager\Tmp <vmc folder>\Vodafone\Vodafone Connection Manager\UserData After removing the VMC software, the following two registry keys remain on the system. Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\WwanSdk HKEY_CURRENT_USER\SOFTWARE\Vodafone\WwanSdk

Where can I find which user data files? The following user data files in <vmc folder>\Vodafone\Vodafone Connection Manager\Use rData are created and used by the Vodafone Mobile Connect software. File Name Description MobileConnectProfile.XML User profile file. ReportingInformation.xml Reporting information. ReportingUsage<date>-<time>.xml Reporting information. ReportingUsage.XML Reporting information. Usage.USG Reporting information. VodafoneMobileConnect.ldb SMS database file. VodafoneMobileConnect.mdb SMS database file. WindowsSettingsMobileConnect.XML File to store and to save the windows settings for the VMC software. Which Registry values are used by VMC 9? The following values in HKEY_LOCAL_MACHINE\Software\Vodafone\Common are used by the Vodafone Mobile Connect software. Value Name Value Type Value Data Description VF_COUNTRY REG_SZ United Kingdom

Germany … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’

Installed OPCO country.

VF_LANG REG_SZ 0x0809 for English 0x0407 for German … Values are detailed in the FAQ section entitled ‘Which language identifier

Installed language.


codes are used by VMC 9?’

VF_OEMID REG_SZ string OEM identifier. VF_PLMN REG_SZ 23415 for Vodafone UK

26202 for Vodafone DE … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’

Installed OPCO code.

VF_PROD REG_SZ VMC R9 VMC product identifier. The following values in HKEY_LOCAL_MACHINE\Software\Vodafone\Settings are used by the WLAN feature. Value Name Value Type Value Data Description VF_LANG REG_SZ 0x0809 for English

0x0407 for German … Values are detailed in the FAQ section entitled ‘Which language identifier codes are used by VMC 9?’

Installed language.

VF_PLMN REG_SZ 23415 for Vodafone UK 26202 for Vodafone DE … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’


The following values in HKEY_LOCAL_MACHINE\Software\Vodafone\VMC are used by the Vodafone Mobile Connect software. Value Name Value Type Value Data Description AcceptedEULA REG_SZ true

false EULA pre-accepted?

BuildVersion REG_SZ <n>.<n>.<n>.<n> Version string identifier. ConflictingApps REG_SZ SilentAndPrompt

SilentAndPromptOnce SilentAndAutomatic SilentAndAutomaticOnce Automatic Manual ManualWLANOnly ManualWWANOnly ManualForFirstRun DisabledCannotBeEnabled DisabledCanBeEnabled

Parameter for controlling conflicting application management.

CustomerAccount REG_SZ contract prepay

Type of customer account.

DetectOpcoAfterInstall REG_SZ true false

Detect OPCO after install.

DetectOpcoBeforeInstall REG_SZ true false

Detect OPCO before install. It is recommended to set this parameter to false if no SIM is present.

DriverDirectory REG_SZ <installdir>\Driver Location of the driver files. DriverInstall REG_SZ yes (default)

no Install any drivers?

DriverType REG_SZ all (default) huawei lg motorola nokia novatel option samsung sierra sonyericsson

Which drivers should be installed? Only one single choice is possible.

FirstRunWizard REG_SZ boolean Controls the first-run wizard. InstallDateTime REG_SZ string Installation time stamp.


LockUpdating REG_SZ boolean Locks the updating feature so it cannot be used.

LockUsage REG_SZ boolean Locks the usage settings window so the settings cannot be changed.

MaintainSettings REG_SZ boolean Preserve settings when an upgrade or update is performed on top of an existing version.

MobileConnectStartMode² REG_SZ 0 1 2 3

First-time installation. Main window. Mini-Window. Minimised in Notification area (“systray”).

OEMDetermined REG_SZ string Indicates how the OEM value was created. Possible values: Automatic Manual

OpcoPropNormalized REG_SZ string Internal identifier. OpcoPropSimReader REG_SZ string Internal identifier. OptimizerClient REG_SZ None

ByteMobile FlashNettGain

Installed optimizer client.

Reporting REG_SZ on off

Enable or disable reporting.

ReportingInfoType REG_SZ string Internal identifier. RouteToMarket REG_SZ string Identifier (default=”1”). SetupDirectory REG_SZ <installdir> Location of the installation folder. SimActivationCheck REG_SZ boolean Allows SIM activation check. TCPIPSettings REG_SZ 1

2 Indicates whether TCP/IP settings are performed or not. The value “1” means that the performance keys have been set, “2” means no change.

Updating REG_SZ weekly (default) monthly daily never

Time interval at which the software checks for updates.

UseDefaultLanguage REG_SZ boolean Use the operating system language for the VMC software. The default for GUI based installations is false whereas the default for silent installations is true.

VodafonePackageCode REG_SZ GUID Msi package code. VodafoneProductCode REG_SZ GUID Msi product code. VodafoneUpdateServer REG_SZ url URL of the Vodafone update server. Wlan REG_SZ On

Off UseOpCoSetting DisabledCannotBeEnabled DisabledCanBeEnabled EnabledCannotBeDisabled EnabledCanBeDisabled

Sets to what extent the user can control the WLAN feature. (Only for GUI based installations)

WlanChangeAllowed REG_SZ boolean (default=true) Allows WLAN state to be changed by the user.

(² available from VMC 9.2.2) The following keys in HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\Common\Installed F eatures are used by the Vodafone Mobile Connect software. The feature is currently installed, if the key exists. The value data has no meaning. Value Name Value Type Value Data Description ByteMobile REG_SZ 1 ByteMobile is installed. FlashNettGain REG_SZ 1 FlashNettGain is installed. TataraWLAN REG_SZ 1 TataraWLAN is installed. VodafoneSMS REG_SZ 1 VodafoneSMS is installed. The following values in HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\WLANClient are used by the Vodafone Mobile Connect software. Value Name Value Type Value Data Description EnableLogging REG_DWORD 0

1 If the value data is zero, logging is switched off.

InstallDir REG_SZ <installdir>\WLANClient Installation folder of the WLAN components. LocationDB REG_SZ Location.db Name of the used file. OpCoConfig REG_SZ OpCoConfig.xml Name of the used file.


Wisp REG_SZ Wisp.xml Name of the used file. The following keys are used by the Vodafone Mobile Connect software. There are no values used by these keys. Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\WwanSdk HKEY_CURRENT_USER\SOFTWARE\Vodafone\WwanSdk The following values in HKEY_CURRENT_USER\Software\Vodafone are used by the Vodafone Mobile Connect software. Value Name Value Type Value Data Description ConfAppsModeStatus REG_SZ SilentAndPrompt

SilentAndPromptOnce SilentAndAutomatic SilentAndAutomaticOnce Automatic Manual ManualWLANOnly ManualWWANOnly ManualForFirstRun DisabledCannotBeEnabled DisabledCanBeEnabled

Parameters for controlling conflicting application management.

ConfAppsProfileVersion REG_SZ string Conflicting applications profile version string.

LockingCode REG_SZ string Locking code. MobileConnectStartMode REG_SZ 0

1 2 3

First-time installation. Main window. Mini-Window. Minimised in Notification area (“systray”).

OemDetermined REG_SZ string Automatic or manually set. ReportingCurrentToSendNumber REG_SZ string Reporting info data. ReportingLastSentNumber REG_SZ string Reporting info data. SetupTime REG_SZ string Installation time stamp. VF_COUNTRY REG_SZ United Kingdom

Germany … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’

Installed OPCO country.

VF_OEMID REG_SZ String OEM identifier. VF_PLMN REG_SZ 23415 for Vodafone UK

26202 for Vodafone DE … Values are detailed in the FAQ section entitled ‘Which network identifiers are used by VMC 9?’



Which network identifiers are used by VMC 9? The following list of network identifiers is used by VMC 9. Network Operator Network Identifier Country A1 23201 Austria Bite Latvija 24705 Latvia Bite Lietuva 24602 Lithuania Celcom Malaysia 50219 Malaysia Cytamobile-Vodafone 28001 Cyprus DIALOG 41302 Sri Lanka Elisa 24405 Finland Elisa Estonia 24802 Estonia LUXGSM 27001 Luxembourg MobileOne 52503 Singapore MTC-Vodafone BH 42602 Bahrain MTC-Vodafone KT 41902 Kuwait M-Tel 28401 Bulgaria Proximus 20601 Belgium SFR 20810 France Si.mobil-Vodafone 29340 Slovenia SmarTone-Vodafone 45406 Hong Kong Swisscom Mobile 22801 Switzerland TDC Mobil 23801 Denmark TDC Song 2380171 Norway Telenor Sweden 24008 Sweden Vipnet 21910 Croatia Vodacom 65501 South Africa Vodafone Albania 27602 Albania Vodafone Australia 50503 Australia Vodafone CZ 23003 Czech Republic Vodafone DE 26202 Germany Vodafone Egypt 60202 Egypt Vodafone Fiji 54201 Fiji Vodafone Greece 20205 Greece Vodafone Hungary 21670 Hungary Vodafone Iceland 27401 Iceland Vodafone IE 27201 Ireland Vodafone IT 22210 Italy Vodafone K.K. 44020 Japan Vodafone Malta 27801 Malta Vodafone NL 20404 Netherlands Vodafone NZ 53001 New Zealand vodafone P 26801 Portugal Vodafone RO 22601 Romania Vodafone Spain 21401 Spain Vodafone TR 28602 Turkey Vodafone UK 23415 United Kingdom XL-Indonesia 51011 Indonesia Which language identifier codes are used by VMC 9? The following language identifier codes are used by VMC 9. Language (Country) Decimal Code Hexadecimal Code String Code Arabic (Egypt) 3073 0x0c01 ar-EG Bulgarian (Bulgaria) 1026 0x0402 bg-BG Chinese (Hong Kong) 3076 0x0c04 zh-HK Chinese (Taiwan) 1028 0x0404 zh-TW Croatian (Croatia) 1050 0x041a hr-HR Czech (Czech Republic) 1029 0x0405 cs-CZ Danish (Denmark) 1030 0x0406 da-DK Dutch (Belgium) 2067 0x0813 nl-BE Dutch (Netherlands) 1043 0x0413 nl-NL English (United Kingdom) 2057 0x0809 en-GB Estonian (Estonia) 1061 0x0425 et-EE Finnish (Finland) 1035 0x040b fi-FI French (Belgium) 2060 0x080c fr-BE French (France) 1036 0x040c fr-FR German (Germany) 1031 0x0407 de-DE


Greek (Greece) 1032 0x0408 el-GR Hungarian (Hungary) 1038 0x040e hu-HU Italian (Italy) 1040 0x0410 it-IT Latvian (Latvia) 1062 0x0426 lt-LT Lithuanian (Lithuania) 1063 0x0427 lv-LV Norwegian (Norway) 1044 0x0414 nb-NO Portuguese (Portugal) 2070 0x0816 pt-PT Romanian (Romania) 1048 0x0418 ro-RO Russian (Russia) 1049 0x0419 ru-RU Slovenian (Slovenia) 1060 0x0424 sl-SI Spanish (Spain) 1034 0x040a es-ES Swedish (Sweden) 1053 0x041d sv-SE Turkish (Turkey) 1055 0x041f tr-TR How to add programs/executables in VMC’s left-hand n avigation bar in the “Other Programs” area. Up to 6 program entries are possible. The entries SMS and VPN are mandatory. If the 4 remaining optional entries are also set by the network operator <opco>.xml file, the user cannot add any further entries. A Transform can be used to change the msi database to replace the modified network operator file <opco>.xml. The element <VmcProgram> uses the attributes in the following list. Property Values Description Name identifier Unique name of the button control (only GUI internal). Reminder true, false Show a connection reminder when this program starts up. Mode Never, Manual, WhenConnectionOpen,

WhenConnectionClosed, OnStart, OnExit

When to start the program.

Type Unknown, SmsApplication, OptimisationByteMobile, OptimisationFlash, VpnClient

The standard opco programs are OptimisationByteMobile, SmsApplication, OptimisationFlash, and VpnClient. All other programs must have Unknown as type.

Minimize true, false

Minimise this program together with VMC.

InToolbar true, false

Show program in the ‘Other Programs’ panel in the left navigation area of VMC.

Once true, false

Start this program only once. If this program is already running, set focus to the running instance (if possible). This property is only used for the standard opco programs. Other opco programs are not supported.

I integer Index in the left navigation area, index starts with zero. Used only if InToolbar is set to true.

Terminate true, false

If the program starts, then exit VMC (Not supported in VMC 9.0).

Style Hidden, Normal, Maximized, Minimized Start program with this style. Editable true,

false If set to false, the user cannot edit this program (Not supported in VMC 9.0).

IsOPCO true, false Has to be true for opco programs. ProgramPath ClientType:Calendar,

ClientType:Contacts, ClientType:Mail, ClientType:Media, ClientType:News, ClientType:InternetBrowser, registry key, registry key and value, URL

Location of the program.

Param string Additional start parameter for this program (optional). ToolbarButtonText string Toolbar button text (only if InToolbar equals true). ToolbarButtonTooltip string Toolbar button tool tip (only if InToolbar equals true). Examples � Default email application <VmcProgram Name=" Mail " Reminder="false" Mode="Manual" Type="Unknown" Min imize="false"

InToolbar="true" Once="false" I=" 4" Terminate="false" Style="Normal" Editable="false" IsOPCO="true">

<ProgramPath> ClientType:Mail </ProgramPath> <Param />


<ToolbarButtonText> email </ToolbarButtonText> <ToolbarButtonTooltip> email </ToolbarButtonTooltip>

</VmcProgram>

� Default internet browser application <VmcProgram Name=" Browser " Reminder="false" Mode="Manual" Type="Unknown" Min imize="false"


<ProgramPath> ClientType:InternetBrowser </ProgramPath> <Param /> <ToolbarButtonText> browser </ToolbarButtonText> <ToolbarButtonTooltip> browser </ToolbarButtonTooltip>

</VmcProgram>

� Default calendar application <VmcProgram Name=" Calendar " Reminder="false" Mode="Manual" Type="Unknown" Min imize="false"


<ProgramPath> ClientType:Calendar </ProgramPath> <Param /> <ToolbarButtonText> calendar </ToolbarButtonText> <ToolbarButtonTooltip> calendar </ToolbarButtonTooltip>

</VmcProgram>

� Default media application <VmcProgram Name=" Media " Reminder="false" Mode="Manual" Type="Unknown" Min imize="false"


<ProgramPath> ClientType:Media </ProgramPath> <Param /> <ToolbarButtonText> media </ToolbarButtonText> <ToolbarButtonTooltip> media </ToolbarButtonTooltip>

</VmcProgram>

How to install the .Net Framework 2.0 silently There is a parameter in the file setup.ini, which controls the silent installation of the .Net Framework, when using the setup_vmc.exe launcher. If .Net installation should be performed silently, then the key DotNetOptionalInstallIfSilent has to be set to Y. File setup.ini [Startup] DotNetOptionalInstallIfSilent=N

Which devices are supported by VMC 9? For a list of supported devices, please have a look into the release notes.

How to disable the WLAN feature after a successful installation If WLAN has been installed, then there is the following key in the registry database. HKEY_LOCAL_MACHINE\SOFTWARE\Vodafone\Common\Installed Features To disable the WLAN feature after install, just delete the key. Value Name Value Type Value Data Description TataraWLAN REG_SZ 1 TataraWLAN is installed.


Further Information The Vodafone Business homepage contains software and documentation for all Vodafone data products. � VMC software downloads � Data card firmware downloads � VPN documentation � FAQ � How-to’s � Etc…

http://www.business.vodafone.com/site/bus/public/en uk/support/p_support.jsp


Appendixes Appendix A lists properties for the network operator file (Opco file) and a sample content of this file. Appendix B lists properties for the mobile connect profile file and a sample content of this file. Appendix C lists properties for the SMS profile file and a sample content of this file. Appendix D lists properties for the settings file and a sample content of this file. Appendix E lists properties for the conflicting applications decisions file and a sample content of this file.


Appendix A1 – Network Operator File (Opco file) XML element Values Description BuildVersionInfo.CreationDate string Build version Information. BuildVersionInfo.VersionInfo string Build version Information. OpcoData.CCMNC string CCMNC. OpcoData.Opco string Opco. OpcoData.Country string Country. OpcoData.Phone string Phone number. Features.WLAN bool ServiceModule WLAN allowed? Features.SMS bool ServiceModule SMS allowed? Features.VPN bool ServiceModule VPN allowed? Features.SavePIN bool The display of the Save PIN checkbox is

OpCo-specific. Some OpCos do not allow the PIN to be saved. For these OpCos, the Save PIN checkbox should not appear.

Features.PowerOn bool For those devices which have an initial radio state of OFF, or software-disabled status, the user can set a start-up setting so that VMC switches the radio of the device ON, via the appropriate internal call. The default setting for this value is true. If the user has made a custom action to disable the radio via the enable/disable mobile device option, then VMC must NOT attempt to power on the device until the user has re-enabled the device.

Features.DisableSIMdetection bool An OpCo can choose if they would like the software to automatically detect the SIM.

Features.NetworkSearchTimeout string If the device is searching in automatic mode, and a network cannot be found, this dialog is not displayed. It is triggered only by manual network searches. The dialog is presented when the software has not been able to register onto the previously-selected network for 6 minutes (360 seconds).

ApnSettings.Contract.LoginUserName string User name (Contract customer). ApnSettings.Contract.Password string Password (Contract customer). ApnSettings.Contract.ApnName string Access point name (Contract customer). ApnSettings.Contract.UseManualDNS bool Use manual DNS settings? (Contract

customer) ApnSettings.Contract.PrimaryDNS string Primary DNS (Contract customer). ApnSettings.Contract.SecondaryDNS string Secondary DNS (Contract customer). ApnSettings.Prepaid.LoginUserName string User name (Prepaid customer). ApnSettings.Prepaid.Password string Password (Prepaid customer). ApnSettings.Prepaid.ApnName string Access point name (Prepaid customer). ApnSettings.Prepaid.UseManualDNS bool Use manual DNS settings? (Prepaid

customer) ApnSettings.Prepaid.PrimaryDNS string Primary DNS (Prepaid customer). ApnSettings.Prepaid.SecondaryDNS string Secondary DNS (Prepaid customer). ApnSettings.Corporate.LoginUserName string User name (Corporate customer). ApnSettings.Corporate.Password string Password (Corporate customer). ApnSettings.Corporate.ApnName string Access point name (Corporate customer). ApnSettings.Corporate.UseManualDNS bool Use manual DNS settings? (Corporate

customer) ApnSettings.Corporate.PrimaryDNS string Primary DNS (Corporate customer). ApnSettings.Corporate.SecondaryDNS string Secondary DNS (Corporate customer). ApnSettings.WebSession.LoginUserName string User name (WebSession customer). ApnSettings.WebSession.Password string Password (WebSession customer). ApnSettings.WebSession.ApnName string Access point name (WebSession customer). ApnSettings.WebSession.UseManualDNS bool Use manual DNS settings? (WebSession

customer) ApnSettings.WebSession.PrimaryDNS string Primary DNS (WebSession customer). ApnSettings.WebSession.SecondaryDNS string Secondary DNS (WebSession customer). DisplayNames.GPRS string Name to be displayed for GPRS connection DisplayNames.G3 string Name to be displayed for 3G connection DisplayNames.HSDPA string Name to be displayed for HSDPA

connection DisplayNames.EDGE string Name to be displayed for EDGE connection DisplayNames.WebSessionsName string Name to be displayed for WebSessions

connection


OptimisationClient.BytemobileServerIP 1.2.3.4 Server IP Address (for ByteMobile client). OptimisationClient.BytemobileServerPort 4201 Server Port (for ByteMobile client). OptimisationClient.FlashPimaryServerIP Italy: 10.128.219.71

France: 10.61.133.1 Primary Server IP (for Flash client).

OptimisationClient.FlashPrimaryServerPort 2913 Primary Server Port (for Flash client). OptimisationClient.FlashSecondaryServerIP Italy: 10.128.219.70

France: 10.61.133.2 Secondary Server IP (for Flash client).

OptimisationClient.FlashSecondaryServerPort 2913 Secondary Server Port (for Flash client). OptimisationClient.OptimiserClient None, ByteMobile,

FlashNettGain Use no optimization (None), or use ByteMobile or Flash NettGain.

UsageLimitData.MaxGprsDataLimit 1 – 1024 MB Maximum data limit for GPRS. UsageLimitData.MaxGprsTimeLimit 1 – 999 hours Maximum time limit for GPRS. UsageLimitData.Max3GDataLimit 1 – 1024 MB Maximum data limit for 3G. UsageLimitData.Max3GTimeLimit 1 – 999 hours Maximum time limit for 3G. UsageLimitData.DefaultUsageIsData bool Default usage display, time or data. UsageLimitData.OnlineBill string Leads to customer service website or online

billing website of the respective Vodafone OpCo.

PrePaidSettings.BalanceCheckType None, SMS, USSD BalanceCheckType: no Prepaid (None), or use SMS, or use USSD.

PrePaidSettings.PrepaidPhoneNumber string Prepaid phone number. PrePaidSettings.PrepaidUssdNumber string Prepaid USSD number: USSD -

Unstructured Supplementary Service Data. Misc.DialNumber string Dial number: "*99***1#". Misc.UseBandGSM900GSM1800 bool If the device does not support some options

- GSM900 and GSM1800 (Europe) or the respective OpCo has decided not to allow some options, those options will be disabled and therefore shown grayed-out in this window.

Misc.UseBandGSM900DCS1900 bool If the device does not support some options - GSM900 and DCS1900 (USA) - or the respective OpCo has decided not to allow some options, those options will be disabled and therefore shown grayed-out in this window.

Misc.MaximumMessageValidity integer The Validity is the length of time (in hours) that the service center will continue to try and deliver a SMS message. Note that the maximum period supported by some service centers may be less than 1 week. The recommended setting is ‘Maximum’, to ensure that a despatched message has the maximum chance of being delivered to the intended recipient.

Misc.MaxDelayLessPreferred integer A delay to avoid a less-preferred service being selected earlier due to faster hardware recognition.

Misc.UssdOwnNumber string Retrieval of MSISDN via USSD Command. Misc.AssumeSmsLength integer Use the specified value both for character

left count and for the warning pop-ups that inform about over-sized, split SMS. Missing tag or value lt 0 (the default) means: Use currently implemented 9.2 mapping. Value > 0 (we would use 160 for the Greek OpCo) means: Don't use internal mapping, instead, use the specified value both for character left count and for the warning pop-ups (example: 170 char => ‘This message will be split into 2 messages’).

Tcp.Optimize bool Enable or disable the TCP/IP optimization settings for the registry database.

Tcp.TcpWindowSize 131072 TCP/IP setting for HSDPA. The TcpWindowSize parameter can be used to set the receive window on a per-interface basis.

Tcp.GlobalMaxTcpWindowSize 131072 TCP/IP setting for HSDPA. This parameter determines the maximum TCP receive window size of the computer.

Tcp.tcp1323Opts 3 TCP/IP setting for HSDPA. This parameter controls RFC1323 time stamps and window-scaling options.


Tcp.TcpMaxConnectRetransmissions 5 TCP/IP setting for HSDPA. This parameter determines the number of times that TCP re-transmits a connect request (SYNC) before aborting the attempt.

Tcp.SaveAndRestoreSettings * not used * * not used * Setup.AskEULA bool Show or hide the License window. Setup.AskReports bool Show or hide the Reporting window. Setup.ReportingEnabled bool Enable or disable reporting. Setup.AskAccountType bool Show or hide the Account window. Setup.AskTcpSettings bool Show or hide the TCP/IP Settings window. Setup.AskInstallationPath bool Show or hide the Installation Option window. Setup.CreateDesktopShortcuts bool Create shortcut items on the desktop for the

Vodafone Mobile Connect and Vodafone SMS software.

Setup.AskDesktopShortcuts bool Should the user be asked whether to create desktop shortcuts? True: yes, no otherwise. If set to false, shortcuts may be created without asking, depending on CreateDesktopShortcuts.

Setup.InstallationPath string Set the installation folder. OpcoButtons.VmcProgram.Name string Unique name of the button control (only GUI

internal). OpcoButtons.VmcProgram.Reminder bool Show a connection reminder when this

program starts up. OpcoButtons.VmcProgram.Mode Never, Manual,

WhenConnectionOpen, WhenConnectionClosed, OnStart, OnExit

When to start the program.

OpcoButtons.VmcProgram.Type Unknown, SmsApplication, OptimisationByteMobile, OptimisationFlash, VpnClient

Known opco programs are OptimisationByteMobile, SmsApplication, OptimisationFlash, and VpnClient. All other programs must have Unknown as type.

OpcoButtons.VmcProgram.Minimize bool Minimize this program together with VMC. OpcoButtons.VmcProgram.InToolbar bool Show program in the ‘Other Programs’ panel

in the left navigation area of VMC. OpcoButtons.VmcProgram.Once bool Start this program only once. If this program

is already running, set focus to the running instance (if possible). This property is only used for built-in programs. External opco programs are not supported.

OpcoButtons.VmcProgram.I integer Index in the lefthand navigation bar. The index starts with zero. Used only if InToolbar is set to true.

OpcoButtons.VmcProgram.Terminate bool If the program starts, then terminate VMC (Not supported in VMC 9.0).

OpcoButtons.VmcProgram.Style Hidden, Normal, Maximized, Minimized

Start program with this style.

OpcoButtons.VmcProgram.Editable bool If set to false, the user cannot edit this program (Not supported in VMC 9.0).

OpcoButtons.VmcProgram.IsOPCO bool Has to be true for opco programs. OpcoButtons.ProgramPath ClientType:Calendar,

ClientType:Contacts, ClientType:Mail, ClientType:Media, ClientType:News, ClientType:InternetBrowser, registry key, registry key and value, URL

Location of the program.

OpcoButtons.Param string Additional start parameter for this program (optional).

OpcoButtons.ToolbarButtonText string Toolbar button text (only if InToolbar equals true).

OpcoButtons.ToolbarButtonTooltip string Toolbar button tool tip (only if InToolbar equals true).

OpcoPlugins * not supported * * not supported * RoamingPartners.SwitchingBehaviour string Switching behaviour mode: Automatic,

Prompt. RoamingPartners.UseWebSessions string Use WebSessions: NotSet, NationalOnly,

AbroadOnly, Always. SimActivation.Phone string Phone number shown when a SIM is

detected as inactive.


SimActivation.Url string Url shown when a sim is detected as inactive.

SimActivation.Email string Email shown when a sim is detected as inactive.


Appendix A2 – Sample Network Operator File A sample Vodafone Mobile Connect network operator (opco) file 23415.xml . Elements related to installation are marked red. <?xml version="1.0" encoding="utf-8"?> <OPCO xmlns:xsi="http://www.w3.org/2001/XMLSchema-i nstance" xmlns:xsd="http://www.w3.org/2001/XMLSchem a"> <BuildVersionInfo> <CreationDate>2006-09-20T18:33:00.6204148+02:00 </CreationDate> <VersionInfo>9.0.0.3310</VersionInfo> </BuildVersionInfo> <OpcoData CCMNC="23415" Opco="Vodafone UK" Countr y="United Kingdom" Phone="+447785016005" /> <Features> <WLAN>true</WLAN> <SMS>true</SMS> <VPN>true</VPN> <SavePIN>true</SavePIN> <PowerOn>true</PowerOn> <DisableSIMdetection>false</DisableSIMdetection > <NetworkSearchTimeout>360</NetworkSearchTimeout > </Features> <ApnSettings> <Contract> <LoginUserName>web</LoginUserName> <Password>web</Password> <ApnName>internet</ApnName> <UseManualDNS>false</UseManualDNS> <PrimaryDNS /> <SecondaryDNS /> </Contract> <Prepaid> <LoginUserName>web</LoginUserName> <Password>web</Password> <ApnName>pp.internet</ApnName> <UseManualDNS>false</UseManualDNS> <PrimaryDNS /> <SecondaryDNS /> </Prepaid> <Corporate> <LoginUserName /> <Password /> <ApnName>mylan</ApnName> <UseManualDNS>false</UseManualDNS> <PrimaryDNS /> <SecondaryDNS /> </Corporate> <WebSession> <LoginUserName /> <Password /> <ApnName /> <UseManualDNS>false</UseManualDNS> <PrimaryDNS /> <SecondaryDNS /> </WebSession> </ApnSettings> <DisplayNames> <GPRS>GPRS</GPRS> <G3>3G</G3> <HSDPA>3G+</HSDPA> <EDGE /> <WebSessionsName>WebSessions</WebSessionsName> </DisplayNames> <OptimisationClient> <BytemobileServerIP>1.2.3.4</BytemobileServerIP > <BytemobileServerPort>4201</BytemobileServerPor t> <FlashPrimaryServerIP>10.128.219.71</FlashPrima ryServerIP> <FlashPrimaryServerPort>2913</FlashPrimaryServe rPort> <FlashSecondaryServerIP>10.128.219.70</FlashSec ondaryServerIP> <FlashSecondaryServerPort>2913</FlashSecondaryS erverPort> <OptimiserClient>ByteMobile</OptimiserClient> </OptimisationClient> <UsageLimitData> <MaxGprsDataLimit>50</MaxGprsDataLimit> <Max3GDataLimit>50</Max3GDataLimit>


<MaxGprsTimeLimit>10</MaxGprsTimeLimit> <Max3GTimeLimit>10</Max3GTimeLimit> <DefaultUsageIsData>true</DefaultUsageIsData> <OnlineBill>http://www.vodafone.co.uk/mcprepay< /OnlineBill> </UsageLimitData> <PrePaidSettings> <BalanceCheckType>USSD</BalanceCheckType> <PrepaidPhoneNumber /> <PrepaidUssdNumber>*0001345#</PrepaidUssdNumber > </PrePaidSettings> <Misc> <DialNumber>*99***1#</DialNumber> <UseBandGSM900GSM1800>true</UseBandGSM900GSM180 0> <UseBandGSM900DCS1900>true</UseBandGSM900DCS190 0> <MaximumMessageValidity>168</MaximumMessageVali dity> <MaxDelayLessPreferred>30</MaxDelayLessPreferre d> <UssdOwnNumber>*#100#</UssdOwnNumber> <AssumeSmsLength>0</AssumeSmsLength> </Misc> <Tcp> <Optimize>true</Optimize> <TcpWindowSize>131072</TcpWindowSize> <GlobalMaxTcpWindowSize>131072</GlobalMaxTcpWin dowSize> <Tcp1323Opts>3</Tcp1323Opts> <TcpMaxConnectRetransmissions>5</TcpMaxConnectR etransmissions> <SaveAndRestoreSettings>false</SaveAndRestoreSe ttings> </Tcp> <Setup> <AskEULA>true</AskEULA> <AskReports>false</AskReports> <ReportingEnabled>true</ReportingEnabled> <AskAccountType>true</AskAccountType> <AskTcpSettings>false</AskTcpSettings> <AskInstallationPath>true</AskInstallationPath> <CreateDesktopShortcuts>true</CreateDesktopShor tcuts> <AskDesktopShortcuts>true</AskDesktopShortcuts> <InstallationPath /> </Setup> <OpcoButtons> <VmcProgram Name="SMS" Reminder="false" Mode="M anual" Type="SmsApplication" Minimize="false" InToolbar="true" Once="true" I="1" Terminate="false " Style="Normal" Editable="false" IsOPCO="true"> <ProgramPath /> <Param /> <ToolbarButtonText /> <ToolbarButtonTooltip /> </VmcProgram> <VmcProgram Name="VPN" Reminder="false" Mode="M anual" Type="VpnClient" Minimize="false" InToolbar="true" Once="true" I="2" Terminate="false " Style="Normal" Editable="false" IsOPCO="true"> <ProgramPath /> <Param /> <ToolbarButtonText /> <ToolbarButtonTooltip /> </VmcProgram> </OpcoButtons> <OpcoPlugins /> <RoamingPartners> <SwitchingBehaviour>Prompt</SwitchingBehaviour> <UseWebSessions>NotSet</UseWebSessions> </RoamingPartners> <SimActivation> <Phone>99999999</Phone> <Url>http://www.vodafone.uk</Url> <Email>[email protected]</Email> </SimActivation>

</OPCO>


Appendix B1 – Mobile Connect Profile File XML element Values Description Wlans.Wlan.Name string Name of the WLAN device. Wlans.Wlan.IsDefault bool Is the device the default device? The default

device is the one which is used if there is more than one device available. There can only be one default device at a time for each bearer type.

Wans.Wan.Id GUID Unique identifier of this device. Wans.Wan.IsDefault bool Is the device the default device? The default

device is the one which is used if there is more than one device available. There can only be one default device at a time for each bearer type.

Wans.Wan.LastIMSI Last IMSI (International Mobile Subscriber Identity) used with this device.

Wans.Wan.ComPort string Com Port on which the device is connected to the computer.

Wans.Wan.Connectivity Connectivity: Unknown, PCMCIA, Embedded, Bluetooth, Irda, Serial and USB.

Wans.Wan.DisableOnExit bool Disable when software exits. Wans.Wan.DriverVersion string Driver version. Wans.Wan.FirmwareVersion string Firmware version. Wans.Wan.EnableOnStart bool Enable when software starts up. Wans.Wan.IMEI string GSM device IMEI (International Mobile Equipment

Identity) is a unique number associated with every GSM and UMTS mobile phone.

Wans.Wan.KeepDisabled bool If true: this is the current device. This is not serialized.

Wans.Wan.Manufacturer string Manufacturer. Wans.Wan.Model string GSM device model. Wans.Wan.Name string Unique identification for the device. Wans.Wan.NickName string User–defined name for the device. Wans.Wan.PinCode string Saved PIN. Wans.Wan.Pin2Code string Saved PIN 2. Wans.Wan.PreferredConnection string PreferredConnection: Not supported, Default,

GPRSonly, G3only, GPRSpreferred, G3preferred. Wans.Wan.SavePin bool Save PIN allowed? Wans.Wan.SuppConnPrefs

string Internal use only. (A bit mask for the

PreferredWanConnection values that can be chosen as preferences.)

Wans.Wan.Type string Type of the device. Possible values: None Pcdatacard MobilePhone WLAN

Sims.Sim.IccId string SIM serial number, which may be reported by the device as part of the device info.

Sims.Sim.HomeOpId string International ID of the SIM's home operator. Sims.Sim.IMSI string GSM device IMSI (International Mobile Subscriber

Identity). This is a unique number that is associated with all GSM and UMTS network mobile phone users. The number is stored in the SIM.

Sims.Sim.OwnNumber string GSM device own number. BuildVersionInfo.CreationDate string Build version Information. BuildVersionInfo.VersionInfo string Build version Information. UserButtons string User buttons. VPN.Location string Program path / location of the VPN client. VPN.UseMsVPN bool Use Microsoft VPN client? VPN.UseOtherVPN bool Use other VPN client? VPN.MsVpnName string Microsoft VPN name. VPN.OtherVpnName string Other VPN name. UpdateMobileConnect.UpdateMode string Call the Update manager. UpdateMobileConnect.LastAccessDate date/time Date/Time of last start of MobileConnect. UpdateMobileConnect.LastUpdateDate date/time Date/Time of last SW Update: The SW Update

and Config Manager component interface maintains the VMC software by retrieving and applying updates to software components, device firmware and configuration data.

Locks.Locks bool PIN settings.


Notification.AskBeforeClosingConnection bool When selected, a dialog will be shown before any Mobile or WLAN connection opened by Vodafone Mobile Connect is closed. If the user clicks on OK, or types Return or Enter on the keyboard, Vodafone Mobile Connect will close the current connection. If the user clicks Cancel, or the red close button on the top right-hand corner of the dialog’s title bar, or types the Esc key on the keyboard, Vodafone Mobile Connect will remain as it was before and the connection will not be closed. If the checkbox is de-selected, the respective Notification preference will be de-selected. This dialog will then not be shown any more, unless the preference is selected again in the Tools/Settings/Notification window.

Notification.AskBeforeSwitchingConnection bool When selected, VMC will switch to the connection settings on the SIM.

Notification.AskBeforeExitingMobileConnection bool When selected, a dialog window will be shown if the user selects File/Exit.

Notification.AskBeforeMinimizeToSystray bool When selected, a dialog window will be shown if the user presses [X] to minimize the application to systray.

Notification.AskBeforeShowingUsageDisclaimer bool When selected, a dialog window will be shown if the user switches to View the Usage screen.

Notification.AskBeforeSwitchingWebSessions bool WebSessions:If the ’Don't tell me again‘ checkbox is selected, and the user closes the switch confirmation window by confirming or cancelling, the user's decision (confirm or cancel) is used the next time a switch is necessary.

Notification.NotificationBehaviour string When selected, connection availability and confirmation is shown above the Windows Notification area (‘systray’) according to the default Windows preference, or always, or never.

Notification.SignalThresholdWlan integer WLAN signal strength threshold limit. Do not show if less! Range: 0 -100.

Notification.AskDataTrafficWarning bool Optimisation preferences changed, show warning. OptimizeMobileConnect.OptImageQuality integer The integrated optimization client will be either

Flash Networks Nettgain, or ByteMobile. The image quality slider will set the image compression higher or lower. High quality images transfer slower than low quality images. 0 = worse, 100 = best (no compression).

OptimizeMobileConnect.Video bool Video: The blocking boxes will enable the content-blocking of ByteMobile/Flash. True: video content will be blocked, false otherwise.

OptimizeMobileConnect.Images bool Images: The blocking boxes will enable the content-blocking of ByteMobile/Flash. True: images will be blocked, false otherwise.

OptimizeMobileConnect.Audio bool Audio: The blocking boxes will enable the content-blocking of ByteMobile/Flash. True: audio content will be blocked, false otherwise.

OptimizeMobileConnect.Applets bool Applets: The blocking boxes will enable the content-blocking of ByteMobile/Flash. True: applets will be blocked, false otherwise.

OptimizeMobileConnect.Animation bool Animation: The blocking boxes will enable the content-blocking of ByteMobile/Flash. True: animations will be blocked, false otherwise.

DisplayConnection.ConnectionTime bool Display connection indicators: Time. DisplayConnection.DataAmount bool Display connection indicators: Data amount. DisplayConnection.DataRate bool Display connection indicators: Data transfer rate. Gui.StartMobileConnectWhenWindowsStartsUp bool Start Vodafone Mobile Connect when Windows

starts up. Gui.PreventStandby bool When selected, Vodafone Mobile Connect will stop

the computer from entering standby or hibernate mode, and will maintain any Mobile or WLAN connection that is open. Allow Standby or Hibernate and close connection Hibernate: This is a system power mode. When a system enters hibernation, the contents of its memory are saved to disk before the computer is turned off.


When the system is restarted, the desktop and previously active programs are restored. Standby: Indicates a system power mode. When a computer is in standby mode, some devices are turned off and the computer uses less power. The system can restore itself more quickly than returning from hibernation. Because standby does not save the memory state to disk, a power failure while in standby can cause loss of information.

Gui.IsWlanEnabled bool Save user setting for enable/disable WLAN (in Manage Devices Screen).

Gui.SelectBand string Select Band: when "Automatic" selected, Vodafone Mobile Connect will automatically select the correct network band.

Gui.LastActiveControlIndex integer Maximum size of logging file in bytes, before the logfile is backed up and a new logfile started. The newly-backed up logfile replaces the previously backed up logfile.

Gui.UserAccount Contract, Prepaid, Corporate

Account type.

Gui.CurrentAccount Contract, Prepaid, Corporate

Account type.

Gui.ModuleSequence.Mode string This property holds the sequence of the service modules as they are preferred by the user.


Appendix B2 – Sample Mobile Connect Profile File Sample of the Vodafone Mobile Connect user profile file MobileConnectProfile.xml . <?xml version="1.0" encoding="utf-8"?> <MobileConnectProfile xmlns:xsi=http://www.w3.org/2 001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <ConnectionData Modified="false" /> <Wlans Modified="true"> <Wlan Name="Intel(R) PRO/Wireless 3945ABG Netwo rk Connection" IsDefault="true" /> </Wlans> <Wans Modified="true"> <Wan Id="c7e341bd-e22f-4909-aec4-04f615db9f01" IsDefault="true" LastIMSI="238012151264655"> <ComPort>COM4</ComPort> <Connectivity>Unknown</Connectivity> <DisableOnExit>false</DisableOnExit> <DriverVersion>3.3.1.3</DriverVersion> <FirmwareVersion>2.6.1Hd </FirmwareVersion> <EnableOnStart>true</EnableOnStart> <IMEI>004401440326227</IMEI> <KeepDisabled>false</KeepDisabled> <Manufacturer>Option N.V.</Manufacturer> <Model>GlobeTrotter HSUPA Modem</Model> <Name>GlobeTrotter HSDPA HSUPA Modem Interfac e</Name> <NickName /> <PinCode>1;0;0;0;208;140;157;223;1;21;209;17; 140;122;0;192;79;194;151;235;1;0;0;0;34;91;70;43;70 ;70; 125;79;143;222;196;163;222;37;170;189;0;0;0;0;2;0;0 ;0;0;0;3;102;0;0;168;0;0;0;16;0;0;0;109;55;187;73;2 34; 208;210;35;223;148;182;10;126;45;70;158;0;0;0;0;4;1 28;0;0;160;0;0;0;16;0;0;0;108;61;248;5;156;237;228; 58; 194;167;216;227;155;92;248;93;8;0;0;0;49;43;69;49;5 3;41;6;241;20;0;0;0;132;156;155;160;84;99;248;139;2 4; 82;102;26;145;144;158;239;38;205;136;33;</PinCode> <Pin2Code /> <PreferredConnection>Default</PreferredConnec tion> <SavePin>true</SavePin> <SuppConnPrefs>GPRSonly G3only GPRSpreferred G3preferred</SuppConnPrefs> <Type>PCdatacard</Type> </Wan> </Wans> <Sims Modified="true"> <Sim IccId="89450143060925576673" HomeOpId="238 01" IMSI="238012151264655" OwnNumber="" /> </Sims> <BuildVersionInfo> <CreationDate>2007-07-21T23:08:06.0547165+02:00 </CreationDate> <VersionInfo>9.2.1.6545</VersionInfo> </BuildVersionInfo> <UserButtons /> <VPN> <Location /> <UseMsVPN>false</UseMsVPN> <UseOtherVPN>false</UseOtherVPN> <MsVpnName /> <OtherVpnName /> </VPN> <UpdateMobileConnect> <Update>Weekly</Update> <LastAccessDate>2007-07-21T23:08:06.0547165+02: 00</LastAccessDate> <LastUpdateDate>2007-07-21T23:08:06.0547165+02: 00</LastUpdateDate> </UpdateMobileConnect> <Locks> <Locks>None</Locks> </Locks> <Notification> <AskBeforeClosingConnection>true</AskBeforeClos ingConnection> <AskBeforeSwitchingConnection>true</AskBeforeSw itchingConnection> <AskBeforeExitingMobileConnection>true</AskBefo reExitingMobileConnection> <AskBeforeMinimizeToSystray>true</AskBeforeMini mizeToSystray> <AskBeforeShowingUsageDisclaimer>true</AskBefor eShowingUsageDisclaimer> <AskBeforeSwitchingWebSessions>false</AskBefore SwitchingWebSessions> <NotificationBehaviour>Default</NotificationBeh aviour> <SignalThresholdWlan>20</SignalThresholdWlan> <AskDataTrafficWarning>true</AskDataTrafficWarn ing> </Notification> <OptimizeMobileConnect> <OptImageQuality>50</OptImageQuality> <Video>false</Video> <Images>false</Images> <Audio>false</Audio> <Applets>false</Applets> <Animation>false</Animation> </OptimizeMobileConnect> <DisplayConnection> <ConnectionTime>true</ConnectionTime>


<DataAmount>true</DataAmount> <DataRate>true</DataRate> </DisplayConnection> <Gui> <StartMobileConnectWhenWindowsStartsUp>true</St artMobileConnectWhenWindowsStartsUp> <PreventStandby>false</PreventStandby> <IsWlanEnabled>true</IsWlanEnabled> <SelectBand>Automatic</SelectBand> <LastActiveControlIndex>0</LastActiveControlInd ex> <UserAccount>Contract</UserAccount> <CurrentAccount>Contract</CurrentAccount> <ModuleSequence> <Mode>Mobile</Mode> <Mode>WLAN</Mode> </ModuleSequence> </Gui> </MobileConnectProfile>


Appendix C1 – SMS Profile File XML element Values Description BuildVersionInfo.CreationDate string Build version Information. BuildVersionInfo.VersionInfo string Build version Information. LastAccessDate string Date/Time of last start of the SMS application. LastCompactDate string Date/Time of last compact database. SmsInBox.AutoForwardPhone string The user may enter a telephone number to which

SMS will be forwarded. Vodafone Mobile Connect will receive an SMS, and then forward that SMS message on to this number automatically.

SmsInBox.LeaveCopyOnSIM bool Leave a copy of all SMS received on your SIM. Messages that have been received will not be removed from the SIM card of the mobile device that is being used with Vodafone Mobile Connect. Messages will therefore continue to be available on the device after it has been disconnected from the computer. Because the SIM may become full, when Vodafone Mobile Connect has detected that the SIM only has space for 2 further messages, a warning message dialog should be shown. Text: "There is almost no space left to receive SMS messages on your SIM. Delete all messages from SIM now?" If false, remove received SMS from the SIM and store only in this program. Messages that are or have been received will then be removed from the mobile device. The messages will be stored in Vodafone Mobile Connect until they are deleted from the SMS Inbox.

SmsInBox.AutoForward bool Auto forward all received SMS. The user may enter a telephone number to which SMS may be forwarded. Vodafone Mobile Connect will receive an SMS, and then forward that SMS message on to this number automatically. When the user selects the checkbox, the ’Forward to:’ field will be enabled, and the user can then enter the required telephone number into the field. If the checkbox is de-selected, the ‘Forward to:’ number will be retained, but disabled. The field label, the ‘Reply to:’ number and the field will then be shown in grey. Messages will not be forwarded, but received as normal by Vodafone Mobile Connect. If the checkbox is re-selected, the existing Forward to number will be re-enabled, and messages will once again be forwarded to this number.

SmsSynchronsisation.SynchroniseTo string Synchronise to: None, Outlook, OutlookExpress, LotusNotes, SimCard.

SmsSynchronsisation.SynchroniseInterval string Interval: None, Daily, Weekly, Monthly. SmsSynchronsisation.LastAccessDate string Date/Time of last start of the SMS application. SmsSynchronsisation.LastSynchronisationDate string Date/Time of last Synchronisation. SmsMessages.RequestStatusReply bool This option will confirm delivery of SMS messages

that are sent from Vodafone Mobile Connect. The confirmation will be returned once the despatched message has been delivered to the recipient’s smscPhoneNumber, and will be in the form of an SMS message. This will appear as normal in the Vodafone Mobile Connect SMS Inbox.

SmsMessages.UseSameSMSC bool Use same SMSC for a Reply message as was used by the incoming message, according to 3GPP TS 23.040 v660. If an SMS message is sent in reply to a message that was received, this setting specifies that the message will be sent back via the same service center that delivered the original incoming message. This option may help if difficulties are encountered replying to a message using the previously-selected service center.

SmsMessages.MessageValidity integer The Validity is the length of time (in hours) that the service center will continue to try and deliver a SMS message. The validity can be set to 1 hour, 6 hours, 1 day, 1 week or the maximum period that the selected service center will support. Note that


the maximum period supported by some service centers may be less than 1 week. The recommended setting is ‘Maximum’, to ensure that a despatched message has the maximum chance of being delivered to the intended recipient.

SmsMessages.MessageClass string The message class determines the delivery location on the recipient’s phone for SMS messages that are sent. The options are: - Default: This delivers the text to the location that the chosen service center uses if a class is not specified. SMS are usually delivered to the SIM. - Screen: This delivers the SMS message directly to the display of the recipient’s phone. - Memory: This delivers the SMS message directly to the recipient’s phone. - SIM Memory: This delivers the SMS message directly to the recipient’s SIM card. The recommended setting for Message Class is Default.

SmsMessages.Signature string This text could include, for example, the user’s name and contact details. Leaving this field blank will not insert a signature at all, leaving all 160 characters free to be used for SMS messages.

SmsMessages.ReplyTo bool When the user selects the value, the ‚ReplyToNumber’ field will be enabled.

SmsMessages.ReplyToNumber string A telephone number can be entered into this field. If an SMS is sent with the Reply-To option set to a different number, no difference is visible in the SMS when despatched. The difference is not visible until the recipient replies to the SMS. When the recipient replies, the reply is not sent to the sender’s number, but to the address set in the Reply-To option when the SMS was sent.

SmsServiceCenter.HomeOpId string SMSC Home Operator. SmsServiceCenter.IsCustom bool True if custom SMSC number. SmsServiceCenter.Phone string Service Center (SMSC) phone number. TimerSettings.WaitUntilNewStateChange integer Internal tuning parameter. Do not change. TimerSettings.WaitSecondsUntilNewReadSmsInfo integer Internal tuning parameter. Do not change. TimerSettings.WaitUntilSendErrornousSMS integer Internal tuning parameter. Do not change.


Appendix C2 – Sample SMS Profile File Sample of the SMS profile file SmsProfile.xml . <?xml version="1.0" encoding="utf-8"?> <SmsProfile xmlns:xsi="http://www.w3.org/2001/XMLSc hema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <BuildVersionInfo> <CreationDate>2007-07-22T15:25:34.2770216+02:00 </CreationDate> <VersionInfo>9.2.1.6545</VersionInfo> </BuildVersionInfo> <LastAccessDate>2007-07-22T15:25:37.5686216+02:00 </LastAccessDate> <LastCompactDate>2007-07-22T15:25:34.2770216+02:0 0</LastCompactDate> <SmsInbox> <AutoForwardPhone /> <LeaveCopyOnSIM>false</LeaveCopyOnSIM> <AutoForward>false</AutoForward> </SmsInbox> <SmsSynchronsisation> <SynchroniseTo>None</SynchroniseTo> <SynchroniseInterval>Weekly</SynchroniseInterva l> <LastAccessDate>2007-07-22T15:25:34.2770216+02: 00</LastAccessDate> <LastSynchronisationDate>2007-07-22T15:25:34.27 70216+02:00</LastSynchronisationDate> </SmsSynchronsisation> <SmsMessages> <RequestStatusReply>false</RequestStatusReply> <UseSameSMSC>false</UseSameSMSC> <MessageValidity>168</MessageValidity> <MessageClass>Default</MessageClass> <Signature /> <ReplyTo>false</ReplyTo> <ReplyToNumber /> </SmsMessages> <SmsServiceCenter> <HomeOpId>23801</HomeOpId> <IsCustom>false</IsCustom> <Phone>+4540390999</Phone> </SmsServiceCenter> <TimerSettings> <WaitUntilNewStateChange>9</WaitUntilNewStateCh ange> <WaitSecondsUntilNewReadSmsInfo>60</WaitSeconds UntilNewReadSmsInfo> <WaitUntilSendErrornousSMS>240</WaitUntilSendEr rornousSMS> </TimerSettings> </SmsProfile>


Appendix D1 – Settings File XML element Values Description BuildVersionInfo.CreationDate string Build version Information. BuildVersionInfo.VersionInfo string Build version Information. IdentificationList.DeviceIdentification.ConnectivityType string Device connectivity type. IdentificationList.DeviceIdentification.DeviceMode string DeviceMode: None, ProbeAlwaysNeeded,

RimEntry. IdentificationList.DeviceIdentification.DisableOnExit bool Disable when software exits. IdentificationList.DeviceIdentification.EnableOnStart bool Enable when software starts up. IdentificationList.DeviceIdentification.FriendlyName string Device friendly name. IdentificationList.DeviceIdentification.Manufacturer string OEM manufacturer. IdentificationList.DeviceIdentification.OemId string OEM identifier. IdentificationList.DeviceIdentification.OemModel string OEM model. Intern.BearerChangedDelay long Logfile rolling: maximal size of logging

files in bytes. Minimal value=999999. Intern.CheckForOpcofileChanged integer Timer (seconds): Check whether OPCO

file changed. Intern.IsWanDiagnosticsTrace bool WAN Diagnostics Trace (PCTEL). Intern.LoggingFileSize integer After connected to a 3G network the

bearer is changing from GPRS to 3G. This delay time (in seconds) mask this inconsistency from the user in the UI, and also from the usage information sent to the Reporting Service.

Intern.WaitConflictingApplications integer Wait time until ConflictingApplications terminated (seconds). Used during exit of MobileConnect.

Intern.WaitConnServicesDisposed integer Wait time until ConnectionServices terminated (seconds). Used during exit of MobileConnect.

Intern.WaitUntilReportingFinished integer Wait until reporting webservice call finished (sec).

Intern.WanInterfaceTrace integer WAN Interface Trace: 0..4 Intern.WlanInterfaceTrace integer Wlan Interface Trace: 0..4

Appendix D2 – Sample Settings File Sample of the settings file Settings.xml . <?xml version="1.0" encoding="utf-8"?> <Settings xmlns:xsi="http://www.w3.org/2001/XMLSche ma-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <BuildVersionInfo> <CreationDate>2007-03-23T18:08:20.4961015+01:00 </CreationDate> <VersionInfo>9.2.0.5022</VersionInfo> </BuildVersionInfo> <Intern> <WlanInterfaceTrace>0</WlanInterfaceTrace> <WanInterfaceTrace>0</WanInterfaceTrace> <IsWanDiagnosticsTrace>false</IsWanDiagnosticsT race> <MaximalWaitTimeConnect>120</MaximalWaitTimeCon nect> <MaximalWaitTimeDisconnect>120</MaximalWaitTime Disconnect> <MaximalWaitTimeViewNetworks>300</MaximalWaitTi meViewNetworks> <MaximalWaitTimeConnectToWan>300</MaximalWaitTi meConnectToWan> <WaitUntilReportingFinished>8</WaitUntilReporti ngFinished> <LoggingFileSize>9999999</LoggingFileSize> <BearerChangedDelay>5</BearerChangedDelay> </Intern> <IdentificationList> <DeviceIdentification> <OemId>Dell Inc.</OemId> <OemModel>MXC062</OemModel> <Manufacturer>Novatel Wireless Incorporated</ Manufacturer> <FriendlyName>Dell Wireless 5505 Mobile Broad band (3G HSDPA) Minicard</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>Dell Inc.</OemId> <OemModel>Latitude D420</OemModel> <Manufacturer>Novatel Wireless Incorporated</ Manufacturer> <FriendlyName>Dell Wireless 5505 Mobile Broad band (3G HSDPA) Minicard Modem</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>Dell Inc.</OemId> <OemModel>Latitude D420</OemModel> <Manufacturer>Novatel Wireless Incorporated</ Manufacturer> <FriendlyName>Dell Wireless 5520 Voda I Mobil e Broadband (3G HSDPA) Minicard</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>Dell Inc.</OemId>  <OemModel>Latitude D420|Latitude D830</OemMod el> <Manufacturer>Novatel Wireless Incorporated</ Manufacturer> <FriendlyName>Dell Wireless 5520 Voda L Mobil e Broadband (3G HSDPA) Minicard</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>FUJITSU SIEMENS</OemId> <OemModel>AMILO Pro Series V3525</OemModel> <Manufacturer>Sierra Wireless, Inc.</Manufact urer> <FriendlyName>Sierra Wireless AT Command Port (UMTS)</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>Lenovo</OemId> <OemModel>874126U|8895JTU|8895KFU</OemModel> <Manufacturer>Sierra Wireless, Inc.</Manufact urer> <FriendlyName>Sierra Wireless AT Command Port (UMTS)</FriendlyName> <ConnectivityType>Embedded</ConnectivityType>


<DeviceMode>None</DeviceMode> <DisableOnExit>false</DisableOnExit> <EnableOnStart>false</EnableOnStart> </DeviceIdentification> <DeviceIdentification> <OemId>HP</OemId> <OemModel>HP</OemModel> <Manufacturer>Sierra Wireless, Inc.</Manufact urer> <FriendlyName>HP hs2300 HSDPA Broadband Wirel ess AT Command Port</FriendlyName> <ConnectivityType>Embedded</ConnectivityType> <DeviceMode>None</DeviceMode> <DisableOnExit>true</DisableOnExit> <EnableOnStart>true</EnableOnStart> </DeviceIdentification> </IdentificationList> </Settings>


Appendix E1 – Conflicting Applications Decisions Fi le XML element Values Description BuildVersionInfo.CreationDate string Build version Information. BuildVersionInfo.VersionInfo string Build version Information. ConflictingApplicationSoftwareManagement string Software Management: Individually,

Automatic, Manual. ConflictingApplicationTimerTick string TimerTicks get/set the waiting time until

the next CA check. ConflictingApplicationStatus string Status of CA ConflictingApplicationList.ConflictingApplication.ParentAppId string A primary key UID used to uniquely

identify a parent application. ConflictingApplicationList.ConflictingApplication.ParentAppName string A user viewable text used to identify the

top level application name. ConflictingApplicationList.ConflictingApplication.SubAppId string A UID used to identify a sub-component

of a parent application. ConflictingApplicationList.ConflictingApplication.SubAppName string A user viewable test used to uniquely

identify a sub-process or sub-application which must be shut down as part of parent application.

ConflictingApplicationList.ConflictingApplication.FileLocation string The actual location of the process/service which must be shut down or restarted.

ConflictingApplicationList.ConflictingApplication.AppVersion string The version of the parent application. ConflictingApplicationList.ConflictingApplication.ApplicationType string Details if the application affects the

WLAN or Mobile (WWAN) element of VMC.

ConflictingApplicationList.ConflictingApplication.CanBeSuspended string It may be possible that this application cannot be suspended.

ConflictingApplicationList.ConflictingApplication.ServiceProcessId string Name of the EXE or service which VMC will search for to determine if the conflicting application is running.

ConflictingApplicationList.ConflictingApplication.ShutDownBehaviour string The technical details and behaviour which VMC will follow to shut down the respective application.

ConflictingApplicationList.ConflictingApplication.RestartBehaviour string The technical details and behaviour which VMC will follow to restart the respective application.

ConflictingApplicationList.ConflictingApplication.OperatingSystem string The operating system to which the conflicting applications logic applies.

ConflictingApplicationList.ConflictingApplication.OemId string An additional tag allowing a conflicting application to be treated differently for different OEMs

ConflictingApplicationList.ConflictingApplication.AppStatus string Current status of the application, possibly after user's decision.

ConflictingApplicationList.ConflictingApplication.RuntimeType string Specifies the type of the CA. Two possible values: Process Service


Copyright 2005-2007 Vodafone Group. All rights reserved.

Published by Vodafone Global and Rudolf Preisenberger

Vodafone Business Global Business product support website www.business.vodafone.com

Appendix E2 – Sample Conflicting Applications Decis ions File Sample of the conflicting applications decisions file ConflictingApplicationsDecisions.xml . <?xml version="1.0" encoding="utf-8"?> <ConflictingApplications xmlns:xsi="http://www.w3.o rg/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <BuildVersionInfo> <CreationDate>2007-04-18T18:30:27.2704819+02:00 </CreationDate> <VersionInfo>9.2.0.0001</VersionInfo> </BuildVersionInfo> <ConflictingApplicationSoftwareManagement>Individ uallyManage</ConflictingApplicationSoftwareManageme nt> <ConflictingApplicationTimerTick>Second5</Conflic tingApplicationTimerTick> <ConflictingApplicationStatus>NotHandle</Conflict ingApplicationStatus> <ConflictingApplicationList> <ConflictingApplication> <ParentAppId>1</ParentAppId> <ParentAppName>VMC Lite</ParentAppName> <SubAppId /> <SubAppName /> <FileLocation /> <AppVersion>vodafone</AppVersion> <ApplicationTyp>MobileWlan</ApplicationTyp> <CanBeSuspended>Yes</CanBeSuspended> <ServiceProcessId>vmc</ServiceProcessId> <ShutDownBehaviour>Kill</ShutDownBehaviour> <RestartBehaviour>Yes</RestartBehaviour> <OperatingSystem>XP</OperatingSystem> <OemId>vodafone</OemId> <AppStatus>NotHandle</AppStatus> <RuntimeTyp>Process</RuntimeTyp> </ConflictingApplication> </ConflictingApplicationList> </ConflictingApplications>

White Paper Vodafone Mobile Connect IT...

Documents

Transcript of White Paper Vodafone Mobile Connect IT...