/build/static/layout/Breadcrumb_cap_w.png

Microsoft Office Communicator

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 5.9k  |  Created: 06/08/2006

Average Rating: 0
Office Communicator has 6 inventory records, 2 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 2 ratings
Most Commonly Reported Deployment Method
Windows Installer with Custom Transform (MST)
123
Note
We have Public IM enabled and to avoid having to purchase yet another SSL certificate (to enable automatic configuration publicly) choose to use "Manual Configuration" to point to our public IM DNS name.

Here's the registry patch we run via the logon script to update everyone's Communicator client:

logon script contains:
regedit /s FixCommunicator.reg

FixCommunicator.reg contains:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Communicator]
"ConfigurationMode"=dword:00000001
"TourPlayed"=dword:00000001
"ServerAddress"="companyLCS.ourcompany.com"
"Transport"=dword:00000004
"PersonalContactStore"=dword:00000001
"AutoRunWhenLogonToWindows"=dword:00000001
"AutoOpenMainWindowWhenStartup"=dword:00000001
"AutoRetrieveOOFSettings"=dword:00000001
"PublishCalendarPresence"=dword:00000001



Explanation of values:
[HKEY_CURRENT_USER\Software\Microsoft\Communicator] (only applies to logged on user)

"ConfigurationMode"=dword:00000001 (This is the radio button that enables the selection of "Configure Settings" vs. "Automatic Configuration" - set to 1 for "Configure Settings")

"TourPlayed"=dword:00000001 (Set this to 1 to avoid the annoying web browser demonstration that pops up on first run of the program)

"ServerAddress"="companyLCS.ourcompany.com" (This would be the servername or IP address of the LCS server, note: If using TLS, the ServerAddress MUST be a DNS name because it uses SSL certs)

"Transport"=dword:00000004 ("Connect using:" TLS is 4, TCP is 1)

"PersonalContactStore"=dword:00000001 ("Select your personal information manager" setting: 0 is "Microsoft Office Outlook", 1 is "Windows Address Book(Contacts)", 2 is "None")

"AutoRunWhenLogonToWindows"=dword:00000001 (Sets the Communicator to startup on logon)

"AutoOpenMainWindowWhenStartup"=dword:00000001 (Will launch the main communicator window when the user logs in)

"AutoRetrieveOOFSettings"=dword:00000001 (Shows status of contacts(i.e., away, online, offline, etc.))

"PublishCalendarPresence"=dword:00000001 (Shows information from Calendar (e.g., "Free until 1PM") in a contact's "Properties" view)

Also, here's the expanded version of the .vbs script that can be used to setup a new user for login to Communicator:
http://www.lcs-guides.com/scripts-ms-commuicator-2005-auto-sign

Hope this helps.

Shannon VanWagner
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

122
Note
Entries I put in my .MST

HKEY_CURRENT_USER\Software\Microsoft\Communicator
TourPlayed:1
ServerAddress:<servername>
FirstTimeUser:0
ConfigurationMode:1

I also used aand modified a VB script to populate current user information, it must either run at every logon or once per user (with something like ActiveSetup). See below.
http://www.appdeploy.com/messageboards/tm.asp?m=22865

Hope this helps some people!!
joeman113@gmail.com
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • elgwhoppo
  • 09/28/2007  
  • Show Comments   ( 0 )

122
Command Line

msiexec.exe /i Communicator.msi TRANSFORMS=customizations.mst /qb!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • elgwhoppo
  • 09/28/2007  
  • Show Comments   ( 0 )

Inventory Records (6)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Office Communicator

Version

1.0.559.226

Uninstall String

MsiExec.exe /X{BE5AD430-9E0C-4243-AB3F-593835869855}

Questions & Answers (2)

Questions & Answers related to Microsoft Office Communicator

19
ANSWERS
Upgrading Communicator 2007 R2 MSI with Jan 2010 Hotfix MSP
By: timread 14 years ago 13.1k views
5
ANSWERS
Repackaging MS Office Communicator 2005
By: cmi2000 15 years ago 5.5k views

Blogs (0)

Blog posts related to Microsoft Office Communicator

Reviews (0)

Reviews related to Microsoft Office Communicator

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ