The GSR Collector can generate anomaly reports to identify issues that might need to be addressed before you create storage policies. The anomaly report, which is generated through data collected by the GSR Collector, lists potential problems according to seven different categories:
|
Tab Name |
Explanation |
|---|---|
|
Orphan Candidates |
Lists home folders that are not currently assigned to a User object in Active Directory. |
|
Name Mismatch |
Lists cases where a username and the associated home folder name do not match. This is frequently the case when a User object is renamed, but the corresponding home folder is not. |
|
Path Overlap |
Lists home folders that are parent paths of other user home folders. For example, a user’s home folder attribute in Active Directory is set to \\SERVER\SHARE\HOME\USERS instead of \\SERVER\SHARE\HOME\USERS\JBANKS. This is a potential conflict because if you move an object that resides in the first path, it moves all users below the user. |
|
Duplicate Storage Pointer |
Lists users that have identical home folder paths. |
|
Missing Primary Folders |
Lists users who do not have assigned home folders. |
|
Other Missing Folders |
Lists users that have auxiliary storage assigned, but the storage is not yet created. |
|
Objects Not Managed |
Lists objects in Active Directory whose managed path is populated with a value but are not managed through Novell Storage Manager. |
In NSMAdmin, click the Reports tab.
Click Anomaly Reports.
Click the tab for the category you want to view.
At this point, because none of your existing users are being managed through Novell Storage Manager, each user in Active Directory should be listed when you click the Objects Not Managed tab. Additionally, you might notice other potential problems by viewing data categorized through the other tabs.