asked on

User Defined Data Collector Sets in Performance Monitor Lose Settings at System Restart

We are utilizing Performance Monitor on a Win Server 2012. There are two collector sets that apparently were created when we installed Exchange 2013. I've modified both to send the output files and reports to a shared drive, and also adjusted the counters and sample intervals to manage the relevance and size of the logs. When the server is re-booted for maintenance, the settings revert back to what they were prior to my modifications, i.e. the output files and reports are pointed back to the local C: drive, the full counter lists are restored, etc. I've searched TechNet and EE, but have not been able to find a solution.

Mahesh

I think you should not alter these default counters, exchange use it for sole purposes and hence got reset most probably.

http://windowsitpro.com/blog/exchange-2013-diagnostic-and-performance-log-files

Mahesh

FFCIT

ASKER

Thanks, Mahesh. I understand that these are default counter sets used by Exchange, but do have disk-capacity issues, since the log files don't purge automatically. I guess I can create the shell command to clean them up, or find a way to point the HMS to the redirected files.

ASKER CERTIFIED SOLUTION

Mahesh

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

FFCIT

ASKER

Followed your link and ended up looking into NTFS junctions. This didn't quite fit the bill, so I'll create a few simple scheduled batch files to move older log files to another volume, then purge them when the target volume gets too full.

Thanks again.

Mahesh

Both links I shared to you are only to highlight importance of Perfmon logs in Exchange

You can disable Exchange perfmon counters through schedule task hopefully, but this is not recommended in case you required MS support if require in future

Not sure where you found NTFS junctions.
Since you have disk space issue, I suggested you to just move log files with scheduled batch files
I have not seen any better option other than this.
may be in next service pack MS will resolve this behaviour (Bug)

Mahesh