Vzaccess Manager Administrator‟S Guide Version 7.4.1.0
Total Page:16
File Type:pdf, Size:1020Kb
VZAccess Manager Administrator‟s Guide Version 7.4.1.0 Overview VZAccess Manager has been enhanced to meet the needs of the enterprise. It is easy to deploy, configure and lock down. The administrator has the ability to create an XML configuration file (Network.xml) that is used during installation to configure the client to the needs of a particular corporation. Installation Options The VZAccess Manager installer is available as an executable as well as an MSI file. The following two sections discuss each format and the available options, switches and behaviors. MSI Installations Windows Installer files (*.msi) are loaded and processed by a Microsoft executable, msiexec.exe (live help with all of the standard switches is available by executing msiexec /?). To install an msi file (ex. VZAccess.msi) one can execute either from a command interpreter or the “run” dialog from the Start menu: msiexec /i “VZAccess.msi” To uninstall the same product: msiexec /x “VZAccess.msi” Additional switches (ex. /qn) can be added to the command line, as well as parameters to the installation (ex. DESKTOPICON=1). msiexec /qn /i “VZAccess.msi” DESKTOPICON=1 Install & Uninstall The /i switch is used to install a file. It should be followed by the file name/path. If the path or name contains spaces, it should be enclosed in quotes. By default VZAccess will be installed to C:\Program Files\Verizon Wireless\VZAccess Manager (drive letter may very depending on your system). The /x switch uninstalls a previously installed file. Its syntax is the same as the install switch. Silent Install/Uninstall A completely silent install or uninstall is enabled by the /qn switch. This should show NO user interface whatsoever. The UI can be displayed at varying levels from none (/qn) up to full (/qf) by providing /q followed by varying letters/symbols. See the live help for a list of all the options. Windows Vista: Version 7.4.1 1 Windows Vista will typically prompt you to elevate a process needing administrative privileges, however, in the case of a completely silent install (/qn) Vista will not prompt you, and the installation will silently fail. Here are a few different workarounds: 1. Open an elevated cmd shell. Locate a shortcut to cmd.exe in the start menu, right click and select “Run As Administrator...” The resulting cmd window should have “Administrator: ...” at the title bar. 2. The default, built-in Administrator user (which must be enabled first) will run the installation elevated by default. 3. Research how to use the runas command from a cmd shell (try runas /?) 4. Disable UAC/LUA. Another entirely different approach would be to install with a non-interactive command-line option instead of completely silently. For example: msiexec /i VZAccess-Enterprise.msi /qb- This will install quietly, without any wizard dialogs, just a progress bar, but you will be prompted to elevate instead of failing the install. All Users/Current User The installation can be installed for all the users on the system, or it can be installed for only the current user. To dictate this at the command line (i.e. in a silent install) you can use the ALLUSERS parameter. This can be assigned three different values, ””, 1, or 2. Of interest are ”” and 2. By default an installation from the command line will install for all users. Also note that to install for all users, the current user must have appropriate privileges, e.g. Administrative privileges. ALLUSERS=”” Install for the current user only – empty quotes ALLUSERS=2 Install for all users Install a Desktop Shortcut/Icon The installation can optionally install a shortcut on the desktop. By default the icon is not installed. To indicate that it should from the command line, use the DESKTOPICON parameter. DESKTOPICON=1 Launch VZAccess after installation The installation can launch VZAccess after the installation. By default this does not happen. To enable it use the LAUNCHPROGRAM parameter: LAUNCHPROGRAM=1 Remove User Data VZAccess generates user data that can persist on the machine if the installation is removed, and is restored if it is reinstalled. This includes WEP keys and usage logs. By default this information is left intact (as advised in the Microsoft “Designed for XP” logo program). To force the removal of this information from a command-line uninstallation use the REMOVE_ALL_USER_DATA parameter. REMOVE_ALL_USER_DATA=1 Version 7.4.1 2 Examples A silent install with all of the non-default options would look like (all on one line): msiexec /qn /i “P:\path\VZAccess.msi” DESKTOPICON=1 LAUNCHPROGRAM=1 A silent uninstall to remove all user data would appear as: msiexec /qn /x “P:\path\VZAccess.msi” REMOVE_ALL_USER_DATA=1 EXE Installations The executable installer is essentially an MSI file with an InstallShield setup launcher. A silent installation can be performed by executing the installer application with the /S /v/qn parameter. For example, if the installation application is on a shared network drive mapped to drive „M‟, the administrator can select Run from the Start menu and type: “M:\VZAccess Manager.exe /S /v/qn” Running the installation application (VZAccess Manager.exe) with the „/v‟ parameter instructs the setup executable to pass any following switches (after „/v‟) to the MSI (i.e. “/qn” above). Similarly, to uninstall VZAccess Manager from a computer without user interaction, the administrator can execute: “M:\VZAccess Manager.exe /x /v/qn” Note that all installation switches used for the MSI can also be used for the exe as long as the „/v‟ parameter is used. If we need to pass more than one switch to the MSI, enclose anything after „/v‟ with double quotes. Examples A silent install with all of the non-default options would look like (all on one line): M:\VZAccess Manager.exe /S /v”/qn DESKTOPICON=1 LAUNCHPROGRAM=1” A silent uninstall to remove all user data would appear as: M:\VZAccess Manager.exe /x /v”/qn REMOVE_ALL_USER_DATA=1” Configuration Tool VZAccess Configuration Tool is available for administrators to create the VZAccess Manager configuration file as desired. This is a small application that runs on Windows 2000, XP or Vista. More advanced users can choose to manually create the configuration file as described below. This configuration tool can be downloaded from the VZAccess Manager Enterprise download site. Version 7.4.1 3 Configuration File To customize VZAccess Manager for enterprise needs, an administrator must configure and distribute a network.xml file with the installation file. Any custom network.xml file should be placed in the System subfolder where VZAccess Manager was installed in order for the desired settings to take effect. The administrator can edit the Network.xml file with any standard text editor such as notepad and insert options as described below in the Network.xml File Details section. An xml parser can help the administrator catch simple problems – for example many web browsers, like Internet Explorer 5.0 and higher, support xml files to some degree and can display the xml content and/or display an error if one exists. Opening the network.xml file with IE can provide the administrator with feedback on the validity of the XML syntax changes, and hints to fixing any syntax problems that may have been introduced. Network.xml File Details For every special behavior the administrator wishes in VZAccess, an entry must be made in the network.xml file. These entries should be xml elements of the names provided below in Table 1 and containing the corresponding data indicating whether the setting is to be applied or not. Each of these elements should be contained within a single EnterpriseOptions element, which will be contained within the qlconfig element (which is topmost and singular). The EnterpriseOptions element must be placed before the networklist element, but may come before or after any of the other elements. Settings not included in the network.xml file will take on the default behavior/value as described in Table 1. An example is provided below in the excerpt from a network.xml file. This example allows the user to view all of the features of VZAccess Manager including the Preferences dialog, but would not be able to change any of the preferences. The user would also not be able to close the application, but would be allowed to minimize it. <?xml version="1.0" encoding="utf-8" ?> - <qlconfig> <csdconnectwarning>ATTENTION Dial Up connections may be charged differently than NationalAccess sessions. Please check your Calling Plan for details.</csdconnectwarning> - <EnterpriseOptions> <DisablePrefs>TRUE</DisablePrefs> <DisableMinimize>FALSE</DisableMinimize> <DisableExit>TRUE</DisableExit> <DisableMove>TRUE</DisableMove> <WindowX>50</WindowX> <WindowY>30</WindowY> </EnterpriseOptions> … </qlconfig> Version 7.4.1 4 Administrator Options These settings can be set by the administrator to hide or disable certain product functionality. These options are read from the Network.xml file every time the application is started so any changes made in this file after deploying the client will be read by the application. - <EnterpriseOptions> <DisablePrefs>TRUE</DisablePrefs> <DisableMinimize>FALSE</DisableMinimize> <DisableExit>TRUE</DisableExit> <DisableMove>TRUE</DisableMove> </EnterpriseOptions> The settings in this table are case sensitive. Setting Default Possible Note Values AdminConfigVersion None Any An administrator can assign a numeric version to their settings. This string is displayed in the About box. If the network.xml file has a version greater than the stored version, then the application will automatically re-detect the device in order to apply changes in the file. Version 7.4.1 5 RequirePrefsCmdLine FALSE TRUE | Setting this will prevent FALSE Default Preferences from being overwritten by those that a user may have set from using the application. By default, VZAccess Manager will restore the Default Preferences in the Network.xml file to the application each time it is run.