Depending on the complexity of the installation scenario, there are several options for installing Communications Server 2007 R2 Attendant.

Microsoft Systems Management Server 2003 (SMS) or Microsoft System Center Configuration Manager 2007.Use these products for more complex software installation scenarios, where scheduling, inventory, reporting, status, and support for an installation across a wide-area network (WAN) are required. For more information, see the Systems Management Server TechCenter at http://go.microsoft.com/fwlink/?Linkid=140326 .
Active Directory Group Policy.You can create a Group Policy object to deploy Communicator 2007 R2 to specific users or computers based on group memberships. For more information about how to use Group Policy, see the Windows Server page at http://go.microsoft.com/fwlink/?linkid=141034 .
Windows logon scripts.The logon script performs an unattended installation of Communicator 2007 R2 when a user logs on. Group policy objects can be used to target logon scripts to specific devices or users.

Additionally, if you are deploying Communications Server 2007 R2 Attendant on computers that are running Windows Vista, and you want to use Communications Server Attendants logging capability to debug issues, the user must be part of the Performance Log Users (PLU) group. Communications Server 2007 R2 Attendant does not add the computer user account automatically to the PLU group. You have to manually add the computer user account to this group.

Windows Installer Command-Line Options

During deployment, you can use Windows Installer command line options to suppress the installation user interface and generate a log file.

Quiet-Mode Installation

When you deploy Communications Server 2007 R2 Attendant, you can suppress the installation user interface by using the Windows Installer command-line option /qn in your script, as follows:

	Copy Code
msiexec /qn /i attendantconsole.msi

Windows Installer command-line options are not case-sensitive. For more information, see Command-Line Options at http://go.microsoft.com/fwlink/?linkid=143014 on the Microsoft Developer Network (MSDN) site.

Generating a Log File

You can generate a log file during Communications Server 2007 R2 Attendant setup by adding /l*v followed by a file name to the Windows Installer command line.

The Communications Server 2007 R2 Attendant setup, attendantconsole.msi, generates the following log file: %TEMP%\Install.log, and an uninstall generates %TEMP%\Uninstall.log.

For example:

	Copy Code
msiexec /qn /i Attendantconsole.msi

The asterisk specifies that all possible errors, warnings, and status messages are written to the log file, and the v specifies that all messages are verbose.

Other log file flags are possible. For example, /lem generates a log file that contains only errors and out-of-memory or fatal exit information. For a complete list of log file options, see the Normal Logging (Windows) topic on the MSDN Web site at http://go.microsoft.com/fwlink/?linkid=141036 .

Event trace log (ETL) files, which can also be generated on your computer in the < username>/Tracing folder, enable administrators and Microsoft support technicians to troubleshoot problems. ETL files are not created by default. To generate ETL files, enable the Turn on Logging in Attendantoption in the Optionsdialog box. This logging option is OFF by default.

The log file for Communications Server 2007 R2 Attendant is overwritten every time that Communications Server 2007 R2 Attendant is started.

For more information, contact Microsoft Customer Service and Support.

Using a Script to Uninstall Communications Server 2007 R2 Attendant

You can uninstall Communications Server 2007 R2 Attendant as part of another task. Include the following command line in your script:

	Copy Code
msiexec /x attendantconsole.msi