DFS-R Health Report for SYSVOL

Distributed File System Replication (DFS-R) was introduced as a replacement for File Replication Service (FRS) in Windows Server 2008, and was further enhanced in Windows Server 2008 R2. When your domain functional level are set to Windows Server 2008, you have the option to migrate SYSVOL-replication from the deprecated FRS to the new and more reliable DFS-R service. A major advantage of using DFS-R over FRS is that FRS copies the whole file when a change are made, while DFS-R only copies the changed bits. This and further details are discussed here. Ive also included some links in the resource section below on how to perform an FRS to DFS-R migration.

Included in the Windows Server 2008 and Windows Server 2008 R2 are the DFS Management-console as well as several command-line tools for administering DFS. A great built-in feature in these tools is the diagnostic reports.

This is available in the DFS Management-console:

image

As well as from the DfsrAdmin.exe command-line tool:

image

Using this feature we can generate an HTML-report containing a great overview of the replication health for the SYSVOL replication group:

image

Any errors and warnings will be shown with detailed explanations. In addition we can view general information and statistics i.e. regarding free diskspace on the domain controllers, bandwith savings and so on (click on the thumbnail to view):

image

Since the reporting feature are available from the DfsrAdmin.exe command-line tool, it makes it easy to set up a script as a scheduled task that also sends the generated report via e-mail i.e. every morning. Ive published a simple PowerShell-script to accomplish this which is available here.

Resources

SYSVOL Replication Migration Guide: FRS to DFS Replication (Word-version available here)

Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration

DFSR SYSVOL Migration FAQ

Configuring DFSR to a Static Port

FRS to DFSR Migration Tool (not for SYSVOL migration)

Lync Server 2010 Remote Administration

When Lync Server 2010 is deployed, there are two main administration tools:

  • Lync Server Control Panel
  • Lync Server Management Shell

Both are available from the Start-menu on a Lync Server:

image

 

Lync Server Control Panel

The Lync Server Control Panel are a web-based graphical administration tool built on Silverlight:

image

When deploying Lync, an administrative access URL needs to be specified, i.e. https://lync-admin.contoso.local. This makes it possible to administer the Lync Server 2010 environment from any web-based client that supports Silverlight.
In fact, every operation were performing in the Lync Server Control Panel is running PowerShell Lync cmdlets in the background.

 

Lync Server Management Shell

The Lync Server Management Shell is based on Windows PowerShell 2.0:

image

Like Exchange Server 2010, Lync Server 2010 provides an IIS (Internet Information Services) PowerShell provider.

This makes it possible to administer the Lync Server 2010 environment using PowerShell remoting. An example:

001
002
$session = New-PSSession -ConnectionUri https://lync-admin.contoso.local/OcsPowershell -Credential (Get-Credential)
Import-PSSession -Session $session

 

When running the above example, you are prompted for credentials. Specify a domain user account that has been delegated permissions to administer the Lync Server 2010 environent, i.e. one of the default security groups CSAdministrator or RTCUniversalServerAdmins. When the session are successfully established all cmdlets in the remote session are imported to your local PowerShell-session. This is whats called PowerShell implicit remoting.

 

Additional resources

Lync Server TechCenter

Microsoft TechNet: Lync Server Management Shell

Lync Server PowerShell Blog

NextHop