Novell Cool Solutions

Locking Out GroupWise Clients for Security Fixes



By:

August 28, 2007 2:54 am

Reads:3,420

Comments:0

Score:Unrated

Print/PDF

Problem

A Forum reader recently asked:

“According to the Security Fixes found in 702HP1a, full Windows/NLM version, it mentions that I need to lock out all GroupWise clients older tha May 24, 2007 via ConsoleOne. How do I do this – is there any step-by-step procedure?”

And here’s the response from Chris Premo …

Solution

1. In the Properties of the Post Office(s), click the Groupwise – Client Access Settings tab.

2. Check the “Minimum Client Release Date:” and select the appropriate date.

For me it is May 22, 2007, because I have a BlackBerry Server, and the server needs the 6.5.7 client. The date on this version is different.

Note: Do NOT checkmark “Minimum Client Release Version (x.x.x):” unless you
don’t have a BB Server.

3. Save your settings and test. You may need to go to your POs WEB management page and verify that the changes are in effect.

4. Now test with an older client.

Also note: If you haven’t updated your WebAccess version, WebAccess will be LOCKED OUT.
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS