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 4 of 59, items 151 to 200 of 2916.

Windows Server 2012 : Configuring IPsec (part 5) - Configuring connection security rules - Creating an authentication exemption rule, Creating a server-to-server rule, Creating a tunnel rule

The following steps can be used to create a new authentication exemption rule using the Windows Firewall with Advanced Security snap-in

Windows Server 2012 : Configuring IPsec (part 4) - Configuring connection security rules - Types of connection security rules, Creating an isolation rule

Connection security rules can be created using the New Connection Security Rule Wizard. As Figure 7 shows, Windows Firewall with Advanced Security supports five types of connection security rules

Windows Server 2012 : Configuring IPsec (part 3) - Configuring IPsec settings - Customizing IPsec tunnel authorizations, Configuring IPsec settings using Windows PowerShell

If IPsec tunnel connections will be allowed with the computer, you can use the Customize IPsec Tunnel Authorizations dialog box shown in Figure 6 to configure this. Using this dialog box, you can specify

Windows Server 2012 : Configuring IPsec (part 2) - Configuring IPsec settings - Customizing IPsec defaults

As described in the previous section, the Customize IPsec Defaults dialog box shown in Figure 2 is used to configure the default IPsec settings that the local computer will use when attempting to establish secure connections with other IPsec-enabled computers

Windows Server 2012 : Configuring IPsec (part 1) - Understanding connection security

IPsec can be implemented using Windows Firewall with Advanced Security by creating and configuring connection security rules.

Microsoft Lync Server 2013 : Director Troubleshooting (part 3) - Synthetic Transactions,Telnet

A feature carried over from Lync Server 2010 are synthetic transactions that are a set of PowerShell cmdlets used to simulate actions taken by servers or users in the environment.

Microsoft Lync Server 2013 : Director Troubleshooting (part 2) - DNS Records, Logs

A good source of information in troubleshooting any server issue is the event log. Lync Server 2013 creates a dedicated event log for informational activities, warnings, and errors within the standard Windows Server Event Viewer console.

Microsoft Lync Server 2013 : Director Troubleshooting (part 1) - Redirects, Certificates

The main advantage to a Director for internal users is to provide the user’s primary and backup registrar information. This way, a client knows exactly which server to contact next if it is unable to contact the primary server.

Microsoft Lync Server 2013 : Administration of the Director Role (part 4) - Services Management, Client Version Filter

One potential use case for a Director is to control the client versions connecting to the Lync Server infrastructure. Since the Director is an initial sign-in point for any client, it makes sense to perform a filter check at the sign-in point.

Microsoft Lync Server 2013 : Administration of the Director Role (part 3) - Topology Status

A relatively easy method of checking the health status of a Director server or pool exists through the Lync Server Control Panel. To check the status of a Director pool, perform the following steps

Microsoft Lync Server 2013 : Administration of the Director Role (part 2) - Ports,Firewall Rules

It can be fairly interesting to view what kind of services and ports are actively listening for connections on a server role. Table 1 shows which ports are specific to Lync and active after installation of a Director.

Microsoft Lync Server 2013 : Administration of the Director Role (part 1) - Services

Installing a Director in Lync Server 2013 creates only a minimal number of Windows services. The following services will be visible within the Services MMC after the Director installation

Microsoft Lync Server 2013 : Configuring the Director (part 2) - Web Services Ports,Reverse Proxy

To support external access to the Director web services, it is recommended to use a reverse proxy as shown in Figure 2. Although this is technically possible, it is not supported by Microsoft to allow Internet traffic directly to the external web services ports

Microsoft Lync Server 2013 : Configuring the Director (part 1) - SRV Records, Web Services FQDN Overrides

When a Director pool is created in the Topology Builder, the web services FQDNs are automatically provisioned with an option to override the internal and external FQDNs.

Sharepoint 2013 : SharePoint Designer 2013 (part 2) - Locking Down SharePoint Designer

SharePoint Designer is a great tool for editing design files, uploading files in bulk to SharePoint, and making configuration changes to lists and sites.

Sharepoint 2013 : SharePoint Designer 2013 (part 1) - New Features

SharePoint 2013 includes all of the existing capabilities of the previous version with some new features and enhancements.

Sharepoint 2013 : Branding with the Design Manager (part 2) - Creating a Brand

You are now getting to the fun part of Design Manager: the capability to design a SharePoint brand from raw HTML, CSS, and JavaScript files.

Sharepoint 2013 : Branding with the Design Manager (part 1)

Branding SharePoint has never been a trivial task. I know a number of talented SharePoint UI designers who have devoted their careers to doing just that. Designing a good user interface brand for any web site requires experience and knowledge of web rendering principles.

Sharepoint 2013 : SharePoint Designer and Branding - SharePoint 2013 User Interface

Because the new Windows 8 branding is less graphic intensive and geared more to simplicity with text, the coding behind the design is less complex. Designers can easily integrate the design of custom functionality with minimal use of Cascading Style Sheet (CSS) elements and HTML. This is not to say that the user interface loses capability.

Sharepoint 2013 : Microsoft Office Integration and Office Web Applications - Office Web Applications

Office Web Applications (Office Web Apps) are web browser–based applications that enable users to edit Word, Excel, PowerPoint, and OneNote files without needing Microsoft Office applications installed on client machines.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 5) - Outlook delegate access

Apart from the control an administrator can exercise over mailbox access, Outlook users can also control access by using the Delegate Access option, found in the backstage area for Outlook 2013.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 4) - Sending messages on behalf of other users

If you plan to send messages on behalf of other users, you should enable the From field in the client interface so that users can select the mailbox from which they want to send the message.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 3) - Mailbox auto-mapping through Autodiscover

Granting Full Access to a mailbox is one thing; a user being able to open the mailbox to access it is quite another. The traditional approach has been to modify the user’s Outlook profile so that the mailbox is opened along with the other resources available to the user.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 2) - Managing Full Access permission

Assigning Send As permission for a mailbox enables a user to impersonate someone else, but apart from being able to create and send messages, the Send As permission does not grant any further access to mailbox contents.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 1) - Mailbox delegation

The ability to change the way messages are processed in a mailbox became a fundamental part of email system functionality a long time ago.

Microsoft Exchange Server 2013 : Mailbox management - Health mailboxes

Exchange 2013 includes a new Managed Availability feature that is incorporated in the system architecture so Exchange can detect and resolve common problems caused by malfunctioning components

Microsoft Exchange Server 2013 : Mailbox management - Discovery mailboxes - Creating additional discovery mailboxes

Discovery mailboxes are used as the repository for the metadata that drives eDiscovery searches and the output the searches generate from user mailboxes.

Windows Server 2012 : Administering Active Directory using Windows PowerShell (part 3) - Performing an advanced Active Directory administration task

Finally, opening the Active Directory Sites And Services MMC console shows the expected configuration of sites, site links, and domain controllers.

Windows Server 2012 : Administering Active Directory using Windows PowerShell (part 2) - Finding Active Directory administration cmdlets

The Get-Command cmdlet, which is new in Windows PowerShell 3.0, can be helpful when you need to find cmdlets to perform some administration task on Active Directory.

Windows Server 2012 : Administering Active Directory using Windows PowerShell (part 1) - Managing user accounts with Windows PowerShell

Creating and managing user accounts is a common Active Directory administration task. Windows PowerShell provides considerable flexibility in how this can be done on the Windows Server 2012 platform.

Windows Server 2012 : Enabling advanced features using ADAC (part 3) - Creating fine-grained password policies

Before you can create fine-grained password policies for a domain, you must ensure that the domain functional level is Windows Server 2008 or newer. This can be done using either ADAC or Windows PowerShell as described in the previous topic in this lesson.

Windows Server 2012 : Enabling advanced features using ADAC (part 2) - Configuring fine-grained password policies

In Windows Server 2003 and earlier, you could have only a single password policy and account lockout policy governing all user accounts in a domain.

Windows Server 2012 : Enabling advanced features using ADAC (part 1) - Enabling and using the Active Directory Recycle Bin

Administrators of Active Directory environments sometimes make mistakes—for example, deleting the user account for a user who still needs access to the corporate network. The effects of such mistakes can range from lost end-user productivity to broken network functionality.

SQL Server 2012 : Latch Contention Examples - UP Latches in tempdb, Spinlock Contention in Name Resolution

It is possible that the resource your request is waiting on might be in tempdb, rather than the database you have designed. You can see this by looking at the wait_resource field in sys.dm_exec_requests and, in particular, the first number, which indicates the database.

SQL Server 2012 : Latch Contention Examples - Queuing

Another typical scenario that can exhibit large amounts of latch contention is a system designed to allow queuing, for similar reasons to the last example, although exhibited in a slightly different way, and certainly resolved with a different method.

SQL Server 2012 : Latch Contention Examples - Inserts When the Clustered Index Key Is an Identity Field

A lot of advice suggests using an identity field for the clustered index on a table. Certainly there are benefits to doing this.

SQL Server 2012 : Latches and Spinlocks - Monitoring Latches and Spinlocks

In terms of monitoring latches, you’ve already been introduced to some of the DMVs. There’s more to monitoring latches than just DMVs, though. Performance Monitor also offers useful information about latches, as do extended events, which also provide information about spinlocks.

SQL Server 2012 : Latches and Spinlocks - SuperLatches/Sublatches

The queuing method of accepting all compatible latches each time the latching check is done only helps so far. It’s still a lot of work to manage all this. Enter the SuperLatch (or sublatch).

SQL Server 2012 : Latches and Spinlocks - Latch Types, Latch Modes

There are hundreds of different types of latch, most of which you are unlikely to encounter in any meaningful way when you are working with SQL Server. While latch waits will occasionally show up in sys.dm_os_wait_stats, you normally have to actively search for them. As a rule, they don’t come to you.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - Client-Side Object Model API Coverage

One of the original drawbacks with the prior implementation of the Client-Side Object Model was its lack of coverage for SharePoint APIs and access to functionality.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - REST and OData (part 3) - Creating, Updating, and Deleting

In this example you use a SharePoint-hosted app using the Napa Office 365 Development Tools and use the REST/OData API to create a new list in the host Web.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - REST and OData (part 2) - Filtering and Selecting

When you query for data it’s important to ask for only the data you really need. This keeps payload sizes down and speeds up delivery of the data. _Api uses OData semantics to let you do this by filtering records and selecting properties you want.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - REST and OData (part 1) - Getting Started with REST and OData

To query for data, issue a GET request. To update data you use either a PUT or MERGE request passing the data you want to update.

Sharepoint 2013 : Integrating Apps for Office with SharePoint (part 2) - Apps for Office Integrated with an App for SharePoint

For standalone Apps for Office, SharePoint provides a nice platform for IT to govern these apps within the enterprise. However, integrating Apps for Office into an app for SharePoint solution also makes a lot of sense.

Sharepoint 2013 : Integrating Apps for Office with SharePoint (part 1) - Standalone Apps for Office

You can integrate Apps for Office with SharePoint in two ways. One method is to configure Office clients to use SharePoint as the central location to browse the available Apps for Office internal to the enterprise.

Sharepoint 2013 : The Office JavaScript Object Model (part 3) - App Security

When delivering any technology solution you must give special attention to the types of security measures that have been taken to keep the user’s computer safe from malicious attacks. As a developer, you need to have a good sense for what the security framework is and the freedom and constraints with which you have to work.

Sharepoint 2013 : The Office JavaScript Object Model (part 2) - Functional Capabilities by Office Client,Mailbox-based Apps

Certainly as widely used by business professionals as Excel is for number crunching and Word is for authoring documents, a vast number of people exist whose days are built around communicating, scheduling, managing contacts, and ordering their day’s tasks with Outlook.

Sharepoint 2013 : The Office JavaScript Object Model (part 1) - Document-based Apps

The Office JSOM provides many capabilities for document-based apps for Office. With Office JSOM, your web application can programmatically interact with a selection the user has made, read or write to your document, react to events as the user enters a specific location or changes data in the document, save one or more settings in the document so that they are persisted for the next time the document is opened, and much more.

SQL Server 2012 : Understanding Latches and Spinlocks (part 3) - Latching Example - With Latching

With latches, Transaction 1 holds the EX latch for as long as it is needed to both write the row and update the page header and offset. Only then does it release the latch and allow another transaction in.

SQL Server 2012 : Understanding Latches and Spinlocks (part 2) - Latching Example - Without Latching

This part of the example represents a world without latches. Assume that the row containing the values (2,200) in Transaction 1 arrived at the page a fraction of a second before Transaction 2, when the values (3,300) are written. Transaction 1 writes to Slot 1