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 18 of 59, items 851 to 900 of 2916.

Using Microsoft SharePoint with Microsoft Dynamics CRM Functions (part 2) - Displaying Data Using BDC in Microsoft Office SharePoint Server

The BDC provides a platform layer between Microsoft Office SharePoint and disparate backend systems. This allows an administrator to build sites with data aggregated from multiple data sources and to enable SharePoint search of records in systems other than SharePoint.

Using Microsoft SharePoint with Microsoft Dynamics CRM Functions (part 1) - Displaying Data in SharePoint Using the List Web Part for Microsoft Dynamics CRM 4.0

A web part is an ASP.NET server control that is used on a web part zone located within web part pages. Web parts can be programmed and can enable users to access the content, appearance, and behavior of the web page within a browser. SharePoint out of the box comes with a few web parts that are supported by Microsoft.

Microsoft Exchange Server 2007 : Single Copy Clusters (part 2) - Installing Exchange Server 2007 on the Active Node

Now that the cluster is established and both nodes are able to control the resources, it is time to install the Exchange Server 2007 mailbox components on the cluster. This process will be broken out by node, and you will start with the node that currently owns the cluster resources. This is referred to as the active node.

Microsoft Exchange Server 2007 : Single Copy Clusters (part 1)

The old model of Exchange clustering, where two nodes have shared resources that hold the Exchange databases and logs, is still available in Exchange Server 2007. This model is now called the Single Copy Cluster (SCC).

Windows Server 2003 on HP ProLiant Servers : Logical Structure Design (part 5) - Trust Definitions

Trusts to external forests, Windows NT domains, or Kerberos realms should be defined in the design document. Windows 2000, supporting only NTLM type external trusts, required individual trusts to be created between all domains in separate forests because NTLM didn't provide transitivity.

Windows Server 2003 on HP ProLiant Servers : Logical Structure Design (part 4) - Group Policy

Windows 2000 Group Policy had approximately 700 settings. Windows Server 2003 added nearly 200 additional settings. Windows XP also added a number of settings.

Windows Server 2003 on HP ProLiant Servers : Logical Structure Design (part 3) - Naming Standards

Naming AD components is entirely up to the architect. Windows doesn't really care what you name anything as long as most objects have a unique name within the domain or the forest.

Windows Server 2003 on HP ProLiant Servers : Logical Structure Design (part 2) - Forest Structure, OU Structure

The OU, of course, is an excellent alternative to multiple domains. Microsoft recommends using OUs to create directory partition structures for changeable entities. For instance, rather than making domains for Engineering, HR, Executive, Finance, and Program offices, OUs are a better solution because these names can change.

Windows Server 2003 on HP ProLiant Servers : Logical Structure Design (part 1) - Domain and OU Structure

The three basic domain structures illustrated in Figure 2 are the single domain model, the multiple domain model in a parent/child relationship, and the multiple domain model in a multiple domain tree relationship. In each model, OUs are used to create subdomain organizations for more granular administration and security purposes.

Microsoft Dynamics GP 2010 : Preventing Errors in Dynamics GP - Ensuring proper year-end closing by checking Posting Types

When setting up accounts in the Chart of Accounts, users are required to select a posting type of either Balance Sheet or Profit and Loss. These selections correspond to their respective financial statements, the Balance Sheet and the Profit and Loss statement, also known as the Income Statement.

Microsoft Dynamics GP 2010 : Preventing Errors in Dynamics GP - Preventing account selection errors with Chart Segment names

Given the typical meticulous tendencies of most accountants, it's a little bit of a surprise that the descriptions in an average chart of accounts are a complete mess. Most charts of accounts are initially very pristine but as accounts are added by various people over time, their descriptions become inconsistent.

Monitoring Windows Small Business Server 2011 : Using Windows SBS Console Monitoring (part 3) - Creating and Viewing Reports

Another way to monitor Windows SBS network activity is to create reports. When you click Reports in the Windows SBS Console, you see the interface shown in Figure 4, which displays the two reports that Windows SBS 2011 creates by default.

Monitoring Windows Small Business Server 2011 : Using Windows SBS Console Monitoring (part 2) - Using Notification Settings

When you click Network in the Windows SBS Console and select the Computers tab, as shown in Figure 3, you see a list of the computers on your network, a column specifying whether each computer is online, and indicators providing the same four categories of information as in the Network Essentials Summary pane.

Monitoring Windows Small Business Server 2011 : Using Windows SBS Console Monitoring (part 1) - Using the Network Essentials Summary

The Windows SBS Console provides administrators with many of the most vital Windows SBS controls and settings, leaving the details and comprehensive access to the standard Windows Server 2008 R2 tools.

System Center Configuration Manager 2007 : Operating System Deployment - Boot Images

You can create images for removable media by right-clicking a task sequence and choosing Create Task Sequence Media. This launches the straightforward Task Sequence Media Wizard, allowing you to choose which type of media to create. You can burn the resulting image to a CD or DVD or place it on a bootable USB device.

System Center Configuration Manager 2007 : Operating System Deployment - Site Systems

Aside from a DP and the ever-present MP, there are also two optional site system roles used by OSD: a PXE service point and a state migration point. DPs serve the same role for OSD that they do in software distribution: to deliver software packages to client systems and are required for OSD to work properly.

BizTalk Server 2006 : Pipeline Component Best Practices and Examples - The Databased Disassembler

The usual response for this is to use the appropriate database adapter, generate the schemas for the SQL statement or the stored procedure, and use some combination of an orchestration/port and adapter to generate the data, publish it to the Messagebox, and send it to the appropriate destination.

BizTalk Server 2006 : Pipeline Component Best Practices and Examples - Using PGP (part 2) - PGP Decode Component

The following code example is the counterpart to the encoding component shown in the preceding subsection. The Decoding component is used on the receive side of BizTalk and is used when encrypted messages are received into BizTalk.

BizTalk Server 2006 : Pipeline Component Best Practices and Examples - Using PGP (part 1) - PGP Encode Component

By default, BizTalk ships with no encryption/decryption component. Many organizations need to encrypt the message data as it is sent from BizTalk and decrypt is as well once it is received.

Microsoft Dynamics CRM 4.0 : Using Microsoft Dynamics CRM with Microsoft SharePoint

Different from the previous sections in which we used Microsoft SharePoint as the primary application to display CRM data, this section illustrates how to use Microsoft Dynamics CRM to display data from SharePoint (which can contain CRM data if properly integrated).

Windows Server 2003 on HP ProLiant Servers : Defining the Windows 2003 Infrastructure

The content of this section depends upon whether the existing domain structure is Windows NT or Windows 2000. If you are migrating from Windows NT, you can take this opportunity to identify key Windows 2003 domain components such as single versus multiple forest structure, single versus multiple domain structure, and naming conventions.

Microsoft Content Management Server : Implementing Server-Side Validation

We have seen how validation can be performed against the HtmlPlaceholderControl using client-side scripts. Client-side validation essentially reduces round-trips to the server just to find out if they have left out any fields.

Microsoft Content Management Server : Preventing Pages with Invalid Content from Being Saved

There’s still a problem to be tackled. Although the custom validation control has all the necessary code, it won’t work unless someone clicks on an ASP.NET control, such as a Button, that has its Control.CausesValidation property set to true. Otherwise, the page will still be saved even if required placeholders are not filled in.

Microsoft Systems Management Server 2003 : Permissions and Security Objects (part 2) - Assigning Permissions

You can assign permissions to an object in four ways: you can use the Security Rights node in the SMS Administrator Console to assign permissions to object classes and instances, you can assign permissions at the specific object class or instance, you can use the SMS User Wizard, or you can clone an existing user.

Microsoft Systems Management Server 2003 : Permissions and Security Objects (part 1)

Instance security is similar to NTFS file security. Just as you can set permissions on files different from those set at the folder level, you can also set security on individual members of an object class.

Microsoft Systems Management Server 2003 : Security - Accounts and Groups

SMS uses a variety of accounts to perform various tasks. Some of these accounts might be created by you, such as a Client Connection account; others are created by SMS automatically, such as the SMS Server Connection account.

Windows Server 2003 on HP ProLiant Servers : Assessment of the Enterprise - Conducting the Assessment

This section is a practical guide to building a template from which the assessment data can be gathered and a resulting document produced. The topics listed here note differences in approach between a Windows NT assessment and a Windows 2000 assessment for a Windows 2003 migration.

Windows Server 2003 on HP ProLiant Servers : Assessment of the Enterprise - The Assessment Team

The assessment team members consist of all stakeholders in the computing environment. There is no magic checklist here that will cover all businesses and situations. I have conducted assessments for large companies that filled a large conference room with participants, as well as for a small government entity where the entire team consisted of two people

Windows Small Business Server 2011 : Disaster Planning - Preparing for a Disaster, Restoring from Backup

The process of restoring your SBS server from backup is something you should test and do before you find yourself in the middle of a disaster. And yes, we know, we’re repeating ourselves.

Windows Small Business Server 2011 : Disaster Planning - Planning for Disaster

A good disaster recovery plan is one that you are constantly examining, improving, updating, and testing. But understand your disaster plan’s limitations: it isn’t perfect, and even the best disaster recovery plan needs to be constantly examined and adjusted or it quickly gets out of date.

SQL Server 2008 : Security - Networking

Connections to SQL Server are established using a standard network protocol such as TCP/IP. Depending on the installed edition of SQL Server, certain protocols are disabled by default.

SQL Server 2008 : Security - Authentication mode

Installing SQL Server presents us with two options for login authentication: Windows Authentication Mode or SQL Server and Windows Authentication Mode (commonly called Mixed Mode).

Microsoft Dynamic GP 2010 : Providing clean vendor information by properly closing Purchase Orders, Protecting against information loss by printing Fixed Asset Reports

Properly closing Purchase Orders in Dynamics GP allows a company to make intelligent sourcing decisions about which vendors are able to meet the firm's needs. Companies gain the data necessary to analyze vendor performance and make decisions based on factors beyond just price.

Microsoft Dynamic GP 2010 : Protecting Dynamics GP with key security settings

Security is an important part of any ERP system and Dynamics GP provides a robust security model that rolls up individual item access into tasks and tasks into roles. Roles can then be applied to individual users, providing fine grain control of security with minimal work after the initial setup.

Working with the Windows Home Server Registry : Finding Registry Entries

The Registry contains only five root keys, but they contain hundreds of subkeys. The fact that some root keys are aliases for subkeys in a different branch only adds to the confusion.

Working with the Windows Home Server Registry : Working with Registry Entries - Changing the Value of a Registry Entry

Changing the value of a Registry entry is a matter of finding the appropriate key, displaying the setting you want to change, and editing the setting’s value. Unfortunately, finding the key you need isn’t always a simple matter.

SharePoint 2010 : Packaging and Deployment Model - Site Definitions

To understand how a custom site definition fits into the overall picture, select New Site from the Site Actions menu on any SharePoint site. Each of the items listed in the Create dialog is an example of a site definition.

SharePoint 2010 : Packaging and Deployment Model - Features (part 3) - Upgrading Features

In SharePoint 2010, one of the important new capabilities from a packaging and deployment perspective is the ability to upgrade features. In previous versions, an upgrade was possible, but it was more a case of replacing an old feature with a new version.

SharePoint 2010 : Packaging and Deployment Model - Features (part 2) - Feature Receivers

A feature receiver is basically an event handler responsible for handling installation and activation events for a feature. We can add feature receivers to any type of feature by right-clicking a Feature node in the Solution Explorer pane and selecting Add Event Receiver.

SharePoint 2010 : Packaging and Deployment Model - Features (part 1) - Feature Designer

You can see in the Feature Designer that features comprise one or more elements, where an element may be a web part, a list definition, a workflow, or a number of different components. Using the Feature Designer, we can select which elements should be included in a feature and therefore specify which functionality will be enabled when the feature is activated.

SharePoint 2010 : Packaging and Deployment Model - Working with Packages

SharePoint packages are created as cabinet (CAB) files with a .wsp extension. We can, however, rename a .wsp file, such as myproject.wsp, to myproject.cab and view the contents in Windows Explorer.

Microsoft Content Management Server Development : Validating the HtmlPlaceholderControl (part 3) - Building the Required HTML Placeholder Validator

We are ready to build the RequiredHtmlPHValidator—a validator that ensures that authors do not leave an HtmlPlaceholderControl empty before the page is saved. To begin, add a class file named RequiredHtmlPHValidator.cs to the MCMSValidators project.

Microsoft Content Management Server Development : Validating the HtmlPlaceholderControl (part 2) - Checking for an Empty HtmlPlaceholderControl

The JavaScript used to check for these conditions is covered in this section. The name of the control to be validated will be added to the name of the routine to ensure that if multiple validation controls have been placed on the same template file; they will each have their own client-side routines.

Microsoft Content Management Server Development : Validating the HtmlPlaceholderControl (part 1) - Retrieving the Current Value of the HtmlPlaceholderControl

We could choose to use server-side scripts and get the value stored in the Html property of the HtmlPlaceholderControl when the page does a postback. However, performing server-side validation introduces several levels of complexity to the design.

Windows Server 2003 on HP ProLiant Servers : Migration Case Studies (part 3) - Hewlett-Packard Company

To describe this migration, we have to go back prior to HP's merger with Compaq. Compaq had nearly completed its migration from Windows NT to Windows 2000 when the merger took place. HP, on the other hand, was still in a Windows NT environment in the midst of finalizing its own plans to migrate to Windows 2000.

Windows Server 2003 on HP ProLiant Servers : Migration Case Studies (part 2) - Eastman Chemical Company

Without the helper machines, Eastman would have had to either do an in-place upgrade on the existing BDC or do a wipe and reload, causing inconvenience to the users as they would have had to authenticate to another BDC.

Windows Server 2003 on HP ProLiant Servers : Migration Case Studies (part 1) - County Government Office

The DNS structure described is a bit unorthodox, but uses the strategy that Compaq used. Clients in the child domain find SRV records in the root by going to the county.gov BIND server and then getting referred to the Windows 2000 DNS server that hosts the four SRV zones.

System Center Configuration Manager 2007 : Network Design - Troubleshooting Configuration Manager Network Issues (part 2) - Identifying Network Issues Affecting Configuration Manager

The following sections discuss some indicators of possible network issues that you may see in the status messages and logs. In addition to troubleshooting, you can use this information to configure proactive monitoring for ConfigMgr, helping to spot many problems before they impact service delivery.

System Center Configuration Manager 2007 : Network Design - Troubleshooting Configuration Manager Network Issues (part 1)

Configuration Manager depends on basic network services such as connectivity and name resolution to work properly. Network-related issues are a common source of problems that can affect Configuration Manager service delivery.

System Center Configuration Manager 2007 : Network Design - Network Discovery

Configuration Manager can use a variety of network protocols to probe your network and gather data about the objects it discovers into the site database. Network discovery can be used to identify potential ConfigMgr clients.