CAS Array and DNS Round Robin. Ok, we've got this setup, but we are having some issues with Outlook clients connecting to the Cicso server load balancer. It says it can't find the Exchange server. Here are the details of our config.... --CASArray1 was setup with mail.qa-na.qa-intranet.msd as the FQDN--The Exchange MDBs are setup for the RPCClientAccessServer to point to the CASArray1 (and show the FQDN as expected for this attribute)--We have an A record in DNS for the mail.qa-na.qa-intranet.msd that points to the Cisco load balancer VIP address and it resolves on the workstations and servers fine. --We have all ports open on this load balancer and have not restricted any ports--We can see the Outlook clients hitting the load balancer on port TCP 135, RPC 1580, 1581 and others (not 443 like I expected) but still don't connect to the CAS server.
I found the technote ... HELP...and thanks! Understanding Recoverable Items: Exchange 2010 SP1 Help. Applies to: Exchange Server 2013 Topic Last Modified: 2012-12-11 To protect from accidental or malicious deletion and to facilitate discovery efforts commonly undertaken before or during litigation or investigations, Microsoft Exchange Server 2013 uses the Recoverable Items folder. The Recoverable Items folder replaces the feature known as the dumpster in Exchange Server 2007. The Recoverable Items folder is used by the following Exchange features: Deleted item retention Single item recovery In-Place Hold Litigation hold Mailbox audit logging Calendar logging Contents Knowledge of the following terms will help you understand the content in this topic.
Delete Describes when an item is deleted from any folder and placed in the Deleted Items default folder. Soft delete Describes when an item is deleted from the Deleted Items default folder and placed in the Recoverable Items folder. Hard delete Describes when an item is marked to be purged from the mailbox database. Understanding Retention Tags and Retention Policies.
Applies to: Exchange Server 2013, Exchange Online Topic Last Modified: 2013-01-24 In Microsoft Exchange Server 2013, Messaging records management (MRM) helps organizations to manage email lifecycle and reduce legal risks associated with e-mail and other communications. MRM makes it easier to keep messages needed to comply with company policy, government regulations, or legal needs, and to remove content that has no legal or business value. Contents MRM in Exchange 2013 is accomplished by using retention tags and retention policies. Assigning retention policy tags (RPTs) to default folders, such as the Inbox and Deleted Items. The following figure illustrates the tasks involved in implementing this strategy. The following table shows requirements for the Mailbox server and client application. Retention tag and retention policy requirements There are three types of retention tags: Default policy tags DPTs apply to untagged mailbox items in the entire mailbox.
Eliminating Traditional Backups using native Exchange 2010 Functionality (Part 3) If you would like to read the other parts of this article series please go to Introduction In part 2 of this multi-part article, we had a quick look at the litigation hold feature and from there jumped over and took a step by step look at how easy it is to recover mail items for a user using the new mailbox search feature in Exchange 2010. In this part 3, I will provide you with the gory details on how and why you might be one of the organizations that can benefit from using lagged database copies. In addition, I will also show you how to configure lagged databases copies in a step by step fashion. Lagged Database Copies In addition to being able to replicate data to multiple targets per storage group, SCR also introduced the concept of replay lag time and truncation lag time. With replay lag time you could configure the Microsoft Exchange Replication service to wait for a specified amount of time before log files that had been copied from the SCR source to the SCR target(s) were replayed.
Eliminating Traditional Backups using native Exchange 2010 Functionality. If you would like to read the other parts of this article series please go to: Introduction Most Exchange customers use a traditional disk or tape based backup solution to backup critical Exchange data. There are two main reasons why this is the case. First, because that’s the way they always did it. Secondly, because this is how all other Exchange customers backup Exchange data. Back when enterprises upgraded or migrated to Exchange 2003 and in most cases consolidated their Exchange messaging infrastructure, they at the same time invested in expensive high-end SAN solution that were used to store Exchange and other application data. Because of the storage requirements as well as memory limits, an Exchange 2003 server typically did not store more than a maximum of 4000 mailboxes.
Because of the storage costs, user’s also had very strict mailbox limits. When it came to backing up Exchange 2007, enterprises still use either a disk or tape based point in time back solution.
You Had Me At EHLO... : Top 10 Exchange Storage Myths. Managing POP3 and IMAP4: Exchange 2010 SP1 Help. Exchange 2003 - Planning Roadmap for Upgrade and Coexistence: Exchange 2010 SP1 Help. Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2 Topic Last Modified: 2012-07-23 You can deploy Microsoft Exchange Server 2010 in an existing Microsoft Exchange Server 2003 organization operating in native mode. Coexistence with these two Exchange versions is supported. This topic provides an overview of the planning considerations and configuration steps that you must take when Exchange 2010 will coexist with Exchange 2003. Any organization upgrading from Exchange 2003 will experience a period of coexistence. In a coexistence scenario, any combination of the following versions of Microsoft Exchange is deployed in a single Exchange organization: Exchange 2003, Exchange 2007, and Exchange 2010.
This topic is concerned primarily with the coexistence of Exchange 2003 and Exchange 2010. In a coexistence scenario, multiple versions of Exchange communicate with each other and share data resources, recipient information, and configuration information. . © 2010 Microsoft Corporation.
Releases improved CPU2006 benchmark. Large number of upgrades in V1.1 add up to significant new release WARRENTON, Va., June 3, 2008 - The Standard Performance Evaluation Corp. has released a new version of SPEC CPU2006 with improvements that impact nearly everyone who uses the benchmark or will potentially use it. SPEC's CPU benchmarks have been the worldwide standard for measuring compute-intensive performance since 1989.
"V1.1 includes dozens of incremental upgrades that add up to a significant new release," says Jeff Reilly, SPEC CPU subcommittee chair. "There are changes and additions that address the needs of practically every segment of the CPU benchmarking community. " Improvements in SPEC CPU2006 V1.1 include: Greater portability – New code makes it easier to move the benchmarking setup from one system to another without recompiling, and updates have been made to 12 benchmarks to improve portability to new and existing platforms. Results generated by SPEC CPU2006 V1.1 are comparable to results from V1.0. About SPEC.
Understanding Server Role Ratios and Exchange Performance: Exchange 2010 SP1 Help. Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2 Topic Last Modified: 2010-01-26 After you've determined your optimal processor, memory, and disk configurations, you should determine how many server roles of each type are required for your deployment. Every environment is different, so consider these recommendations as starting points that can be tailored to your environment.
Contents Recommended processor core ratio based on server role configuration When considering these recommendations, be aware of the following: The preceding ratios are a general rule (not definitive), and they may not be valid for every topology. To determine how many Edge Transport servers are required, you must measure or estimate the following metrics during peak periods: Connections per second Messages per second Average message size Sizing is based on the number of connections and messages processed, with average message size being a secondary factor.
. © 2010 Microsoft Corporation. TechNet Script Center Repository. Exchangepedia.
Exchange 2010 DAG - Failover selection between sites. SMTP Security. Exchange LDAP. Set-DatabaseAvailabilityGroup: Exchange 2010 Help. Applies to: Exchange Server 2013 Topic Last Modified: 2013-10-14 Use the Set-DatabaseAvailabilityGroup cmdlet to configure properties of a database availability group (DAG). This example sets the witness directory to C:\DAG1DIR for the DAG DAG1. Set-DatabaseAvailabilityGroup -Identity DAG1 -WitnessDirectory C:\DAG1DIR This example preconfigures an alternate witness server of CAS3 and an alternate witness directory of C:\DAGFileShareWitnesses\DAG1.contoso.com for the DAG DAG1. Set-DatabaseAvailabilityGroup -Identity DAG1 -AlternateWitnessDirectory C:\DAGFileShareWitnesses\DAG1.contoso.com -AlternateWitnessServer CAS3 This example configures the DAG DAG1 to use DHCP to obtain an IP address. Set-DatabaseAvailabilityGroup -Identity DAG1 -DatabaseAvailabilityGroupIpAddresses 0.0.0.0 This example configures the DAG DAG1 to use a static IP address of 10.0.0.8.
Set-DatabaseAvailabilityGroup -Identity DAG1 -DatabaseAvailabilityGroupIpAddresses 10.0.0.8 This example configures the DAG DAG1 for DAC mode. 2010 DAG File Share Witness. Migrating from Exchange 2003 to Exchange 2010 | NetworkWorld.com Community. As I covered in my blog post on “The Good, The Bad, and the Ugly in Migrating to Exchange 2010,” I mentioned I would provide more details on the steps needed to migrate from Exchange 2003 to Exchange 2010. In this post, I’m going to outline the sequence and provide tips, tricks, and best practices to look forward to in the migration process. Since the migration from Exchange 2003 to Exchange 2010 is similar if not almost identical to the process of migrating from Exchange 2003 to Exchange 2007, if you have already done your design and plan to migrate to Exchange 2007, you’ll find the process to be similar for getting you to Exchange 2010. The sequence for a migration from Exchange 2003 to Exchange 2010 is as follows: Key to note in the migration process from Exchange 2003 to Exchange 2010 is that many concepts go away such as the concept of routing groups and administrative groups.
Datacenter Switchovers: Exchange 2010 Help. Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2 Topic Last Modified: 2012-02-14 By combining the native site resilience capabilities in Microsoft Exchange Server 2010 Service Pack 1 (SP1) with proper planning, a second datacenter can be rapidly activated to serve the failed datacenter's clients. A datacenter or site failure is managed differently from the types of failures that can cause a server or database failover. In a high availability configuration, automatic recovery is initiated by the system, and the failure typically leaves the messaging system in a fully functional state.
By contrast, a datacenter failure is considered to be a disaster recovery event, and recovery must be manually performed and completed for the client service to be restored, and for the outage to end. There are four basic steps that you complete to perform a datacenter switchover, after making the initial decision to activate the second datacenter: Contents. Understanding Datacenter Activation Coordination Mode: Exchange 2010 Help.
Applies to: Exchange Server 2013 Topic Last Modified: 2013-04-15 Datacenter Activation Coordination (DAC) mode is a property setting for a database availability group (DAG). DAC mode is disabled by default and should be enabled for all DAGs with two or more members that use continuous replication. DAC mode shouldn't be enabled for DAGs in third-party replication mode unless specified by the third-party vendor. If a catastrophic failure occurs that affects the DAG (for example, a complete failure of one of the datacenters), DAC mode is used to control the startup database mount behavior of a DAG. When DAC mode isn't enabled and a failure occurs that affects multiple servers in the DAG, and then when a majority of the DAG members are restored after the failure, the DAG will restart and attempt to mount databases.
For example, consider a scenario where the first datacenter contains two DAG members and the witness server, and the second datacenter contains two other DAG members. Exchange 2010, Creating DAGs and Quorum Shares | www.extropy.com. Database Availability Group (DAG) -Exchange 2010. Database Availability Group (DAG) Now that Exchange 2010 has been officially released and I am allowed to blog on the topic I wanted to start with what I believe is one of the best features added to Exchange 2010. There may be some heart break of the removal of a few features from Exchange 2007 however Database Availability Groups (DAG) is a feature that has been ask for over years. To better under what a DAG is let’s recap through Exchange. Exchange 2007 introduced LCR, CCR, SCC and SCRLCR (local continuous replication) this was mainly used for small business who wanted to replicate a copy of their Exchange database to another disk on the same server. SCC (Single copy cluster) was what I would call a traditional Exchange cluster which used shared storage to host the Exchange database.
Basic architecture of an SCC Basic deployment of CCR How did it use to work? The concept of a DAG and how it functions I believe is easier learned by someone who hasn’t worked with Exchange clusters previously. You Had Me At EHLO... : Updates to the Exchange 2010 Mailbox Ser. Important: The results of the Exchange 2010 calculator are not applicable to Exchange 2013. For instance, the megacycle calculations in Exchange 2010 leverage a different server baseline than those in Exchange 2013, therefore, the two calculations cannot be compared. Version 20.8 Updates Bug Fixes Fixed an error with secondary CAS CPU calculations Version 20.7 Updates Fixed CAS and HT memory calculations formulas to not report #NAME when designing site resilient topologies. Version 20.6 Updates Enhancements Calculator now supports defining server requirements for dedicated Hub Transport and Client Access servers; specifically CPU and memory sizing.Calculator will state how many dedicated Hub Transport and Client Access servers should be deployed in a datacenter.
Version 19.9 Updates Version 18.9 Updates Version 18.2 Updates Version 17.8 Updates Version 17.2 Updates Version 16.5 Updates Fixed an issue with diskpart.ps1 that prevented the script from executing. Version 16.4 Updates Version 14.4 Updates.
Mailbox Server Storage Design: Exchange 2010 Help. Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2 Topic Last Modified: 2011-02-08 Storage design is a critical piece of a successful Microsoft Exchange Server 2010 Mailbox server role deployment. Multiple requirements such as storage performance, capacity, manageability, and cost must all be considered to achieve the optimal storage design for Exchange 2010.
This section covers the storage design process as well as the storage design options, support criteria, and best practices related to the Exchange 2010 Mailbox server role. Information is also provided about required storage inputs and storage testing and validation. Other topics in this section include: © 2010 Microsoft Corporation. Exchange Server 2010, 2007: Articles, Downloads, Support | TechN. Mailbox Server Storage Design: Exchange 2010 Help. Exchange 2010 System Requirements: Exchange 2010 Help. Support Policies and Recommendations for Exchange Servers in Har. New installation of Exchange 2010 - Deployment Checklist – Excha.
You Had Me At EHLO... : Exchange 2007 Mailbox Server Role Storag. You Had Me At EHLO... : Exchange 2010 Mailbox Server Role Requir. Understanding High Availability and Site Resilience: Exchange 20.