locked
DFS Backlog Monitoring is blank RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    After following the guides to enable DFS replication backlog monitoring (found at http://blogs.technet.com/b/filecab/archive/2009/10/27/configuring-the-dfs-replication-management-pack.aspx and http://blogs.technet.com/b/filecab/archive/2009/10/27/optional-configuration-for-the-dfs-replication-management-pack.aspx) the Backlog Monitoring is blank. The guide says it takes some time but I gave it 24 hours with no change.

    On one of the two servers, there are no errors in the Windows event log. Should there be entries for when the backlog discovery script runs?

    On the other server, I am getting the following error. Both servers have the RunAs account as local administrators and the event log says this account is succussfully logged on. I am currently stuck and would love some ideas!

    The process started at 8:24:28 AM failed to create System.Discovery.Data, no errors detected in the output.  The process exited with 4294967295

    Command executed: "C:\Windows\system32\cscript.exe" /nologo "BacklogDiscovery.vbs" 0 {B1849E22-43F0-A3F5-AA58-3BCF580D1040} {4725CA8E-6788-822B-904C-9F21F6AC0BA4} TOPS-REPORT02.DBHOSTING2.local

    Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\3963\

    One or more workflows were affected by this. 

    Workflow name: Microsoft.Windows.DfsReplication.DFSRBacklogDiscovery

    Instance name: TOPS-REPORT02

    Instance ID: {4725CA8E-6788-822B-904C-9F21F6AC0BA4}

    Management group: DBUSI

    Thursday, February 23, 2012 3:14 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    I added the RunAs account as a local admin after it was pushed to the monitored servers. After realizing this account may need to be logged off in order to get its admin priviledges, I removed the RunAs account and performed the whole process again. After doing this, backlog monitoring is now working correctly.


    Thursday, February 23, 2012 4:06 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    I added the RunAs account as a local admin after it was pushed to the monitored servers. After realizing this account may need to be logged off in order to get its admin priviledges, I removed the RunAs account and performed the whole process again. After doing this, backlog monitoring is now working correctly.


    Thursday, February 23, 2012 4:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please check AddOn DFS Replication Management Pack on TechNet Gallery: https://gallery.technet.microsoft.com/AddOn-DFS-Replication-33d233a8

    It addresses some of the shortcomings of the Microsoft MPs.
    • Proposed as answer by Stelian Postea Tuesday, October 25, 2016 5:26 PM
    Tuesday, October 25, 2016 5:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    To add,

    After configuration leave default interval as it is.....Interval here is like how long to run script and if you keep less interval, our discovery will be affected.



    Thursday, January 18, 2018 11:13 AM