I have seen the same issue, and been unable to program a way out of it. (I have 8 scheduled tasks to clean up the SB 5.1.8 server/db). Right now, finding duplicates is a manual process, so it just doesn't happen very often. There's something about not having an audit trail, that causes the sbadmcl to not find old machines, either.
Great - so I'm not a complete lemming! Someone else noticed it too :-)
I know it is actually trying to do something, because when i change the checkforseq from Yes to No, the script runs 10 times faster. I have tried to move the place in the script it executes, but to no avail.
The 'no audit information' I believe is the safe option. Although it would be nice to create a custom script to override that. The Check for Sqe is really impt for me as I have thouands of dups and it's really a royal pain doing it manually as you have been. I have better things to be doing on a Saturday night, I'm sure you are of the same opinion!
thx for the response.
My memory is a bit fuzzy on this one, but I think -check for seq only works if the machine has an entry in its audit log. So if you have a bunch of duplicate machines with no audit events, then they get skipped or ignored. You'd have to test to confirm this.
How would one force a client to create another db object Dan? Mostly, it's autodomain doing it here, and there are never any seq events... I'd really like to use the "desc" field instead of the audit log?
Something like - if sequence found (ignore audit log) and desc is set to 'not encrypted' then delete.
How did you arrive with "thousands" of duplicate machine objects?
You could clean inactive ones (no audit) if they were created long time ago. With precautions taken, of course.
yes, it requires the audit to be non-overlapping, and there to be audit.
it's not designed to capture the case of a lot of machine templates, only the real case of a refreshed machine.
Wow - I am going to have carpal tunnel syndrome by the time I am done here. Hopefully with a SQL back end it'll be prettier? Please oh please say it will?
Thanks for the feedback everyone.
You can start playing with EEv6 (was released to world few days ago) to get a feel for that "SQL" easyness...
Speaking of which, what is the querry to get EE user failed login attempts info? Oops, that question should be in new discussion thread...
just dump the audit for all users and all groups for that event and you'll get that - or use the report generator to do the same. Getting the failed attempt list is easy.