Windows Server - tutorial.wmlcloud.com

Change page: < 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ... > | Displaying page 9 of 59, items 401 to 450 of 2916.

Microsoft Exchange Server 2010 : Setting Up Transport Rules (part 3) - Selecting Actions

As with conditions and exceptions, your choice of possible actions depends on whether you're creating the rule on a Hub Transport server or an Edge Transport server. The Exchange 2010 help files contain detailed descriptions of how each of these actions is defined and applied.

Microsoft Exchange Server 2010 : Setting Up Transport Rules (part 2) - Selecting Conditions and Exceptions

Because conditions and exceptions are both involved in identifying whether a given message should be processed by the rule, it should be no surprise that they give you the same set of options. Which options you get depends on whether you're creating the rule on a Hub Transport or Edge Transport server.

Microsoft Exchange Server 2010 : Setting Up Transport Rules (part 1) - Transport Rules Coexistence Between Exchange 2007 and 2010 , Transport Rules and Server Design Decisions

A number of factors will come into play when you are sizing and making server design decisions around Transport servers. The number of messages per hour and the number of transport rules will affect your design decisions regarding the amount of RAM and number of processors that are on the Hub Transport servers.

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Using SMS Trace (part 2)

If you’re looking for a particular text string—perhaps a filename or an extension or a package or advertisement ID—you can ask SMS Trace to find the log entry that contains that text string.

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Using SMS Trace (part 1) - Obtaining SMS Trace

SMS Trace is one of several tools that Microsoft has made available to help you manage your SMS site. This set of tools is called the SMS 2003 Toolkit 1, and you can obtain it through the SMS Web site .

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Using SMS Service Manager

Status messages will be, and should be, your first stop when you’re trying to understand an SMS process or to troubleshoot a problem on your site. However, in addition to status messages, you can also study the log files that each component can generate.

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Status Message Process Flow

Now that we’ve examined the different tools for handling status messages, let’s look at the status message process flow. Nearly every SMS 2003 service and component generates status messages.

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Working with Status Message Queries

The SMS development team, being one step ahead of the rest of us in this thinking, created status message queries as a means of accomplishing just that. In fact, there are currently 70 existing default queries that might well satisfy most of your message viewing needs.

Microsoft Systems Management Server 2003 : Filtering Status Messages (part 2) - Status Filter Rules

The second way to globally affect how status messages are reported is by using status filter rules. SMS creates 15 status filter rules of its own to control how status messages are reported and viewed, as shown in Figure 2.

Microsoft Systems Management Server 2003 : Filtering Status Messages (part 1) - Configuring Status Reporting Properties

By selecting the appropriate message types from the drop-down lists, you can control how much data is reported. For example, to only show milestone messages that are errors or warnings, select the Error And Warning Milestones option from the drop-down list in the Server Component Status Reporting frame of the dialog box.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 6) - Upgrading Domain and Forest Functional Levels

Windows Server 2003 does not immediately begin functioning at a native level, even when all domain controllers have been migrated. In fact, a fresh installation of Windows Server 2003 supports domain controllers from Windows NT 4.0, Windows 2000, and Windows Server 2003.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 5) - Moving Operation Master Roles

Active Directory sports a multimaster replication model, in which any one server can take over directory functionality, and each domain controller contains a read/write copy of directory objects.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 4) - Replacing Existing Domain Controllers

If you need to migrate specific domain controller functionality to the new Active Directory environment but plan to use new hardware, you need to bring new domain controllers into the environment before retiring the old servers.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 3) - Upgrading the AD Schema Using adprep

The introduction of Windows Server 2003 domain controllers into a Windows 2000 Active Directory requires that the core AD database component, the schema, be updated to support the increased functionality.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 2) - Upgrading a Single Member Server

The direct upgrade approach from Windows 2000 to Windows Server 2003 is the most straightforward approach to migration. An upgrade simply takes any and all settings on a single server and upgrades them to Windows Server 2003.

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 1) - Beginning the Migration Process

As you plan your migration to Windows Server 2003, it would help if you knew exactly what needs to be on Windows 2003. There are many components in a network from the server on which Exchange 2007 is installed to the Active Directory to which the Exchange server is connected.

Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 3) - Configuring Status Summarizers - Site System Status Summarizer

Notice that the Enable Status Summarization and Replicate To Parent Site options are selected by default. If you want to disable site system status summarization, clear the option Enable Status Summarization.

Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 2) - Configuring Status Summarizers - Component Status Summarizer

You can configure three status summarizer components: Component Status Summarizer, Site System Status Summarizer, and Advertisement Status Summarizer. To access these status summarizers, in the SMS Administrator Console expand the site’s Site Settings node and then expand the Status Summarizers node.

Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 1) - Display Interval , Status Message Thresholds

The status messages that are displayed are filtered first by a display interval. By default, only status messages generated since midnight are displayed. This limitation doesn’t mean that all previous status messages have been deleted

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Working with Status Messages (part 2) - Setting Status Message Viewer Options

When SMS components or services generate status messages, they’re written to the site database. The Status Message Viewer uses the SMS Provider to query the database for the detailed messages when you use the technique described in the preceding section.

Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Working with Status Messages (part 1) - Viewing Site Status Messages

Virtually every SMS 2003 component and service generates status messages as it goes about its business. These messages aren’t the sometimes vague or unhelpful variety you might have come to dread in the Windows Event Viewer.

Microsoft Dynamic CRM 4 : Data Migration (part 4) - Creating a Data Migration

If your publisher is showing as active (not paused), after a short time you will have a message in your ScribeIn queue. In the Scribe Console, you can open this Microsoft Message Queuing (MSMQ) message and opt to Save Body.

Microsoft Dynamic CRM 4 : Data Migration (part 3) - Creating a CRM Adapter Publisher

Life will be easier for you if you create a CRM Adapter publisher as the first step, because the CRM Adapter publisher is responsible for capturing changes that occur in CRM, and uses that change event to trigger an integration to occur (for example, integrate a new account into the ERP system.)

Microsoft Dynamic CRM 4 : Data Migration (part 2) - Scribe Workbench - Target Configuration

Choosing the target system is nearly identical to choosing the source data, but the process varies after you have provided the necessary connection parameters.

Microsoft Dynamic CRM 4 : Data Migration (part 1) - Scribe Workbench - Source and Target Definitions, Source Configuration

Defining the source data begins with choosing how to connect to the data (using an application adapter, ODBC, or XML). After you choose the connection parameters, a series of prompts helps you define the query set for the source data. This can be a single “object” or can be a custom query joining multiple objects together.

BizTalk 2006 : Using BizTalk Framework 2.0 Reliable Messaging (part 2) - Acknowledgement Verification

In many cases, a business process orchestration will be implemented in either the send or thereceive side of a business process, and it is more suitable to configure the BizTalk Framework properties there.

BizTalk 2006 : Using BizTalk Framework 2.0 Reliable Messaging (part 1)

Continuing from the previous examples, let's assume that the order processing system notonly needs to update your downstream systems, which are internal to your organization, but also needs to notify a trading partner of the transactions.

Microsoft Exchange Server 2010 : Managing Transport and Journaling Rules - Setting Up Message Classifications (part 2)

When you create or modify classifications, they are automatically visible to OWA users. In what is a particularly painful oversight, the same is not true for Outlook 2007 users

Microsoft Exchange Server 2010 : Managing Transport and Journaling Rules - Setting Up Message Classifications (part 1)

At their heart, message classifications are simply labels that are set on certain messages. These labels in turn allow other software, such as Outlook and Outlook Web Access (OWA), to display a visual warning for the user and, optionally, take special action when processing the message with rules.

Windows Server 2012 : Managing Users with Local Security and Group Policies (part 3) - Troubleshooting Group Policy Applications

When policies are used throughout an organization, sometimes the policy settings do not apply to a user or computer as originally intended. To begin basic troubleshooting of Group Policy application issues, you need to understand the policy application hierarchy.

Windows Server 2012 : Managing Users with Local Security and Group Policies (part 2) - Configuring and Optimizing Group Policy

When multiple group policies exist, they are applied in a predefined order. For a particular user or computer, the order can be derived using the Resultant Set of Policies snap-in.

Windows Server 2012 : Managing Users with Local Security and Group Policies (part 1) - Viewing Policies with the Group Policy Management Console, Creating New Group Policies

The preceding section described how to locate a group policy. Using the Group Policy Management Console, you can also create, configure, and open site, domain, and organizational unit (OU) group policies for editing.

Windows Server 2012 Administration : Creating Groups (part 2) - Populating Groups, Group Management

After you create a group, you can add members to it. The domain level that the domain is running in determines whether this group can have other groups as members.

Windows Server 2012 Administration : Creating Groups (part 1) - Domain Functional Level and Groups , Creating AD Groups

When it comes to creating groups, understanding the characteristics and limitations of each different type and scope is only half the battle. Other points to consider for group creation are how the group will be used and who will need to be a member of the group.

Windows Server 2012 Administration : Windows Server 2012 Active Directory Groups

An Active Directory group is made up of a collection of objects (groups containing users and computers that are often used to simplify resource access permissions and sending emails).

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Messages in Flight

You can imagine that for organizations that maintain thousands of mailboxes, and therefore have very busy Hub Transport servers, the queue database can become very large.

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Send and Receive Connectors (part 3)

When you install Exchange 2010 in an existing Exchange 2003 organization, to allow coexistence and facilitate routing, Setup creates an administrative group, a routing group, and a Windows security group for backward compatibility.

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Send and Receive Connectors (part 2)

Although receive connectors are configured for each server, send connectors are organizational connectors that you can assign to a number of different Hub Transport servers. Each server also has an implicit send connector, but that connector is used only for transferring mail to other Hub Transport servers.

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Send and Receive Connectors (part 1)

The receive connector is the point where inbound SMTP mail is received on the Hub Transport server. Receive connectors do not deliver outbound mail (unlike the Exchange 2000/2003 SMTP virtual server).

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Message Routing in the Organization

In earlier versions of Exchange, the message-routing architecture was based on a structure that was defined by the administrator. For example, in Exchange 2000/2003, the message-routing architecture was defined by a collection of servers separated by full-time and reasonably good available bandwidth.

Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Transport Improvements in Exchange Server 2010

Prior to Exchange Server 2007, all messages were processed by the same server that connected MAPI clients, managed the information store, and hosted Outlook Web Access.

Windows Server 2012 Administration : Configuring Sites (part 3) - Establishing Site Links, Delegating Control at the Site Level

Site links establish connectivity between domain controllers to allow Active Directory replication to be managed and scheduled. The Active Directory database, Global Catalog, group policies, and the domain controller SYSVOL directory replicate according to the replication schedule configured in a site link.

Windows Server 2012 Administration : Configuring Sites (part 2) - Creating a Site - Adding Domain Controllers to Sites

If a new domain controller is added to a forest, it will dynamically join a site with a matching subnet if the site topology is already configured and subnets have been previously defined.

Windows Server 2012 Administration : Configuring Sites (part 1) - Creating a Site - Creating Site Subnets

The address prefix is the IP address and the mask entered in network prefix notation. This is the format “IP network address/prefix length.” This is very similar to the IP address and subnet mask format. Table 3 lists some common subnet masks and their prefix length values.

Windows Server 2012 Administration : Examining Active Directory Site Administration

Sites can be different things, depending on whom you ask. If you ask an operations manager, she might describe a site as any physical location from which the organization conducts business.

Windows Server 2012 Administration : Defining the Administrative Model

Before the computer and networking environment can be managed effectively, an organization and its IT group must first define how the systems and components will be assigned and managed

Sharepoint 2013 : Backup and Restore (part 6) - Farm Backup and Restore - Performing a Restore, Using PowerShell

Performing a SharePoint farm restore is much the inverse of the backup process. Assuming you have performed a successful farm backup, the following steps demonstrate the farm restore process

Sharepoint 2013 : Backup and Restore (part 5) - Farm Backup and Restore - Performing a Backup

Checking the check box at the top Farm level will enable all the options below it, which include backup of the content databases, web application settings, and service application configuration.

Sharepoint 2013 : Backup and Restore (part 4) - Farm Backup and Restore - Farm Backup Settings

The CPU in the server slices time given to threads in a process to give the illusion of multi-threading or multiple things happening at once. Modern CPUs consist of multiple cores, which can process separate threads of a process at the same time (true multi-threading).

Sharepoint 2013 : Backup and Restore (part 3) - Unattached Content Database Data Recovery

IT staff and database admins like to back up SQL databases—and there is nothing wrong with that! SQL Server provides options to administrators to run nightly backups, and many good backup applications include a SQL agent to back up live SQL database data to backup storage.