Generally, I’m a fan of taking the high road. I’d much rather talk about what we do than talk about what the competition is doing. But sometimes you can’t let things slide… Red Hat has recently been out talking about preparing a real time Linux offering later this year. In the course of this, they’ve …
There is no automated function to remove managed devices that have not “checked in” to ZLM for a defined period of time. Philip Cockrell shares a handy script that will help with the cleanup chores.
I figured I would impart a couple more tips on you all regarding WebAccess, which seems to be the most confusing part of GroupWise for most people.
Firstly, enabling the admin interface on the servlet. Nice and easy this one. Go to the webacc.cfg file – sys:\novell\webaccess on NW, /opt/novell/groupwise/webaccess/webacc.cfg on linux. Edit it and look for Admin.WebConsole. Change Admin.WebConsole.enable to true and set a user name and password to something else. Now restart tomcat, or wait the default 10 mins for the settings to be reread and now you can log in with:
http://serveraddress/gw/webacc?action=Admin.Open (case sensitive).
You can see who is logged into WebAccess and which GWINTER they have been redirected to.
Next, forcing your webserver to direct you to a particular GWINTER. This is useful if you have multiple WebAccess Agents and you want to make sure that they are all working. Use the URL format http://serveraddress/gw/webacc?GWAP.ip=10.10.10.10 where 10.10.10.10 is the IP address of your GWINTER. You can then check that it worked by going to the Admin.Open link from above.
Next, changing the templates. Another URL command. http://serveraddress/gw/webacc?User.interface=simple
You can substitute css or frames (if you still have those installed) for simple. You should note that all these commands are case sensitive.
One last useful tip to find out what version of the servlets (or WebAccess Application) you are running. Log into WebAccess and then clieck Novell GroupWise WebAccess up at the top left. This page will show you what version and build date you are running on the servlets.
Think that’s it for now unless anyone has questions?
Stop going the Insert | Picture | From File route. You can drag and drop any image you want when you use the OpenOffice.org Gallery. Here’s a tip from BrainStorm, Inc. to show you how.
The observant amongst you will have noticed that SP2 came with a security flag on it. We fixed a buffer overflow in WebAccess and people are asking what needs to be updated. Well, the ports affected are 7205 and 7211, which are the GWINTER ports for communication with the servlets, and the HTTP interface – so the answer is the WebAccess Agent is the only thing that needs updating for this vulnerability. Is it high risk? In my opinion, no. Most of you should have these ports blocked off from the outside world, only exposing 80 and 443. I have not heard of this vulnerability being exploited.
If you plan to update check out my previous thread on getting it all installed.
Cameron Seader shares a script that you can use if you have a need in your OES Linux environment to apply patches without having a new kernel being applied.
Congrats to the winners of the recently concluded “Race to Linux 2.0” context. Hosted by DevX and jointly sponsored by Novell, Mainsoft and IBM, the “Race to Linux 2.0” challenged developers to see how quickly they could port an application from Windows to Linux. The Novell-sponsored Mono project was one of the key tools developers …
Last week, openSUSE maintainers sent a note to the openSUSE mailing list telling folks that openSUSE will now be focusing on native software management using YaST and “zypp”, the package management library. As a result, openSUSE 10.3 will not include the ZENworks Management Daemon (zmd). Here’s what that means: First, and most important, patch, update …
Last month I wrote about the beta program for ZENworks Configuration Management.
I wrote a few weeks ago about the closed beta program for ZENworks Configuration Management; and several people asked me about a public, or open, beta for this exciting new product.
Unfortunately we will not be running an open beta for this particular release.
We are working closely with our global beta customers and partners, and that is producing some very detailed, deep and valuable feedback from a variety of customer environments.
I understand many of you wanted to ‘kick the tyres’, test, plan or just get an early look at this product. I’ll commit that we will be sharing more and more information, documents, whitepapers and videos of this product online in the coming weeks.
Sorry for the disappointment. As a team we will make sure we share details of the next set of ZENworks beta programs later this year.
Well – the response was pretty incredible. Both in the comments on Cool Blogs, via your sales teams, directly to my email – the loud and vocal comment was “We want a public beta”.
We listened. We acted.
We have now added a public beta round to the release of ZENworks Configuration Management. Look for more details in the coming weeks; but we expect to have something for you in June to download, test, become familiar with – and also to give us feedback.
I look forward to your comments.
Written at: Draper, UT
If you find that you have to reboot twice after changing group policies, check out this tip from James Davey to save yourself a bit of time.