Tool
Program Purpose And Benefits
The purpose of these programs is to give you a workable method to deal with the inconsistencies that creep in over time as regards the ZENworks for Desktops inventory databases. It provides you with a means to purge dead workstation objects and defunct / duplicate inventory data from your inventory databases.
The reports will help you identify workstation containers that have been 'missed' by your inventory polices (the containers are not associated with an inventory policy), and also identify any workstations which are being inventoried by more than one inventory policy (inventory is incorrectly going in to more than one leaf database).
You are also given a report that helps pinpoint which containers held workstations that have been removed but the associated inventory data has not been purged from the inventory databases.
It also identifies all duplicate workstation objects and duplicate user objects throughout your directory tree. You are also provided with a chronological list of all users ordered by last login time, which allows you to identify redundant user accounts, and accounts that have never been used (no last login time).
The leaf database statistics are also useful for identifying where inventory roll-up policies are not being applied or are not working correctly.
The output produced by these programs includes:-
- Workstation last-registered-date reports, including statistical data:-
Number of workstation registered during the Last 30 days
Number of workstation registered during the Last 60 days
Number of workstation registered during the Last 90 days
Number of workstation registered during the Last 120 days
Number of workstation registered over 120 days ago
Number of LDIF Delete entries generated
Number of workstation with no last registered date
Number of workstation with no last scanned date
Number of workstation not scanned within the last 7 days
LDIF delete file containing records to force purge of 'dead' workstation objects.
Duplicate directory tree workstation object report.
Duplicate workstation inventory in master inventory database.
Removal files which can be used to automatically delete much of the bad inventory data from
both the master and leaf inventory databases.
Inconsistency reports comparing workstations in the directory tree, master database and leaf
databases. This identifies which workstation objects have not been inventoried and any
inventory data that is defunct.
Directory tree workstation object container totals.
User objects by last login time.
Duplicate user objects in the directory tree.
Duplicate workstation inventory in leaf server inventory database.
Overall workstation object, inventory and user statistics, including:-
- Directory Tree Workstations:
No. Duplicate Workstation Objects
No. Workstations with Duplicate Objects
Total No. of Workstations (Inc. Dup Objects)
Total No. of WKS NOT Inc. Dup Objects
Master DB Workstations:
- Duplicate Workstation Records
No. Workstations with Duplicate Records
No. WKS Records No Longer In Directory Tree
No. WKS Records in Master DB Only
Total Master DB WKS Inc. Dups/Redundant
Master DB Total WKS NOT Inc. Dups/Redundant
No. WKS NOT in Master DB (Less Tree Dups)
No. WKS in Master DB/Tree but Not In SUBDBs
Master DB WKS in Tree/SUBDBs (Inc Dups)
SUBDB Workstations:
- Duplicate Workstation Records
No. Workstations with Duplicate Records
No. WKS Records No Longer In Directory Tree
No. WKS Records in SUBDBs Only
Total SUBDB WKS Inc. Dups/Redundant
SUBDB Total WKS NOT Inc Dups/Redundant
No. WKS Not In SUBDBs (Less Tree Dups)
No. WKS in SUBDBs/Tree but Not in Master DB
SUBDB WKS in Tree/Master DB (Inc.Dups)
Statistical Summary
- Percentage of Bad/Defunct WKS in SUBDBs
Percentage of Bad/Defunct WKS in Master DB
Percentage of Duplicate WKS Objects in Tree
Percentage of Tree WKS in SUBDBs
Percentage of Tree WKS in Master DB
Percentage of Tree WKS in ALL DB's
| Adjunto | Tamaño |
|---|---|
| Inventory Cleanup.zip | 11.34 MB |
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- %count lecturas


0