Enterprise Install Guide: Vodafone Mobile Broadband
Contents Introduction .......................................................................................................................... 3 Corporate Setup Package ................................................................................................ 4 Prerequisites for Vodafone Mobile Broadband .......................................................................5 Customisation Files .........................................................................................................
Introduction Introduction This document covers the installation of the Vodafone Mobile Broadband 10.2 application on Microsoft® Windows® operating systems in corporate environments. It covers scenarios for IT administrators, customisation, and the rollout of the application using transform files. For an introduction to corporate rollouts of the Vodafone Mobile Broadband application, please refer to the Standard Install Guide.
Corporate Setup Package Corporate Setup Package The Corporate Setup Package is provided as a compressed release, where all program files are stored into a single cabinet file, it comprises the following files in folder DISK1. Vodafone Mobile Broadband.msi File Description Installer database file Setup_vmb.exe InstallShield’s setup launcher application Setup.ini Configuration file for InstallShield’s setup launcher application setup_vmb.exe Data1.
Prerequisites for Vodafone Mobile Broadband Setup prerequisites are Wireless LAN API hotfix, Installer 3.1, .Net Framework 2.0, and Visual C++ 2005 SP1. Wireless LAN API (for Windows XP SP2 only) Microsoft’s hotfix Wireless LAN API (KB918997), this hotfix is contained in Service Pack 3 of Windows XP. http://www.microsoft.com/downloads/details.
Customisation Files In addition of the user profile file MobileBroadbandProfile.exe, there are two other profile files, one for VMB’s SMS application named SmsProfile.xml, and one for VMB’s Dial-Up feature named VodafoneMobileBroadband.pbk. At least all Operator specific XML customisation files, like 23415.xml, Opco-23415.xml, for example for Vodafone UK can be replaced by modified ones. These customisation files and of course all other files can be replaced during the setup process using Transform files.
Customisation Files Optional: Modify XML elements as you require. 5. Create a Transform file. Refer to the Using Transforms for Customisation chapter. 6. Apply your Transform file to the Vodafone Mobile Broadband 10 setup procedure. Refer to the Using Transforms for Customisation chapter. Customisation using a modified Dial-Up Phonebook file If the ‘Dial-Up’ feature is set to ‘true’ in the OpCo XML file, a default dial-up phonebook called VodafoneMobileBroadband.
Customisation Files Windows XP :\Documents and Settings\\Application Data\Vodafone\Vodafone Mobile Broadband\UserData Windows Vista and Windows 7 :\Users\\AppData\Roaming\Vodafone\Vodafone Mobile Broadband\UserData The Vodafone Mobile Broadband application uses some entry attributes which are not supported by the operating system.
Customisation Examples Customisation Examples A good starting point for finding the correct xml element to be set for a certain task is to install VMB on a test machine and then to set the required setting from within the GUI. After exiting VMB, the modifications can then be viewed in the file MobileBroadbandProfile.xml, when compared to a saved file MobileBroadbandProfile.xml.
Customisation Examples Which File to modify? If these changes should be applied for all OPCPs, then we must modify the template file MobileBroadbandProfile.xml, otherwise we have to change the OPCO file for one or more OPCOs, the OPCO file for Vodafone UK for instance is Opco-23415.xml. What xml element to modify The default xml elements in the file MobileBroadbandProfile.xml for the Start and Close options are: ...
Customisation Examples Gui/Start Misc/Start DoNotStart Do not start this application Gui/Exit Misc/Exit DoNotStartNewInstance Exit this application So, to change for instance the Start and Close options for Vodafone UK, please do the following: 1. Open file Opco-23415.xml and add or change the xml element Gui to ... 2. Perform the steps described in chapter Using Transforms for Customisation of this document.
Customisation Examples package on the local system. With the /b option, one can specify the directory in which to cache the installation files, as in /b"%LOCALAPPDATA%\Vodafone". A local cache of the installation files is necessary when installing VMB, the recommended local folder would be %LOCALAPPDATA%\Vodafone, but can be changed if required. The environment variable %LOCALAPPDATA% is defined in Windows Vista and in Windows 7, for Windows XP the environment variable %APPDATA% can be used as well.
Customisation Examples How to disable features? Certain features can be set in the opco file using xml node element . Xml element with default value false Description Should Always Best Connected be enabled in VMB software? If 'Yes' the software will display the ABC function in the main view. ABC provides best connectivity at any time. false Dial-Up allowed? Tell VMB how to deal with the corresponding Dial-Up service module.
Customisation Examples to enable a setting in the start-up settings panel which allows VMB to switch the radio of the device on. The default setting for this value will be true. Where the user has made a custom action to disable the radio via the enable/disable mobile device option then VMB must NOT attempt to power on the device until the user has re-enabled the device. true If SavePIN is ‘true’ the PIN will be saved in the software and used automatically when the SIM is used.
Customisation Examples File nnnnn.xml: false ... How to disable the optimiser? The optimiser, i.e. ByteMobile can be disabled using the following xml settings in the opco file.
Customisation Examples Set command line installer property LOCKINGCODE or modify Property Table via Transform. After installation of VMB the locking code is stored without encryption in registry hive HKLM\SOFTWARE\Vodafone\VMB:LockingCode. Command line example: msiexec.exe /i "Vodafone Mobile Broadband.msi" LOCKINGCODE=500503 TRANSFORMS=....
Customisation Examples ApplicationConflicts Page 17 of 35 August 2011
Appendix A: Supported VPN Clients Appendix A: Supported VPN Clients Vodafone Mobile Broadband 10 supports the following VPN clients: • Cisco (the new Cisco VPN Client called ‘Any Connect’ is currently not supported) • Checkpoint • Fortinet • Microsoft VPN.
Appendix A: Supported VPN Clients Configuration via the User Interface If a supported VPN client is installed and configured in Windows, the Vodafone Mobile Broadband application will automatically display a button for it (Microsoft, Cisco, Checkpoint or Fortinet). If one of these buttons is selected, a drop-down menu with the available profiles from the VPN client will be shown.
Appendix A: Supported VPN Clients MS VPN must be the name of the Microsoft VPN connection that has been configured in Windows. Cisco VPN To manage a Cisco VPN connection, Vodafone Mobile Broadband uses vpngui.exe. The connection will be created using the default profile. The necessary entries in MobileBroadbandProfile.XML are: true C:\Program Files\Cisco Systems\VPN Client\vpngui.
Appendix B: Always Best Connected (ABC) - Reference Appendix B: Always Best Connected (ABC) - Reference Always Best Connected enhances the Vodafone Mobile Connect application, allowing it to manage all available types of connection, as opposed to only being able to manage mobile connections: • LAN (Ethernet) • Mobile Networks (eg. GPRS, 3G, HSPA) • Wi-Fi (e.g. public hotspots, Wi-Fi routers, or corporate Wi-Fi networks). Always Best Connected has been built on core Windows services, including the .
Appendix B: Always Best Connected (ABC) - Reference In this element, additional features can be defined by the OpCo, e.g. VPN, SavePIN, PowerOn, and so on. Xml element ABC Value boolean Comment Feature can be disabled by the user. DisplayName string DisplayName, e.g. Always best connected. DisableSetting boolean Feature can be disabled by the user.
Appendix B: Always Best Connected (ABC) - Reference • or has only been open for a short time - the default is 0 minutes. The PreventWhenVpn and PreventWhenBusy tags are Boolean. The PreventWhenNew tag is numeric and defines the number of minutes for which a connection will be considered ‘new’. Xml element PreventWhenVpn Value boolean Comment Prevent when a VPN is open. PreventWhenNew number Prevent when a connection is new.
Appendix B: Always Best Connected (ABC) - Reference connection needs to be closed in order to switch to a higher-prioritised connection.
Appendix B: Always Best Connected (ABC) - Reference National and International The AlwaysBestConnected element contains two objects that prioritise the connection types: • The sub-tag in the International tag sets the priority of this connection type when the user is in a roaming situation • The sub-tag in the National tag sets the connection’s priority in non-roaming situations, ie. when the user is located in coverage of their home network.
Appendix B: Always Best Connected (ABC) - Reference http://www.vodafone.
Appendix B: Always Best Connected (ABC) - Reference AnchorPoint1 url URL of server acting as the corporate anchor point. AnchorPoint2 url URL to be used if AnchorPoint1 is not available. Latency number To accept the connection as usable, the anchor point must be reachable within this latency time (seconds). ResponsePattern string The server must send back a response matching this response pattern. Server url The name of the anchor point.
Appendix B: Always Best Connected (ABC) - Reference In this example, the XML defines that a server is accessible in a corporate intranet at the URL http://myserver, and serves an HTML file called ACK.html. The content of the file includes the word ACK, and this is defined as the expected response pattern. When a connection is opened, ABC will send a request to myserver.
Appendix C: Using Transforms for Customisation % ProgramFiles%\Cisco Systems\VPN Client\ipsecdialer.exe false true Cisco VPN Here the location of an existing VPN client is defined in the LOCATION tag, and the start parameter /c is defined in the VpnParam to connect automatically when the client is started.
Appendix C: Using Transforms for Customisation 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.
Appendix C: Using Transforms for Customisation 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.
Appendix C: Using Transforms for Customisation 3. Open Orca.exe. 4. From the File menu, select Open and browse to the file Vodafone Mobile Broadband.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 MobileBroadbandProfile.xml row. 8. Select the column FileSize and enter the file size of the new MobileBroadbandProfile.xml file. 9. In the right pane, select the row which displays filename 23415.xml in the third column. 10.
Appendix C: Using Transforms for Customisation 2. Provide the modified MobileBroadbandProfile.xml file for setup_vmc.exe launcher. Copy the new MobileBroadbandProfile.xml file that should replace the existing file into the related folder of the source media. For example, navigate to the folder DISK1\program files\Vodafone\Vodafone Mobile Broadband\Templates, and replace the existing MobileBroadbandProfile.xml file. 3. Provide the modified file 23415.xml for setup_vmc.exe launcher.
Appendix C: Using Transforms for Customisation The installation process should now use the modified MobileBroadbandProfile.xml and 23415.xml files.
Further Information Further Information The Vodafone support website contains software and documentation for all Vodafone data products. • Vodafone Mobile Broadband application downloads • VPN documentation • FAQs • How-to documents • Etc… http://support.vodafone.com © Vodafone Group 2011. Vodafone, the Vodafone logos and Vodafone Mobile Broadband are trade marks of the Vodafone Group. Other product and company names mentioned herein may be the trade marks of their respective owners.
