Installation of clients, support for Windows 2000/2003

Client part of Faxchange
Support for Windows 200x
UMS Remote Installer

Client part of Faxchange

Faxchange client consists of Outlook forms for working with faxes (+components necessary for their running), eventually of fax printer.
Client installation is different according to the operating system used by your users.

Windows 9x/Me/NT4.0 - even common user of these systems has sufficient rights for software installation, so there is no need to install any client components after the FaxChange server has been installed. All necessary files and forms will be installed automatically when user sends or receives the first fax. If client fax printer was not installed during first automatic client setup, it can be installed later using shortcut "Install FaxChange Client Printer" in Start menu or by setup program from installation CD or from shared folder fxloader. More details are here.
After finishing installation restart computer. After restart, you can see FaxChange Client Printer icon on taskbar.
Windows 200x/XP/Terminal server - common user has very limited rights, so you must use one of options described in next paragraphs.

Support for Windows 200x

Windows 2000/XP and later (include terminal servers) introduces the brand new security model. "Common user" can't write everywhere in registry and filesystem he/she want, but can write only to his/her profile directory and into HKEY_CURRENT_USER registry key. This is great but many of standard applications can't run on system configured with that big security under account other than administrator.

One of basic FaxChange features is that all clients components are installed automatically and without administrator's work. Forms, COM objects, FaxChange client printer... all of this are installed when user needs it. But unfortunatelly, this feature won't work on unpatched Windows 2000/XP and higher (include terminal servers).

UMS instalation CD contains tool, that sets access rights to some registry keys and directories, so FaxChange automatic client installation can run. You can find it in directory \support\Win2000_support\. There is a script _fx.cmd for FaxChange users. This script should be run (for example via MS SMS server) under administrator's NT account on every Windows 2000/XP computer (eventually terminal server), where Faxchange client should run.

Script fx.cmd had to be modified before running; enter name of your FaxChange server to line
FXSERVER=
at the beginning of script.

If you use this script, you will lower your system's security! Therefore use rather remote installation with Remote Installer tool, see next paragraph.

Users of Windows 2000 and higher can use only shared client printer (mapped from FaxChange server), even after running that scripts. If you want to install local client printer, you have to add permission to install printer to users in Domain Security Policy tool.

Base program of those scripts is umsetacl.exe. Its documentation can be found in the same directory.

What is it?

UMS Remote Installer is a tool for remote unattended UMS components installation on client computers. For correct installation of any client component are necessary administrative privileges (for component registration and registry writing). Common users of Windows 2000 and newer systems don't have such privileges, so installation must be done by administrator.

This tool was developed to avoid necessity of coming round all client computers or buying expensive SW for remote installation (e.g. System Management Server from Microsoft). It allows to perfom installation from central point.

First of all you install client side, what is service running on client PC. Then administrator can create requests for package installation using UMS Remote Install Manager tool (located in Start menu). When installation request is created, client service is notified by Install Manager and service downloads the package, installs it and result of installation is sent back to the Install Manager. Client side is also installed using Install Manager, so administrator does all the work centrally.

Intranet interface is also available to save administrator's work, using which even common users can create installation requests (include client part installation). But unlike administrator, common users can make requests only for components installation on their own computers.

Installation and configuration

Installer of Remote Install Manager can be found in \support\UMSRmtInst folder of installation CD, run setup.exe program here.

Setup does these steps:

checks if Microsoft .NET framework 1.1 is installed - if not, it is installed
asks for folder, where UMS Remote Installer will be installed to
asks for account, under which installation service will be run on client PC. It MUST be domain account in form domain\account, which MUST be member of "Domain Admins" group - otherwise it will not have sufficient privileges to install packages. Additionally this account requires "Logon As a Service" system right on client computers.

Then UMS Remote Installer is installed, necessary folders and shares used by client services are created and packages for installation of all UMS client parts are prepared. So administrator must only to install client service and can create requests for package installation.
ATTENTION when using clients with firewall installed (e.g. Windows XP SP2) - firewall inhibits to receive notifications about new packages, so packages are installed till automatic check occurs (once per hour). For immediate installation you must allow incoming connection on port 24680 on the clients.

Installation of intranet interface can be done by this way:

copy content of support\UMSRmtInst\WebService folder from installation CD to disk on server, e.g into C:\rmtinst.
make this folder accessible through WWW using Internet Services Manager (create virtual directory)
create an application, see picture

Next you must set correct permissions for correct working:

for ASPNET account, if UMS Remote Installer is installed on Windows 2000 server, which is not DC
for IIS_WPG group, if UMS Remote Installer is installed on Windows 2000, which is DC or on any Windows 2003 server

in this way:

on share RmtInst assign Change a Read rights; on requests subfolder of this share assign these NTFS rights: Modify, Read & Execute, List Folder Contents, Read, Write.
on registry key HKLM/Software/Datasys/UMS/Remote Install assign Read and Full Control rights.

Intranet interface parameters can be changed on http://server/RmtInst/Configure.aspx web page, which stores parameters into HKLM/Software/Datasys/UMS/Remote Install registry key.

Registry item name Config page item name Description

InstallServiceDomain Doména Domain of account for client service installation.

InstallServicePassword Současné heslo Encrypted password for client service installation - not displayed. When changed, it is entered twice for verification. If any configuration item is changed, you must enter this password - it is security action to prevent common users from configuration changing. Better way is to secure this page by Windows authentication + NTFS permissions only for administrator.

InstallServiceUserName Uživatelské jméno Account for client service installation.

ListeningPort Port pro naslouchání Port where client service listens to (24680).

PackagesPath Umístění balíčků Network path to installation packages.

RequestsPath Umístění požadavků Network path to installation requests.

ServiceAccountName Účet pro spuštění Account for client service run (domain\name).

ServiceAccountPassword Nové heslo Encrypted password for client service run; when changed, it is entered twice for verification.

ServicePath Cesta k souboru Network path to client service file prepared for distribution.

Registry item name	Config page item name	Description
InstallServiceDomain	Doména	Domain of account for client service installation.
InstallServicePassword	Současné heslo	Encrypted password for client service installation - not displayed. When changed, it is entered twice for verification. If any configuration item is changed, you must enter this password - it is security action to prevent common users from configuration changing. Better way is to secure this page by Windows authentication + NTFS permissions only for administrator.
InstallServiceUserName	Uživatelské jméno	Account for client service installation.
ListeningPort	Port pro naslouchání	Port where client service listens to (24680).
PackagesPath	Umístění balíčků	Network path to installation packages.
RequestsPath	Umístění požadavků	Network path to installation requests.
ServiceAccountName	Účet pro spuštění	Account for client service run (domain\name).
ServiceAccountPassword	Nové heslo	Encrypted password for client service run; when changed, it is entered twice for verification.
ServicePath	Cesta k souboru	Network path to client service file prepared for distribution.

Usage

Brief documentation can be found also in \support\UMSRmtInst\Doc folder of installation CD.

Creating requests by administrator
UMS Remote Install Manager window contains three tabs:

Computers - you can create lists of computers here. Using "New domain list" button you create list of all PCs in domain - enter list name and NetBIOS domain name, program reads list of PCs from domain controller and saves it. You can also create your own lists of computers - check PCs in existing domain list which you want to insert into own list and press "New list" to create a new list. If you want to change list members, set checkboxes according your needs and press "Update list".
ATTENTION - do not be confused that you see in Computers listbox always the same PCs. PC membership in list is given by checkbox before PC name, not by content of Computers listbox. All functions of program work with PCs being checked.
You can also create requests for package instalation - select one or more PCs and after pressing "New request" list of available packages is displayed. Select which one you want to install and set parameters. Request is displayed in Requests listbox for selected PC; when you click to request, details and log about processing are showed.
Also lists of packages are supported together with individual packages. List is file with .list extension located in the same folder as normal packages. Every line of this file describes installation of one package in this syntax:
"Package name.exe" "package parameters" "installation service parameters".
Quotations can be left out, if given item doesn't contain spaces.
Request for installation of package list named Default.list (if such list exists) is automatically added to request list during installer service installation on target computers. Administrator can save some work with requests definition in this way - simply creates list of necessary packages and then only installs installer service.
Requests - here is displayed list of requests. When you click to request, a list of PCs where request was sent is displayed. When you click to PC, request details and log are displayed.
Client Service - installation of installer service to client PC is done here. Select one or more PCs and press "Install service" button. A window appears, where you can change service parameters (destination path, service account and password). After confirmation service is installed. Status and result of installation can be discovered by clicking on PC name.
By "Uninstall service" button you can uninstall service from the client PC.

Creating requests by comon user
User starts web browser and enters address in form http://server/RmtInst/NewRequest.aspx?InstallClientService=true&PackageName=package, where:
server = server name, where intranet interface for Remote Installer is installed
RmtInst = virtual directory of intranet application, you can get it from administrator
InstallClientService = install client installation service? (true=yes/false=no). If this expression is missing, false is used (client service is necessary to install only during first use)
PackageName = name of package to be installed, INCLUDE extension (e.g. DsSetup.exe). Must be always stated.
PackageArguments = possible parameters for installed package.

List of packages for Faxchange 6.x

List of packages necessary for FaxChange client installation:

dssetup.exe - setup engine. All other packages use this engine for their setup, so it must be installed first.
oft.exe - Outlook forms for working with faxes (for Outlook client).
fxprinter.exe - client fax printer (you can define client type - Outlook, Notes, other).
frmfullp.exe - contains oft.exe, fxprinter.exe (for Outlook client).
OutlookSO.exe - Send options for Outlook XP and higher