Change page: < 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 >  |  Displaying page 9 of 15, items 241 to 270 of 433.

Exchange Server 2010 : Designing Upgrade and Coexistence Strategies Whether you are upgrading from Exchange Server 2003 or Exchange Server 2007, the upgrade process, in a nutshell, is similar

Exchange Server 2010 : Risk Mitigation Achieving high availability requires that risks are identified and addressed. Many organizations employ risk management practices to capture and address potential disruptions to business processes.

Exchange Server 2010 : Planning Cross-site Failovers (part 2) - Cross-site Switchover Deploying a DAG across two sites can allow database copies to exist in two locations and provide site resiliency. This allows a single mailbox database to fail over and switch over to the secondary site.

Exchange Server 2010 : Planning Cross-site Failovers (part 1) The high-availability improvements in Exchange 2010 make it even easier to deploy cross-site failover solutions without a need for third-party network and storage solutions.

Exchange Server 2010 : Availability Planning for Transport Servers Within the Exchange organization, it is important to deploy multiple transport servers to provide message path redundancy. Deploying multiple Hub Transports in each Active Directory site automatically provides redundancy and load balancing for message delivery.

Exchange Server 2010 : Availability Planning for Client Access Servers (part 4) - Creating a Client Access Server Array Using a load-balancing product will allow you to load-balance connectivity across the Client Access servers for all communication types. To represent the RPC Client Access load-balanced cluster in a single Active Directory site a Client Access array is created.

Exchange Server 2010 : Availability Planning for Client Access Servers (part 3) - Global Server Load Balancing Global server load balancing (GSLB), or wide-area load balancing, is a more sophisticated version of DNS round robin available from some hardware load balancer vendors.

Exchange Server 2010 : Availability Planning for Client Access Servers (part 2) - Selecting a Load Balancer Type To lower cost and complexity, you should select a single load-balancing solution that works for each type of traffic. A large number of load-balancing options are available on the market; it is important to make an informed choice

Exchange Server 2010 : Availability Planning for Client Access Servers (part 1) - Affinity Some Exchange communications are stateful, meaning the application requires that the communication context be maintained with the same host until the session is completed.

Using asynchronous services in BizTalk with WCF (part 2) - Exposing asynchronous services Exposing BizTalk processes through asynchronous channels is also a clear-cut task. Once again, you cannot expose WCF service from BizTalk that have the isOneWay attribute set to True

Using asynchronous services in BizTalk with WCF (part 1) - Consuming asynchronous services BizTalk Server natively promotes an asynchronous messaging pattern and readily embraces an event driven architecture. What BizTalk adds to the standalone WCF patterns we've seen above is the injection of a message broker. This middle layer loosely couples the enterprise systems on both ends of the service call while enabling a new set of messaging capabilities not available in standard service implementations.

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 8) - Designing and Configuring DAGs When deploying a CCR environment in Exchange 2007, the sizing was straightforward—the databases were running on one node or the other. In Exchange 2010, which offers you the ability to have 16 members with up to 1,600 databases, sizing and designing the layout is far more complex.

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 7) - Managing Database Copies You can use a number of cmdlets to manage database copies. Understanding the function of each is essential to being able to manage database copies.

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 6) - Controlling Database Activation In large environments you may want to limit which servers can host an active database in the event of a failure so that a database is not brought online in a secondary datacenter if you are performing maintenance on a server or the database is a lagged copy

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 5) - Mailbox Database Activation When an active database failure occurs, Active Manager uses a set of selection criteria to determine which copy should be activated.

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 4) - DAG Networks A DAG network is a set of subnets that can be configured for replication or MAPI communication. Exchange supports the use of a single network adapter and path for DAG members

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 3) - Adding Database Copies Creating a database availability group is just the first step in making a database highly available. A database that exists on one of the DAG members must be set up with additional copies on other DAG members

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 2) - Active Manager Windows failover clustering is not used to replicate or manage the active database copies in a DAG; however it is used to store information for several pieces of volatile information about the DAG such as the state of active database copies

Exchange Server 2010 : Availability Planning for Mailbox Servers (part 1) In addition to normal IT best practices and redundant hardware, the DAG is the primary high-availability option for Exchange 2010 Mailbox servers. A DAG is a collection of servers that provides continuous replication and availability for mailbox databases

Exchange Server 2010 : Achieving High Availability A number of barriers stand in the way of achieving high availability. For example, a poor implementation of Exchange might be one where Exchange is installed on improperly sized servers and installed without following best practices.

BizTalk Server 2009 : Using asynchronous services in WCF (part 3) - Building a client-side asynchronous experience Now that our synchronous service is up and running, let's see how we interact with it from the client perspective. Go ahead and add a new Console Application Add a new Service Reference

BizTalk Server 2009 : Using asynchronous services in WCF (part 2) Notice that we have a single, synchronous service operation defined. This operation accepts an adverse event, and returns the resulting action that the submitter should take.

BizTalk Server 2009 : Using asynchronous services in WCF (part 1) - Creating the synchronous service We start out by creating a new, empty Visual Studio.NET 2008 solution. Then we add a project of type WCF Service Library to the solution. This project type automatically adds an interface class, service class, and application configuration file

Exchange Server 2010 : Troubleshooting Federated Delegation (part 3) - Troubleshooting Calendar and Contacts Sharing Although Calendar and Contacts do not use organization relationships, they do depend on having valid federation trusts in place in both organizations for two-way sharing.

Exchange Server 2010 : Troubleshooting Federated Delegation (part 2) - Troubleshooting Organization Relationships The Get-FederationInformation cmdlet is arguably the most important tool in troubleshooting existing organization relationships as well as establishing new ones.

Exchange Server 2010 : Troubleshooting Federated Delegation (part 1) - Troubleshooting the Federation Trust The EMS cmdlet named Test-FederationTrust verifies several aspects of your federation with the Microsoft Federation Gateway. This cmdlet must be run from either an Exchange Server 2010 Hub Transport or Client Access server

Exchange Server 2010 : Federation Scenarios (part 3) - Federating with Online Services Federation and federated delegation are also used in a cross-premises scenario where an organization hosts some mailboxes on-site and hosts others in the Exchange Online service

Exchange Server 2010 : Federation Scenarios (part 2) - Calendar and Contacts Sharing The sharing of Calendars and/or Contacts with users in external Exchange Server 2010 organizations is accomplished on a per-user basis, between a user in your organization and someone in an external Exchange Server 2010 organization.

Exchange Server 2010 : Federation Scenarios (part 1) - Free/Busy Access Let's see how the basic principles of federation and federated delegation and the various components and fundamentals of federated delegation in Exchange Server 2010 all fit together. We'll do this by covering the various federation scenarios in an Exchange Server 2010 environment, and the advantages and drawbacks to each of them.

Active Directory Domain Services 2008: View Settings Defined in Password Settings Objects You need to determine the settings that are applied in a PSO.