0
Answered

Auto-configuration should not require the archiving of run profile history

Matthew Woolnough 5 years ago • updated by anonymous 3 years ago 4

If you dont want to save run profile history, you still need archive location. Should not be required.

Hi Matt,

Was this when you were configuring through the auto-configuration wizard? If so, I believe the 0 days is unrelated to whether or not it archives, as 0 would simply imply things should be archived immediately. The wizard mandates that run profiles are archived, which may not be appropriated. Do you think it should be optional, and if so, do you think the terminology on that page needs clarification?

As a work around, you can go in the operation in the operation list and manually disable it.

No, I don't think this is appropriate. You shouldn't be forced to save the Run Profile history. I know BCE have already expressed that they don't wish to save this.

The Clear Runs page in FIM does provide an option of keeping a configurable amount of Run Profile history in the DB too. I think most people use this option as it removes the necessity of keeping it in logs if you have the most recent x days of runs in the DB. Would be good to have it in Event Broker too.

i.e. run daily - delete anything older that 30 days.

http://social.technet.microsoft.com/wiki/cfs-file.ashx/__key/communityserver-wikis-components-files/00-00-00-00-05/5756.clearrunsdialog.png

Updated description from "Event Broker wont save '0' as retention period without run profile archive directory"

Migrated to Visual Studio Online.