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 6 of 59, items 251 to 300 of 2916.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 6) - Configuring a DHCPv6 server, IPv6 transition technologies

The ultimate goal of IPv6 is for IPv4 to eventually be retired and all nodes on all TCP/IP networks to use only IPv6. However, such a goal might take years, or even decades, to achieve.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 5) - Stateless address autoconfiguration,Stateful address autoconfiguration

Stateless address autoconfiguration is one of the most valuable aspects of IPv6 because it allows IPv6 nodes to communicate on a network without the need of manually assigning addresses to them or deploying a DHCP server.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 4) - IPv6 address assignment - Manual address assignment

On IPv4 networks, addresses can be assigned to interfaces in three ways: manually using static addresses, dynamically using DHCP, or automatically using APIPA.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 3) - IPv6 address representation

IPv4 addresses are usually represented in the familiar dotted-decimal form, such as 65.55.58.201, where each number represents 8 bits of the 32-bit address. By contrast, the much longer IPv6 addresses are typically represented by dividing the 128-bit address into 16-bit (4-byte) segments.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 2) - Default IPv6 functionality

On Windows platforms, IPv6 is installed by default and cannot be uninstalled because it is a fundamental component of Tcpip.sys, the TCP/IP driver file on these platforms.

Windows Server 2012 : Configuring IPv6/IPv4 interoperability (part 1) - IPv6 concepts and terminology

While some IPv6 concepts and terminology are similar to those for IPv4, others are quite different. The following list is a brief summary of some of the important IPv6 terminology you should be familiar with to begin developing an IPv6 migration plan for your organization.

Multi-Tenancy in SharePoint 2013 (part 2) - Multi-Tenant Use Cases, Partitioning in the Enterprise

Just as it would in a hosted scenario, a large enterprise needs to handle data and services in a manner similar to the hosted world. Consider, for instance, managed metadata.

Multi-Tenancy in SharePoint 2013 (part 1) - Managing Service Application Groups, Creating a Site Subscription

In SharePoint 2007, the walls of security and the isolation of data and services went along the lines of web application to site collections to webs.

Sharepoint 2013 : Service Application Administration (part 4) - Setting Up the Farm Trust, Publishing a Service Application

If you have multiple farms you want to trust, make sure in steps 13 and 16 that you use unique names for each farm for PublishingFarm and Collaboration.

Sharepoint 2013 : Service Application Administration (part 3) - Managing Service Application Proxy Groups

Now that you know how useful these groups are, this section demonstrates how to manage and consume them. After a brief walk through the GUI tools, we’ll take a look at some of the hardcore things you can do with the SharePoint 2010 Management Shell.

Sharepoint 2013 : Service Application Administration (part 2) - Using the Ribbon to Manage Service Applications

Service applications are built by developers and then bolted into SharePoint through the service application framework, which enables developers to use the Ribbon to manage their service applications.

Sharepoint 2013 : Service Application Administration (part 1) - Creating a New Instance of a Service Application

That was a great way to quickly get up and running; but now you are ready for prime time, and HR is screaming for its own instance of the Managed Metadata service application.

Windows Server 2012 : Managing networking using Windows PowerShell (part 2) - Examples of network-administration tasks

The best way to learn how to use Windows PowerShell to administer network settings and services on Windows Server 2012 is to experiment with performing different tasks in a test environment.

Windows Server 2012 : Managing networking using Windows PowerShell (part 1) - Identifying networking cmdlets

In Windows Server 2012, there are now hundreds of Windows PowerShell cmdlets that can be used to view, configure, and monitor different networking components and services in the platform.

Sharepoint 2013 : Managing Site Security - Create Permission Levels for a Site

To create permission levels, open the site’s permissions management page and click the Permission Levels button in the Manage section of the ribbon.

Sharepoint 2013 : Managing Site Security - Edit a SharePoint Group’s Settings

To change a SharePoint group’s settings, navigate to the site’s People and Groups settings page, as shown earlier in this chapter, and then click the name of the group in the left navigation bar.

Sharepoint 2013 : Managing Site Security - Create a SharePoint Group for a Site

By default, when you create a site, SharePoint automatically creates some groups for you to use in that site. To create a new SharePoint group, open the site permissions settings page, as shown earlier in this chapter, and then click the Create Group button in the Grant section of the ribbon.

Sharepoint 2013 : Assign Users’ Permissions on a Site

To allow users to view a site to which they previously didn’t have access, you can either add them to one of the SharePoint groups or add them to the site directly, without adding them to a specific group. The following sections explain how to perform these options.

Sharepoint 2013 : Get to a Site’s Permission Management Page (part 2) - Check What Permissions a User or a Group Has on a Site

To check what permission a specific user or a group has on a site, open the site’s Permissions Management page and click the Check Permissions button in the Check section of the ribbon .

Sharepoint 2013 : Get to a Site’s Permission Management Page (part 1)

To get to a site’s security settings page, open the site’s Site Actions menu and click the Site Settings option to open the site’s settings page, then click the Site Permissions link under the Users and Permissions heading

Microsoft Exchange Server 2013 : Creating new mailboxes (part 4) - Automating mailbox settings,Ready-to-go custom attributes

Exchange has always provided administrators with a set of custom attributes by which to store information about mailboxes, contacts, and groups. The logic here is that it is impossible for the designer of any general-purpose directory to include all the attributes required by every company that might use the directory.

Microsoft Exchange Server 2013 : Creating new mailboxes (part 3) - Default folders, Manipulating mailbox settings

Exchange does not create the actual mailbox in the assigned database until the user first logs on to the mailbox or, if required, to deliver a message to the new mailbox.

Microsoft Exchange Server 2013 : Creating new mailboxes (part 2) - Languages

Exchange 2013 is a highly capable multilingual product that supports server components running in at least 11 languages and client components (Outlook Web App and EAC) in over 60 languages from Amharic to Welsh.

Microsoft Exchange Server 2013 : Creating new mailboxes (part 1)

Creating a new mailbox with EAC is easy. Open Recipients, select Mailboxes, and click the + (plus) sign to expose the dialog box to collect details about the new mailbox

Microsoft Exchange Server 2013 : Mailbox management - The need for mailboxes, Naming mailboxes

Email address policies enable you to define and apply different patterns for the SMTP addresses that are assigned to mail-enabled objects. The application of address policies makes sure that the SMTP addresses are consistent throughout the organization.

Microsoft Exchange Server 2013 : Mailbox management - Managing Recipients - Exporting EAC information to CSV files

An email server such as Exchange deals with huge differences in terms of object numbers. The largest Exchange organizations running outside Office 365 have over half a million mail-enabled objects.

Windows Server 2012 : Implementing DNSSEC (part 2) - How DNSSEC works,Deploying DNSSEC

DNSSEC works by combining public key infrastructure (PKI) cryptography with DNS to use digital signatures and cryptographic keys to sign DNS zones and validate that DNS responses are authentic.

Windows Server 2012 : Implementing DNSSEC (part 1) - Benefits of DNSSEC, DNSSEC in previous Windows Server versions

DNS is used for locating resources on a TCP/IP network and the Internet. For example, when a user types www.bing.com into the address bar of Internet Explorer, the DNS client on the user’s computer sends a name query request to a DNS server.

Windows Server 2012 : Ensuring DHCP availability (part 3) - Managing DHCP failover

After DHCP failover is enabled and configured, you can manage your DHCP failover solution using the DHCP console. Examples of management tasks you can perform for DHCP server failover include the following

Windows Server 2012 : Ensuring DHCP availability (part 2) - Implementing DHCP failover

To enable DHCP failover, begin by installing two DHCP servers running Windows Server 2012, designating one of them as the primary server and the other as the secondary server. If the DHCP servers are domain members, they must be authorized in Active Directory. However, you can also implement DHCP failover on standalone DHCP servers in a workgroup.

Windows Server 2012 : Ensuring DHCP availability (part 1) - Previous approaches to implementing DHCP availability

DHCP failover is a new approach to ensuring DHCP availability that is included in Windows Server 2012. With this approach, two DHCP servers can be configured to provide leases from the same pool of addresses.

Sharepoint 2013 : Managing Security - See Who Is a Member of a SharePoint Group

SharePoint groups are defined at a site level. To see who is a member of a SharePoint group, you need the right permissions on the site itself. If you have those rights, you can click on the cogwheel icon at the top of the page to open the menu and select Site Settings

Sharepoint 2013 : Managing Security - Grant Permissions to a File or List Item

You want to change the permissions a certain user or group of users has on a file or list item. Because permissions for items are inherited from the list or library they are in, the items or files have the same permissions as the list.

Sharepoint 2013 : Managing Security - See What Permissions Are Set (part 2) - Read the Permissions Page, Check the Permissions for a Specific User or Group

By clicking the Advanced link from the Shared With dialog, you get to the permissions page for either a file, item, list, or library. This page is used to administrate the permissions of the object in question.

Sharepoint 2013 : Managing Security - See What Permissions Are Set (part 1) - Check Permissions on Files and List Items

You want to see what permissions are given to whom in a list or library or on a specific list item. For example, you want to know who can read, write, or delete files in a document library. Alternatively, you want to know who has permissions to read a specific document or to edit it.

Microsoft Exchange Server 2010 : Creating and Managing Accepted Domains (part 3) - Changing the Accepted Domain Type and Identifier , Removing Accepted Domains

In the Exchange Management Shell, you can use the Set-AcceptedDomain cmdlet to modify accepted domains. Example 3 provides the syntax and usage. Use the –AddressBookEnabled parameter to enable recipient filtering for this accepted domain.

Microsoft Exchange Server 2010 : Creating and Managing Accepted Domains (part 2) - Creating Accepted Domains

Only domain names you specify can be used as part of an e-mail address policy. Because of this, if you want to use a subdomain as part of an e-mail address policy, you must either explicitly configure the subdomain as an accepted domain or use a wildcard character to include the parent domain and all related subdomains.

Microsoft Exchange Server 2010 : Creating and Managing Accepted Domains (part 1) - Viewing Accepted Domains

An accepted domain is any SMTP namespace for which an Exchange organization sends or receives e-mail. Accepted domains include domains for which the Exchange organization is authoritative, as well as domains for which the Exchange organization relays mail.

Microsoft Exchange Server 2010 : Managing Message Pickup, Replay, Throttling, and Back Pressure (part 2) - Configuring Message Throttling

Message throttling sets limits on the number of messages and connections that can be processed by a Hub or an Edge Transport server. These limits are designed to prevent the accidental or intentional inundation of transport servers and help ensure that transport servers can process messages and connections in an orderly and timely manner.

Microsoft Exchange Server 2010 : Managing Message Pickup, Replay, Throttling, and Back Pressure (part 1) - Configuring and Moving the Pickup and Replay Directories

When a Hub Transport or an Edge Transport server receives incoming mail from a server using a non-SMTP connector, it stores the message in the Replay directory and then resubmits it for delivery using SMTP.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Windows Backup (part 2) - Creating and managing backup jobs

We will start by creating a new scheduled backup job that will backup the data on our server, using the bare meta recovery option which will backup all data on the server including the operating system configuration

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Windows Backup (part 1) - Installing Windows Server Backup

Windows Server 2008 R2 provides a fairly feature-rich backup solution for backing up individual servers. Windows Server Backup is a feature that can be added to a Windows Server 2008 R2 server to be used to perform backups of the local system only. It cannot backup data from remote servers.

Windows Server 2008 R2 high-availability and recovery features : Planning for Backups and Disaster Recovery

One of the most important and overlooked functions of administering a Windows network is planning for and implementing good backup and recovery solutions.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Network Load Balancing (part 2) - Creating a Network Load Balancing cluster

After installing the NLB feature on each server that will become a cluster node, you are ready to create a new cluster. Perform the following to create a new NLB cluster

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Network Load Balancing (part 1) - Adding Network Load Balancing feature

The first step to setting up NLB is to add the feature from Server Manager. You will need to perform this on each server you want to add to the NLB cluster.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 8) - Administering a Failover Cluster

After you set up a new cluster, you will need to make sure that you are familiar with the management interface and understand how to perform basic cluster administration tasks.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 7) - Create shared folder on cluster, Testing Failover of Cluster

The file server cluster should now be configured and accessible to clients using the cluster name established for client connectivity. You are now ready to create a new file share for clients to access.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 6) - Add primary storage to cluster, Configure service or application

Now that the cluster is set up, you are ready to set up the service or application you wish to support on the cluster. In our example, we will be using the cluster to provide HA to a windows file server.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 5) - Creating a new Failover Cluster

Enter the name and IP address to be used for the cluster (see Figure 20). The name you choose is the name that will be used to administer the cluster. After entering the cluster name and IP address, click Next.

Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 4) - Verifying cluster configuration using the Cluster Validation Wizard

The Cluster Validation Wizard will perform a series of rigorous tests to ensure that you storage, nodes, and network are configured properly to support a Windows Server 2008 R2 failover cluster.