Microsoft Certification Examples, exercises, practises, tutorials, solutions about Applications Server

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

Designing and Optimizing Storage in an Exchange Server 2010 Environment : Defining the Technologies

To understand how and when to use technologies such as NAS or SAN, you need to understand what they are and what they offer. The technologies differ in how they are used and what advantages they provide

Active Directory Domain Services 2008: Create Shadow Groups

You recently created a PSO in your domain. You need to apply the PSO to all user accounts located in an organizational unit called New York.

Active Directory Domain Services 2008: View the Resultant Password Settings Objects for a User or Group

You have multiple PSOs defined in your domain. You need to determine the effective PSO for a user account.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2007 (part 3)

To move mailboxes from Exchange Server 2007 to Exchange Server 2010, the Exchange Server 2007 Mailbox server must be running Exchange Server 2007 SP2

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2007 (part 2) - Upgrading Message Connectivity From Exchange Server 2007

Although both Exchange Server 2007 and Exchange Server 2010 use least cost routing, and use Active Directory sites for internal message routing, there are considerations for upgrading to Exchange Server 2010.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2007 (part 1)

You need to apply Exchange Server 2007 SP2 to all Exchange Server 2007 CA and UM servers in your organization prior to installing the first server running Exchange Server 2010.

BizTalk Server 2009 : Using queues within asynchronous scenarios (part 3)

After building and deploying this sample, we need to assemble the necessary messaging ports from within the BizTalk Administration Console. First, import the BizTalk WCF Service Publishing Wizard-generated binding to produce our concluding WCF-NetMsmq adapter send port

BizTalk Server 2009 : Using queues within asynchronous scenarios (part 2)

The MSMQ service endpoint is configured using the netMsmqBinding with the path to the private queue as the service address. As we are hosting our service within IIS 7.0, we do not need a separate MEX endpoint for MSMQ, but rather, can simply apply a standard HTTP metadata behavior to our service.

BizTalk Server 2009 : Using queues within asynchronous scenarios (part 1)

Queue-based technology is an underrepresented but powerful way to exchange data and events between disconnected clients. WCF has full support for Microsoft's queuing implementation and BizTalk has an adapter specifically targeted at the netMsmqBinding WCF binding.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 13) - Removing Legacy Exchange Servers

Although public folder servers can be replicated to Exchange Server 2010 at the same time as the rest of the Exchange Server 2010 infrastructure is implemented, you should retain public folder replicas on Exchange Server 2003 until all mailboxes have been migrated to Exchange Server 2010

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 12) - Planning Public Folder Access and Migration

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 11)

In addition to considering the Outlook version or versions deployed in the environment, you need to consider how recipients are provisioned in Exchange Server 2010 compared to Exchange Server 2003 as well as how e-mail address policies are applied.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 10) - Recipient Update Service Migration

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 9) - Moving Offline Address Books

In Exchange Server 2003 and earlier, offline address books (OABs) were stored in and distributed from public folders—system folders in particular—but Exchange Server 2010 (similar to Exchange Server 2007) can distribute OABs by means of a Web-based distribution method that uses HTTP (or HTTPS) and BITS.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 8)

In Exchange Server 2003, filters for address lists and e-mail address policies were based on LDAP syntax; Exchange Server 2010 uses OPATH filtering syntax. Although LDAP syntax filters are supported in Exchange Server 2010, they must be upgraded to OPATH syntax if you want to edit them in Exchange Server 2010, and LDAP filters can't be created in Exchange Server 2010

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 7) - Coexistence for Management

Coexistence for management includes managing mailboxes on Exchange Server 2003 and Exchange Server 2010, configuring and managing Exchange servers, and organization parameters and message tracking.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 6) - Upgrading Message Connectivity From Exchange Server 2003

This section will cover the issues and best practices surrounding upgrading your messaging connectivity to Exchange Server 2010, including internal and external message routing.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 5)

It is quite common for organizations to have modified OWA in Exchange Server 2003 to meet their organization's needs, and you will want to reflect these modifications in your Exchange Server 2010 deployment as well.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 4)

In your Exchange Server 2003 environment, both free/busy functionality and offline address book distribution are provided by public folders—in particular, system folders. The Availability service in Exchange Server 2010 replaces or supplements the free/busy system folders in Exchange Server 2003, depending on the version of Outlook deployed.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 3)

The Client Access services you should take into account during an upgrade to Exchange Server 2010 includes multiple services and functionalities, not all of which are immediately obvious

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 2)

The first step in preparing your Exchange Server 2003 organization for Exchange Server 2010 is to grant specific Exchange permissions in each domain Exchange Server 2003 computer.

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 1)

Before you install the first Exchange Server 2010 computer, you must take numerous steps to prepare the environment and to ensure proper coexistence between Exchange Server 2010 and Exchange Server 2003.

Exchange Server 2010 : Useful Tools for an Upgrade (part 1)

A new downloadable tool released for Exchange Server 2010 is the Exchange Pre-Deployment Analyzer (ExPDA). This tool provides an Exchange 2010 Readiness Check; previously, the Exchange Server 2007 Readiness Check was provided as part of the downloadable version of the ExBPA.

Exchange Server 2010 : Useful Tools for an Upgrade (part 1)

A number of useful tools are available for planning, deploying, and troubleshooting your upgrade to Exchange Server 2010

Active Directory Domain Services 2008: Modify the Precedence for Password Settings Objects

You have multiple PSOs in your domain that are applied to global security groups. You want to ensure that a particular PSO is always applied to members of the IT Administrators AD DS group.

Active Directory Domain Services 2008: Apply a Password Settings Object to Users and Security Groups

You created a new PSO in your domain. You want to ensure the PSO is applied to all IT administrators.

Active Directory Domain Services 2008: Modify Settings Defined in Password Settings Objects

You previously created a PSO. You need to change the minimum password length in this PSO.

BizTalk Server 2009 : Getting results from asynchronous invocations (part 3)

Before we use this contract in our client code, we should set up the appropriate endpoint in the client application's configuration. In this case, our endpoint contract is the one constructed above, the binding is the wsDualHttpBinding, and the address should match the value specified by our in-process receive location.

BizTalk Server 2009 : Getting results from asynchronous invocations (part 2)

BizTalk has mixed support for WCF-based callbacks. On the receiving side, BizTalk does not have an explicit adapter for the WsDualHttpBinding, but does have "hidden" support for this WCF feature

BizTalk Server 2009 : Getting results from asynchronous invocations (part 1) - Building WCF services that support client callbacks

WCF has rich support for client callbacks and efficiently handles service response events. What you need in order to support duplex patterns is a service contract that requires sessions, and one of the two available duplex bindings in WCF: NetTcpBinding and WSDualHttpBinding.