RTCPOLICY_MESSENGER_RTC_CAT="SIP Microsoft Office Communicator Service Policies"
PolicyPreventRun="Prevent users from running Microsoft Office Communicator"
ExplainText_PreventRun="Prevents users from running Microsoft Office Communicator.\n\nIf you enable this policy setting, users cannot run Microsoft Office Communicator and therefore cannot send or receive requests for Remote Assistance.\n\nIf you disable or do not configure this policy setting, users can run Microsoft Office Communicator.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyDisableVideo="Prevent video calls"
ExplainText_DisableVideo="Prevents Microsoft Office Communicator from sending or receiving video calls.\n\n If you enable this policy setting, Microsoft Office Communicator cannot send or receive video calls. It will instead attempt to send or receive computer-to-computer audio calls.\n\n If you disable or do not configure this policy setting, Microsoft Office Communicator can send and receive video calls.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyDisablePC2PCAudio="Prevent Computer to Computer Audio Calls"
ExplainText_DisablePC2PCAudio="Prevents users of Microsoft Office Communicator from sending or receiving computer-to-computer audio calls.\n\nThis policy is disabled by default.\n\nIf you enable this policy setting, Microsoft Office Communicator cannot send or receive computer-to-computer audio calls. All entry points for making computer to computer calls from the Communicator user interface will be hidden or disabled.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator can send and receive computer-to-computer audio calls.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
ExplainText_EnableConferencingService="Enables users of Microsoft Office Communicator to initiate and participate in audio conferences using a third party audio conferencing service. In addition this policy enables users of Microsoft Office Communicator to initiate and participate in audio/video conferences via connecting to an MCU deployed internally within a company.\n\nThis policy is disabled by default.\n\nWhen this policy is disabled, users will not be able to start, join, or schedule a conference from Communicator. All entry points from the contact list and conversation window will be hidden from the user. In addition users will not be able to receive invitations to a conference via Communicator.\n\nWhen this policy is enabled, all entry points in Communicator will be enabled allowing users to schedule, join, participate in and conduct conferences."
PolicyEnablePC2Phone="Enable Computer to Phone Calls"
ExplainText_EnablePC2Phone="Enables users of Microsoft Office Communicator to make calls from their Computer to phone numbers.\n\nThis policy is disabled by default.\n\nWhen this policy is disabled, users will not be able to make a computer to phone call from Communicator. While in audio mode in the conversation window, all phone numbers listed in the click to call widget or from the action menu for roster entries will be disabled. In the contact list or in phone mode in a conversation window, it is important to note that users will be able to select phone numbers from the click to call widget or right click/action menu assuming that PolicyEnablePhoneControl is enabled. In the options dialog, the default device for calling on the phone tab is disabled.\n\nWhen this policy is enabled, all of the above mentioned entry points in the user interface are enabled, and the user will be able to make calls from their computer to a phone number."
PolicyDisableFileTransfer="Prevent file transfer"
ExplainText_DisableFileTransfer="Prevents Microsoft Office Communicator from transferring files.\n\nIf you enable this policy setting, Microsoft Office Communicator cannot transfer files.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator can transfer files.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyDisableSavingIM="Prevent users from saving instant messages"
ExplainText_DisableSavingIM="Prevents Microsoft Office Communicator from saving instant messages.\n\nIf you enable this policy setting, Communicator will be unable to save instant messages.\n\nIf you disable or do not configure this policy setting, Communicator will be able to save instant messages.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
ExplainText_DisableCollaborationApps="Prevents Microsoft Office Communicator from using its application sharing and whiteboard features.\n\nIf you enable this policy setting, Microsoft Office Communicator cannot use these features.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator can use these features.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
Explaintext_DisableNTCredentials="Requires the user to provide logon credentials for Microsoft Office Communicator rather than automatically using the Windows credentials when Microsoft Office Communicator authenticates the user using NTLM or Kerberos.\n\nIf you enable this policy setting, Microsoft Office Communicator requires the user to provide logon credentials.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator authenticates the user based on the logon credentials for Windows.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyMaxAVBW="Limit bandwidth for audio and video calls"
ExplainText_MaxAVBW="Limits bandwidth that Microsoft Office Communicator can use for audio and video calls.\n\nIf you enable this policy setting, you limit the bandwidth that Microsoft Office Communicator can use for audio and video calls.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator uses as much bandwidth as is available and necessary for audio and video calls."
MaxAVBW_VALUE="Maximum bandwidth"
PolicyPC2PCAVEncryption="Specify encryption for computer-to-computer audio and video calls"
ExplainText_PC2PCAVEncryption="Specifies whether encryption is supported, required, or no supported when Microsoft Office Communicator makes and receives audio and video calls.\n\nIf you disable this policy setting, do not configure this policy setting, or enable this policy setting and then click "Support Encryption (default)," Microsoft Office Communicator sends and receives audio and video data whether it is encrypted or not.\n\nIf you enable this policy setting and then click "Require Encryption," Microsoft Office Communicator sends and receives audio and video data only if it is encrypted. Microsoft Office Communicator rejects audio and video data that is not encrypted.\n\nIf you enable this policy setting and click "Don't Support Encryption," Microsoft Office Communicator sends and receives audio and video data only if it is not encrypted. Microsoft Office Communicator rejects encrypted audio and video data.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PC2PCAVEncryption_VALUE="How to handle encryption:"
ExplainText_EnableSIPHighSecurityMode="Enables Microsoft Office Communicator to send and receive instant messages securely when using the SIP Communications Service.\n\nIf you enable High Security, Microsoft Office Communicator requires the TLS transport. If the server authenticates users, it must use either NTLM or Kerberos authentication. Instant messages and Subscribes must pass through the SIP server, preventing outbound peer-to-peer communication.\n\nIf you enable Low Security, Microsoft Office Communicator can use any transport and any authentication method (including Basic or Digest). Instant messages can pass directly between clients, enabling outbound peer-to-peer communication.\n\nIf you enable Medium Security, all the High Security applies, except that TLS is not required.\n\nIf you do not configure this policy setting, Microsoft Office Communicator can use any transport, but if it does not use TLS and the server authenticates users, it must use either NTLM or Kerberos authentication. Instant messages must pass through the SIP server, preventing outbound peer-to-peer communication.\n\nNote: This policy does not affect Remote Assistance.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
ExplainText_EnableUPNP="Enables UPNP in Microsoft Office Communicator."
PolicySavePassword="Allow storage of user passwords"
ExplainText_SavePassword="Allows Microsoft Office Communicator to store user passwords.\n\nIf you enable this policy setting, Microsoft Office Communicator can store a password on request from the user.\n\nIf you disable this policy setting, Microsoft Office Communicator cannot store a password.\n\nIf you do not configure this policy setting and the user logs on to a domain, Microsoft Office Communicator does not store the password. If you do not configure this policy setting and the user does not log on to a domain (for example, if the user logs on to a workgroup), Microsoft Office Communicator can store the password.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyConfigurationMode="Specify transport and server"
ExplainText_ConfigurationMode="Specifies how Microsoft Office Communicator identifies the transport and server.\n\nIf you enable this policy setting, you must specify the transport and either the server name or the server IP address that Microsoft Office Communicator uses.\n\nIf you disable this policy setting, Microsoft Office Communicator uses a DNS lookup to identify the transport and the server.\n\nIf you do not configure this policy setting, the user can choose automatic configuration, or the user can specify the transport and either the name or the IP address of the server in Microsoft Office Communicator user preferences. To set the user preferences, from the Microsoft Office Communicator Tools menu, click Options, click the Accounts tab, within the SIP Communications Service Account area click Advanced, select Configure Settings, type the server name or IP address in Server name or IP address, and then select a transport.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
ServerAddress_VALUE="DNS name or IP address of the server"
Transport_VALUE="Transport"
TransportTCP="TCP (default)"
TransportUDP="UDP"
TransportTLS="TLS"
PBXPhoneDomain_VALUE="PBX Phone Domain"
PBXPhoneMaxNumberOfExtensions_VALUE="PBX Phone Maximum Number Of Extensions"
PolicyPortRange="Specify dynamic port ranges"
ExplainText_PortRange="Specifies the ranges of dynamically-allocated ports that Microsoft Office Communicator can use to transmit signaling data using SIP and to transmit audio and video data using RTP. If you open specific ranges of ports on a firewall between two clients to allow the clients to communicate, this policy forces the clients to use ports in those ranges.\n\nNote: If you enable this policy setting, avoid creating SIP and RTP port ranges that overlap.\n\nIf you enable this policy setting, both ranges must fall between 1024 and 65535 inclusive, in each range the minimum must be less than the maximum, the SIP range must contain at least two ports, and the RTP range must contain at least four ports (if the lowest port number in the range is even) or five ports (if the lowest port number in the range is odd). If you specify a range that violates one of these rules, Microsoft Office Communicator cannot use the SIP Communications Service.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator attempts to send and receive SIP and RTP data using ports selected at random throughout the range of 1024 to 65535 inclusive."
ExplainText_CEIP="Specifies whether Microsoft Office Communicator always records user actions, never records user actions, or allows the user to choose whether user actions are recorded.\n\nIf you enable this policy setting, instrumentation is enabled and the user cannot disable it.\n\nIf you disable this policy setting, instrumentation is disabled and the user cannot enable it.\n\nIf you do not configure this policy setting, the user can choose to enable or disable instrumentation.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyDisableInkIM="Prevent Ink in instant messages"
ExplainText_DisableInkIM="Prevents Microsoft Office Communicator from sending or receiving instant messages that contain Tablet PC Ink.\n\nIf you enable this policy setting, Microsoft Office Communicator cannot send or receive instant messages that contain Tablet PC Ink.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator can send or receive instant messages that contain Tablet PC Ink.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyEnableURL="Permit hyperlinks in instant messages"
ExplainText_EnableURL="Enables Microsoft Office Communicator to replace Internet and network paths with hyperlinks in instant messages.\n\nIf you enable this policy setting, Communicator will allow active hyperlinks in instant messages.\n\nIf you disable or do not configure this policy setting, Communicator will disable hyperlinks in instant messages. Hyperlinks will appear as text only in the instant message.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
SUPPORTED_WindowsXP="At least Microsoft Windows XP"
PolicyDisableStrictDNSNaming="Allow additional server DNS names"
ExplainText_DisableStrictDNSNaming="Allows Microsoft Office Communicator to automatically detect and securely communicate with SIP servers that have non-standard fully-qualified domain names (FQDNs). \n\nNote: This policy setting takes effect only if Microsoft Office Communicator uses "automatic configuration" to query DNS for a list of SIP servers, and only if Microsoft Office Communicator communicates with the SIP server using the TLS transport. In this case, the set of supported server FQDNs depends on the SIP URI of the user who starts Microsoft Office Communicator. \n\nFor example, if you disable or do not configure this policy setting, and the user’s SIP URI is SIP:USER1@EXAMPLE.COM, Microsoft Office Communicator can communicate with a SIP server in TLS transport only if its FQDN is either EXAMPLE.COM or SIP.EXAMPLE.COM. In other words, the FQDN of the server must exactly match the domain portion of the user’s SIP URI, or else the FQDN must be "SIP." followed by the domain portion of the user’s SIP URI. This prevents a "man-in-the-middle" security vulnerability: an attacker can detect the UDP message that the client uses to perform the DNS lookup, and respond to the client with the name of an unauthorized SIP server. The attacker could then impersonate a trusted user, or the server could cause the client to authenticate using weak encryption. \n\nHowever, if you enable this policy setting, Microsoft Office Communicator can communicate in TLS transport with any SIP server that has an FQDN that ends with the domain portion of the user’s SIP URI. Continuing the previous example, by enabling this policy setting you allow Microsoft Office Communicator to communicate with servers named SIP.DIVISION.EXAMPLE.COM or LC.EXAMPLE.COM. However, an attacker can respond to the initial DNS query with a response that contains the server name ATTACKER.EXAMPLE.COM.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyDisableCRLChecking="Disable Certificate Revokation List Checking"
ExplainText_DisableCRLChecking="The Disable Certificate Revocation List Checking policy prevents clients from connecting to the certificate authority to check for revocation. \n\nEnable this policy if clients cannot connect to the certificate authority in your environment."
ExplainText_DisableCalendarPresence="When this policy is enabled, Calendar information is not published to Presence."
PolicyEnablePhoneControl="Enable Phone Control"
ExplainText_EnablePhoneControl="Enables users of Microsoft Office Communicator to control their desk phone.\n\nThis policy is disabled by default.\n\nWhen this policy is disabled, users will not be able to control their desk phone from Communicator. The phone mode icon in the toolbar and all entry points from the top level menus of a conversation menu will be hidden from the user. In the contact list, users may still be able to select phone numbers if Pc to Phone is configured and running on the server and the EnablePC2Phone policy is enabled. In the options dialog all options related to phone control will be disabled.\n\nWhen this policy is enabled, all of the above mentioned entry points in the user interface are enabled, and the user will be able to control their desk phone from Communicator."
PolicyDisablePresenceNote="Disable Presence Note"
ExplainText_DisablePresenceNote="When this policy is enabled, the Presence Note functionality becomes unavailable."
ExplainText_DisablePhonePresence="When this policy is enabled, phone, voip, video, and conference call states will not be published as part of the presence information."
ExplainText_EnableRemoteAssistance="Allows Microsoft Office Communicator to use the Remote Assistance feature.\n\nIf you enable this policy setting, Microsoft Office Communicator will use this feature.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator will not use this feature.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyHelpMenu="Help Menu"
ExplainText_HelpMenu="This policy is used to extend the Help Menu in Microsoft Office Communicator. An administrator can specify a help web site for Microsoft Office Communicator using these keys. Help Menu Text is a string value that specifies the text to display to the user in the Help Menu for the help web site. Help Menu URL is a string value that specifies which web site to open when the user selects the Help Menu Text item in the Help Menu.\n\nNote that both Help Menu Text and Help Menu URL need to be specified in order for the Help Menu item to appear in Microsoft Office Communicator."
PolicyHelpMenuText="Help Menu Text"
PolicyHelpMenuURL="Help Menu URL"
PolicyTabURL="Tab URL"
ExplainText_TabURL="This policy specifies the location of the XML file Microsoft Office Communicator should use to display tabs. For each tab, the XML file specifies at minimum the name of the tab, the location of the tab’s icon, and the location of the tab’s contents."
PolicyDisableLiveMeetingIntegration="Disable Live Meeting Integration"
ExplainText_DisableLiveMeetingIntegration="Prevents users of Microsoft Office Communicator from initiating and joining live Meeting sessions.\n\nThis policy is disabled by default.\n\nWhen this policy is disabled, users can initiate and invite others to, and join a Live Meeting session from Communicator.\n\nWhen this policy is enabled users will not be able to initiate and invite others to a Live Meeting session. All entry points in contact list and conversation window will be hidden from the user.\n\nNote: The user must have the Live Meeting add in pack installed, and must have established and configured a Live Meeting account."
PolicyBlockIMFromFederatedContacts="Block IMs From Federated Contacts"
ExplainText_BlockIMFromFederatedContacts="The Block IMs From Federated Contacts policy prevents federated contacts from inviting users to IM conversations unless they have an ALLOW ACL from the user. In addition, it blocks messages that are not part of a session from reaching the user from such contacts. This in affect blocks inbound federated IM traffic from contacts that are not on the user's contact list.\n\nThis policy will override any user preference set in the options dialog Privacy tab."
PolicyBlockIMFromFederatedContacts_VALUE="How to handle federated IMs:"
PolicyBlockIMFromFederatedContactsVal2="Do not block"
PolicyMaximumNumberOfContacts="Set Maximum Allowed Number of Contacts"
ExplainText_MaximumNumberOfContacts="If you specify a maximum number of contacts, users will be limited in the number of contacts they can add to their contact list."
MaximumNumberOfContacts_VALUE="Maximum Number Of Contacts"
PolicyTourLaunch="Launch Microsoft Office Communicator Tour"
ExplainText_TourLaunch="This policy defines the behavior of the Microsoft Office Communicator Tour. Whether it's enabled or not, whether it should be launched automatically or not, and the optional URL for the Communicator Tour."
TourLaunchMode="Whether to launch the Microsoft Office Communicator Tour or Not"
TourLaunchVal0="Enabled with Auto Launch"
TourLaunchVal1="Disabled"
TourLaunchVal2="Enabled without Auto Launch"
TourUrl="Optional URL for the Microsoft Office Communicator Tour"
AllowUnencryptedFileTransfer="Allow Microsoft Office Communicator to transfer unencrypted files"
ExplainText_Allow_Unencrypted_File_Transfer="This policy controls the ability to send or receive unencrypted file thru File Transfer. \nIf you enable this policy, you will be able to transfer/receive file with an unencypted client. This is particularely needed to transfer files between Microsoft Office Communicator and older clients that doesn't support encryption."
DisableEmoticons="Disable Emoticons in Instant Messages"
ExplainText_Disable_Emoticons="Prevents Microsoft Office Communicator from showing emoticons in Instant Messages.\n\nIf you enable this policy setting, Microsoft Office Communicator will not use emoticons in Instant Messages.\n\nIf you disable or do not configure this policy setting, Microsoft Office Communicator will use emoticons in Instant Messages.\n\nNote: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence."
PolicyIMWarning="Warning Text"
ExplainText_IMWarning="This policy allows the administrator to configure the initial text that appears in the instant messaging area when a conversation window is opened."
PolicyAbsUseFallback="Address Book URL Fallback logic"
ExplainText_AbsUseFallback="If you configured a Client side Address Book URL and you want to configure retry capabilities on the client (fallback to a Server side Address Book URL), set the following registry key:\n"AbsUseFallback"\n0 = Do not attempt a "fallback" URL. Do not use Address Book URL configured on the Live Communications server or Pool to retry if the configured URL on the client does not work.\n1 = Use the registry setting for the configured in the AbsInsideUrl policy key for the Address Book URL and if this URL does not work, attempt the internal URL configured on the Live Communications Server or pool.\n2 = Use registry setting for outside URL in the AbsOutsideURL policy key. If this URL does not work then attempt the external URL configured on the Live Communications server or pool.\n3 = Use registry setting for both the internal and external URLS configured in AbsInsideURL and AbsOutsideURL respectively. If the attempted URL fails, then use the appropriate URL (internal or external) configured on the Live Communications server or pool.\n\nLack of AbsUseFallback registry key will give it a value of 0xFFFFFFFF (all bits set) --- means "Use registry setting for both the internal and external URLS configured in AbsInsideURL and AbsOutsideURL respectively. If the attempted URL does not work, then use the appropriate URL (internal or external) configured on the Live Communications server or pool."
AbsUseFallbackNone="0 = Do not use alternate URL"
AbsUseFallbackInside="1 = Use AbsInsideURL, then alternate URL"
AbsUseFallbackOutside="2 = Use AbsOutsideURL, then alternate URL"
AbsUseFallbackBoth="3 = Use AbsInsideURL and AbsOutsideURL, else alternate URL"
PolicyABSInsideURL="Address Book Server Inside URL"
ExplainText_ABSInsideURL="This policy provides a location on the Live Communication Server 2005 Address Book Service files for intranet connected Microsoft Office Communicator clients. This registry is needed for intranet clients to be able to search for contacts in the corporate Active Directory. The URL must use one of the http, https, or file protocols."
PolicyABSOutsideURL="Address Book Server Outside URL"
ExplainText_ABSOutsideURL="This policy provides a location on the Live Communication Server 2005 Address Book Service files for internet connected Microsoft Office Communicator clients. This registry is needed for internet clients to be able to search for contacts in the corporate Active Directory. The URL must use the https protocol. The URL should be externally accessible by clients outside the corporate intranet."
