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 10 of 15, items 271 to 300 of 433.

Active Directory Domain Services 2008: Delete Password Settings Objects

You previously created a PSO in your domain. The PSO is no longer required and you want to prevent it from being used in the future.

Active Directory Domain Services 2008: Create Password Settings Objects

Your company wants to enforce a stronger password policy for all IT administrators. This policy can apply only to IT administrators.

Exchange Server 2010 : Fundamentals and Components of Federated Delegation (part 4)

Organization relationships allow for sharing of availability information between organizations. Sharing polices enable your users to share calendar and/or contact information on a person-to-person basis with external users in other federated Exchange Server 2010 organizations

Exchange Server 2010 : Fundamentals and Components of Federated Delegation (part 3) - Organization Relationships

After you have created and configured a federation trust, you can establish organization relationships with other organizations (assuming that they have established a federation trust of their own).

Exchange Server 2010 : Fundamentals and Components of Federated Delegation (part 2)

When you create the federation trust with either the New-FederationTrust cmdlet or the New Federation Trust Wizard, the task also copies the certificate used to all CA and Hub servers in the same Active Directory site

Exchange Server 2010 : Fundamentals and Components of Federated Delegation (part 1)

The primary components of federation delegation are the federation trust, organization relationships, and sharing policies.

Introduction to Federated Delegation in Exchange Server 2010

Federated delegation in Exchange Server 2010—and the underlying federation infrastructure with the Microsoft Federation Gateway—is an innovative means of securely sharing information with external recipients with minimal management overhead compared with traditional federation technologies.

BizTalk Server 2009 : Service-oriented endpoint patterns (part 2)

While the BizTalk WCF Service Publishing Wizard produces a fairly clean WSDL file, we are clearly establishing more structural control by building these contracts by hand

BizTalk Server 2009 : Service-oriented endpoint patterns (part 1)

What can we do to make our endpoints as service-oriented as possible? We can retain our focus on reusability, abstraction, interoperability, and loose coupling in order to accomplish this.

Exchange Server 2010 : Office Communication Server 2007 R2 Integration (part 3) - Deploying Instant Messaging for OWA

A new feature in Exchange 2010 is the integration of Instant Messaging (IM) into Outlook Web App, so your OWA users can see who is online and directly chat with the users without the requirement of installing Office Communicator on their client computer.

Exchange Server 2010 : Office Communication Server 2007 R2 Integration (part 2) - Deploying UM and OCS 2007 R2 Integration

If you want to implement OCS 2007 R2 or later into your Exchange 2010 UM, your environment should consider the following requirements

Exchange Server 2010 : Office Communication Server 2007 R2 Integration (part 1) - Integrating OCS 2007 R2 in Exchange 2010 Architecture

Exchange Server 2010 UM provides OCS 2007 R2 with the voice mail feature, and OCS 2007 R2 can make presence information and instant messaging features available to your OWA users

Exchange Server 2010 : Managing Unified Messaging (part 1) - Testing Unified Messaging Functionality

Testing the UM functionality is a bit trickier than testing other features such as message routing because it involves multiple components in the testing process such as voice, mailbox access, and so on.

Exchange Server 2010 : Managing Unified Messaging (part 1)

To manage the UM server role, you need to make sure you understand the tools available and how to troubleshoot UM.

Exchange Server 2010 : International Considerations of Unified Messaging

In an international environment it is especially important to consider the foreign language aspect of UM. In governmental agencies in particular it is common to speak and work not in a common language, but in the local language, such as German.

BizTalk Server 2009 : Service-oriented schema patterns (part 6) - Exploiting generic schemas

While I've been preaching so far about all the benefits and capabilities of structured schemas, there are real cases where you need to be exceedingly flexible in the way you take data in.

BizTalk Server 2009 : Service-oriented schema patterns (part 5) - Node feature mapping for service clients

Note that the BizTalk WCF Service Publishing Wizard is infinitely better than the classic BizTalk Web Services Publishing Wizard when it comes to respecting the initial schema

BizTalk Server 2009 : Service-oriented schema patterns (part 4) - Node data type conversion for service clients

You may have noticed that the Schema Editor provided by BizTalk Server 2009 delivers a comprehensive list of data types for schema nodes. In this table, I call out each schema type, what it is, and what .NET type it converts to when consumed by the WCF svcutil.exe proxy generation tool.

BizTalk Server 2009 : Service-oriented schema patterns (part 3) - Building and applying reusable schema components

If I want to put the content of one schema into the definition of another, I can either import or include it. When the target namespace between the schemas differs, then the import option must be used.

BizTalk Server 2009 : Service-oriented schema patterns (part 2) - Canonical schemas

By injecting a common schema, you can reduce coupling between the source formats and destination formats. At any one time, a message only needs to be translated to or from the canonical format.

BizTalk Server 2009 : Service-oriented schema patterns (part 1) - Designing schemas based on service type

The BizTalk WCF Service Publishing Wizard, unlike the classic BizTalk Web Services Publishing Wizard, does not offer the option of Bare (document-style services) or Wrapped (RPC-style services)

Exchange Server 2010 : Deploying Unified Messaging (part 3)

Exchange 2010 UM no longer supports inbound fax transcripts as it was available in the core product with Exchange 2007, but the UM server role retains fax configuration properties and forwards fax calls to a partner fax solution

Exchange Server 2010 : Deploying Unified Messaging (part 2)

For every UM IP gateway you also need at least one UM hunt group. To create a UM hunt group you need the following information

Exchange Server 2010 : Deploying Unified Messaging (part 1)

Before you can use UM, you need to install an Exchange server that includes the UM server role. You can add the UM role to every server role except for the Edge Transport server role.

BizTalk Server 2009 : Types of services

A Remote Procedure Call(RPC) is a means of executing a function on a distant object. These remote invocations are meant to appear as if they were happening locally and typically following the request/response communication pattern.

BizTalk Server 2009 : Identifying Standard Message Exchange Patterns (part 3)

There are cases where the caller of a service wants the benefits of non-blocking asynchronous service invocation, but also needs an actual data response from the service. In this case, a callback pattern can best fit your needs.

BizTalk Server 2009 : Identifying Standard Message Exchange Patterns (part 2) - One-way services

This is your straightforward fire and forget pattern. The message is sent unidirectionally and asynchronously to a waiting receiver. If you grew up building components with fine-grained functional request/reply interfaces, this idea of throwing a message out of your application and not expecting anything back may seem a bit useless.

BizTalk Server 2009 : Identifying Standard Message Exchange Patterns (part 1) - Request/Response services

When we talk about Message Exchange Patterns, or MEPs, we're considering the direction and timing of data between the client and service. How do I get into the bus and what are the implications of those choices

Exchange Server 2010 : Planning for Unified Messaging (part 3)

You configure UM mailbox policies to standardize UM configuration settings, policies, or security settings for UM-enabled users. When creating a UM dial plan, a respective UM mailbox policy is created automatically, including default settings

Exchange Server 2010 : Planning for Unified Messaging (part 2)

The UM dial plan is the basic Unified Messaging administrative unit and used for telephony extension-numbering. The UM dial plan, plus the extension number, provides the unique identifier for each UM-enabled user.