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 10 of 59, items 451 to 500 of 2916.

Sharepoint 2013 : Backup and Restore (part 2) - Export and Import - Using PowerShell, STSADM, Central Administration

In this section, I demonstrate how to use Central Administration to export a site, list, or library. You may have noticed that this section does not cover import via the Central Administration web browser interface—this is because Central Administration does not provide a mechanism for site, list, or library import from a file.

Sharepoint 2013 : Backup and Restore (part 1) - Site Collection Backups

Site collection backups are compelling in that they enable administrators to save a complete site collection to a file on disk. Administrators may back up a site collection using the STSADM command, PowerShell, or Central Administration.

Sharepoint 2013 : Health Monitoring and Disaster Recovery - Maintaining Content Integrity (part 2) - Versioning

Document and page versioning is another way in which users may self-maintain integrity of their content in SharePoint. Library owners may enable versioning on a list or library so that when users with collaborative permissions upload changes, SharePoint keeps track of the version history.

Sharepoint 2013 : Health Monitoring and Disaster Recovery - Maintaining Content Integrity (part 1) - The Recycle Bin

Since SharePoint 2007 (WSS 3), the Recycle Bin has provided a mechanism for users to retrieve deleted lists and list items—this includes documents and document libraries. Users can find the Recycle Bin on the top right of the Site Contents page .

Sharepoint 2013 : Health Monitoring and Disaster Recovery - SharePoint Farm Design

The design of your SharePoint farm has a large impact on the level of disaster recovery. At the lower end of the scale, a simple farm with minimal redundant hardware provides little to no recovery in the event of failure, whereas a multiple server farm with multiple redundant servers provides rapid recovery.

Sharepoint 2013 : Planning for Disaster Recovery

It is never a happy day for the IT group when an online service goes down, and this includes SharePoint. As fantastic as SharePoint is, it is inevitable that at some point in the life cycle, your SharePoint solution will suffer from downtime.

System Center Configuration Manager 2007 : Distributing Packages - Creating Collections (part 5) - Exclusion Collections

Exclusion collections are useful in situations where you want software to deploy to a large number of systems but have specific systems you want to exclude. An example of where this applies is with validated systems. A validated system is one that has a strict process to validate system functionality any time software is installed on it.

System Center Configuration Manager 2007 : Distributing Packages - Creating Collections (part 4) - Dependent Subcollections

With all the information ConfigMgr gathers from hardware and software inventory, it can be difficult to identify which criteria to use to restrict collection membership. Although the Criterion Properties dialog box provides a list of values available for the various categories, it is often helpful to see the fields and values in a different format to find what you are looking for.

System Center Configuration Manager 2007 : Distributing Packages - Creating Collections (part 3) - Creating a Dynamic Collection Limited to a Collection

After creating a collection that includes all the Windows XP and Windows Vista systems, you can use that collection to limit the available members of another collection, in this case a Forefront collection, to target the Forefront client software for deployment.

System Center Configuration Manager 2007 : Distributing Packages - Creating Collections (part 2) - Creating a Dynamic Collection

The SCCMUnleashed.com organization is starting the process of deploying the Forefront client to a set of workstations, but wants to limit the size of the deployment to mitigate the risk of affecting large numbers of workstations simultaneously.

System Center Configuration Manager 2007 : Distributing Packages - Creating Collections (part 1) - Static Collections

Static collections are the easiest type of collection to create, and they are useful when you want to define a limited number of systems or users in a collection when the collection membership does not change frequently.

Sharepoint 2013 : New Installation and Configuration - Configuring Your SharePoint Farm

If you skip the Farm Configuration Wizard after completing the SharePoint Products Configuration Wizard, you may execute it at any time from the bottom-right link of the main Central Administration home page.

Sharepoint 2013 : New Installation and Configuration - Managed Accounts

SharePoint makes use of various domain-level accounts to operate securely. Even if your SharePoint installation operates on a single server and is part of a work group, all accounts used in SharePoint 2013 require the full domain name syntax: DOMAIN\username (domain is the machine name in a stand-alone installation). SharePoint 2010 had the same requirement.

Sharepoint 2013 : New Installation and Configuration - SharePoint Products Configuration Wizard

We are now ready to proceed through the SharePoint Products Configuration Wizard—or Configuration Wizard for short. The Configuration Wizard performs the tasks necessary to join a server (with SharePoint binaries installed) to an existing farm, or to provision a new farm.

Sharepoint 2013 : New Installation and Configuration - Choosing the Installation Type

Like its predecessor, SharePoint allows an administrator to install either a stand-alone or a server farm configuration. Running setup.exe from the installation media presents you with the dialog shown in Figure 1, at which point you must make a choice.

Sharepoint 2013 : New Installation and Configuration - SharePoint 2013 Prerequisites

SharePoint 2013 includes a prerequisites installer application, which ensures that SharePoint has all the necessary software components to operate. Such components include various hot fixes, SQL Server Reporting and Analysis components, .NET 4.5, Microsoft Sync Framework, Windows Server AppFabric, and Windows Identity Framework. . . to name a few.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - GPO Administrative Delegation

GPO administrative delegation is a process that administrators can follow to delegate permissions to specific users or configure security rights across all GPOs or specific GPOs and GPO-related tasks on specific Active Directory containers, such as sites, domains, and OUs.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - Troubleshooting Group Policies

When group policies are not processing as intended, it may become necessary to enable logging to decipher where the issues are occurring. Before logging and tracing defaults are changed, it is important to note that logging for warnings and errors is enabled by default for all extensions.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - Backing Up and Restoring Domain GPOs

Restoring a domain GPO from a backup does not re-create or restore any links previously associated with that GPO. GPO links must be re-created and reconfigured manually, but they can be referenced by viewing the settings within the GPO backup using GPMC.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - Creating and Linking WMI Filters to GPOs

When applying security filtering to a GPO is not granular enough to target a specific set of computers, a WMI filter can be linked to the GPO. For this example, we will create a WMI filter that includes a computer with an OS name of Windows 8.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - Creating and Using Starter GPOs

The Windows 8 and Windows Server 2012 GPMC includes a feature and GPO function named Starter GPOs. This function allows administrators to create or load base GPOs with preconfigured administrative template settings and values, which can be used to prepopulate new GPOs.

Windows Server 2012 Group Policies and Policy Management : GPO Administrative Tasks - Creating a GPO Central Store

For a central store to work properly, the Active Directory Forest and Domain Schema must be upgraded to at least Windows Server 2008 Schema even though the domain controller requirement is only Windows Server 2003 with the latest service pack.

Windows Server 2012 Group Policies and Policy Management : Designing a Group Policy Infrastructure

The site, domain, and OU design of an Active Directory infrastructure usually follows a few key elements, including physical office locations, network connectivity, and delegation of administration, including branch office management, separation of Active Directory management tasks, desktop and server administration, and, of course, security and reliability.

Microsoft Lync Server 2013 : Deploying Lync Online - Configuring an Auto Attendant Number

If the auto attendant feature of Exchange UM will be used with Lync Online, each auto attendant number used must be added to the Exchange UM dial plan, and also must be configured as an access number within Lync Online.

Microsoft Lync Server 2013 : Deploying Lync Online - Enabling Users for Exchange UM, Configuring a Subscriber Access Number

If the Outlook Voice Access feature of Exchange UM will be used with Lync Online, each subscriber access number used must be added to the Exchange UM dial plan, and also must be configured as an access number within Lync Online.

Microsoft Lync Server 2013 : Deploying Lync Online - Configuring Lync-to-Phone, Creating a SIP URI Dial Plan

If a hosted voice service has been purchased from an approved Microsoft partner, you can enable the service for each user by configuring the Lync-to-phone provider for the user account, and then adding the user’s phone number to the Office number field.

Microsoft Lync Server 2013 : Deploying Lync Online - Configuring Dial-in Conferencing, Configuring Lync Properties for User Accounts

If a dial-in conferencing service has been purchased from an approved Microsoft partner, dial-in conferencing can be enabled for each user by configuration of the dial-in conferencing properties of the user accounts.

Microsoft Lync Server 2013 : Deploying Lync Online - Adding User Accounts in Bulk, Configuring Federation and Public IM

User accounts can be added to Lync Online/Office 365 using a comma-separated values (CSV) file. The CSV file must be specifically formatted with the correct column headings to be successfully imported.

Microsoft Lync Server 2013 : Deploying Lync Online - Adding User Accounts Using the Online Portal

Although it might not seem evident, the user location setting is actually quite important, because certain Lync Online/Office 365 services are not available in some locations. After the user location is configured, the following page will allow licensing to be applied only for services that are available in that location.

Microsoft Lync Server 2013 : Deploying Lync Online - Adding Domains to Lync Online

The first task involved in getting Lync Online up and running is adding the SIP domains that will be used with the service. When you are signing up for a Lync Online or Office 365 subscription, a single DNS domain is assigned.

Microsoft Lync Server 2013 : Office 365 and Lync Online - Experiencing Lync Online

For users that do not have Outlook installed on their client system, and therefore cannot benefit from the Online Meeting Add-in that enables meetings to be scheduled from within Outlook, the Lync Web Scheduler is provided.

Microsoft Lync Server 2013 : Office 365 and Lync Online - System Requirements

Lync Online is a service offering that can be purchased either separately or as part of Office 365 Enterprise, Microsoft’s cloud collaboration and productivity suite, which also includes Exchange Online, SharePoint Online, Office Professional Plus, and Office Web Apps.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 10)

Although the installation of all the Active Directory components, prerequisites, operating system components, updates, and hot fixes might seem to have taken forever, we are now finally ready to kick off the Exchange Server 2013 installation.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 9)

Depending on how you obtain the media for Exchange Server 2013, you may need to copy the installation media to a local drive and run the setup from that local drive.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 8)

Exchange Server 2013 can be installed on Windows Server 2008 R2 Standard or Enterprise with SP1, Windows Server 2008 R2 Datacenter RTM or later, or Windows Server 2012 operating systems. Although either Standard or Enterprise can be used, the Enterprise version is required for some of the more advanced Exchange Server features such as DAGs.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 7)

After the AD domain controller has been installed, it is necessary to configure Sites and Services to support the future Exchange Server deployment. In our example, we are going to configure two sites for a future installation of Exchange servers in two locations. We cover how to rename the default first site and how to create the second site from scratch.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 6)

There were many improvements in the Active Directory Domain Services Installation Wizard in Windows Server 2008. Although all of these improvements are available by default, some of the wizard pages will appear only if the administrator selects Use Advanced Mode Installation.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 5)

To reduce risks, prevent end-user downtime, and minimize the exposure of the production environment, it is typically recommended that the first implementation of Exchange Server 2013 be conducted in an isolated test lab rather than being installed into a production environment.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 4)

Administrators should be aware of the best practices for designing a proper Sites and Services architecture to support Exchange Server 2013. From a high-level perspective, within AD it is necessary for administrators to create sites, allocate subnets to sites, and then create site links between sites for communication to occur.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 3)

Active Directory uses a multimaster replication scheme for replicating directory information between domain controllers; however, certain domain and enterprisewide operations are not well suited for a multimaster model.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 2)

An AD infrastructure running on Windows Server 2012, Windows Server 2008 R2 Standard or Enterprise, or Windows Server 2008 Standard or Enterprise must be in place before an organization can deploy Exchange Server 2013. Exchange Server depends on the services provided by AD to successfully function, and the design and implementation of the AD environment can have an enormous impact on the success of the Exchange Server deployment.

Installing and Configuring the Basics of Exchange Server 2013 for a Brand-New Environment (part 1)

As with Exchange Server 2010, Exchange Server 2013 has various roles that can be installed on the server to perform specific functions. With Exchange Server 2010, there were five major server roles.

Reporting in Dynamics AX 2009 : Ad Hoc Reporting

Reporting Services ad hoc reporting, the second major category of Dynamics AX reports, enables users to create and view Dynamics AX reports without needing assistance from developers or IT staff. Users can simply use SQL Server Report Builder to create their own ad hoc reports.

Reporting in Dynamics AX 2009 : Building Dynamics AX Reporting Services Reports Using Visual Studio

Developers can use the Visual Studio integrated development environment (IDE) to create Dynamics AX Reporting Services reports. In this section, we cover the tools and processes that developers and administrators can use to develop Reporting Services production reports.

Reporting in Dynamics AX 2009 : Inside the Dynamics AX 2009 Reporting Framework

In this section, we identify the key components of the Reporting Services reporting framework and describe their functions. We also show how data flows through those components to provide production reports and ad hoc reports, and to allow Excel to access Dynamics AX OLAP data.

Reporting in Dynamics AX 2009 : Reporting Overview

Before delving into the details of building Reporting Services reports and creating ad hoc reporting models, you should know the primary reporting concepts in Dynamics AX and have a high-level understanding of how the Dynamics AX Reporting Framework is designed. We discuss these topics in the following subsections.

Windows Server 2012 : Installing roles and features (part 2) - Installing roles and features using Windows PowerShell

You can also install roles and features on servers running Windows Server 2012 by using Windows PowerShell commands. This approach can be useful for administrators who work in midsized to large environments that have many servers deployed—for example, in a datacenter.

Windows Server 2012 : Installing roles and features (part 1) - Installing roles and features using Server Manager

In previous versions of Windows Server, you could use the Add Roles Wizard and Add Features Wizard to install roles and features, respectively, on the server. Windows 2012 now includes a single redesigned Add Roles And Features Wizard that provides greater flexibility and control for installing roles and features on servers.

System Center Configuration Manager 2007 : Desired Configuration Management - Troubleshooting

As with all automated systems, many assumptions are made about the environment where the system is functioning. When these assumptions no longer hold true, the system fails to operate as expected. DCM is an automated system and therefore operates on certain assumptions.

System Center Configuration Manager 2007 : Desired Configuration Management - DCM Strategies

The actual functionality of DCM is relatively straightforward—create a baseline of settings and assign those to a set of systems. However, what do you do then? It really depends on what you are going to do with the data DCM provides.