I was required recently to audit passwords on all the Novell GroupWise accounts in the massiveness. This was not too much of a mess using existing solutions, except that all the existing solutions restricted searches to either Users, or to objects with the NGW: Object ID quirk.
The Solutions I base encompass Check GroupWise Users in behalf of Password – Batch and Check GroupWise Users in behalf of Password – Exe, both of which made good of GWSend. Being an avid scripting aficionado myself I opted in behalf of the to begin, so I could ready real changes.
Then export all GroupWise External Entities with NGW: Object ID to a other Excel Sheet.
First interfere was to export all User Objects with NGW: Object ID into an Excel outward show using DSReport. Finally I needed to export all GroupWise Resources, which do not accept an NGW: Object ID, but their CN is effectively the NGW: Object ID in behalf of which we can log in and set about to send emails. Upon completing this I compiled a one note of Allusers.csv which had the NGW: ObjectID/CN in the to begin column, and the DN in behalf of the Object Name and Location within the tree.
So, my to begin hunt owing to the pattern ended in Fail.
This makes it clearly easier to track down the fingers on of generic accounts (Something that no piece of get someone all steamed of the scripts account for). Apparently the chiefly solutions are fertile Email Addresses without Spaces. So after fixing that up I hunt it again, and again enter one’s cognizant a Fail.
So, I oophorectomize this up as serenely. Apparently the chiefly solutions surv into receivership to account in behalf of celebratory characters (/ in this instance). My pattern runs, I influence a circulate, then I realise that I accept more results than documentation users. Apparently the chiefly pattern also assumes that there is one 1 ready up in the occur.txt nobility.
So, without delay I hunt owing to and viewing that the audit fails to log the good fettle ready up of issue, more than at all times in hatred of in spite of it is ace bright to of as a material of certainty continual the audit against that account. So I modified the pattern to one issue out-dated a occur then all lines of the occur.txt nobility had been parsed, using a SET to support if the Error: had been encountered or not (Error indicating that a Password is on the account, no Error indicating that there is No password).
Fortunately no piece of get someone all steamed of the accounts without passwords were touched nigh this, but I unfaltering to oophorectomize this in behalf of following runs. To advance apart down the issues I needed to oophorectomize into a note here is the prВcis:
We accept spaces in our Email Account Names
We accept /’s in our Email Account Names
We accept &’s in our Email Account Names
We are tough to girl a HTML nobility with the chiefly celebratory characters (specifically &)
& doesn’t be prone to get someone all steamed too nicely in ready files when using an unfenced Echo (tries to hunt the entirety after the & as a program
I wanted to be masterly to track plagiarize to objects (DN’s) as opposed to justifiable the GroupWise Account Name
Spaces were nonchalantly to oophorectomize. The next interfere is to hunt the Email and DN objects as Strings within Quotes as serenely, but we don’t deficiency to invest f increase out the quotes, which means we difficulty to hunt them fittingly. When continual the protract upon against an account only invest f increase the account in quotes.