KB Articles

Page 1 of 74112345...102030...Last »

"You don’t have sufficient permissions" error when you try to remove or make a change to a distribution group

When you try to remove or make a change to a distribution group by using the Exchange admin center in Exchange Online for Office 365 or in on-premises Exchange Server 2013, you receive the following error message:

You don’t have sufficient permissions. This operation can only be performed by a manager of the group.

This issue may occur if the ManagedBy attribute of the distribution group is empty or is set up for a user who is no longer active in Exchange Online or in Exchange 2013. This issue could be caused by one of the following conditions:
  • You don’t have sufficient permissions.
  • The admin who originally created the group is no longer in the organization.
  • You are assigned the “Security Group Creation and Membership” role in the Exchange admin center. However, you can’t remove the group.

Note Customers who set up groups may later have to remove the groups even if those customers don’t own the groups.

To resolve this issue, follow these steps:
  1. Do one of the following, as appropriate for your situation:
  2. Make the change that you want to the distribution group by using the appropriate Windows PowerShell cmdlet.

    For example, to remove the distribution group, use the Remove-DistributionGroup cmdlet together with the BypassSecurityGroupManagerCheck parameter. Here’s an example:

    Remove-DistributionGroup  -BypassSecurityGroupManagerCheck

    Note In this cmdlet and other cmdlets in the “Examples” section, the distribution group is represented by a placeholder.

Examples

Here are some more examples of other Windows PowerShell cmdlets that you can use to manage distribution groups.

  • To assign ownership of a group, use the Set-DistributionGroup cmdlet. Here’s an example.
    Set-DistributionGroup  -ManagedBy "Admin@contoso.com" -BypassSecurityGroupManagerCheck
  • To add a user to a group, use the Add-DistributionGroup cmdlet. Here’s an example.
    Add-DistributionGroupMember -Identity  -Member user@contoso.com
  • To remove a user from a group, use the Remove-DistributionGroup cmdlet. Here’s an example.
    Remove-DistributionGroupMember -Identity  -Member user@contoso.com
  • To check the members list for a group, use the Get-DistributionGroupMember cmdlet. Here’s an example.
    Get-DistributionGroupMember -identity |fl DisplayName,WindowsLiveID,RecipientType
For info about managing distribution groups that are synced to Office 365 from the on-premises environment, see the following Microsoft Knowledge Base article:
2417592

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

Owners of an on-premises distribution group that’s synced to Office 365 can’t manage the distribution group in Exchange Online

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2731947 – Last Review: October 1, 2014 – Revision: 9.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
o365e o365p o365 o365a o365m o365022013 KB2731947

Visit site:
"You don’t have sufficient permissions" error when you try to remove or make a change to a distribution group

Using WAN Optimization Controller devices with Office 365

Summary

Microsoft Office 365 does not require you to use WAN Optimization Controller devices (also known as WAN acceleration and caching devices), nor can we comment on the effectiveness of these solutions. Customers may decide to use such devices to increase performance under conditions of high latency or low bandwidth for Microsoft Exchange Online and Microsoft SharePoint Online. We advise customers to use their own discretion in deploying these devices with Office 365, whether in Multi-Tenant (MT), Dedicated (D), or ITAR service deployment configurations.

Microsoft does not offer first-party technical customer support for WAN Optimization Controller (WOC) devices. As with other network infrastructure equipment, we have not tested the use of these devices with Office 365 to make sure that they work, nor do we take any responsibility for making sure that they continue to work as part of regular service updates. Customers should work directly with their WOC vendors to receive technical support.

During support incidents, we do require customers to inform us if they are using WOC devices. We also require that customers have an easy way to bypass the WAN optimization service for Office 365. When we try to resolve a customer service issue in Office 365, we may ask that these devices be put in bypass mode before we continue with diagnosis and issue resolution. By bypass mode, we mean any combination of network or device configuration that logically or physically removes the device from the infrastructure path between the customer and Office 365.

More Information

Office 365 Dedicated and ITAR customers may install and use WOC devices with the service at their own discretion. We do enable co-location of these devices in Microsoft data centers in which a customer’s private network ends. Be aware that we enable this option only for Office 365 Dedicated and ITAR deployments, not for Multi-Tenant service. To realize the same benefits, some WOC vendors do offer the option to deploy only in the customer’s data center, and they do not require co-location in a Microsoft data center. Because the use of WOC devices can potentially affect the reliability of the Office 365 service, customers must agree to the following when they opt to use these devices:

  • If a customer’s support request involves diagnosing a service access issue, the customer must disclose WOC devices that are being used when he or she contacts Microsoft Online Services Support by online submission (see http://support.microsoft.com/kb/2694621

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

    ) or by telephone (see http://support.microsoft.com/kb/2573289

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

    ).

  • If these devices are found to affect the performance or availability of Office 365 service components during troubleshooting by Microsoft, we may ask the customer to bypass the WOC device to make sure that service availability is maintained.
  • Before a customer re-enables such devices, he or she must directly engage the technical support resources of the device vendor to investigate issues that are caused by the existing device.
  • Any event that adversely affects service and that we determine to be caused by the existing WOC device will be identified as a Service Level Agreement (SLA) exclusion.

For all customer deployments, Microsoft does not provide first-party technical customer support for the integration and use of WOC devices with Office 365 (in Multi-Tenant, Dedicated, and ITAR configurations). Our position and rationale are outlined as follows:

  • We cannot provide proactive support for these devices or for related third-party software that we do not control. These devices sit between the client and our servers. They affect every network communication and can potentially affect our service. We cannot take responsibility for any issues caused by these devices.
  • As we cannot diagnose the devices directly, we may ask to bypass them during support diagnosis or troubleshooting. If bypassing the WOC devices fixes a problem, the customer must work with the device manufacturer to obtain a long-term resolution (such as a code update) and to then re-enable the device.
  • We realize that our customers may have to deploy such devices. But because of their complexity, these devices remain the customer’s responsibility when any issues arise. 

In summary WOC devices are considered part of the customer’s on-premises landscape, and if they are used, any related issues are the customer’s responsibility. As we continue to improve the Office 365 service, changes can potentially affect the performance of these devices. It is the responsibility of the customer and the device manufacturer to make any necessary modifications to support our service changes.

Article ID: 2690045 – Last Review: September 30, 2014 – Revision: 12.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Office 365
Keywords: 
vkbportal226 o365 o365022013 KB2690045

Follow this link:
Using WAN Optimization Controller devices with Office 365

Compatibility with Microsoft Dynamics CRM

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: 2669061 – Last Review: September 30, 2014 – Revision: 51.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 4.0
  • Microsoft Dynamics CRM Online Professional Edition
  • Microsoft Dynamics CRM 2013
kbmbsmigrate kbsurveynew KB2669061

Read the original post:
Compatibility with Microsoft Dynamics CRM

Compatibility with Microsoft Dynamics CRM 2011

Product Minimum CRM version CRM build number Status .Net Framework 4.0 RTM 5.0.9688.583 Compatible .Net Framework 4.0 PU3 - - TBD .Net Framework 4.5 Update Rollup 8 5.0.9690.2243 Compatible .Net Framework 4.5.1 Update Rollup 15 5.0.9690.3731 Compatible .Net Framework 4.5.2 Update Rollup 17 5.0.9690.4150 Compatible Active Directory Federation Services in Windows Server 2008 (AD FS 2.0) RTM 5.0.9688.583 Compatible Active Directory Federation Services in Windows Server 2008 R2 RTM 5.0.9688.583 Compatible Active Directory Federation Services in Windows Server 2012 Update Rollup 13 5.0.9690.3432 Compatible

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

Active Directory Federation Services in Windows Server 2012 R2 - - Not compatible Azure virtual machines (support for Microsoft Azure virtual machines)

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

- - Not compatible Exchange Online (O365) Update Rollup 5 5.0.9688.1533 Compatible Exchange Online (BPOS) RTM 5.0.9688.583 Compatible Exchange Server 2000 - - Not compatible Exchange Server 2003 SP2 RTM 5.0.9688.583 Compatible Exchange Server 2003 SP3 RTM 5.0.9688.583 Compatible Exchange Server 2007 RTM 5.0.9688.583 Compatible Exchange Server 2010 RTM 5.0.9688.583 Compatible Exchange Server 2010 SP1 Update Rollup 12 5.0.9690.3236 Compatible Exchange Server 2010 SP2 Update Rollup 12 5.0.9690.3236 Compatible Exchange Server 2010 SP3 Update Rollup 13 5.0.9690.3448 Compatible Exchange Server 2013 Update Rollup 15 5.0.9690.3731 Compatible Internet Explorer 6 - - Not compatible Internet Explorer 7 RTM 5.0.9688.583 Compatible

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

*** Internet Explorer 8 RTM 5.0.9688.583 Compatible Internet Explorer 9 RTM 5.0.9688.583 Compatible Internet Explorer 10 Update Rollup 10 5.0.9688.2730 Compatible

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

* Internet Explorer 11 Update Rollup 17 5.0.9690.4150 Compatible

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

Microsoft Application Virtualization (App-V) 4.6 - - Not compatible Microsoft Office Communications Server 2007 RTM 5.0.9688.583 Compatible Microsoft Office Communications Server 2007 R2 RTM 5.0.9688.583 Compatible Microsoft Report Viewer 2010 RTM 5.0.9688.583 Compatible Microsoft SharePoint 2010 (all editions) RTM 5.0.9688.583 Compatible Microsoft SharePoint 2013 Update Rollup 12 5.0.9690.3236 Compatible Microsoft Office SharePoint Server 2007 RTM 5.0.9688.583 Compatible Microsoft Visual C++ Redistributable 2008 RTM 5.0.9688.583 Compatible Microsoft Visual C++ Redistributable 2010 Update Rollup 6 5.0.9690.1992 Compatible Microsoft Windows Installer (MSI) 4.5 RTM 5.0.9688.583 Compatible MSXML 4.0 RTM 5.0.9688.583 Compatible Office 2003 SP3 (Cached-Exchange Mode Only) RTM 5.0.9688.583 Compatible

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

* Office 2007 SP2 (Cached-Exchange Mode Only) RTM 5.0.9688.583 Compatible Office 2007 SP3 (Cached-Exchange Mode Only) Update Rollup 5 5.0.9688.1533 Compatible Office 2010 (Cached-Exchange Mode Only) RTM 5.0.9688.583 Compatible Office 2010 SP1 (Cached-Exchange Mode Only) RTM 5.0.9688.583 Compatible Office 2010 SP2 (Cached-Exchange Mode Only) Update Rollup 15 5.0.9690.3731 Compatible Office 2013 MSI (Cached-Exchange Mode Only) Update Rollup 10 5.0.9688.2730 Compatible

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

* Office 2013 C2R (stand-lone) (Cached-Exchange Mode Only) Update Rollup 10 5.0.9688.2730 Compatible

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

* Office 2013 C2R (side-by-side with Office 2010)(Cached-Exchange Mode Only) Update Rollup 10 5.0.9688.2730 Compatible

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

* Office 2013 SP1 (Cached-Exchange Mode Only) Update Rollup 17 5.0.9690.4150 Compatible SharePoint 2013 Update Rollup 12 5.0.9690.3233 Compatible Small Business Server 2008 Premium (x64) RTM 5.0.9688.583 Compatible Small Business Server 2008 Standard (x64) RTM 5.0.9688.583 Compatible Small Business Server 2008 Standard RTM 5.0.9688.583 Compatible Small Business Server 2011 Essentials Update Rollup 3 5.0.9688.1244 Compatible SQL Server 2000 - - Not compatible SQL Server 2005 - - Not compatible SQL Server 2008 Express Edition SP1 RTM 5.0.9688.583 Compatible SQL Server 2008 Standard SP1 (x64) RTM 5.0.9688.583 Compatible SQL Server 2008 SP2 (x64) Update Rollup 8 5.0.9690.2243 Compatible SQL Server 2008 SP3 (x64) Update Rollup 8 5.0.9690.2243 Compatible SQL Server 2008 R2 (x64) RTM 5.0.9688.583 Compatible SQL Server 2008 R2 SP1 (x64) Update Rollup 8 5.0.9690.2243 Compatible SQL Server 2008 R2 SP2 (x64) Update Rollup 8 5.0.9690.2243 Compatible SQL Server 2008 R2 SP2 (CTP) (x64) Update Rollup 8 5.0.9690.2243 Compatible SQL Server Compact 3.5 SP2 RTM 5.0.9688.583 Compatible SQL Server Compact 4.0 Update Rollup 4 5.0.9688.1450 Compatible SQL Server Active/Active Cluster** Update Rollup 1 5.0.9688.1045 Compatible SQL Server 2012**** Update Rollup 6 5.0.9690.1992 Compatible

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

* SQL Server 2012 SP1 Update Rollup 10 5.0.9688.2730 Compatible Windows 7 (32bit and 64bit) RTM 5.0.9688.583 Compatible Windows 7 SP1 RTM 5.0.9688.583 Compatible Windows 8 (requires manual WIF enablement) Update Rollup 10 5.0.9688.2730 Compatible

(http://support.microsoft.com/KB/2744954)

* Windows 8.1 Update Rollup 17 5.0.9690.4150 Compatible Windows RT - - Not compatible Windows Server 2003 - - Not compatible Windows Server 2008 Standard SP2 (x64) RTM 5.0.9688.583 Compatible Windows Server 2008 Standard R2 RTM 5.0.9688.583 Compatible Windows Server 2008 Enterprise SP2 (x64) RTM 5.0.9688.583 Compatible Windows Server 2008 Enterprise R2 RTM 5.0.9688.583 Compatible Windows Server 2008 Datacenter SP2 (x64) RTM 5.0.9688.583 Compatible Windows Server 2008 Datacenter R2 RTM 5.0.9688.583 Compatible Windows Web Server 2008 SP2 (x64) (front-end role only) RTM 5.0.9688.583 Compatible Windows Web Server 2008 R2 (front-end role only) RTM 5.0.9688.583 Compatible Windows Server 2012 Datacenter or Standard***** Update Rollup 13 5.0.9690.3432 Compatible Windows Server 2012 R2 Datacenter or Standard - - Not compatible Windows Web Server 2008 SP2 (x64) (front-end role only) RTM 5.0.9688.583 Compatible Windows Web Server 2008 R2 (front-end role only) RTM 5.0.9688.583 Compatible Windows Vista (x86 and x64) RTM 5.0.9688.583 Compatible Windows XP SP3 RTM 5.0.9688.583 Compatible

Continue Reading:
Compatibility with Microsoft Dynamics CRM 2011

Compatibility with Microsoft Dynamics CRM 4.0

This article focuses on recent and upcoming compatibility testing for Microsoft Dynamics CRM 4.0. It also focuses on the most common compatibility questions that are processed by Microsoft Dynamics Technical Support. This article does not indicate Microsoft Dynamics CRM compatibility for all products. This article supplements the information in the Microsoft Dynamics CRM Implementation Guide.
The products that have a status of “TBD” are being considered for future compatibility. When the testing of these products is complete, this article will be updated to show the revised status values.

Microsoft Dynamics CRM 4.0

The following list of products have been tested or are currently being tested for compatibility with Dynamics CRM 4.0. The Minimum CRM version and CRM build number fields list the minimum Microsoft Dynamics CRM version that is compatible with the listed product.

Collapse this tableExpand this table

Product Minimum CRM version CRM build number Status
Azure virtual machines (support for Microsoft Azure virtual machines)

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

- - Not compatible
.Net 3.5 Update Rollup 1 4.0.7333.1113 Compatible
.Net 3.5 SP1 Update Rollup 2 4.0.7333.1312 Compatible
.Net 4.0 Update Rollup 18 4.0.7333.3531 Compatible
.Net 4.0 PU3 - - TBD
.Net 4.5 RC Update Rollup 21 4.0.7333.3822 Compatible
Exchange Online with Office 365 Update Rollup 18 4.0.7333.3531 Compatible
Exchange Online (BPOS) Update Rollup 10 4.0.7333.2741 Compatible
Exchange Server 2000 - - Not compatible
Exchange Server 2003 SP2 RTM 4.0.7333.3 Compatible
Exchange Server 2007 RTM 4.0.7333.3 Compatible
Exchange Server 2010 Update Rollup 8 4.0.7333.2542 Compatible
Exchange Server 2010 SP1 Update Rollup 12 4.0.7333.2861 Compatible
Exchange Server 2010 SP2 Update Rollup 21 4.0.7333.3822 Compatible
Exchange Server 2010 SP3 Update Rollup 21 4.0.7333.3822 Compatible
Exchange Server 2013 Not compatible
Internet Explorer 6 RTM 4.0.7333.3 Compatible
Internet Explorer 7 RTM 4.0.7333.3 Compatible
Internet Explorer 8 Update Rollup 4 4.0.7333.1551 Compatible
Internet Explorer 9 Update Rollup 16 4.0.7333.3335 Compatible
Internet Explorer 10 - - Not compatible
Microsoft Application Virtualization (App-V) 4.6 - - Not compatible
Microsoft Report Viewer 2005 RTM 4.0.7333.3 Compatible
Microsoft Report Viewer 2008 Update Rollup 11 4.0.7333.2861 Compatible
Microsoft SharePoint 2010 Update Rollup 14 4.0.7333.3135 Compatible
Microsoft SharePoint Foundation 2010 Update Rollup 11 4.0.7333.2861 Compatible
Office 2003 SP3 (Cached-Exchange Mode Only) RTM 4.0.7333.3 Compatible
Office 2007 SP3 (Cached-Exchange Mode Only) Update Rollup 19 4.0.7333.3628 Compatible
Office 2010 (Cached-Exchange Mode Only) Update Rollup 11 4.0.7333.2861 Compatible
Office 2010 SP1 (Cached-Exchange Mode Only) Update Rollup 14 4.0.7333.3135 Compatible
Office 2010 SP2 (Cached-Exchange Mode Only) - - Not compatible
Office 2013 (Cached-Exchange Mode Only) - - Not compatible
SQL Server 2005 SP2 RTM 4.0.7333.3 Compatible
SQL Server 2005 SP4 Update Rollup 20 4.0.7333.3732 Compatible
SQL Server 2008 R2 Update Rollup 7 4.0.7333.2138 Compatible
SQL Server 2008 R2 SP1 Update Rollup 21 4.0.7333.3822 Compatible
SQL Server 2008 SP1 Update Rollup 4 4.0.7333.1551 Compatible

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

*

SQL Server 2008 SP2 Update Rollup 12 4.0.7333.2861 Compatible
SQL Server 2008 R2 SP2 (CTP) Update Rollup 21 4.0.7333.3822 Compatible
SQL Server 2008 SP3 Update Rollup 21 4.0.7333.3822 Compatible
SQL Server Active/Active Clustering** Update Rollup 16 4.0.7333.3335 Compatible
SQL Server 2012 Update Rollup 21 4.0.7333.3822 Compatible

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

*

SQL Server 2012 SP1 Update Rollup 21 4.0.7333.3822 Compatible
Windows Server 2000 - - Not compatible
Windows Server 2003 SP2 RTM 4.0.7333.3 Compatible
Windows Server 2008 RTM 4.0.7333.3 Compatible

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

*

Windows Server 2008 (Server Core) - - Not compatible
Windows Server 2008 R2 Update Rollup 6 4.0.7333.1750 Compatible
Windows Server R2 SP1 Update Rollup 19 4.0.7333.3628 Compatible
Windows Server R2 SP1 RC Update Rollup 13 4.0.7333.3018 Compatible
Windows Server 2008 SP2 Update Rollup 4 4.0.7333.1551 Compatible
Windows 7 Update Rollup 7 4.0.7333.2138 Compatible
Windows 7 SP1 Update Rollup 19 4.0.7333.3628 Compatible
Windows 8 - - Not compatible
Windows Server 2003 SP2 RTM 4.0.7333.3 Compatible
Windows Vista RTM 4.0.7333.3 Compatible
Windows XP SP3 RTM 4.0.7333.3 Compatible

* For non-production environments only.

** Active/Active Clustering is supported, but not as a load-balancing configuration.

  • The CRM for Outlook client does not support Outlook configured in Online for tracking or synchronization (non-Cached Exchange mode)

For more information about System Requirements, see the System Requirements and Required Components

(http://technet.microsoft.com/en-us/library/dd979161.aspx)

topic in the Microsoft Dynamics CRM 4.0 Implementation Guide.

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: 3005186 – Last Review: September 30, 2014 – Revision: 1.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbmbsmigrate kbsurveynew KB3005186

View the original here:
Compatibility with Microsoft Dynamics CRM 4.0

Compatibility with Microsoft Dynamics CRM 2013

Product Minimum CRM version CRM build number Status .Net Framework 4.5.2 Update Rollup 2 6.0.2.46 Compatible Active Directory Federation Services in Windows Server 2008 (AD FS 2.0) RTM 6.0.0.809 Compatible Active Directory Federation Services in Windows Server 2008 R2 RTM 6.0.0.809 Compatible Active Directory Federation Services in Windows Server 2012 RTM 6.0.0.809 Compatible Active Directory Federation Services in Windows Server 2012 R2 RTM 6.0.0.809 Compatible Azure virtual machines (support for Microsoft Azure virtual machines)

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

- - Not Compatible CRM 2011 for Outlook Client Update Rollup 12 5.0.9690.3236 Compatible Exchange Online RTM 6.0.0.809 Compatible Exchange Server 2000 - - Not Compatible Exchange Server 2003 - - Not Compatible Exchange Server 2007 Standard RTM 6.0.0.809 Compatible Exchange Server 2007 Enterprise RTM 6.0.0.809 Compatible Exchange Server 2010 Standard RTM 6.0.0.809 Compatible Exchange Server 2010 Enterprise RTM 6.0.0.809 Compatible Exchange Server 2013 Standard Update Rollup 2 6.0.0002.0043 Compatible Exchange Server 2013 Enterprise Update Rollup 2 6.0.0002.0043 Compatible IIS 7.0 RTM 6.0.0.809 Compatible IIS 7.5 RTM 6.0.0.809 Compatible IIS 8.0 RTM 6.0.0.809 Compatible Internet Explorer 8 RTM 6.0.0.809 Compatible Internet Explorer 9 RTM 6.0.0.809 Compatible Internet Explorer 10 RTM 6.0.0.809 Compatible Internet Explorer 11 Update Rollup 2 6.0.0002.0043 Compatible iOS7 Safari on iPad (web application) Update Rollup 2 6.0.0002.0043 Compatible iPad Air using Safari (web application) Update Rollup 2 6.0.0002.0043 Compatible iPad Air using CRM for Tablets Update Rollup 2 6.0.0002.0043 Compatible Microsoft SharePoint 2010 SP1 (all editions) RTM 6.0.0.809 Compatible Microsoft SharePoint 2010 Foundation 2013 RTM 6.0.0.809 Compatible Microsoft SharePoint 2013 RTM 6.0.0.809 Compatible Microsoft SQL Server 2000 - - Not compatible Microsoft SQL Server 2005 - - Not compatible Microsoft SQL Server 2008 Workgroup - - Not compatible Microsoft SQL Server 2008 Web - - Not compatible Microsoft SQL Server 2008 Compact (CRM server) - - Not compatible Microsoft SQL Server 2008 Express (CRM server) - - Not compatible Microsoft SQL Server 2008 Standard SP3 (x64) RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Standard R2 SP2 RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Enterprise SP3 (x64) RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Enterprise R2 SP2 RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Datacenter SP2 (x64) RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Datacenter R2 SP2 RTM 6.0.0.809 Compatible Microsoft SQL Server 2008 Developer SP3 (x64) RTM 6.0.0.809 Compatible* Microsoft SQL Server 2008 Developer R2 SP2 RTM 6.0.0.809 Compatible* Microsoft SQL Server 2012 Enterprise SP1 (x64) RTM 6.0.0.809 Compatible Microsoft SQL Server 2012 database engine - - Not compatible Microsoft SQL Server 2012 BI SP1 (x64) RTM 6.0.0.809 Compatible Microsoft SQL Server 2012 Standard SP1 (x64) RTM 6.0.0.809 Compatible Office 2013 C2R (stand-alone)(Cached-Exchange Mode Only) RTM 6.0.0.809 Compatible Office 2013 C2R (side-by-side with Office 2010)(Cached-Exchange Mode Only) RTM 6.0.0.809 Compatible Office 2013 SP1 (Cached-Exchange Mode Only) Update Rollup 2 6.0.0002.0043 Compatible Office 2013 SP1 with CRM 2013 SP1 (Cached-Exchange Mode Only) Service Pack 1 6.1.0000.0581 Compatible Windows 8.1 Update Rollup 2 6.0.0002.0043 Compatible Windows 8.1 w/ update KB2919355 (web client only) Update Rollup 3 6.00.0003.0106 Compatible Windows Server 2003 - - Not compatible Windows Server 2008 Standard SP2 (x64) RTM 6.0.0.809 Compatible Windows Server 2008 Standard R2 SP1 RTM 6.0.0.809 Compatible Windows Server 2008 Enterprise SP2 (x64) RTM 6.0.0.809 Compatible Windows Server 2008 Enterprise R2 SP1 RTM 6.0.0.809 Compatible Windows Server 2008 Datacenter SP2 (x64) RTM 6.0.0.809 Compatible Windows Server 2008 Datacenter R2 SP1 RTM 6.0.0.809 Compatible Windows Web Server 2008 Datacenter SP2 (x64) RTM 6.0.0.809 Compatible Windows Web Server 2008 Datacenter R2 SP1 RTM 6.0.0.809 Compatible Windows Server 2012 Foundation - - Not compatible Windows Server 2012 Essentials - - Not compatible Windows Server 2012 Datacenter RTM 6.0.0.809 Compatible Windows Server 2012 Standard RTM 6.0.0.809 Compatible Windows Server 2012 R2 (CRM server) Update Rollup 2 6.0.0002.0043 Compatible Windows Small Business Server - - Not compatible

Read more here:
Compatibility with Microsoft Dynamics CRM 2013

Transitioning to the Role Based Access Control (RBAC) model in Exchange Server 2013

This article contains information about the transition to the Role Based Access Control (RBAC) model in Microsoft Exchange Server 2013.

The RBAC model in Exchange Server 2013 enables more flexibility and functionality. Run-state customers should understand the following information:

How RBAC in Exchange Server 2010 differs from RBAC in Exchange Server 2013

The RBAC model in Exchange Server 2010
  • Customers create universal security groups (USG) in their source environment.
  • USGs are members of a linked role group in the managed environment.
  • The linked role groups are assigned specific management roles that provide access to cmdlets and parameters that are defined in these roles.


RBAC model in Exchange Server 2013

  • Local role groups are deployed to the managed environment.
  • Local role groups are assigned specific management roles that provide access to cmdlets and parameters that are defined in these roles.
  • Administrators are added to local role groups directly in the managed environment.


More information about the RBAC model in Exchange Server 2013

  • Customers can change the baseline roles. This includes creating more limited write scopes.
  • Administrators must have a managed mailbox in order to be added to local role groups. Otherwise, linked role groups should be created.
  • Transition roles that match functionality to Exchange Server 2010 will be deployed to help with the change to the new RBAC model in Exchange Server 2013. The customer can remove them when they are no longer needed.

Transition process

As a part of the transition to Exchange Server 2013 or the service on-boarding process, an administrator is added to the SSA-Role Management role group. Members of this role group let customers populate all other role groups and change the baseline RBAC configuration as necessary.

When a customer is transitioned from Exchange Server 2010, the legacy RBAC groups remain. Transition to the new RBAC model can be completed at the customer’s discretion. These legacy role groups can’t be configured in any way, and there may be a limitation in functionality in the Exchange admin center (EAC). All commands that use Remote PowerShell continue to function.  

There are many advantages to the new roles. Customers are urged to move to the new model for the available customization options, full functionality in the EAC, and additional cmdlets and parameters. 

Article ID: 2920204 – Last Review: September 30, 2014 – Revision: 4.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

See the original post:
Transitioning to the Role Based Access Control (RBAC) model in Exchange Server 2013

OrgDBOrgSettings tool for Microsoft Dynamics CRM

Option Name Default Value Type Description Min Supported Version Max Supported Version ActivityConvertDlgCampaignUnchecked True Boolean Controls the default value of the Record Closed Campaign Response option. When you convert an activity to an opportunity, this default option controls whether the source campaign is set or not.

False- Record Closed Campaign Response checked and source campaign will be set.

True - Record Closed Campaign Response not checked and source campaign is not set.

5.0.9690.2720 6.9.9999.9999 ActivateAdditionalRefreshOfWorkflowConditions False Boolean Enables an additional refresh of workflows that contain wait conditions and that may have to be resumed. This is required to be enabled to enable a fix that was originally released as a Critical On Demand hotfix, and was publically released starting with Update Rollup 13. When events in a Wait Until condition are met, the condition is not triggered as documented in KB 2918320

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

. 5.0.9690.3445 5.0.9690.3731 AddressBookMaterializedViewsEnabled True Boolean Changes the way the CRM Client queries SQL CE 5.0.9690.2903 6.9.9999.9999 AutoCreateContactOnPromote True Boolean Disables the ability of the organization to create contact records automatically when an email message is tracked in CRM. This option can also be disabled from the user settings area for each user.

False - Disables the automatic creation of contacts.

True - Enables the autoatic creation of contacts.

5.0.9688.583 6.9.9999.9999 BackgroundSendBatchSize 10 Int Sets the number of email messages to download in one batch for the BackgroundSend API. 5.0.9690.583 6.9.9999.9999 ChangeDoubleQuoteToSingleQuote False Boolean Changes double quotation marks to single quotation marks within KB articles when the article is viewed. 5.0.9690.3541 6.9.9999.9999 ClientDisableTrackingForReplyForwardEmails False Boolean Enables a user not to automatically track replies and forwarded email messages. Set this to ”True” to disable tracking replies and forwarded email messages.  5.0.9690.2903 6.9.9999.9999 ClientUEIPDisabled False Boolean Disables the sending of customer experience feedback for the organization. This option can also be disabled from the user settings area for each user.

False - Enables the sending of experience feedback.

True - Disables the sending of experience feedback.

5.0.9688.583 6.9.9999.9999 DisableImplicitSharingOfCommunicationActivities False Boolean Changing this to “True” will disable implicit sharing of records to recipients that are added to existing activities. 5.0.9690.2903 6.9.9999.9999 DisableInactiveRecordFilterForMailMerge False Boolean When you perform a mail merge, inactive records are not included. This option lets you override that functionality.

False - Inactive records will not be included in the mail merge.

True - Inactive records will be included in the mail merge.

5.0.9688.583 6.9.9999.9999 DisableMapiCaching False Boolean When this value is set to “True,” users can still pin the views. However, the query is sent to the CRM Server to retrieve the results instead of to the local cache to prevent performance issues.  

Note This value is not valid with CRM 2013.

5.0.9690.2903 6.9.9999.9999 DisableSmartMatching False Boolean Disables the smart matching functionality and relies on the tracking token on the incoming e-mails for email tracking.

False - Enables smart matching.

True - Disables smart matching.

5.0.9688.583 6.9.9999.9999 DoNotIgnoreInternalEmailToQueues False Boolean If you disable the “Track email sent between CRM users as two activities” setting, email messages from a CRM user to a queue are not delivered. Additionally, if a workflow rule sends an email message to a queue, email messages that are sent by the workflow rule are not delivered.

False - Internal email messages to queues will not be delivered.

True - Internal email messages to queues will be delivered.

5.0.9690.1533 6.9.9999.9999 EnableQuickFindOptimization 1 Int For more information, see the ”Optimizing the Performance of Quick Find Queries” section in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure

(http://go.microsoft.com/fwlink/?LinkID=213093)

. 5.0.9690.2720 6.9.9999.9999 EnableRetrieveMultipleOptimization 1 Int For more information, see the ”Optimizing the Performance of Queries against Large Datasets section” in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure

(http://go.microsoft.com/fwlink/?LinkID=213093)

. 5.0.9690.1533 6.9.9999.9999 EnableReLinkingToExistingCRMRecord 0 Int Enables a user to re-track contact records. 5.0.9690.3445 6.9.9999.9999 GrantSharedAccessForMergeToSubordinateOwner True Boolean To turn this setting off, this must be set to false. Records are shared with inherited access to subordinate owners during merge. This will not occur when set to false. 5.0.9690.3911 6.9.9999.9999 IdsCountBeforeUsingJoinsForSecurity 1000 Int Not documented in optimization paper. 5.0.9690.2720 6.9.9999.9999 IdsCountForUsingGuidStringsForSecurity 20 Int Not documented in optimization paper. 5.0.9690.2720 6.9.9999.9999 JumpBarAlphabetOverride null String How to customize the Alphabet Bar for the CRM Application Grids for Microsoft Dynamics CRM 4.0

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

5.0.9690.2243 6.9.9999.9999 JumpBarNumberIndicatorOverride null String How to customize the Alphabet Bar for the CRM Application Grids for Microsoft Dynamics CRM 4.0

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

5.0.9690.2243 6.9.9999.9999 LookupNameMatchesDuringImport False Boolean Importing a solution that was created from an upgraded 4.0 deployment fails. Changing this setting makes the import solution look up the names for forms, views, workflows and security roles. 5.0.9690.583 6.9.9999.9999 OverrideTrackInCrmBehaviour 0 Int When this option is Enabled, the “Track in CRM” button functions as the Set Regarding button.

0 - Normal behavior of the “Track in CRM” button not having to set a Regarding record. 

1 - The “Track in CRM” button functions as the “Set Regarding” button, and makes you select a regarding record.

5.0.9690.2720 6.9.9999.9999 OverrideV5SenderConflictResolution False Boolean When multiple records with the same email address exist in the Dynamics CRM Organization and email is automatically tracked, the email address is resolved to the record that was created first. This option lets you override that functionality.

False - E-mails are tracked to the first record created.

True - E-mails are not tracked automatically if there are multiple records with the same email address.

5.0.9690.2243 6.9.9999.9999 RecordCountLimitToSwitchToCteSecuritySql 75000 Int For more information see the Optimizing the Performance of Queries against Large Datasets” section in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure

(http://go.microsoft.com/fwlink/?LinkID=213093)

. 5.0.9690.2720 6.9.9999.9999 RetrieveMultipleSharingCountThreshold 1000 Int For more information, see the ”Optimizing the Performance of Queries against Large Datasets section” in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure

(http://go.microsoft.com/fwlink/?LinkID=213093)

. 5.0.9690.2720 6.9.9999.9999 SendEmailSynchronously 0 Int If you have a plugin registered on the email send flow, you should change this setting to ”1.” 

0 - Email is sent asynchronously.

1 – Email is sent synchronously.

5.0.9690.2720 6.9.9999.9999 SetRegardingLookupDefaultEntityType null String Changes default entity for Regarding Lookup Dialog. 5.0.9690.2835 5.0.9999.9999 SharingLimitForPOASnapshotTable 10 Int Not documented in optimization paper. 5.0.9690.2720 6.9.9999.9999 SkipGettingRecordCountForPaging False Boolean Disables the record count query. This query is responsible for retreiving the total number of records returned for each view. This query can cause longer search times and may cause SQL timeouts or exceptions.

False - Enables record depend on views.

True - Disables record depend on views.

5.0.9690.1992 6.9.9999.9999 SkipSuffixOnKBArticles False Boolean Disables the suffix from being used on the automatically generated KB article numbers.

False - Enables the suffix on KB articles.

True - Disables the suffix on KB articles.

5.0.9690.1992 6.9.9999.9999 UsePlainTextForEmailTemplateBody False Boolean Changes the Email Template to use plain text where otherwise text with the following symbols would not appear . 5.0.9690.2720 6.9.9999.9999 VerboseErrorsOnPromoteToCRM 0 Int Enables verbose user error messaging when tracking items from Outlook to Dynamics CRM. By default, some error messages during the tracking are suppressed from being shown to the end-user, and this setting enables those errors to be shown.

0 - Disables the verbose errors.

1 – Enables the verbose errors.

5.0.9690.2165 6.9.9999.9999 IntegratedAuthenticationMethod null String Changes the request sent to the ADFS server. This changes the authentication when users access the org by using the context https://internal.domain.com/org.
Integrated – urn:federation:authentication:windows
Forms – urn:oasis:names:tc:SAML:1.0:am:password 5.0.9690.2835 6.9.9999.9999 IfdAuthenticationMethod null String Changes the request sent to the ADFS server. This changes the authentication when users access the org by using the context https://org.domain.com.
Integrated – urn:federation:authentication:windows
Forms – urn:oasis:names:tc:SAML:1.0:am:password 5.0.9690.2835 6.9.9999.9999

More:
OrgDBOrgSettings tool for Microsoft Dynamics CRM

Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

After October 26, 2014, Exchange Server users who are in Russian time zones may see the one of following issues in the Calendar.
Microsoft Exchange Server 2007 users

Meeting times might be incorrect, and time zone display names will be outdated after October 26, 2014, even if you have installed the 2014 time zone update for Russia (KB 2998527)

(http://support2.microsoft.com/kb/2998527)

for the Windows Server that hosts the Exchange Server.

Microsoft Exchange Server 2010 and Microsoft Exchange Server 2013 users

Time zone display names will be outdated after October 26, 2014. Meeting times will be updated if you install the 2014 time zone update for Russia (KB 2998527)

(http://support2.microsoft.com/kb/2998527)

for the Windows Server. Exchange Server 2010 and Exchange Server 2013 rely on Windows for time zone information.

For more information about the changes in Russian time zone, see Announcement: Update for Russian time zone changes

(http://blogs.technet.com/b/dst2007/archive/2014/08/22/announcement-update-for-russian-time-zone-changes.aspx)

.

Microsoft is planning to release updates in the middle of November that fix these issues. The fixes are expected in the following updates:
  • Update Rollup 15 for Exchange Server 2007 Service Pack 3
  • Update Rollup 8 for Exchange Server 2010 Service Pack 3
  • Cumulative Update 7 for Exchange Server 2013

Article ID: 3004235 – Last Review: September 30, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
kbsurveynew kbtshoot kbexpertiseinter KB3004235

See the article here:
Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

Mail-routing problems in Office 365 Dedicated/ITAR

Microsoft Office 365 Dedicated/ITAR users who are synchronized to Microsoft Azure Active Directory (Azure AD) experience email-routing problems. 
This issue occurs if one of the following conditions occurs:
  • The mailbox is configured incorrectly.
  • The domain that’s associated with the email address is not externally routable through Domain Name System (DNS). Or, the domain is included in an outbound connector in Microsoft Exchange Online Protection (EOP).
The TargetAddress attribute is synchronized from the customer Active Directory service to the object in the Azure AD. This attribute is used by EOP to route mail. If the TargetAddress attribute differs from the customer domain, mail is routed to the target address. 

Review the configuration of the TargetAddress attribute in the source Active Directory service, the managed Active Directory service, and Azure AD to make sure that each is configured to route mail correctly.

Article ID: 3004254 – Last Review: September 29, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Read the original post:
Mail-routing problems in Office 365 Dedicated/ITAR

Page 1 of 74112345...102030...Last »

Recent Comments

    Archives

    Categories