 |
» |
|
|
|
|
|
|
|
|
|
|
|
|
|
Upgrading from Version 1.1 to Version 2.0
Users of Resource Partitioning Manager Version 1.1 can upgrade to Version 2.0 keeping all current partition definitions intact. To maintain existing Resource Partition configurations from an existing Version 1.1 installation, simply follow the installation instructions included within the Version 2.0 User Guide. Version 1.1 will be detected on your system and the installation program will provide you with the option to maintain your existing partition configuration information.
Note: Version 2.0 includes many additional Resource Partition configuration settings. Once the upgrade to Version 2.0 is complete, review your Resource Partition definitions to determine whether additional features can be implemented.
Upgrading from v2.0 Evaluation Software to Version 2.0
To maintain Resource Partition configurations defined using v2.0 Evaluation software, simply follow the installation instructions included within the Version 2.0 User Guide. The Evaluation software will be detected on your system and the installation program will automatically maintain your existing partition configuration information.If you wish to discard the existing partition definitions, you can delete them via the Resource Partitioning Manager user interface either before or after performing the upgrade.
|
|
|
|
|
|
Batch Files
Using the Auto launch feature, Resource Partitioning Manager (RPM) can be configured to automatically launch processes whenever a Resource Partition is activated. In this case, when the partition is activated, RPM will launch the process(es) configured to "Auto Launch" and begin to manage their resource allocations. While RPM will capture the child processes of any process that has been auto launched, a period of time must elapse for this to occur. In some cases, a batch file may be executed and closed in less time than RPM requires to query for child processes. In this instance, RPM may not successfully capture all processes launched from the batch file.
If you choose to auto launch a batch file which then launches other process(es), include a wait time of five seconds before closing the batch file to allow RPM the time to properly capture all the child processes.
Job Objects created by other applications
Resource Partitioning Manager utilizes the Job Object API available in Windows 2000 and Windows .NET. In some cases, other applications may also create job objects using this technology. Job objects created by either the operating system or applications other than RPM should not be captured by Resource Partitioning Manager unless a specific need to do so has been identified. Capturing those objects and modifying their properties could create conflict between RPM and the originating application.
|
|
|
|
|
|
Connecting to .NET Servers
Microsoft has enhanced the security features for remote logins in Windows .NET. The Windows .NET Local Security Policy is enabled by default, preventing users from remotely logging in to a Windows .NET server using an administrator account with a blank password. Therefore, the Local Security Policy on the server running Windows .NET must be manually set to Disable before RPM will accept a connection from a remote system using a blank administrator password. The security policy is refreshed every 90 minutes, or you may reboot the server for the change to take place immediately.
To disable the Local Security Policy:
- Click Start > Programs.
- Select Administrative Tools.
- Select Local Security Policy > Security Options > Accounts.
- Select Limit local account use of blank passwords to console logon only.
- Check Disable.
- Click OK or Apply to confirm the new settings.
|
|
Printable version
