Page 22 of 748« First...10...2021222324...304050...Last »

Introduction to the Lync Server Central Managemet Store

This article explains the following topics to its readers:
  • A description of the Lync Server data structure and its replication process
  • An introduction to deploying the Lync Server CMS
  • An introduction to CMS management using Lync Server PowerShell cmdlets

Introduction to Lync Server

Lync Server is the next generation of Microsoft Office Communications Server. Lync Server provides real-time communication for audio and video conferencing, instant messaging, file transfer.

Lync Server provides small businesses with the opportunity to take advantage of advanced cloud-based telecommunication and collaboration while lowering costs.

Introduction to the Lync Server Central Management Store

The Central Management Store (CMS) is an important Lync Server component. The CMS is an Microsoft SQL Server repository that stores configuration data about the servers and services in the Lync Server deployment. In Office Communications server, this information was stored in Active Directory (AD), Windows Management Instrumentation (WMI) as well as SQL Server. 

Note Lync Server still stores user object information in AD to maintain backward compatibility with Office Communications Server. For example, Lync stores user phone numbers in AD.

By storing this configuration data in SQL Server, Lync Server is easier to administer:

  • The configuration data is easier to find because it is stored in a single location.
  • Administrators no longer have to extend AD schemas when they add features and functions.

The following types of data are stored in the CMS as XML documents:

  • Topology – The CMS stores topology information that was generated by the Topology Builder tool.
  • Policy – The CMS stores all of the different available policies that you can configure in Lync.
  • Configuration – The CMS stores configuration information such as certificate and dial-in conferencing access numbers.

Scope levels

You can also store information in different scope levels:

There is one XML document per information type and scope. For example, there is one XML document that contains dial-in conference information with a Global scope and another XML document that contains dial-in conference information in a Site scope.

How to update data in the CMS

You can use any of the following Lync Server tools to update the data in the CMS:

  • Topology Builder
  • Lync Server Management Shell
  • Lync Server Control Panel

The Lync Server management tools write to the XML documents through Microsoft.Rtc.Management.Core programming interface. This DLL enforces validation and scope for all data written to the CMS.

Note Manually changing XML documents is not supported.

Installing the CMS

We recommend that you install the CMS per the following guidelines:

  • Microsoft Lync Server Enterprise Edition - Install the CMS on a Front End pool to take advantage of the high-availability features that are built-in the Enterprise Edition. In this configuration, the master xds database is located in the same SQL Server instance as the back-end database. A replica copy of the xds database is located locally on each Lync Server role as an instance of SQL Server Express named “RTCLOCAL”
  • Microsoft Lync Server Standard Edition - The master xds database is located locally as part of the SQL Server Express instance named ”RTC”. A backup copy of the xds database is located in an SQL Server Express instance named “RTCLOCAL” on the same server.

Note Lync Server 2013 uses the rtcxds database to maintain an backup of user data

How the CMS replicates

All server-level information is stored in the CMS. The CMS uses a single master with multiple replicas format. In every Lync Server deployment, there is a single master CMS store. When the information in the master CMS store is updated, this configuration is copied to the other servers. This provides redundancy for remote servers.

The shared folder structure that the CMS stores the master copy of the topology in is described below:

  • Lync Server front end pool’s FileStore share which is user defined in the Lync Server topology will list the 1-CentralMgmt-1CMSFileStore folders underneath it.
  • The xds-master folder and its subfolders that are used in the CMS replication process will be listed under the CMSFileStore folder.
  • The xds-masterreplicas folder contains a folder for each replica. This folder is named after the FQDN of the replica. Each of the replica folders contains two folders named, from-replica and to-replica.

Each replica uses a network share to synchronize with the CMS master. The network path for the share on the replica is FDQN_of_the-replica_serverxds-master. The xds-master folder on the replica server contains from-master and t0-master subfolders.

The process to replicate data is:

  1. The CMS store information is written to a local shared folder on the CMS store master.
  2. Every 60 seconds, the CMS master determines whether changes have been made to the data.
  3. If the data has changed, the XML document that contains the change(s) is placed in a Data.zip file. The Data.zip file contains all of the XML documents that have changed since the last replication.

    Note The Data.zip file is typically less than 100 kilobytes. This helps to reduce the time that is required for replication.

  4. The File Transfer Agent service copies the Data.file to the replica servers, except Edge servers, by using the Server Message Block (SMB) protocol.
  5. On the replica, the Replica Replicator Agent service extracts the data from the Data.zip file and applies the changes to the CMS on the replica.
  6. The status of the replica server updates is reported back to the CMS store master in a file named Status.zip.

    Note Edge Servers use the ReplicationWebService over an HTTPS connection to copy the Data.zip file. The ReplicationWebService at https://Edge_Server_FQDN:4443/ReplicationWebService uses the server certificate that is issued to the internal edge of the Edge Server.

Using the Lync Server Management Shell to manage replication

The following table lists some the Lync Server Management Shell cmdlets that you can use to manage CMS replication:

Collapse this tableExpand this table

Lync Server Management Shell Cmdlet Purpose
Get-CsManagementStoreReplicationStatus Check the replication status for a Lync Server deployment
Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus Check the replication status for the active CMS master in a Lync Server Deployment
Invoke-CsManagementStoreReplication Force replication in a Lync Server deployment
Set-CSConfigurationStoreLocation -SqlServerFqdn-SQLInstanceName Change the location of the CMS master
Get-CsManagementConnection Get the connection information that is used when communicating with the CMS, Topology Builder, and the Lync Server Control Panel
Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus Designate the Front End server that will become CMS master if the current CMS master server fails.
Export CsConfiguration Filename data.zip Export the CMS data. This command can be used to back up CMS data.

Note The local Services on a Lync Server always read from the local CMS replica. Therefore, many of the Get-Cs* cmdlets accept the LocalStore parameter.

Article ID: 2667713 – Last Review: July 25, 2014 – Revision: 3.0


Applies to
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2013
kbsurveynew kbinfo KB2667713

More here:
Introduction to the Lync Server Central Managemet Store

SDP 340f1b532-ec88-4501-98af-393262ef4b2b Microsoft Online UserCheck Diagnostic

The Microsoft Online UserCheck Diagnostic is a Support Diagnostic package that collects user identity information from Microsoft cloud services. The diagnostic prompts the user who is running the tool for a company administrator (also known as global administrator) username and password. 

Note Without company administrator credentials, the tool cannot collect other user information from the Microsoft cloud service.

The diagnostic can be used to collect MSOnline identity details from one user or to collect the details from a list of users. The users must be in user principal name (UPN) format. The list of users must be separated by spaces or lines and may be any file name extension as long as the contents are text readable.

The list of users to check can be large and still work successfully. The tool has been tested with up to 25,500 users in a list. Larger lists should also work.

When providing a list of users, the tool will calculate the estimated time to completion. The estimate is based on a single user check taking one second to be completed. The estimate is provided on the diagnostic in hours and minutes. It’s updated after each user is completed so that a running estimate is given to the administrator of how long until estimated completion.

This section describes the information that may be collected from a computer when running the Microsoft Online UserCheck Diagnostic.

Information collected

MSOnline tenant information

Collapse this tableExpand this table

Description File Name
Details about the MSOnline Company Administrator who entered credentials for the diagnostic. MSOnline licensing for that user, and details regarding the domains in the tenant such as Authentication mode and Verification status. Formatted results of the Microsoft Azure Active Directory PowerShell module cmdlets Get-MSolUser, Get-MSolAccountSku, Get-MSolDomain, and Get-MSolRole. Computername_TenantInfo.txt

ResultReport.xml

Microsoft Online user details output files

Collapse this tableExpand this table

Description File Name
Single User Check MSOnline tenant name_CloudUserDetails.txt
Multiple Users Check MSOnline tenant name_CloudUserDetails.csv
Microsoft Online user details values

Collapse this tableExpand this table

Description Example
User DisplayName Joe Testuser
UserPrincipalName (sign in name) joetestuser@contoso.com
Single Sign On Enabled User

This value details whether the user will be redirected back from the cloud service portal to the company’s federated services logon server for sign in.

True or False
DirSynced User

This value shows whether the user is one that is or has been synchronized using any version of cloud directory synchronization.

True or False
LastDirSyncTime

If the user is one that has been synchronized using any version of cloud directory synchronization this date will be populated with the last synchronization success date and time.

Time-Date or NEVER
ImmutableID

If the user is one that is or has been one that is synchronized using cloud synchronization then this value will be populated with a unique ID.

GUID or NONE
Role Billing Administrator, Company Administrator, Exchange Administrator, Helpdesk Administrator, Lync Administrator, Service Support Administrator, User Administrator
Validation Status

Whether or not the user has any errors.

Healthy or Errors
LiveID GUID
ObjectID GUID
ProxyAddresses

Additional email addresses the user has.

SMTP:joe@contoso.com SMTP:emp223454@contoso.com
AlternateEmailAddresses

Alternate email address of the user (external to Microsoft cloud services).  

joetestuser@treyresearch.com
IsLicensed

If licensed to use any Microsoft cloud service.

True or False
LicenseReconciliatonNeeded

Whether or not the user currently has a mailbox without a license. In this case, the user should be licensed with 30 days to avoid losing their mailbox.

True or False
Credential Blocked True or False
Strong Authentication Methods List of enabled methods
Title title or NONE
Department Department or NONE
Street Address Street Address or NONE
City City or NONE
State State or NONE
PostalCode PostalCode or NONE
Phone Number Phone Number or NONE
Mobile Phone Mobile Phone or NONE
License:YAMMER_ENTERPRISE (7547a3fe-08ee-4ccb-b430-5077c5041653) Success, Disabled or PendingInput
License:RMS_S_ENTERPRISE (bea4c11e-220a-4e6d-8eb8-8ea15d019f90) Success, Disabled or PendingInput
License:OFFICESUBSCRIPTION (43de0ff5-c92c-492b-9116-175376d08c38) Success, Disabled or PendingInput
License:MCOSTANDARD (0feaeb32-d00e-4d66-bd5a-43b5b83db82c) Success, Disabled or PendingInput
License:SHAREPOINTWAC (e95bec33-7c88-4a70-8e19-b10bd9d0c014) Success, Disabled or PendingInput
License:SHAREPOINTENTERPRISE (5dbe027f-2339-4123-9542-606e4d348a72) Success, Disabled or PendingInput
License:EXCHANGE_S_ENTERPRISE (efb87545-963c-4e0d-99df-69c6916d9eb0) Success, Disabled or PendingInput
License:future or other license type Success, Disabled or PendingInput
Errors

An array of errors. These are validation errors that may result in loss of services.

Errors or NONE

Additional information

The CSV file output result file for the “multiple users” selection may be used to review the data that is returned in more detail. To do this, follow these steps:

  1. Open the file in Excel.
  2. Select the Sort and Filter option in the top row. After you do this, the top row is selectable as drop-down lists.
  3. To refine or reselect the data in the file, select the values from the list that match what you want to review.

For example, if you need a list of users who are not single sign-on enabled, in the drop-down list in the Single Sign On Enabled column, make sure that the False check box is the only one selected, and then click OK.

For more info, see the following Microsoft Knowledge Base article:
926079

(http://support.microsoft.com/kb/926079/
)

Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT)

Article ID: 2986857 – Last Review: July 24, 2014 – Revision: 2.0


Applies to
  • Microsoft Azure Active Directory
  • Microsoft Office 365
  • Microsoft Exchange Online
  • Microsoft Exchange Online Protection
  • Microsoft Lync Online
  • Office 365 Identity Management
o365022013 o365 o365a o365e o365p o365m KB2986857

Read More:
SDP 340f1b532-ec88-4501-98af-393262ef4b2b Microsoft Online UserCheck Diagnostic

Access denied when you try to give user "send-as" or "receive as" permission for a Distribution Group in Exchange Server 2010 or Exchange Server 2013

Active Directory operation failed on . This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : WriteError: (0:Int32) Add-ADPermission, ADOperationException
+ FullyQualifiedErrorId : 5557AD82,Microsoft.Exchange.Management.RecipientTasks.AddADPermission

More:
Access denied when you try to give user "send-as" or "receive as" permission for a Distribution Group in Exchange Server 2010 or Exchange Server 2013

Group Expansion and or Contact pictures not working or showing, EWS is not discovered

Users within the customers network complained that their contact pictures in Lync 2010 were not showing.  This applied to added contacts as well as their own contact picture.  However, contact pictures worked when Lync client connected outside of the customers network. 

Checked the client setup and discovered that the EWS was not populated.  Lync uses EWS to pull through pictures.Checked the client and discovered that group expansion does not work as well as searching for contacts or distribution lists. 

In the ETL, the client creates a webservice to https://webpoolsn20a02.infra.lync.com:443/groupexpansion/service.svc, for example: 

TRACE_LEVEL_INFORMATION 11CB4.1678::03/20/2013-16:54:36.127 (WebServices::CWebServicesManager::CreateWebRequest:CWebServicesManager_cpp328)0x001F6240Credential user 6 created a web service at 084F9750,baseServerUrl=https://webpoolsn20a02.infra.lync.com:443/groupexpansion/service.svc

Then it will error with:

TL_ERROR 11CB4.14F8::03/20/2013-16:55:04.170 (WebServices::CLiveIdTokenProvider::GetToken:CLiveIdTokenProvider.cpp(54))0x001F2AF0GetTokenInternal return hr=0×80048849 for https://webpoolsn20a02.infra.lync.com/WebTicket/WebTicketService.svc/WsFed_bearer

TL_WARN 11CB4.14F8::03/20/2013-16:55:04.170 (WebServices::CLiveIdTokenProvider::GetToken:CLiveIdTokenProvider.cpp(61))0x001F2AF0Posting credential error report: CredentialErrorReport : errorClass 27, errorSource 2042616TL_WARN 11CB4.14F8::03/20/2013-16:55:04.170 (WebServices::CLiveIdTokenProvider::GetToken:CLiveIdTokenProvider.cpp(70))0x001F2AF0Received IDCRL temporary error for userId(10) 0×80048849,hr will be adjusted to 80f10332TL_ERROR 11CB4.14F8::03/20/2013-16:55:04.170 (WebServices::CSamlBearerTokenXmlTransformation::ConstructWsSecurityFragment:CManagedWebRequest.cpp(16))0x084CAD90Retrieving token from a token provider failed!, hr=0x80f10332TL_WARN 11CB4.14F8::03/20/2013-16:55:04.170 (WebServices::CSamlBearerTokenXmlTransformation::ConstructWsSecurityFragment:CManagedWebRequest.cpp(16))0x084CAD90Failed to prepare soap fault from error report HRESULT = S_FALSE

0×80048849  = PPCRL_REQUEST_E_UNKNOWN

Disable access to webservices / lync infrastructure websites, but leave MAPI working with a local outlook client.  No error will occur just strange client behaviour.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2985849 – Last Review: July 23, 2014 – Revision: 1.0


Applies to
  • Microsoft Lync Server 2010 Standard Edition

Read More:
Group Expansion and or Contact pictures not working or showing, EWS is not discovered

Office 2013 Language Pack installed with Office 2007 or 2010 causes send error for Office document attachment

Consider the following scenario:
  • You have the 2007 Microsoft Office system or Microsoft Office 2010 installed, and a language pack for the same Office version.
  • You have a Microsoft Office2013 application, such as Word, Excel, PowerPoint, or Lync 2013 installed.
  • You have a Microsoft Office 2013 Language Pack installed.

In this scenario, you experience the following symptoms:

Office 2010

In Office 2010 Applications such as Word, Excel and PowerPoint, after you click File, Save & Send, Send Using Email, and then Send as Attachment, you receive the following error message:

Either there is no default mail client or the current mail client cannot fulfil the messaging request. Please run Microsoft Outlook and set it as the default mail client.

After you click OK, you receive the following additional error message, specific to the application that is running:

  • Microsoft Word 2010
    Word couldn’t send mail because of MAPI failure: “Unspecified error”.
  • Microsoft Excel 2010
    General mail failure. Quit Microsoft Excel, restart the mail system, and try again.
  • Microsoft PowerPoint 2010

    An error occurred while sending the presentation.

Office 2007

In Word 2007, you click FileSend as E-mail Attachment and receive the following error message:

Logon failed.  You must log on to Microsoft Exchange to access your address book.  Error code: “Unspecified error”.
The Language Pack installs a new version of msmapi32.dll for Microsoft Office 2013, but Outlook 2007 and Outlook 2010 require the earlier version of the DLL.
Delete the msmapi32.dll file from the following location, depending on the bitness of the Operating System and the Office Application, where xxxx is the problem Locale ID Language Code:
  • C:Program Files (x86)Common FilesSystemMSMAPIxxxx
  • C:Program FilesCommon FilesSystemMSMAPIxxxx

Note A list of supported Locale ID Language Codes can be found in KB221435

(http://support.microsoft.com/kb/221435/EN-US/
)

.

Run the localized version of Microsoft Word, then click File, Save & Send, Send Using Email, and then Send as Attachment. This causes the installer to run and replace the missing msmapi32.dll file that has the build needed for Office 2007 or 2010, depending on the version that you are running.

Microsoft is aware of this issue.  New information will be posted to this article as it becomes available.

Article ID: 2984293 – Last Review: July 23, 2014 – Revision: 2.0


Applies to
  • Microsoft Office Multi-Language Pack 2013
  • Microsoft Office 2013 Service Pack 1
  • Microsoft Office 2010 Service Pack 1
  • Microsoft Office 2010 Service Pack 2
  • Microsoft Office 2007 Compatibility Pack Service Pack 1
  • Microsoft Office 2007 Service Pack 2 for Language Interface Pack

See more here:
Office 2013 Language Pack installed with Office 2007 or 2010 causes send error for Office document attachment

Information about Internet Explorer versions

This article contains version information about Internet Explorer. This article also discusses how to determine which version of Internet Explorer is installed on your computer.

Release versions of Internet Explorer for Windows

Internet Explorer version numbers for Windows 95, Windows NT 4.0, Windows 98, Windows 98 Second Edition, Windows Millennium Edition (Me), Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows 7, and Windows 8 use the following format:

major version.minor version.build number.subbuild number

This table shows possible Internet Explorer version numbers.

Collapse this tableExpand this table

Version Product
4.40.308 Internet Explorer 1.0 (Plus! for Windows 95)
4.40.520 Internet Explorer 2.0
4.70.1155 Internet Explorer 3.0
4.70.1158 Internet Explorer 3.0 (Windows 95 OSR2)
4.70.1215 Internet Explorer 3.01
4.70.1300 Internet Explorer 3.02 and 3.02a
4.71.544 Internet Explorer 4.0 Platform Preview 1.0 (PP1)
4.71.1008.3 Internet Explorer 4.0 Platform Preview 2.0 (PP2)
4.71.1712.6 Internet Explorer 4.0
4.72.2106.8 Internet Explorer 4.01
4.72.3110.8 Internet Explorer 4.01 Service Pack 1 (Windows 98)
4.72.3612.1713 Internet Explorer 4.01 Service Pack 2
5.00.0518.10 Internet Explorer 5 Developer Preview (Beta 1)
5.00.0910.1309 Internet Explorer 5 Beta (Beta 2)
5.00.2014.0216 Internet Explorer 5
5.00.2314.1003 Internet Explorer 5 (Office 2000)
5.00.2614.3500 Internet Explorer 5 (Windows 98 Second Edition)
5.00.2516.1900 Internet Explorer 5.01 (Windows 2000 Beta 3, build 5.00.2031)
5.00.2919.800 Internet Explorer 5.01 (Windows 2000 RC1, build 5.00.2072)
5.00.2919.3800 Internet Explorer 5.01 (Windows 2000 RC2, build 5.00.2128)
5.00.2919.6307 Internet Explorer 5.01 (Office 2000 SR-1)
5.00.2920.0000 Internet Explorer 5.01 (Windows 2000, build 5.00.2195)
5.00.3103.1000 Internet Explorer 5.01 SP1 (Windows 2000 SP1)
5.00.3105.0106 Internet Explorer 5.01 SP1 (Windows 95/98 and Windows NT 4.0)
5.00.3314.2101 Internet Explorer 5.01 SP2 (Windows 95/98 and Windows NT 4.0)
5.00.3315.1000 Internet Explorer 5.01 SP2 (Windows 2000 SP2)
5.00.3502.1000 Internet Explorer 5.01 SP3 (Windows 2000 SP3 only)
5.00.3700.1000 Internet Explorer 5.01 SP4 (Windows 2000 SP4 only)
5.50.3825.1300 Internet Explorer 5.5 Developer Preview (Beta)
5.50.4030.2400 Internet Explorer 5.5 & Internet Tools Beta
5.50.4134.0100 Internet Explorer 5.5 for Windows Me (4.90.3000)
5.50.4134.0600 Internet Explorer 5.5
5.50.4308.2900 Internet Explorer 5.5 Advanced Security Privacy Beta
5.50.4522.1800 Internet Explorer 5.5 Service Pack 1
5.50.4807.2300 Internet Explorer 5.5 Service Pack 2
6.00.2462.0000 Internet Explorer 6 Public Preview (Beta)
6.00.2479.0006 Internet Explorer 6 Public Preview (Beta) Refresh
6.00.2600.0000 Internet Explorer 6 (Windows XP)
6.00.2800.1106 Internet Explorer 6 Service Pack 1 (Windows XP SP1)
6.00.2900.2180 Internet Explorer 6 for Windows XP SP2
6.00.2900.5512 Internet Explorer 6 for Windows XP SP3
6.00.3663.0000 Internet Explorer 6 for Windows Server 2003 RC1
6.00.3718.0000 Internet Explorer 6 for Windows Server 2003 RC2
6.00.3790.0000 Internet Explorer 6 for Windows Server 2003 (release)
6.00.3790.1830 Internet Explorer 6 for Windows Server 2003 SP1 and Windows XP x64
6.00.3790.3959 Internet Explorer 6 SP2 for Windows Server 2003 SP1 and Windows XP x64
7.00.5730.1100 Internet Explorer 7 for Windows XP and Windows Server 2003
7.00.5730.1300 Internet Explorer 7 for Windows XP and Windows Server 2003
7.00.6000.16386 Internet Explorer 7 for Windows Vista
7.00.6000.16441 Internet Explorer 7 for Windows Server 2003 SP2 x64
7.00.6000.16441 Internet Explorer 7 for Windows XP SP2 x64
7.00.6001.1800 Internet Explorer 7 for Windows Server 2008 and for Windows Vista SP1
8.00.6001.17184 Internet Explorer 8 Beta 1
8.00.6001.18241 Internet Explorer 8 Beta 2
8.00.6001.18372 Internet Explorer 8 RC1
8.00.6001.18702 Internet Explorer 8 for Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008
8.00.7000.00000 Internet Explorer 8 for Windows 7 Beta
8.00.7600.16385 Internet Explorer 8 for Windows 7 and for Windows Server 2008 R2 (release)
9.0.8080.16413 Internet Explorer 9 RC
9.0.8112.16421 Internet Explorer 9 RTM
10.0.8250.00000 Internet Explorer 10 Consumer Preview
10.0.8400.00000 Internet Explorer 10 Release Preview
10.0.9200.16384 Internet Explorer 10 for Windows 8

Internet Explorer 11 will have a version number that starts with 11 (for example, 11.0.9600). The version number will change based on the updates that have been installed for Internet Explorer. To see the version number and the most recent update installed, go to the Help menu and select About Internet Explorer.

Notes

Changes to the About Internet Explorer dialog box in Internet Explorer 9 and Internet Explorer 10

You can open the About Internet Explorer dialog box by clicking Help and then clicking About Internet Explorer. Or, press Alt+X and then press A.

Collapse this imageExpand this image

Collapse this imageExpand this image

One change from previous versions of Internet Explorer is how we use the Update Versions field. The field is updated every time Internet Explorer 9 or Internet Explorer 10 is updated. The version number has the following components:

  • The App Major version field will remain 9 or 10.
  • The App Minor version field will remain 0.
  • The Update revision field will increment by 1 for each Internet Explorer update that is released.

Collapse this imageExpand this image

Every update has an associated Knowledge base article (for example, KB2360131

(http://support.microsoft.com/kb/2360131)

– MS10-071: Cumulative security update for Internet Explorer) associated with it. The article provides detailed information about what is included in the update, and it also provides detailed information about the binaries that are updated. The About Internet Explorer dialog box provides a link to the Microsoft Knowledge Base Article that is associated with the most recently installed update to Internet Explorer as an easy way to get more information.

For example, if the first update for Internet Explorer 9 has been installed, the About Internet Explorer dialog box will have a link to “Update versions: 9.0.1 (KB2530548

(http://support.microsoft.com/kb/2530548)

).”

Collapse this imageExpand this image

How to determine the version of Internet Explorer for Windows

To determine the version of Internet Explorer, use any of the following methods:

  • In all versions of Internet Explorer, click About Internet Explorer on the Help menu. The product and version information are displayed in the dialog box that appears.
  • Use the registry. You can determine the version of Internet Explorer by viewing the following registry key:

    HKEY_LOCAL_MACHINESoftwareMicrosoftInternet Explorer

    If a “version” value appears in this key, Internet Explorer 4.0 or a later version is installed. The version string value contains the version number of Internet Explorer 4.0 (or a later version) that is installed on your computer. (For example, the version string value for Internet Explorer 5 is “5.0.2014.0216″). Be aware that only one zero is stored in the registry for the minor version number if the minor version number is 00. If the minor version number is not 00, the full version value is stored. (For example, 5.50.4807.2300 is stored in the registry as 5.50.4807.2300.)

    Note The version string value for Internet Explorer 10 is 9.10.9200.16384, and the svcVersion string value is 10.0.9200.16384.

    Internet Explorer 3.x does not add the version value to the registry. Instead, it adds a “build” value to the same registry key and updates the “IVer” string value to “103.” For backward compatibility, Internet Explorer 4.0 and later versions change or add the build value. For Internet Explorer 3.x, the build value is a string that contains the four-character build number. (For example, “1300″ is the build value for Internet Explorer 3.02). For Internet Explorer 4.0 and later versions, the build value is a string that contains a five-character value, followed by a period and four more characters, in the following format:

    major versionbuild number.subbuild number

    For example, the “build” value for Internet Explorer 5 is “52014.0216.”

  • Determine the version of Internet Explorer by using the
    Shdocvw.dll file:

    For Internet Explorer 3.0 through 6, the browser is implemented in the Shdocvw.dll (Shell Document Object and Control Library) file. You can use the version of the Shdocvw.dll file to determine the version of Internet Explorer 3.0 through 6 that is installed on your computer. To determine the version number of Internet Explorer 7, you must determine the version number of Iexplore.exe. To do this, follow these steps:

    1. Click Start, point to Find, and then click Files Or Folders.
    2. In the Named box, type shdocvw.dll, and then click Find Now.
    3. In the list of files, right-click the Shdocvw.dll file, and then click Properties.
    4. Click the Version tab.
    5. Repeat steps 2 through 4, but in step 2, instead type iexplore.exe. If the version of Iexplore.exe is 7.x, Internet Explorer 7 is installed. Use the table of Internet Explorer versions earlier in this article to compare the version number to release versions of Internet Explorer 7.

    This table lists the different versions of the Shdocvw.dll file and the corresponding versions of Internet Explorer.

    Collapse this tableExpand this table

    Version Product
    4.70.1155 Internet Explorer 3.0
    4.70.1158 Internet Explorer 3.0 (Windows 95 OSR2)
    4.70.1215 Internet Explorer 3.01
    4.70.1300 Internet Explorer 3.02 and 3.02a
    4.71.1008.3 Internet Explorer 4.0 Platform Preview 2.0 (PP2)
    4.71.1712.5 Internet Explorer 4.0
    4.72.2106.7 Internet Explorer 4.01
    4.72.3110.3 Internet Explorer 4.01 Service Pack 1 (Windows 98)
    4.72.3612.1707 Internet Explorer 4.01 Service Pack 2
    5.00.0518.5 Internet Explorer 5 Developer Preview (Beta 1)
    5.00.0910.1308 Internet Explorer 5 Beta (Beta 2)
    5.00.2014.213 Internet Explorer 5
    5.00.2314.1000 Internet Explorer 5 (Office 2000)
    5.00.2516.1900 Internet Explorer 5.01 (Windows 2000 Beta 3, build 5.00.2031)
    5.00.2614.3500 Internet Explorer 5 (Windows 98 Second Edition)
    5.00.2919.800 Internet Explorer 5.01 (Windows 2000 RC1, build 5.00.2072)
    5.00.2919.3800 Internet Explorer 5.01 (Windows 2000 RC2, build 5.00.2128)
    5.00.2919.6307 Internet Explorer 5.01 (Office 2000 SR-1)
    5.00.2920.0000 Internet Explorer 5.01 (Windows 2000, build 5.00.2195)
    5.00.3103.1000 Internet Explorer 5.01 SP1 (Windows 2000 SP1)
    5.00.3105.0106 Internet Explorer 5.01 SP1 (Windows 95/98 and Windows NT 4.0)
    5.00.3314.2100 Internet Explorer 5.01 SP2 (Windows 95/98 and Windows NT 4.0)
    5.00.3315.2879 Internet Explorer 5.01 SP2 (Windows 2000 SP2)
    5.00.3502.5400 Internet Explorer 5.01 SP3 (Windows 2000 SP3 only)
    5.00.3700.6668 Internet Explorer 5.01 SP4 (Windows 2000 SP4 only)
    5.50.3825.1300 Internet Explorer 5.5 Developer Preview (Beta)
    5.50.4030.2400 Internet Explorer 5.5 & Internet Tools Beta
    5.50.4134.0100 Internet Explorer 5.5 for Windows Me (4.90.3000)
    5.50.4134.0600 Internet Explorer 5.5
    5.50.4308.2900 Internet Explorer 5.5 Advanced Security Privacy Beta
    5.50.4522.1800 Internet Explorer 5.5 Service Pack 1
    5.50.4807.2300 Internet Explorer 5.5 Service Pack 2
    6.00.2462.0000 Internet Explorer 6 Public Preview (Beta)
    6.00.2479.0006 Internet Explorer 6 Public Preview (Beta) Refresh
    6.00.2600.0000 Internet Explorer 6 (Windows XP)
    6.00.2800.1106 Internet Explorer 6 Service Pack 1 (Windows XP SP1)
    6.00.2900.2180 Internet Explorer 6 for Windows XP SP2
    6.00.2900.5512 Internet Explorer 6 for Windows XP SP3
    6.00.2800.1278 Internet Explorer 6 Update v.01 Developer Preview (SP1b Beta)
    6.00.2800.1314 Internet Explorer 6 Update v.04 Developer Preview (SP1b Beta)
    6.00.3663.0000 Internet Explorer 6 for Windows Server 2003 RC1
    6.00.3718.0000 Internet Explorer 6 for Windows Server 2003 RC2
    6.00.3790.0000 Internet Explorer 6 for Windows Server 2003 (release)
    6.00.3790.1830 Internet Explorer 6 for Windows Server 2003 SP1 and Windows XP x64

    Notes

    • The minor version number, build number, and subbuild number may be displayed without trailing zeros. For example, version 7.00.5730.1100 may be displayed as 7.0.5730.11.
    • The Shdocvw.dll file is installed in the %Windir%System folder in Windows 95, in Windows 98, and in Windows Millennium Edition. The Shdocvw.dll file is installed in the %Windir%System32 folder in Windows NT 4.0, in Windows 2000, in Windows XP, and in Windows Server 2003. If the Shdocvw.dll file does not exist, Internet Explorer is either incorrectly installed or is not installed.
    • If the version of the Shdocvw.dll file on your computer is not listed in this table, you have installed an Internet Explorer hotfix, an update, or a security update that contains a later version of the Shdocvw.dll file. For example, Shdocvw.dll version 6.0.2800.1170 for Internet Explorer 6 SP1 is included with the MS03-015: April, 2003, Cumulative Patch for Internet Explorer (813489) package. If your version of Shdocvw.dll is not listed in this table, you are running the version of Internet Explorer that has the closest version number that is earlier than your version number. To determine which Internet Explorer hotfix, update, or security update is installed, search for the Shdocvw.dll version number on your computer and for “Shdocvw.dll” in the Microsoft Knowledge Base.
    • Internet Explorer 6 Update v.01 and v.04 are prerelease versions of Internet Explorer 6 that change the behavior of Internet Explorer when the program loads ActiveX controls. These prerelease updates are installed in side-by-side mode and will not affect the installation or version number of Internet Explorer 6 SP1 (6.00.2800.1106). Internet Explorer 6 Update v.01 and v.04 require Windows XP Service Pack 1. For more information about these prerelease updates, visit the following Microsoft website:
    • The version numbers of Internet Explorer in the list are based on the versions of Windows. The list numbers might be changed by the latest hotfix.
  • Determine the version of Internet Explorer by using a script:

    All versions of Internet Explorer send version information in the Hypertext Transfer Protocol (HTTP) user agent information header. This information can be read from script on a webpage. For information about how to use a script to obtain the version number of Internet Explorer, please see the following articles in the Microsoft Knowledge Base:

    167820

    (http://support.microsoft.com/kb/167820/
    )

    How to determine browser version from a script

    272413

    (http://support.microsoft.com/kb/272413/
    )

    How to determine browser type in server-side script without the BrowserType object

    Webpage developers can use this information to take advantage of new features in later versions of Internet Explorer (such as Dynamic HTML or Channels in Internet Explorer 4.x) and downgrade for earlier versions of Internet Explorer that do not support these features.

    If you have to uniquely identify Internet Explorer version 5.0 or later versions of the program (on Microsoft Win32 and on UNIX platforms only), use the isComponentInstalled or getComponentVersion methods of the CLIENTCAPS behavior. For information about these methods, see the following Microsoft websites:

    Note These methods do not work if the client is not Internet Explorer 5 or a later version (on Microsoft Win32 and UNIX platforms only).

Internet Explorer versions for other operating systems

Internet Explorer for Windows 3.1, Internet Explorer for UNIX on Sun Solaris, Internet Explorer for UNIX on HP-UX, and Internet Explorer for Macintosh are no longer available from or supported by Microsoft.

Internet Explorer for Macintosh or Windows 3.1

In Internet Explorer, click About Internet Explorer on the Help menu. On the Macintosh, click About Internet Explorer on the Apple menu. The version number is displayed in the dialog box that appears. Possible version numbers include the following:

Collapse this tableExpand this table

Windows 3.1 Macintosh Classic* Macintosh OS X
2.0 2.0 5.1.1
2.01 2.1 5.1.2
2.1 3.0 5.1.3
3.0 3.0a 5.1.4
3.0a 3.01a 5.2
3.01 4.0 5.2.1
3.02a 4.5 5.2.2
4.0 4.5.1 5.2.3
5 5.01
5.1
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7

Note If the version number is 3.0, you should also check the build
number next to the version number.
To determine whether you are running the 128-bit strong encryption version of Internet Explorer for Macintosh, click About Internet Explorer on the Apple menu, and then click Support. The Encryption box should contain the current encryption level. Here are examples:

  • 40 Bit International/Export Version
  • 128 Bit US Domestic (Not for Export)

Another way to determine whether you are running the 128-bit strong encryption version is to use the Get Info command on one of the following files (depending on your processor family, PowerPC or 68xxx), and then examine the version information:

  • System Folder:Extensions:MS Library Folder:MS Internet
    Library (PPC)
  • System Folder:Extensions:MS Library Folder:MS Internet
    Library (68K)

Internet Explorer for UNIX on Sun Solaris

To determine the version of Internet Explorer that is currently installed on a Solaris SPARC computer, follow these steps:

  1. Open a Terminal window. Determine the path of the installed Internet Explorer files. (The default path is /usr/local/microsoft/, which is used in the following steps as the example path).
  2. At the prompt, type cd
    /usr/local/microsoft
    , and then press Enter.
  3. Type ls -d ie*, and then press Enter. If “ie4″ is displayed, you are running Internet Explorer 4.0. If “ie” is displayed, you are running Internet Explorer 5.0.
  4. At the prompt, type cd ie*/sunos5, and then press Enter.
  5. Type ls -l libschannel.so, and then press Enter.
  6. Compare the file information to the following table to
    determine the version of Internet Explorer that is currently installed on your
    computer.

    Collapse this tableExpand this table

    File Version Size Product
    libschannel.so 4.71.2011.4 257,668 Internet Explorer 4.01 40-bit
    libschannel.so 4.71.2011.4 257,744 Internet Explorer 4.01 128-bit
    libschannel.so 5.00.2013.1312 524,692 Internet Explorer 5.0 40-bit
    libschannel.so 5.00.2013.1312 523,180 Internet Explorer 5.0 128-bit
    libschannel.so 5.00.2013.2002 523,672 Internet Explorer 5.0 SP1 Beta 128-bit

Internet Explorer for UNIX on HP-UX

To determine the version of Internet Explorer that is currently installed on an HP-UX computer, follow these steps:

  1. Open a Terminal window. Determine the path of the installed Internet Explorer files. (The default path is /usr/local/microsoft/, which is used in the following steps as the example path).
  2. At the prompt, type cd
    /usr/local/microsoft
    , and then press Enter.
  3. Type ls -d ie*, and then press Enter. If “ie4″ is displayed, you are running Internet Explorer 4.0. If “ie” is displayed, you are running Internet Explorer 5.0.
  4. At the prompt, type cd ie*/ux10, and then press Enter.
  5. If you have Internet Explorer 4.0, type ls -l
    libschannel.sl
    , and then press Enter. If you have Internet Explorer 5.0, type ls -l libcrypt32.sl, and then press Enter.
  6. Compare the file information to the following table to
    determine the version of Internet Explorer that is currently installed on your
    computer.

    Collapse this tableExpand this table

    File Version Size Product
    libschannel.sl 4.71.2004.9 181,023 Internet Explorer 4.01 40-bit
    libschannel.sl 4.71.2004.9 181,025 Internet Explorer 4.01 128-bit
    libcrypt32.sl 5.00.2013.1312 1,064,393 Internet Explorer 5.0 40-bit
    libcrypt32.sl 5.00.2013.1312 1,072,589 Internet Explorer 5.0 128-bit

Article ID: 969393 – Last Review: July 23, 2014 – Revision: 13.0


Applies to
  • Microsoft Internet Explorer 5.0
  • Microsoft Internet Explorer 6.0
  • Windows Internet Explorer 7
  • Windows Internet Explorer 8
  • Windows Internet Explorer 9
  • Internet Explorer 10
  • Internet Explorer 11

View article:
Information about Internet Explorer versions

"Object reference not set to an instance of an object" error occurs when configuring the Microsoft Dynamics CRM for Outlook client

When configuring the Microsoft Dynamics CRM 2011 or CRM 2013 for Outlook client to a Microsoft Dynamics CRM Online instance, an “Object reference not set to an instance of an object” error occurs after entering your credentials, choosing your organization, and clicking OK:

There is a problem communicating with the Microsoft Dynamics CRM server. The server might be unavailable. Try again later. If the problem persists, contact your system administrator.

Object reference not set to an instance of an object.

at Microsoft.Crm.Passport.IdCrl.OnlineServicesFederationLogOnManager.GetBrowserClientAuthInfo(String redirectEndpoint, String partner, String policy, String& postData)

at Microsoft.Crm.Outlook.ClientAuth.PassportAuthProvider`1.SignIn()

at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.SignIn(Uri endPoint, Credential credentials, AuthUIMode uiMode, IClientOrganizationContext context, Form parentWindow, Boolean retryOnError)

at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.GetAuthProvider(Uri endPoint, Credential credentials, AuthUIMode uiMode, Uri webEndPoint, IClientOrganizationContext context, Form parentWindow)

at Microsoft.Crm.Application.Outlook.Config.ServerInfo.LoadUserId()

at Microsoft.Crm.Application.Outlook.Config.ServerInfo.Initialize(Uri discoveryUri, OrganizationDetail selectedOrg, String displayName, Boolean isPrimary)

at Microsoft.Crm.Application.Outlook.Config.ServerForm.LoadDataToServerInfo()

at Microsoft.Crm.Application.Outlook.Config.ServerForm.b__2(Object sender, DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

This issue occurs if you are using a version of the Microsoft Online Services Sign-in Assistant that is incompatible with Microsoft Dynamics CRM 2011 or Microsoft Dynamics CRM 2013. When configuring the Microsoft Dynamics CRM for Outlook client and connecting to a Microsoft Dynamics CRM Online instance, the only supported versions of the Microsoft Online Services Sign-in Assistant are 7.250.4259.0, 7.250.4287.0, and 7.250.4303.0.
To resolve this issue, please perform the following steps:

1. Click Start, type appwiz.cpl, and then press Enter to open the Programs and Features item in Control Panel.

2. Uninstall the Microsoft Online Services Sign-in Assistant if its version does not match 7.250.4259.0, 7.250.4287.0, or 7.250.4303.0.

3. Download

(http://www.microsoft.com/en-us/download/details.aspx?id=28177)

and reinstall version 7.250.4303.0 of the Microsoft Online Services Sign-in Assistant.

4. Restart your workstation and configure the Microsoft Dynamics CRM for Outlook client to verify the issue is resolved.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2986728 – Last Review: July 22, 2014 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2013
  • Microsoft Dynamics CRM 2013 Service Pack 1
  • Microsoft CRM client for Microsoft Office Outlook
kbmbsmigrate kbsurveynew KB2986728

View article:
"Object reference not set to an instance of an object" error occurs when configuring the Microsoft Dynamics CRM for Outlook client

Office Applications experience a serious problem with an add-in

You start an Office application, such as Outlook, Word, Excel or PowerPoint and you recieve the following error message:

 experienced a serious problem with the <Add-in Name> add-in. If you have seen this message multiple times, you should disable this add-in and check to see if an update is available. Do you want to disable this add-in?

If you examine the Microsoft Office Alerts log you will also find an event with the following parameters:

Event log: Microsoft Office Alerts
EventID = 300
Message =
Microsoft Office Application
 experienced a serious problem with the <Add-in Name> add-in. If you have seen this message multiple times, you should disable this add-in and check to see if an update is available. Do you want to disable this add-in?

P1: 700160
P2: 14.0.6029.1000
P3: xath
P4: 
Source = Microsoft Office 14 Alerts (or Microsoft Office 15 Alerts)

Note In this error message and event, Office Application> is replaced with the name of the Office application such as Outlook, Word, Excel or PowerPoint, and Add-in Name> is replaced with the name of the add-in that experienced the problem.

The add-in listed in the error message caused the Office Application to crash in the previous session.
If the add-in continues to cause this problem, check with the vendor to see whether there is an updated version of the add-in.
To view the list of add-ins in the Office application and enable a disabled add-in, follow these steps:
  1. Click File, Options, and then click Add-ins.
  2. In the list of Add-ins, the Disabled Application Add-ins section will display the add-in(s) currently disabled.
  3. Next to Manage, select Disabled Items, and then click Go.

    Collapse this imageExpand this image

  4. Select the disabled add-in by its DLL name, and then click Enable.

    Collapse this imageExpand this image

Note The mssphtb.dll file is listed in the Disabled Items dialog box by default because it is intentionally disabled in Outlook 2013. You do not have to enable this particular add-in.  

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2986404 – Last Review: July 22, 2014 – Revision: 1.0


Applies to
  • Microsoft Outlook 2010
  • Microsoft Word 2010
  • Microsoft Excel 2010
  • Microsoft PowerPoint 2010

View original post here:
Office Applications experience a serious problem with an add-in

Considerations for Lync Online when you change an Office 365 sign-in address

When a user’s Office 365 sign-in address (also known as the User Principal Name, UPN, or user ID) is changed, the Lync Online SIP address for the user is automatically synchronized. Previously, when a user’s Office 365 sign-in address was changed, the IT administrator had to update the user’s SIP address separately to match the new Office 365 sign-in address. Otherwise, the two values would be mismatched. A mismatch between a user ID and the user’s SIP address may cause confusion for the Lync Online user during sign in.
After the user ID of a Lync Online user is updated, there are some actions that the user must take to make sure that the service continues to work without any interruptions. These actions are as follows:
  • Reschedule Lync Online meetings. Because of the way that the Lync Online service generates meeting URLs, any meetings that were scheduled by using the old Lync Online SIP address must be rescheduled. If these meetings aren’t rescheduled, meeting participants may receive an error message when they try to join any Lync Online conferences that are scheduled by that user.
  • Communicate changes to external contacts in Lync Online contact lists. External contacts (this includes other federated Lync organizations), Windows Live users, and MSN users must be notified about the change to the user’s SIP address. Until external contacts remove and update the old contact, the contact object for the user is displayed as either Presence Unknown or Offline.
Some companies may want a configuration that uses disjointed sign-in addresses for Lync Online and Office 365 and although this configuration is supported, the end-user experience on initial sign-in will be less than ideal for some Lync clients. Lync Online users will have to enter the UPN and SIP address separately in the user interface for a successful sign-in. Running the Office 365 Desktop Setup Tool will resolve this issue on computers that are running Lync 2010.

Note The Office 365 Desktop Setup Tool isn’t available for mobile devices or Lync 2013.

If you want to manually configure the setting for Lync 2013, see the following Office 365 website:

If the Office 365 organization is using Directory Synchronization and has or previously had a Office Communications Server 2007 R2, Lync Server 2010, or Lync Server 2013 deployment on-premises, the SIP Address can be updated independently by populating the msRTCSIP-PrimaryUserAddress value in Active Directory. Review the following Knowledge Base article to make sure that the values in Office 365 aren’t in conflict with on-premises values:

2430520

(http://support.microsoft.com/kb/2430520/
)

Error in the Office 365 portal: “Value of msRTCSIP-PrimaryUserAddress or the SIP address in the ProxyAddresses field in your local Active Directory is not unique”

Article ID: 2537764 – Last Review: July 21, 2014 – Revision: 43.0

o365 o365e o365p o365a o365022013 o365m KB2537764

Taken from:
Considerations for Lync Online when you change an Office 365 sign-in address

Costing Error Detection and Data Correction White Paper for Microsoft Dynamics NAV

Article ID: 893788 – Last Review: July 21, 2014 – Revision: 4.0


Applies to
  • Navision Attain 3.10
  • Navision Attain 3.6
  • Microsoft Business Solutions–Navision 3.70
  • Microsoft Dynamics NAV 4.0
kbmbsinventory kbmbsmigrate kbinfo KB893788
Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered “as is” and will no longer be updated.

View article:
Costing Error Detection and Data Correction White Paper for Microsoft Dynamics NAV

Page 22 of 748« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories