Exchange Online and Exchange Server 2010
Exchange Server 2010 was designed from the ground up for services. Its rollout will enhance the capabilities of Exchange Online: lighting up new features, giving you more control over your hosted e-mail environment, and improving coexistence between hosted and on-premises Exchange deployments.
A beta of the Exchange Online service powered by Exchange Server 2010 will be available to businesses in the second half of this year. Organizations that move to Exchange Online today will benefit from an easy migration to the new version of the service, enjoying an “evergreen deployment” that gives administrators and users access to the latest Exchange capabilities.
Deployment choice and flexibility
Because Exchange Server is available both as on-premises software and a hosted service, you have the freedom to choose the right deployment option for your organization. Regardless of whether you choose to deploy Exchange Server on-premises, host your mailboxes with Exchange Online, or combine these two options in a hybrid deployment, your employees will have messaging and collaboration tools that maximize their productivity. Exchange enables your business needs, rather than technology constraints, to drive the choice.
Search This Blog
Custom Search
Thursday, June 4, 2009
Tuesday, June 2, 2009
Update Rollup 8 for Exchange Server 2007 Service Pack 1 release announcement!
A few key ones which I would like to call out are as follows:
KB 969690 - Ffixed the bug introduced in Update Rollup 7 which caused the sender of the Delivery Status Notification (DSN) to be unresolved.
Disable kernel mode authentication in Windows Server 2008 for CAS servers - As documented here, it was required to manually take the additional step to configure the CAS servers running Windows Server 2008 to disable kernel mode authentication. Starting this rollup, the installer will configure this for you.
X-Header promotion to named properties- Change to the way X-headers are promoted to named properties. More on this in Jason Nelson's blog post Named Properties, X-Headers, and You.
KB 961606 - We have fixed a bug where Outlook Web Access (OWA) users may find that the font size of plain text messages is extremely small on third-party Web browsers.
KB 968012 has more details about this release and a complete list of all fixes included in this rollup.
As a follow up to the Exchange Server 2007 Service Pack 2 (SP2) announcement, all fixes in this Update rollup and the previous ones we have released for Exchange Server 2007 will be included with Exchange Server 2007 SP2. We will have a blog post soon which covers:
When update rollups can be expected for Exchange 2007 SP2.
Support plans for Exchange 2007 SP1 which will be in support as per the timeline in Microsoft's Service Pack Support Policy.
KB 969690 - Ffixed the bug introduced in Update Rollup 7 which caused the sender of the Delivery Status Notification (DSN) to be unresolved.
Disable kernel mode authentication in Windows Server 2008 for CAS servers - As documented here, it was required to manually take the additional step to configure the CAS servers running Windows Server 2008 to disable kernel mode authentication. Starting this rollup, the installer will configure this for you.
X-Header promotion to named properties- Change to the way X-headers are promoted to named properties. More on this in Jason Nelson's blog post Named Properties, X-Headers, and You.
KB 961606 - We have fixed a bug where Outlook Web Access (OWA) users may find that the font size of plain text messages is extremely small on third-party Web browsers.
KB 968012 has more details about this release and a complete list of all fixes included in this rollup.
As a follow up to the Exchange Server 2007 Service Pack 2 (SP2) announcement, all fixes in this Update rollup and the previous ones we have released for Exchange Server 2007 will be included with Exchange Server 2007 SP2. We will have a blog post soon which covers:
When update rollups can be expected for Exchange 2007 SP2.
Support plans for Exchange 2007 SP1 which will be in support as per the timeline in Microsoft's Service Pack Support Policy.
Maximum number of members in a Distribution Group?
We frequently get this question in many newsgroups and forums - what's the maximum number of members you can add to a Distribution group? The member attribute of groups - both Distribution and Security groups, is a multi-valued attribute. So the answer is more about how many values can a multi-valued Active Directory attribute hold.
Many of you may remember the recommendation of 5000 values in a multi-valued attribute in Windows 2000, and the fact that the limitation no longer exists in subsequent versions. So what's the actual limit? Or is there a limit at all?
To find out more, we queried our friends in the Directory Services team, who quickly researched it and added this information to Active Directory Maximum Limits. The doc, which answers all kinds of questions about maximum limits and recommendations, has some interesting factoids:
Maximum number of objects in Active Directory: A little less than 2.15 billion
Maximum number of SIDs in a domain: About 1 billion
Maximum number of group memberships for Security Principals: 1015*This is for Security groups. Each Security group you're a member of results in its SID being added to your access token at logon.
The doc provides more nuanced answers, recommendations, and workarounds to overcome some limitations, for those times when you absolutely must create more than 2 billion AD objects.
Many of you may remember the recommendation of 5000 values in a multi-valued attribute in Windows 2000, and the fact that the limitation no longer exists in subsequent versions. So what's the actual limit? Or is there a limit at all?
To find out more, we queried our friends in the Directory Services team, who quickly researched it and added this information to Active Directory Maximum Limits. The doc, which answers all kinds of questions about maximum limits and recommendations, has some interesting factoids:
Maximum number of objects in Active Directory: A little less than 2.15 billion
Maximum number of SIDs in a domain: About 1 billion
Maximum number of group memberships for Security Principals: 1015*This is for Security groups. Each Security group you're a member of results in its SID being added to your access token at logon.
The doc provides more nuanced answers, recommendations, and workarounds to overcome some limitations, for those times when you absolutely must create more than 2 billion AD objects.
Subscribe to:
Posts (Atom)