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 3 of 59, items 101 to 150 of 2916.

Microsoft Lync Server 2013 : Persistent Chat Deployment (part 1) - Topology Options and Scaling

Several topology options are available with Persistent Chat, and these are dependent on the overall Lync deployment. Similar to the Lync Front End Services, an instance of Persistent Chat is referred to as a pool, even if just a single server is used.

Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 2) - Processing meeting requests according to policy

The AutomateProcessing property of a room mailbox tells the Resource Booking Attendant how to handle incoming meeting requests within the structure established by the booking policy for the mailbox.

Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 1) - Providing policy direction to the Resource Booking Attendant

Another important property is shown on the Resource General tab. When you enable the Resource Booking Attendant, you instruct Exchange that the attendant should monitor incoming meeting requests for the room to decide whether the requests should be accepted.

Microsoft Exchange Server 2013 : Mailbox management - Mail-enabled contacts, Mail users

Mail-enabled contacts are a convenient way to add external correspondents (people who have email accounts outside your Exchange organization) to the GAL.

Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 2) - Processing moderation requests, Moderated mailboxes

Provided that a supported client is used (Outlook 2013, Outlook 2010, or Outlook Web App; other clients do not include the necessary UI), the process is very straightforward and requires only a simple click from the moderator to allow the message to proceed.

Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 1) - Moderated groups

Many companies use distribution groups as a convenient way of communicating with large audiences. It is very convenient to be able to send a message and have it delivered to many people, but sometimes you want to ensure that only appropriate content is sent to large distributions.

Microsoft Exchange Server 2013 : Mailbox management - Shared mailboxes , Recalling messages

Exchange clients have offered users the ability to recall a sent message for many years. Unfortunately, this feature seldom works.

SQL Server 2012 : Transact-SQL - Functions, Triggers

A trigger is a special kind of stored procedure that is executed when a special event happens within SQL Server. An event could include the execution of a given DDL or DML statement or a login to SQL Server.

SQL Server 2012 : Transact-SQL - Stored Procedures

A stored procedure is a block of T-SQL or .NET code that is stored within a database. This code is similar to other procedures in other languages because it accepts parameters as inputs and can provide output to the calling application or user. Stored procedures make building database applications easy.

SQL Server 2012 : Transact-SQL - Transactions

Transactions enable users to create T-SQL batch statements that are either completely applied or do nothing to the existing data. When changes are applied, it is said that the transaction has committed.

SQL Server 2012 : Transact-SQL - Data Manipulation Language (part 2)

Alternatively, you could have omitted the specific columns you wanted to insert. If you do this, SQL Server will assume that the first value will be for the first column definition, the second value entered will be for the second columns definition, and so on.

SQL Server 2012 : Transact-SQL - Data Manipulation Language (part 1)

Most of what you’ll do with T-SQL centers around the Data Manipulation Language (DML). DML consists of the four statements SELECT, INSERT, UPDATE, and DELETE. These are the four statements that you use to get data into a database, update and delete that data, and get it back out again.

SQL Server 2012 : Transact-SQL - The VetClinic Sample Database Revisited, Data Types

Each data type has different characteristics, including how much space on disk each value takes up. A VARCHAR data type can be defined for 20 characters but takes up only a few bytes on disk.

Microsoft Sharepoint 2013 : Claims Authentication and Oauth - Server-to-Server Authentication

Server-to-Server authentication (S2S) represents an example of application-to-application OAuth. This approach uses a Microsoft extension of the OAuth protocol to enable applications or servers to share resources on behalf of users, without user authentication.

Microsoft Sharepoint 2013 : Application Authentication (part 3) - App Authentication - App Catalog App Authentication

This example illustrates the second approach to app authentication. In this case, your app is hosted on-premises in servers that are not a part of the SharePoint farm, and not in the cloud as in the previous example.

Microsoft Sharepoint 2013 : Application Authentication (part 2) - App Authentication - SharePoint Store App Authentication

his example demonstrates installing an app from the SharePoint Store, and using ACS as the STS. Your on-premises SharePoint farm can use an external STS, such as ACS, and in general SharePoint can be configured to trust many different token providers

Microsoft Sharepoint 2013 : Application Authentication (part 1) - Cloud App Model, OAuth

The new SharePoint 2013 Cloud App Model enables developers to provide solutions, called apps in the new terminology, to extend the capabilities of SharePoint 2013.

Microsoft Sharepoint 2013 : User Authentication (part 4) - Using Claims-Based Identity - Federated User Authentication Process

As collaboration boundaries expand and need for information increases, access to resources that are not hosted by your company or an organization that knows you is needed.

Microsoft Sharepoint 2013 : User Authentication (part 3) - Using Claims-Based Identity - Understanding the User Authentication Process and Authentication Providers

User authentication scenarios in SharePoint 2013 can be as straightforward as using Windows Integrated Security and Active Directory or as complicated as using Windows Azure Access Control Service as a federation provider.

Microsoft Sharepoint 2013 : User Authentication (part 2) - Using Claims-Based Identity

The purpose of this section is to show how claims identity is used to authenticate users. It begins with a real-world analogy that illustrates the use of claims. Then you will learn the technical requirements for implementing claims authentication. Finally, you will walk through the actual claims authentication process.

Microsoft Sharepoint 2013 : User Authentication (part 1) - Claims-Based Identity

The answers to these questions are associated with the key challenges related to providing users with access to information. These challenges include user identity, user access, and user information and storage. As you will see, claims-based identity presents a solution to these challenges.

Microsoft Sharepoint 2013 : What’s New with Claims and Authorization?

Several new capabilities are introduced in SharePoint 2013, and the following sections cover those most pertinent to the administrator.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 3)

Using the REST API from a C# application is certainly possible, but it is easily the least attractive of all the programming options. You will find that retrieving form digests, parsing out properties, and creating payloads can be tedious and messy. This section details the steps necessary to work with the REST API in C#.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 2) - Working with the REST API in JavaScript

When you choose to use JavaScript with your app, you will find that by using the REST API, you can write cleaner code than CSOM. Furthermore, you will find built-in support for REST in the jQuery library, which makes it much easier to use than CSOM.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 1) - Understanding REST fundamentals

Remote Procedure Call (RPC) is a software architecture that uses a generated client-side proxy to communicate with a remote web service. Simple Object Access Protocol (SOAP) is the protocol that is used along with the RPC architecture in classic SharePoint web services.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 7)

After a new Exchange 2007 server is added to the network to functionally replace an old Exchange 2000 or 2003 server, there comes a time when the old server should be removed.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 6)

Just as mailboxes are migrated from Exchange 2000 or 2003 servers to Exchange 2007 systems, public folders need to be replicated before retiring the old Exchange 2000 or 2003 servers.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 5) - Moving Mailboxes

After a new Exchange 2007 server has been inserted into an existing Exchange 2000 or 2003 organization, the movement of mailboxes from an old Exchange back-end server to a new Exchange 2007 Mailbox server is as simple as selecting the mailbox or mailboxes, and through a few mouse clicks, selecting the new destination server.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 4) - Installing Exchange Server 2007 on a Server System

After the Exchange 2007 prerequisites have been installed on the server that will become the Exchange 2007 system, the next step is to install the Exchange 2007 application.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 3) - Installing Exchange Server 2007 Prerequisites

To install the Microsoft Management Console 3.0, with the Exchange 2007 CD or DVD Setup Wizard already active, choose the second option, which is to install the Microsoft Management Console 3.0 on the system.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 2)

Whether you are performing this migration in a lab environment or in production, after performing a backup of your production environment, the first step in the migration process is to prepare the permissions in Exchange 2000 or 2003.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 1) - Planning Your Migration

The planning process in migrating from an environment that has Exchange 2000 or 2003 to Exchange 2007 involves ensuring that the existing environment is ready for a migration, and that the hardware necessary to accept the migrated server roles is compatible with Exchange 2007.

Migrating to Exchange Server 2007 : Deploying a Prototype Lab for the Exchange Server 2007 Migration Process

Regardless of the method that is chosen to migrate Exchange, care should be taken to test design assumptions as part of a comprehensive prototype lab. A prototype environment can help simulate the conditions that will be experienced as part of the migration process.

Migrating to Exchange Server 2007 : Moving to Native Mode in Exchange

For an organization that previously had Exchange Server 5.5 in their environment, or possibly still has Exchange 5.5 servers in the environment, before the migration to Exchange 2007 can begin, the organization must remove all Exchange 5.5 servers.

Migrating to Exchange Server 2007 : Understanding What’s New and What’s Different with Exchange Server 2007

This section covers what is new and what is different with Exchange 2007, not from a product function and feature basis, but rather how certain changes in Exchange 2007 impact the migration process to Exchange 2007.

Migrating to Exchange Server 2007 : Understanding How to Migrate to Exchange Server 2007

For larger organizations, the various server roles will likely be applied to systems dedicated to a particular server role for purposes of performance and scalability. In many cases, a larger organization will already have existing roles for front-end and back-end servers, as well as bridgehead servers.

Sharepoint 2013 : Working with the CSOM (part 6) - Working with the JavaScript client object model - Creating, reading, updating, and deleting in the JavaScript client object model

Creating, reading, updating, and deleting list items by using the JavaScript client object model is more complex than with the managed client object model.

Sharepoint 2013 : Working with the CSOM (part 5) - Working with the JavaScript client object model - Handling errors

Just like the managed client object model, the JavaScript client object model must deal with the potential for server-side errors during the round trip.

Sharepoint 2013 : Working with the CSOM (part 4) - Working with the JavaScript client object model - Returning collections

The JavaScript client object model supports both a load and loadQuery method. The loadQuery method can be used to store a collection into a variable other than the one referencing the desired collection.

Sharepoint 2013 : Working with the CSOM (part 3) - Working with the managed client object model - Creating, reading, updating, and deleting

In the conditional scope shown in Example 4, a new list is created if the user has the appropriate permissions. Creating new lists and items using the managed client object model is done with the creation information objects.

Sharepoint 2013 : Working with the CSOM (part 2) - Working with the managed client object model - Handling errors

Because of the disconnected nature of the client object model, error handling is especially important. You might see errors thrown when you attempt to access an object or value that has not yet been retrieved from the server.

Sharepoint 2013 : Working with the CSOM (part 1) - Understanding client object model fundamentals

The managed and JavaScript client object models are maintained in separate libraries, which are located under the SharePoint system directory.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 6) - Tracking installed roles, role services, and features

As discussed previously, you can determine the roles, roles services, and features that are installed on a server by typing get-windowsfeature at a PowerShell prompt.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 5) - Installing components at the prompt

When you want to manage server configuration at a prompt or in a script, you’ll use Windows PowerShell and the ServerManager module.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 4) - Managing server binaries

If you want to remove binaries, you use Windows PowerShell to do this and not Server Manager. The ServerManager module for Windows PowerShell is the command-line counterpart of Server Manager.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 3) - Adding server roles and features

When you select All Servers in Server Manager, the Roles And Features pane provides details on the current roles and features that are installed on all managed servers.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 2) - Installing components with Server Manager - Viewing configured roles and role services

Server Manager automatically creates server groups based on the roles of managed servers. When you select a role-based group in the left pane, the Servers panel shows the managed servers that have this role.

Managing Windows Server 2012 Systems : Configuring Roles, Role Services, and Features (part 1) - Using roles, role services, and features

Although you typically want to combine complementary roles, doing so increases the workload on the server, so you need to optimize the server hardware accordingly.

Windows Server 2012 : Configuring IPsec (part 7) - Configuring connection security rules - Monitoring IPsec

After you create and configure connection security rules, you can use both the Windows Firewall with Advanced Security snap-in and Windows PowerShell to monitor IPsec communications between the local computer and other computers on the network.

Windows Server 2012 : Configuring IPsec (part 6) - Configuring connection security rules - Creating a custom rule, Configuring authenticated bypass

One of the configuration options in that wizard was deferred until later because it had to do with how firewall rules interact with IPsec. That setting is the Allow The Connection If It Is Secure option on the Action page.