IT-Managed Installation
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Office Communicator 2007 can be deployed in a managed-desktop environment using the following methods:
Microsoft® Systems Management Server 2003 (SMS) or Microsoft® System Center Configuration Manager 2007 (Beta 2). 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 Microsoft Systems Management Server Web site.
Active Directory Group Policy. You can create a Group Policy object to deploy Communicator 2007 to specific users or computers based on group memberships. For more information about using Group Policy, see the Windows Server 2003 R2 Web site.
Windows logon scripts. The logon script performs an unattended installation of Communicator 2007 when a user logs on. Group policy objects can be used to target logon scripts to specific devices or users.
Installing on Machines with Multiple Users
After Communicator 2007 is installed on an individual computer, it is available to all users of that computer. Configuration settings for each user are stored in the HKEY_CURRENT_USER registry hive. Communicator 2007 cannot be installed on a per-user basis on an individual computer.
Windows Installer Command Line Options
Quiet-Mode Installation
When deploying Communicator 2007, you can suppress the installation user interface by using the Windows Installer command-line option /qn in your script, as follows:
msiexec /qn /i Communicator.msi
Note
The file Communicator.msi is used as an example only. The actual name of the Communicator 2007 .msi file that you deploy may be different.
Windows Installer command line options are not case sensitive. For more information, see Windows Installer documentation on the Microsoft Developer Network (MSDN) Web site.
Generating a Log File
You can generate a log file during Communicator 2007 setup by adding /l*v followed by a file name to the Windows Installer command line. For example:
msiexec /qn /i Communicator.msi /l*v logfile.txt
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 more information, see Command-Line Options on the Microsoft Developer Network (MSDN) Web site.
Event trace log (ETL) files, which may also be generated on your computer in the <username>/Tracing folder, enable administrators and Microsoft support technicians to troubleshoot problems. For more information, contact your Microsoft support representative.