User Guide
64 Configuring Contribute and Contribute Publishing Server to work with your website
To deploy Contribute by using SMS, you must first create a package and add an optional
advertisement, which then initiates the deployment process. The package is automatically sent to
all the client computers in the organization. The SMS client on each client computer receives the
package and then runs it to install the Contribute application. The installation process does not
require any user intervention.
To deploy Contribute using SMS, do the following:
1.
Uninstall previous versions of Contribute.
2.
Set up the server.
3.
Create the SMS package.
4.
Create an advertisement.
Uninstalling previous versions
It is recommended that you first uninstall any existing versions of Contribute. You can uninstall
Contribute by using either the Add/Remove Programs feature in the Windows Control Panel or a
separate SMS package.
Note: If the uninstall process prompts you to restart the computer, do so.
Setting up the server
SMS 2003 offers greater control and flexibility than previous versions. With SMS 2003, you can
force a package to run by using a specified account with administrative rights on the target
computer. This lets you distribute the package to client computers who are not logged into the
network or to a user who does not have administrator rights.
To specify an administrative account for SMS to use:
1.
From the Windows Start menu, select Start > Programs > Systems Management Server, and
then double-click SMS Administrator Console.
The Microsoft Management Console (MMC) appears.
2.
In the left pane of the MMC, expand Site Database Tree, and then expand the Site Hierarchy
node.
3.
Select the site by right-clicking the site, and then select Properties.
The Properties dialog box appears.
4.
On the Accounts tab in the Properties dialog box, click the Set button next to SMS Client
Remote Installation Account.
Also specify the account to use to perform the software installation. The account must have
domain Administrator rights as well as local Administrator rights on the workstations. The
Remote Client Installation component primarily uses the account, but software distribution
also uses the account to run packages on computers that are not logged into the network.