Archive

Posts Tagged ‘Messaging’

To Edge or Not to Edge? …That is the Question

October 12, 2010 Comments off

Good Discussion on this topic at Linked in is HERE

Elan Sudnow Wrote: “..It’s based on business and technical drivers. Each solution needs to fit a need. Does the current solution in the environment provide adequate capabilities to meet those needs? If the answer is no, then the Exchange Edge may benefit your organization….”

Edge Role – HMC & Exchange 2010 SP1 Hosting:

I see that in the new EX2010 SP1 Hosting that the Edge Role is no longer supported.
What’s not available in Exchange 2010 SP1 Hosting Mode…..
http://technet.microsoft.com/en-us/library/ff923272.aspx

Implement.com SI Wrote….
“…HMC 4.5 replaced the Edge Server Role with Internet Facing HUB Servers. This was primarily due to the Accepted Domain and Email Address replication delays associated with getting up to date values out to the Edge Servers and also the Edge Cache refresh which combined meant it could be up to 8 hours for Edge servers to start accepting email for a new organization or email address. Most Service Providers found this to be unacceptable and so never deployed the Edge Role…”

Interesting blog post here on Mail Transport…
http://blogs.technet.com/b/provtest/archive/2010/07/27/exchange-server-2010-sp1-beta-hosting-deployment-part-7-transport-segregation.aspx

msexchange.org topic on Edge for AS

E2010 Calculator, Megacycles, SPECInt2006, and Cores…Huh?

October 12, 2010 Comments off

Taken from….
http://msexchangeteam.com/archive/2010/10/11/456573.aspx

“…Since the release of v12.8 of the Exchange 2010 Mailbox Server Role Calculator, I have received several questions with regards to the changes in the processor input section.
In particular, the one question that keeps coming up is “Why doesn’t the CPU results change when I change the number of cores (e.g., change from 12 cores to 6 cores)?”
The answer is relatively simple: you didn’t change the SPECInt2006 Rate value when you changed the number of total cores that are in the system. Remember that the SPECInt2006 Rate value is a function of the server’s architecture, processor architecture, and the number of processors being deployed in the server. The same server with 1 processor versus 2 processors will have completely different SPECInt2006 Rate values…”

Exchange 2010 Calculator v12.8 can be downloaded HERE

Can I get a Witness – Part Deux

October 12, 2010 Comments off

Witness server requirements.. Taken from: Technet-Planning for High Availability and Site Resilience#Witness Server Requirements

A witness server is a server outside of a DAG that’s used to achieve and maintain quorum when the DAG has an even number of members. DAGs with an odd number of members do not use a witness server. All DAGs with an even number of members will use a witness server. The witness server can be any computer running Windows Server. There is no requirement that the version of the Windows Server operating system of the witness server match the operating system used by the DAG members.

Quorum is maintained at the cluster level, underneath the DAG. A DAG has quorum when the majority of its members are online and can communicate with the other online members of the DAG. This notion of quorum is one aspect of the concept of quorum in Windows failover clustering. A related and necessary aspect to quorum in failover clusters is the quorum resource. The quorum resource is a resource inside a failover cluster that provides a means for arbitration leading to cluster state and membership decisions. The quorum resource also provides persistent storage for storing configuration information. A companion to the quorum resource is the quorum log, which is a configuration database for the cluster. The quorum log contains information such as which servers are members of the cluster, what resources are installed in the cluster, and the state of those resources (for example, online or offline).

“…It is critical that each DAG member have a consistent view of how the DAG’s underlying cluster is configured. The quorum acts as the definitive repository for all configuration information relating to the cluster. The quorum is also used as a tie-breaker to avoid “split-brain” syndrome. Split brain syndrome is a condition that occurs when DAG members cannot communicate with each other but are up and running. Split brain syndrome is prevented by always requiring a majority of the DAG members (and in the case of DAGs with an even number of member, the DAG witness server) to be available and interacting for the DAG to be operational….”

Witness Server in two node DAG… Elan Shudnow – How to deploy a two-node Exchange 2010 RTM Database Availability Group (DAG) on Windows Server 2008 R2.

Loads more on File Share Witness Here

Can I get a Witness…

October 12, 2010 Comments off

Busting the Exchange Trusted Subsystem Myth….

The below is taken from the following Blog Post: http://www.thecabal.org/2009/12/busting-the-exchange-trusted-subsystem-myth/

“….I’ve been building a brand new Exchange 2010 lab environment and ran smack into a myth that seems to be making the rounds among people who are deploying Exchange 2010. This myth gives bum advice for those of you who are deploying an Exchange 2010 DAG and not using an Exchange 2010 Hub Transport as your File Share Witness (FSW). I call it the Exchange Trusted Subsystem Myth, and the first hint of it I see seems to be on this blog post. However, that same advice seems to have gotten around the net, as evidenced by this almost word-for-word copy or this posting that links to the first one. Like many myths, this one is pernicious not because it’s completely wrong, but because it works even though it’s wrong.

If you follow the Exchange product group’s deployment assumptions, you’ll never run into the circumstance this myth addresses; the FSW is placed on an Exchange 2010 HT role in the organization. Although you can specify the FSW location (server and directory) or let Exchange pick a server and directory or you, the FSW share isn’t created during the configuration of the DAG (as documented by fellow Exchange MVP Elan Shudnow and the “Witness Server Requirements” section of the Planning for High Availability and Site Resilience TechNet topic). Since it’s being created on an Exchange server as the second member of the DAG is joined, Exchange has all the permissions it needs on the system to create the share. If you elect to put the share on a non-Exchange server, then Exchange doesn’t have permissions to do it.

Hence the myth:

** Add the FSW server’s machine account to the Exchange Trusted Subsystem group.
** Add the Exchange Trusted Subsystem group to the FSW server’s local Administrators group.

The sad part is, only the second action is necessary.

True, doing the above will make the FSW work, but it will also open a much wider hole in your security than you need or want….”

Dude, wheres my Exchange GUI Gone!

October 11, 2010 Comments off

No EMC in Exchange 2010 Hoster

No EMC in Exchange 2010 Hoster

Install Exchange 2010 Hosting and its PowerShell only for you my friend….
http://blogs.technet.com/b/provtest/archive/2010/06/25/exchange-server-2010-sp1-beta-hosting-deployment-the-first-look-part-1.aspx

%d bloggers like this: