TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

I am running into pretty much the same issue.

I am running Site Protector 1.0 SR3, and trying to upgrade a 6.01 server
sensor to 6.5, and am getting the same issues you are having.

One of my colleagues called ISS support and apparently Site Protector does
not support upgrading server sensors? 

Anyone with any more ideas?

-----Original Message-----
From: Cameron Humphries [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:34 AM
To: [EMAIL PROTECTED]
Subject: SiteProtector and RealSecure ServerSensor 6.5


L
I@R     ⁥[rz+,~)⁳w*ʋ,j⭢fhw
i慥bɨw'z楦᳥ᡕHi all
 
I've recently rolled out my first SiteProtector site and have come across a
problem relating to managing RealSecure ServerSensor 6.5.  Basically
SiteProtector uses an XML formatted file which details the XPU and Service
Releases available for the products which can be managed - it includes
pre-requisites, order informations, etc.  Now I am currently managing  a
handful of NetworkSensors, an InternetScanner and a bunch of ServerSensors
however even though there are some Service Releases available for
ServerSensor I cannot install them from the console as there is no mention
of ServerSensor in the current XML file.
 
Is anyone else running SiteProtector?  Have you seen this issue?  Have you
corrected this issue?
 
Thanks
-Cameron
 


SecureNet voted best e-Commerce Company
http://www.securenet.com.au

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



Reply via email to