IT-Managed Installation of Lync 2010 Attendant
Topic Last Modified: 2012-10-14
Depending on the complexity of the installation scenario, there are several options for installing Microsoft Lync 2010 Attendant.
Microsoft Systems Management Server (SMS) 2003 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 details, see the System Center TechNet Library at http://go.microsoft.com/fwlink/p/?Linkid=140326.
Active Directory Domain Services (AD DS) Group Policy. You can create a Group Policy object to deploy Lync 2010 Attendant to specific users or computers based on group memberships. For details about how to use Group Policy, see the Windows Server Group Policy TechNet Library at http://go.microsoft.com/fwlink/p/?linkid=141034.
Windows logon script. The logon script performs an unattended installation of Lync 2010 Attendant when a user logs on. You can use Group Policy objects to direct logon scripts to specific devices or users.
Additionally, if you are deploying Lync 2010 Attendant on computers that are running Windows Vista operating systems and you want to use the logging capability to debug issues, the users must be part of the performance log users group. Lync 2010 Attendant does not add the computer user account automatically to the performance log users group. You must manually add the computer user account to this group.
Windows Installer Command-Line Parameters
During deployment, you can use Windows Installer command-line parameters to suppress the installation user interface and generate a log file.
Suppressing the Installation User Interface
When you deploy Lync 2010 Attendant, you can suppress the installation user interface by using the Windows Installer command-line parameter /qn in your script, as follows:
msiexec /qn /i attendantconsole.msi
Windows Installer command-line parameters are not case-sensitive. For details, see “Command-Line Options” in the Microsoft Developer Network (MSDN) Library at http://go.microsoft.com/fwlink/p/?linkid=143014.
Generating a Log File
You can generate a log file during Lync 2010 Attendant set up by adding /l*v followed by a file name to the Windows Installer command line. 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.
The Lync 2010 Attendant setup file, attendantconsole.msi, generates the log file %TEMP%\Install.log, and an uninstall generates the file %TEMP%\Uninstall.log.
msiexec /qn /i Attendantconsole.msi
In addition to /l*v , 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 “Normal Logging (Windows)” in the MSDN Library at http://go.microsoft.com/fwlink/p/?linkid=141036.
Event trace log (ETL) files, which can be generated on your computer in the <username>/Tracing folder, enable administrators and Microsoft support technicians to troubleshoot issues. ETL files are not created by default. To generate ETL files, enable the Turn on Logging in Attendant option in the Options dialog box. This logging option is off by default.
The log file for Lync 2010 Attendant is overwritten every time Lync 2010 Attendant is started.
You can uninstall Microsoft Office Communications Server 2007 R2 Attendant by including the following command line in your script:
msiexec /x attendantconsole.msi