You need to install Your Assistant client to test and verify the implementation of the Your Assistant server. Each client PC must have the .Net Framework and the MDAC installed before installing Your Assistant.
The Your Assistant client installer ships as a Windows Installer package. There is one property that must be set when installing: the IP of the Your Assistant server. Depending on how Your Assistant is installed will dictate how this property is set. See To install Your Assistant client on page 43 or Transforms on page 42 for each install method and how to set this property.
Downloading Your Assistant
Your Assistant can be downloaded from the Your Assistant product portal on Mitel Online.
The zipped file you download contains the following items:
• The Client Installer (Mitel Your Assistant 3.0.msi)
• The Server Installer (YourAssistantServer.exe)
• The FCI (Field Change Instructions)
• The Administrator Guide
• The User Guide
Microsoft .NET Framework Version 1.1
Your Assistant requires the Microsoft .Net Framework.
To obtain the .NET Framework:
• Download the .NET Framework from
http://www.microsoft.com/downloads/details.aspx?familyid=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en.
Microsoft Data Access Components (MDAC) 2.7
Your Assistant requires the Microsoft Data Access Components.
To obtain the MDAC
• Download the MDAC 2.7 from
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=B41304CA-874F-421D-8820-182F179779A4.
Upgrading Your Assistant
Your Assistant will safely upgrade previous versions. Simply install Your Assistant. All client call logs, personal contacts and settings will be migrated to the upgraded version. Favourites are also retained except when upgrading from Your Assistant 2.x.
Transforms
Windows Installer packages can be customized with installer transforms, a file that when run with the installer package modifies certain installation properties and application features. The Your Assistant installer package requires that Your Assistant server IP property be set at install time. If the installer package is executed without any command-line parameters setting this property, the installer package prompts the user for it. Alternatively, a transform can be created that will set this property. The transform can be specified in the command string used to install Your Assistant or can be specified when installing software using an Active Directory Group Policy.
Creating a transform
There exist third-party tools that will create transforms. These tools are usually bundled with MSI authoring tools. However, the transform is simple and can be created with tools bundled with the Microsoft Installer SDK. Three scripts bundled with the SDK will do everything needed to create a transform: WiRunSQL.vbs, WiGenXfm.vbs and WiSumInf.vbs. The procedure is to make a copy of the base client installer and modify the copy with the WiRunSQL.vbs script, then create a transform from the differences between the two files. Finally, the summary information stream of the transform is updated. The syntax for updating the copy is:
%>cscript WiRunSQL.vbs ModYourAssistant.msi "INSERT INTO `Property`
(`Property`.`Property`,`Property`.`Value`) VALUES ('YOUR_ASSISTANT_SERVER_IP','192.168.1.55')"
where ModYourAssistant.msi is the copy and 192.168.1.55 is the IP of the YA Server to create the transform for. ModYourAssistant.msi is now modified such that it contains the IP property for the YA Server.
Next, to generate the transform use the WiGenXfm.vbs script as follows:
%>cscript WiGenXfm.vbs YourAssistant.msi ModYourAssistant.msi transform.mst where YourAssistant.msi is the original, ModYourAssistant.msi is the modified copy and transform.mst is the transform file containing the YA Server property set to 192.168.1.55.
The last step is to update the transform summary information stream with the minimum version of the Windows Installer service required. This is done with the WiSumInf.vbs by invoking it as:
%>cscript WiSumInf.vbs transform.mst Pages=200
These steps can be encapsulated in the following DOS batch file passing the base installer and IP as arguments:
set basefile=%1 set modfile=temp.msi
set property=YOUR_ASSISTANT_SERVER_IP
set sql="INSERT INTO `Property` (`Property`.`Property`, `Property`.`Value`) VALUES ('%property%', '%2')"
copy %1 %modfile%
cscript WiRunSQL.vbs %modfile% %sql%
cscript WiGenXfm.vbs %basefile% %modfile% transform.mst cscript WiSumInf.vbs transform.mst Pages=200
del %modfile%
The transform transform.mst is now ready for deployment with the base installer.
To install Your Assistant client
Note:The Your Assistant installer (Mitel Your Assistant 3.0.msi) requires elevated privileges to install Your Assistant correctly. For this reason, the installer must be run from an
administrative account when using the software distribution point and the logon script deployment methods.
Software Distribution Point
Installing Your Assistant using a distribution point is done with an administrative install of the installer package to a network share. The share point must accessible to all users that will install Your Assistant. The command for the administrative installation is:
%>msiexec /a “Mitel Your Assistant 3.0.msi”
The administrative install wizard will prompt for a folder to put the administrative image. Users can be instructed to install Your Assistant from this folder via the network share. The users can run the installation wizard by clicking the file and entering the Your Assistant server IP when prompted. Alternatively, an explorer shortcut could be provided that included the IP property in the command parameters or a transform file (see Error! Reference source not found.).
%>msiexec /i “Mitel Your Assistant 3.0.msi” YOUR_ASSISTANT_SERVER_IP=”192.168.1.66”
Where YOUR_ASSISTANT_SERVER_IP property set to the IP of the Your Assistant server.
Suppressing the installation wizard dialogs can further customize the installation by using the /qn flag. More customization options can be found in the Windows Installer SDK documentation here
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/command_line_options.asp). If installing for all users that may logon to the target computer, add the argument ALLUSERS=”1” to the command. If this argument is not added, the installer will only install for the currently logged in user.
IntelliMirror
There are two policies that must be addressed when deploying Your Assistant for IntelliMirror
• User Data Management; and
• Software Installation and Maintenance.
Your Assistant persists user settings such as window settings, call logs, history, personal contacts, and favourites. This data is saved in the users Local Settings folder. With IntelliMirror, this data will follow the user to whatever computer is used in the domain.
For deployment, Your Assistant should be assigned to users such that when a Your Assistant user logs into a PC that does not have Your Assistant installed, Your Assistant gets installed.
The Your Assistant IP property should be set using an installer transform (see Error! Reference source not found. on page Error! Bookmark not defined.).
For more information see Step-by-Step Guide to Software Installation and Maintenance.
Logon Script
A logon scripts uses the same installation techniques as the software distribution point except the mechanism used to run the installer is a script rather than an Explorer shortcut. The logon script is set through a Active Directory Group Policy. An example of a logon script that will install Your Assistant might be
oShell = CreateObject(“Wscript.Shell”)
oShell.Run “msiexec /i /q “Mitel Your Assistant 3.0.msi”
See the Windows Script Host (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/wsoriwindowsscripthost.asp) site for more information on scripting.
SMS
Again, refer to the syntax shown for Software Distribution Point to create the installer command that SMS will run to install Your Assistant on the client computer. See Systems Management Server Home for more information on SMS.
Group Policy
For a network install, the installer can be assigned to users with a Group Policy object (GPO).
The GPO should install the software from an administrative image installed on a network share.
For a detailed explanation on how to install software using an Active Directory Group Policy, see Step-by-Step Guide to Software Installation and Maintenance.