DFS-N: Client Side DFS Folder Availability

Microsoft.Windows.FileServer.DFSN.Client.HealthStateUnitMonitor (UnitMonitor)

This rule accesses DFS folders (links) from a client computer and enters a Critical health state if the folders are inaccessible.

Knowledge Base article:

Summary

This rule monitors the availability of DFS folders (links) by accessing them from a client computer and enters a Critical health state if the folders are inaccessible.

Configuration

Override the UNCPaths parameter on this monitor to specify which DFS folders to monitor. Use a colon “:” to separate multiple folders.

Causes

This monitor enters a Critical health state if it is enabled and cannot access any of the paths listed in the UNCPaths parameter of the monitor. This can occur if the client computer on which the monitor is enabled could not resolve the DFS paths to the actual folder target or if the folder target is offline or inaccessible.

Resolutions

Click the Client Alerts view in the Operations console to see which paths are not accessible and then perform the following actions:

Check Namespace Health

Use the Dfsdiag /testreferral command to check the health of a namespace. To do so in the Operations console, use the following procedure:

If any tests fail, escalate the resolution of this problem to a technician who can troubleshoot DFS Namespaces issues.

Verification

To verify that the folder (link) and folder targets are functioning properly, use the Dfsutil link command. To do so in the Operations console, use the following procedure:

1. Click the Dfsutil task.

2. Click Override in the Run Task – DFSUTIL dialog box.

3. Type link \\<namespace>\<folder> in the DfsServerTask.CommandLine box, where <namespace> is the namespace root and <folder> is the DFS folder whose folder targets you would like to verify are online.

4. Confirm that the state of the folder is OK and that the states of the appropriate targets are Online.

If the link (folder) is not OK, escalate the resolution of this problem to a technician who can troubleshoot DFS Namespaces issues. If the folder target is Offline, troubleshoot the server hosting the folder target.

Element properties:

TargetMicrosoft.Windows.FileServer.DFSN.Client
Parent MonitorSystem.Health.AvailabilityState
CategoryCustom
EnabledTrue
Alert GenerateFalse
Alert Auto ResolveFalse
Monitor TypeMicrosoft.Windows.FileServer.DFSN.Library.DFSPathAvailabilityUnitMonitorType
RemotableTrue
AccessibilityPublic
RunAsMicrosoft.Windows.FileServer.DFSN.DFSTargetAccessAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.FileServer.DFSN.Client.HealthStateUnitMonitor" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.FileServer.DFSN.Client" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RunAs="Microsoft.Windows.FileServer.DFSN.DFSTargetAccessAccount" TypeID="Microsoft.Windows.FileServer.DFSN.Library.DFSPathAvailabilityUnitMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId48c71c866f164610bffb981b14a160cc" MonitorTypeStateID="Accessible" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateId9c6deac0737c4d379ca8fbcc5b818b30" MonitorTypeStateID="NotAccessible" HealthState="Error"/>
</OperationalStates>
<Configuration>
<IntervalSeconds>3600</IntervalSeconds>
<SyncTime/>
<UNCPaths/>
<TimeoutSeconds>300</TimeoutSeconds>
</Configuration>
</UnitMonitor>