This Article will walk you through changing the necessary registry settings to get your database pointed to the right place.
Towards the bottom of the page is the section (section 7) that specifically answers your question.
Thanks, this looks helpful. For some reason though since the database has reached it's limit we can't login to the page https://22.214.171.124:8443 we use ldap authentication with our AD servers. How can we get round this?
Hi Gonzouk, I think you will need to free some space in your database bedore preceeding. You may also check that your HD isn't full or you won't get access to ePO.
You can't delete some space through OSQL commands:
When I was administrating ePO w/ SQL Express, I would periodically go into the database and manually purge the event logging tables via queries to make space then compact the database to remove excess free space. If you are unsure how to use SQL queries, backup a SQL db or access the database, don't pass go & contact support for assitance.
You can purge the audit log periodically through the console if you remember to do it prior to hitting the size limit. The only problem I found with my previous environment was that it would fail if I tried to purge more than 15-20 days at a time.
We managed to remove some old event logs fromthe DB, how can where can I use the ePolicy console to purge old data?
Automation -> Server Task Log
Change the display range w/ filter in upper left
Action -> Purge
User Management -> Audit Log
Purge -> Define range to purge