Lync Server 2013
- Unknown Server Name in incoming HTTPS certificate. Server FQDN: %1 Issuer: %2 Cause: A connection attempt from an unknown ...
- Update Conflict occurred for {0}. File is opened with read/write access by some other process. Current Retry Count= {1}, ...
- Update pool assignment overwrite rules in service. Please use Get-csProvisionPoolAssignmentOverwriteRules -asXml to get more ...
- Update the deployment configuration store location using Set-CsConfigurationStoreLocation or change the central management ...
- Updates to settings associated with the service '{0}' are not allowed since its associated registrar '{1}' is in failed over ...
- Updating session key failed. It will be retried after some time. Error %1 Cause: This could be due to low resource conditions. ...
- Upload schema failed. Try running the ldifde command directly for more details about the error. Verify that Active Directory ...
- Use of wildcard "*" for SIP domains is not supported in Lync Server 2013. To correct this problem, please use the Global ...
- Use of wildcard in "{0}" SIP domain is not supported in Lync Server 2013. To correct this problem, please use the Global ...
- Use Set-CsKerberosAccountPassword to correct the Kerberos configuration data of the computer. This may require transferring ...
- Use the task Add/Edit/Remove to configure or change your Office Communications Server 2007 R2 Edge configuration, and then ...
- Used for Address Book downloads, Address Book Web Query service, client updates, meeting content, device updates, group expansion, ...
- User %1 provided a routing document with errors. Default call handling was applied instead. %2 Problems with this user's ...
- User %1 provided a routing preamble that references an unknown built in script. Missing script name=%2 version=%3. Problems ...
- User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
- User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
- User authentication with NTLM protocol failed with error SEC_E_UNSUPPORTED_FUNCTION. This indicates a potential mismatch ...
- User authentication with NTLM protocol took longer than expected (more than 15 seconds). There were %2 instances of NTLM ...
- User entry update in Active Directory failed while moving user. (0) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
- User entry update in Active Directory failed while moving user. (4) User: %1 Error: 2 Cause: Domain controller may be unreachable. ...
- User failed to join the conference. %1 Cause: Administration issues. Resolution: Verify that Conferencing Attendant is installed ...
- User has a phone number that is associated with other user(s). %1 shares same phone number with following other users (up ...
- User is at an unsupported country/region. TenantId: '%1', ObjectId: '%2' User location: '%3' Cause: User is at an unsupported ...
- User is enabled for SIP and homed on w14 server, but required Cluster Policy or Deployment Locator is missing. Resolve the ...
- User principal name (UPN) is not set for user "{0}". You must set a UPN for the user to use role-based access control (RBAC). ...
- User Replicator connected to domain controller %1 in domain %2 (DN: %3) to perform synchronization The source of the replication ...
- User Replicator failed to put Active directory objects data into the database for an unknown reason. The attempt will be ...
- User Replicator has completed initial synchronization of domain %1 (DN: %2) and the database. Future synchronization for ...
- User Replicator has started initial synchronization of domain %1 (DN: %2) and the database. Initial synchronization occurs ...
- User Service Pools status. Normal Pools: '%1' Standby Pools: '%2' Reserved for legacy tenant Pools: '%3' In Migration Mode:'%4' ...
- User was found in migrating mode. Because you used the Force option, unified contact store mode was set to disabled for the ...
- User was found in ucs mode and was rolled back but an error occurred while replicating the data. Run the cmdlet again to ...
- User was found in unified contact store mode. Contact list was successfully rolled back and any future migration attempts ...
- User was not found in unified contact store mode. An attempt to hold off future migrations for a preconfigured time failed ...
- User was not in unified contact store mode. Unified contact store mode was set to disabled for the user and any future migration ...
- User's voicemail URI is not specified. Please verify and ensure that the user is not UM enabled and enterprise voicemail ...
- Users are not indexed in the database that should be. Expected indexed user count: %1 Actual indexed user count: %2 Cause: ...
- Users who don't have these settings can't schedule meetings with dial-in conferencing. Click "yes" to turn off dial-in conferencing ...
- Users who have already been migrated to the Unified Contact Store (UCS) or who are about to be migrated to the Unified Contact ...
- Using the mirroring endpoint with name "{0}" and port {1} on database server "{2}". If the computer running this SQL Server ...
- Validate that replication is complete. In Lync Server Management Shell, run the Get-CsManagementStoreReplicationStatus cmdlet. ...
- Validating that conference directory with ID "{0}" is in a suitable state and checking for consistency between configuration ...
- Value is not valid external access prefix. Must be no longer than 4 characters long and can contain only digits, # or a *. ...
- Value may only begin with a letter or underscore and can only contain letters, digits, underscores, hyphens, and periods. ...
- Value may only begin with a letter, underscore, or colon and can only contain letters, digits, underscores, colons, hyphens, ...
- Value of registry key parameter {0} under {1} in {2} does not exist or is not valid. Only supported values are {3}, {4} or ...
- Verify that the account used to run this cmdlet has sufficient permissions to update the management connection in Active ...
- Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
- Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
- Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
- Verify that the Central Management Store is accessible and that the account used to run this cmdlet has sufficient permissions ...
- Verify that the connection path points to the Central Management Store, or that the document type can be written to the local ...
- Verify that the connection string points to a valid configuration database or replica, and that your account has sufficient ...
- Verify that the Lync Server 2013, Core Components are correctly installed and that the "{0}" interface is registered on the ...
- Verify that the Lync Server Backup Service is running on source pool '{0}' or run the cmdlet with the -Force parameter to ...
- Verify that the SQL Server instances are available and that the accounts running the primary and mirror SQL Server instances ...
- Verify that your user account has administrative privileges, and that you selected "Run as administrator" when you started ...
- Verify the computer account exists and has the correct configuration in Active Directory, and run Enable-CsTopology to restore ...
- Version of service "{0}" does not match current allowable version "{1}". Run the cmdlet again with the ProxyPool parameter. ...
- Voice quality is determined by the Differentiated Services Code Point (DSCP) value that you select (that is, 0-63). The default ...
- Voice, video, and presenting features aren't working because Desktop Experience isn't turned on. To turn it on, go to Windows ...
- Waiting on a response from the replica machine %1. Microsoft Lync Server 2013, File Transfer Agent will continue to wait ...
- Warning: It is possible to lose data when you use backup files to move the Central Management Server. Use backup files only ...
- Warning: Not all of the sites in the topology have been configured for call admission control. If call admission control ...
- Warning: Pairing two pools in the same site is not recommended for disaster recovery purposes. If the site fails, both pools ...
- Warning: Pool '{0}' is currently hosting the call admission control (CAC) component for site '{1}'. Assign CAC to a different ...
- Warning: Target Central Management Server Pool does not have a mirror set while the original pool has mirroring enabled. ...
- Warning: The Archiving settings for the following Survivable Branch Appliances will be updated with the new setting: {0}. ...
- Warning: The archiving settings for the following Survivable Branch Appliances will not be updated with the new setting because ...
- Warning: The associated Front End Server or pool is not associated with a Monitoring Server. We recommend that Survivable ...
- Warning: The associated Front End Server or pool is not associated with an Archiving Server. We recommend that Survivable ...
- Warning: The associated Front End Server or pool uses Archiving Server '{0}'. We recommend that Survivable Branch Appliances ...
- Warning: The associated Front End Server or pool uses Monitoring Server '{0}'. We recommend that Survivable Branch Appliances ...
- Warning: The cmdlet is not being run from a computer in the pool '{0}', which is where the Central Management service will ...
- WARNING: The monitoring reports will overwrite existing reports already deployed in the specified SQL Server Reporting Services ...