- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Server Management (Insight Manager 7)
- >
- Problems with installing CIM on NT Terminal Server...
Server Management (Insight Manager 7)
1825061
Members
5261
Online
109679
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2001 04:00 PM
тАО03-12-2001 04:00 PM
Problems with installing CIM on NT Terminal Server.
Have followed the tech support provided by Compaq on how to install CIM on Winodows NT Terminal Server but faced problems of activating the CIM and the apps hang at launch. Have to end task it and and relaunch the apps and this will work for 1 time. But the next time the apps is launched again, the apps hangs again. Pls help.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2001 04:00 PM
тАО03-15-2001 04:00 PM
Re: Problems with installing CIM on NT Terminal Server.
What service pack is installed on Terminal Server? Is there a specific agent or app that hangs or...?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2001 04:00 PM
тАО03-26-2001 04:00 PM
Re: Problems with installing CIM on NT Terminal Server.
Hi service pack 6a is installed and everything works fine except the CIM has to be launched for 2 times before it can really work on a NT terminal server. Everytime only the CIM apps not responding. Any comments???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2001 04:00 PM
тАО04-11-2001 04:00 PM
Re: Problems with installing CIM on NT Terminal Server.
If multiple users are intended to use that CIM installation, I wouldn't recommend it. The console uses one set of databases (located in its own cim_db subfolder) and was not designed to share them among concurrent users. If shared, there is a great likelihood of data corruption.
FWIW, I am running CIM over the Windows 2000 terminal services. I installed TS in remote administration mode and don't have to deal with changing from install to execute and all that.
The setup has been running fine this way without all the crashes I read about. However, I am the only user, and have tried to make sure (knock on wood) I don't ever run it from more than one session concurrently. Too much trouble recollecting all the data again when the databases are corrupted.
FWIW, I am running CIM over the Windows 2000 terminal services. I installed TS in remote administration mode and don't have to deal with changing from install to execute and all that.
The setup has been running fine this way without all the crashes I read about. However, I am the only user, and have tried to make sure (knock on wood) I don't ever run it from more than one session concurrently. Too much trouble recollecting all the data again when the databases are corrupted.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP