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.
FFCITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
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
FFCITAuthor Commented:
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.
MaheshArchitectCommented:
Yes, you are right.
I think you can create schedule task with some simple batch file to move these logs to else where
below article focus on importance of these log files
http://blogs.technet.com/b/rischwen/archive/2013/02/21/exchange-2013-logging-and-space-requirements.aspx

Mahesh

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FFCITAuthor Commented:
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.
MaheshArchitectCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.