| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Why is Probewatch not a member of the polycenter product family ? This questions has been asked to me often by customers. Being member of polycenter would be a big marketing feature and accelerate selling the product. Regards, Karl
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 969.1 | not convinced that Polycenter PROBEwatch or HUBwatch makes sense | NAC::FORREST | Wed Jul 06 1994 21:52 | 12 | |
For the same reason that HUBwatch is not. It's an organizational and naming issue. Polycenter is part of the software group, and HUBwatch comes from the Networks hardware group. We do cooperate, and HUBwatch is listed in the Polycenter solutions guide. We don't want to name it Polycenter Xwatch, because it might give people the impression that Polycenter NetView is a prerequisite. Also, I'm not sure that Polycenter HUBwatch for HP OpenView for Windows makes a lot of sense as a product name. jack | |||||
| 969.2 | MFRNW1::SCHUSTER | Karl Schuster @UFC OMS/Network Services Munich | Thu Sep 29 1994 07:10 | 5 | |
But it would be very important that Probewatch works together with
Polycenter Netview ( eg. uses the Netview database for address to name
translation )
Karl
| |||||