TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Hi Joe,
Below is a write up our (wonderful) tech support did that should fix your
problem. The "update.policy" file they mentioned is something that comes
with every new RealSecure release and contains all the new signatures that
were added with that release.
------------------------------------------------------------
Scenario:
Customer has just upgraded to RS 3.2.1 and has imported their policy from RS
3.2 . When they select customize or apply to detector, they are not being
prompted to add the new signatures.
Reason:
The policy version number in the update.policy was not changed. Hence,
RealSecure doesn't think there has been an update.
Work around:
On the RealSecure engine:
1. Open the update.policy file using a text editor.
2. Find the line showing- PolicyVersion =S 3.2.1999.218; (This should
be on line 5)
3. Change the last 3 numbers to 350.
The line should now read PolicyVersion =S 3.2.1999.350;
4. Save the file and exit.
>From the console:
5. Highlight the engine in the detectors window|right click, select
properties
6. Select your imported policy and choose customize.
7. The console should prompt you with a message asking if you want to
update the policy. Choose Yes.
8. Make any changes and apply the policy to the detector.
NOTE:
It is important that you customize the policy by highlighting the engine and
selecting properties. This is the only way that the update.policy file will
be read since it resides on the engine only. If you choose View|Network
engine policies from the console menu, it is not going to work.
-----Original Message-----
From: Joe McMahon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 16, 2000 12:48 PM
To: [EMAIL PROTECTED]
Subject: RealSecure Upgrade from 3.2 to 3.2.1
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
In the process of upgrading to RealSecure 3.2.1, we
noticed that if you imported the policies, then the
trinoo and TFN aren't part of the policies. We can
get them if we create a new policy base don Maximum
Coverage and then modifiy the settings to our specific
filters, but we'd like to avoid doing this manually.
Are we doing something wrong or is this a problem with
the upgrade?
-- Joe
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
