See Installing and Configuring PowerExpert SRM.
See Microsoft Hot Fix for Web UI.
The SCAlloc or SCBlock command line utilites only affect allocation and blocking attributes, respectively. Use the SCSRM command or the user interface to create a policy that contains both allocation and blocking attributes.
To view centralized audit information, you must configure a central database and have all servers write to the central database.
After installing the operating system, you must apply the following hot fixes before using the PowerExpert SRM Web UI:
You can obtain information about hot fixes through Microsoft.
When the Auto Detect Disks option is selected in preferences and the server is rebooted, all disk partitions and mount points are scanned. Correct property values of the objects are displayed only after the scanning is complete.
If the space limit on %system Drive%\Documents and Settings is active and is exceeded, the system cannot open the policy database (QAPolicyV5.mdb) and association with objects cannot be established. It is not recommended to enforce a space limit on the Documents and Settings folder because this is where user profiles are stored.
Scanned Objects table
Set ObjectID as Primary key.
Make sure "Yes" shows for identity property for ObjectID.
Drive Usage table
Make sure "Yes" shows for Allow Nulls property for Type and Volume.
File Type Usage table
Make sure "Yes" shows for Allow Nulls property for File Type.
Real Time Allocation Objects
Make sure "Yes" shows for Allow Nulls property for Server and Object.
Message table
Set ID as primary key
Make sure "Yes" shows for identity property for ID.
Change Datatype for Message column to varchar and set length to 2048.
[HKEY_LOCAL_MACHINE\SOFTWARE\WQuinn\StorageCentral SRM \5.0]
Installing the AD version of PowerExpert SRM 5.0 in a child domain requires extending the AD schema. For this reason, you must ask the Schema Administrator to first extend the schema using the ExtSche.exe program.
To extend the schema and build the PowerExpert SRM data structure in Active Directory:
Typing RegToAD /? will display the usage.
Allow enough time for schema changes to replicate to all of the child domains. Then install PowerExpert SRM 5.0 in the child domain, and answer "Yes" when prompted, "Do you want the product to support Microsoft's Windows 2000 Active Directory?," "No" when prompted, "Do you want to run Extend Schema program?" and "Yes" when prompted "Do you want to run RegToAD program?"
After installation, you will be able to use the policies in the child domain. ExtSche.exe and RegToAD.exe program are included in the \Utilities folder on the PowerExpert SRM CD.
See Web Pages Do Not Display Information.
See Program Continues To Run Report After Selecting Close.
See Auto Detect Folder Space Limit.
See Cluster Resource Groups with Only One Node as a Possible Owner.
See QAQuotasV4.DAT Not Deleted During Uninstall.
When attempting to access the AD version of PowerExpert SRM server (scenario 1, described below) or a remote PowerExpert SRM Registry version server (scenario 2, described below) through a remote web client, the managed objects, policies, file groups, and reports web pages do not display any information.
Computer(1): IIS server with Internet Explorer client
Computer(2): PowerExpert SRM server AD version
Computer(1): IIS server
Computer(2): PowerExpert SRM server Registry version
Computer(3): Internet Explorer client
Windows NT Challenge/Response (NTLM) Authentication will not allow access to any network resources beyond the Internet Information Server (IIS) computer. This is because NTLM authentication does not pass a user's credentials over the wire. It only passes a security token created at the time the user is authenticated on the network. Consequently, the username and password are unavailable to IIS when it is challenged for access to a network resource, and IIS is unable to create and pass a user's security token over the network. Thus, access to network resources requiring authentication will be denied.
If Internet Explorer is running on the same computer as the Internet Information Server, this error will not occur using NTLM, since the username and password credentials are available.
If you click Close while running a report, the program continues to run the report and closes the dialog after it has finished scanning the object.
While connected to another AD level in the WebUI, the managed objects, audit info, and most of the tabs under Preferences reflect the info from local computer instead of the AD level user is connected to.
When an auto detect folder space limit is created on the root of a drive (other than the boot drive), all subfolders are successfully detected but a folder limit object is also created on the root of the drive. This will be fixed in a future release.
When setup creates the cluster resource groups, it creates them with only one node as a possible owner and the other nodes are not included in possible owners. Because of this, cluster resource groups can't fail over to the other node. The following error is generated in Cluster Administrator when it is started on node 2 after node 1 becomes unavailable:
An error occurred attempting to read properties for the "Cluster Group StorageCentralSRM5" resource:
The specific node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
"Do you want to ignore this error and continue?"
If you ignore this error, you will get another similar error regarding 'Disk Group 1 StorageCentralSRM5' resource. To work around this problem, manually change the properties of both cluster resources, and include the other nodes as possible owners.
For computer policies to function properly, the service log on account for CapacityShield Server service and FileMonitor Server service must be marked as "Account is trusted for delegation" and must not be marked as "Account is sensitive and cannot be delegated." Also, a collector must be selected while adding a new computer policy.
When uninstalling PowerExpert SRM, the QAQuotasV4.DAT file, if it exists, does not get deleted for mount points. As a result, when the product is reinstalled, the mount points may appear to be auto detected even when the Auto Detect Disks option is unchecked in PowerExpert SRM properties. To prevent this, manually delete the QAQuotasV4.DAT file from the mount points after uninstalling the product.
The migration tool allows you to convert PowerExpert 4.1 quotas, screening rules, and reports into a format that can be used by PowerQuest PowerExpert SRM 5.0.
The migration tool is located on the PowerExpert SRM CD.
This will convert the policy database on each disk drive to the PowerExpert SRM 5.0 format and will convert all CapacityShield templates, DiskReport reports and report sets as well as the FileMonitor rules and groups so that they are usable by PowerExpert SRM 5.0. A backup of PowerExpert 4.1 will be created in the Temp directory called SC4backup.reg . PowerExpert 4.1 will then be uninstalled.
PowerQuest has a free monthly electronic newsletter that is dedicated to official announcements regarding PowerQuest products. It contains tips and techniques for getting the most out of your PowerQuest products. You can view the newsletter online (in English only) at http://www.powerquest.com/newsletter/index.html.
© PowerQuest Corporation 2002. All rights reserved. U.S. Patent 6,092,163; other patents pending in the U.S.A. and elsewhere. PowerQuest is a registered trademark of PowerQuest Corporation in the U.S.A. and elsewhere. PowerQuest PowerExpert is a trademark of PowerQuest Corporation. All other brand and product names are the property of their respective owners.