One of the cornerstone features to GroupWise in the upcoming release of Windermere is a completely new Administration Console. I thought I would share a few details and screen shots of how this experience is going to change.

First of all, there are a few components that help explain the architecture of the new Administration service. There is the GroupWise Admin Service which is installed when you install the GroupWise Server components. These components now include the Admin Service, the MTA, and the POA. After the installation is complete, usually on the same machine where the Primary Domain resides, the Admin service automatically starts. On Windows, the Admin Service is installed in C:\Program Files\Novell\GroupWise Server. With the Admin Service running, you can now launch the Admin Console. This is where you configure your new or existing GroupWise system. You will navigate your browser to the correct URL and accept the self-signed certificate that is automatically provided and the GroupWise Configuration wizard will start: See screen shot….

Configuraton Wizard

Click to view.

After you have created your new system, added a new domain or post office, you can then launch the GroupWise Administration Console to configure a new or existing GroupWise system. Here is what it might look like:

Administration Console

Click to view.

You can see from this view , launch points for all of the general tasks that an Administrator needs to complete. This blog will discuss a few of these, but will spend more time highlighting some of the advantages and new capabilities with the new Administration Console.

Recent/Favorites/Search

You will notice a few of menus/buttons/controls near the top of the console that allows you to customize and simplify your administration tasks. Easily trace your movements around the console using the ‘Recent’ menu. Effortlessly bookmark and return to common areas or settings or possibly deeply embedded functionality through the ‘Favorites’ menu. This mechanism allows you to easily surface and personalize locations for each administrator. Then there is ‘Search’. The ability to easily find/filter lists of domains, post offices, users, resources, etc. Personally, those features alone make the Administration experience so much better!

New User

Creating new users, domains, post offices or other entities is fairly simple and somewhat routine. You will notice many familiar tasks and screens. This familiarity seamlessly integrated with a new look and feel, easier navigation, and more intuitive interactions makes the transition from ConsoleOne to the GroupWise Administration Console natural and expected.

Click to view.

I hope you enjoyed this brief view of the Administration Console. Let me know if you have questions or want to know how a particular scenario will work with the Windermere software.

Dean

• Cool Blogs: Official Novell Bloggers

We recently received a question from Daniel P. about whether GroupWise lets people know if their messages are delivered, read, and/or deleted by recipients. Evidently his users are clamoring for that kind of insight, and he wants to make sure GroupWise provides it before he purchases it.

The answer is a resounding Yes. GroupWise will happily tell you all of that, and more, but it only works fully if you are sending to another GroupWise mailbox at your company. Here's how you look to see what happened to the email you sent.

1. Go to your Sent Items, and find the email you're curious about.
2. Open the email by double-clicking it.
3. Click the Properties tab, and you will see a list of your recipients and the most recent action they have taken with your email (Replied, Read, Deleted, Forwarded, etc.) If you see Response Pending, that means they haven't opened it yet. If you see "Emptied" that means they not only deleted it, but they emptied it from their Trash as well. (For some reason, that kind of stings.)

This is a very popular feature for managers who want to know exactly who they can hold responsible for having read their email. (We've also heard it is a useful feature for people attempting to flirt in the workplace.)

Now remember, this will only work within your own company. If you sent the email to a user outside of your company (whether or not they use GroupWise at their company), you won't see anything about their actions except "Transferred". (Not quite as satisfying, right?) But as long as you confine your curiosity to the actions of your co-workers, you should have a lot of info to work with.

Bonus Tip: We have a nifty related feature as well -- you can actually retract any email you have sent to a user at your company, UNLESS they have already opened it. This is where it is handy to be able to tell if they have opened it or not. If it says Response Pending, and you are sorry you sent it, hurry and do this:

1. Click Delete.
2. Select "Delete from Recipient's Mailbox"

Bam, this snatches it out of their mailbox without a trace. At this point you can rewrite it to sound even smarter, fix typos, add forgotten attachments, or even delete it from your own mailbox.

This has saved many a career, and many an ego.

• Cool Solutions

Paula N. wrote:

Q. Does Novell have the capability to display the last time I logged on to my email account?

A. This question crops up quite a bit. We have an answer posted over in the Cool Solutions Freezer -- which contains older content that was never migrated to this community platform -- and it's still true. But we'll put it here too and expand a bit on it because it is obviously still interesting to folks.

The answer is, it depends on who you are. If you are an administrator with access to ConsoleOne, you can find out when someone last used their email account. As it says in the old tip from 2007:

1. In GWCheck, select Audit Report (instead of the default Analyze/Fix Databases).

2. Have it report on accounts where users haven't logged into their accounts in x days.

3. Set that to something like one day, and you'll get a listing of nearly all your users (anyone who hasn't logged in for the last day), along with the last time they used GroupWise.

The reason GroupWise admins need to do it from time to time is all about managing licenses. Once a year or once every other year, GroupWise customers have to provide information to our License team on the amount of licenses they use. They use this report to see when the last login times are for users. If they find some that haven't logged in for some time, they can expire those accounts to get that license back.

However, if you're a normal GroupWise end user, there is nothing available that will let you look up your last login date. But honestly, we can't think of a reason you'd want to do that. If you can think of one, post a comment. We're really curious.

• Cool Solutions

Have you seen Blueprint for Reload?

Blueprint extracts important business intelligence data from your GroupWise message store by performing in-depth analysis on your Reload backups. Blueprint plugs directly into your Reload server to deliver timely reports that you can easily analyze and put into action - even on your mobile device or tablet computer.

To find out why you should be using Blueprint, download the paper, “Blueprint: Top 5 Reasons You Need It.”

To download this paper, click here

For more info on Blueprint, click here

• Cool Solutions

You are invited to the Osterman Research and GWAVA webinar titled “Managing BYOD in Corporate Environments” on Wednesday, May 29, 2013.

Webinar: Managing BYOD in Corporate Environments
Date: May 29, 2013
Time: 2:00 PM Eastern
To register, click here

The Bring Your Own Device (BYOD) trend is pervasive today in organizations of all sizes and across all industries. It enables improved worker productivity, higher employee satisfaction, reduced operational costs, faster innovation and sustained competitive advantage.

Attend this webinar for the following key takeaways:

• BYOD is well entrenched across organizations of all sizes
• Employee-deployed, cloud-based applications are widely used (e.g., Dropbox, Apple iCloud, Google Docs)
• BYOD creates risks for organizations when not managed properly
• BYOD brings benefits that outweigh risks if managed well
• With proper IT management and controls in place, companies can leverage the productivity benefits of BYOD

All attendees will receive a copy of the Osterman whitepaper "Managing BYOD in Corporate Environments.”

We hope to see you there!

Thank you!

• Cool Solutions

You are invited to take a first look at the all new Retain Mobile

Date: 30 May 2013
Time: 1:00 pm Eastern (-4 GMT)
To register, click here

Discover unified archiving in a whole new way with Retain Mobile.

As BYOD and mobile devices begin to permeate organizations you need to maintain compliance by having the ability to quickly archive all mobile communications data.

Retain Mobile helps you maintain compliance with regulation standards and reduces liability.

Join us to learn more!

To register, click here

• Cool Solutions

Stay current with the latest discussion between GroupWise administrators, partners and consultants. Free and complete with high speed text search, topics range include GroupWise technical issues to Attachmate/Novell business discussions.

The May 2013 edition of the GroupWise Resource Archive is available from:

http://www.advansyscorp.com/atg-groupwise-resource...

Collated by Advansys since November 1999 and created using Archive To Go, the GroupWise Resource Archive is a rich information resource derived from the GroupWise administrators' NGW List.

If you have collated valuable information in your GroupWise email account, you can also create portable, searchable knowledge archives using Advansys Archive To Go. If you have any questions or comments, please feel free to contact us.

The Advansys Archive To Go Team
www.archive2go.com

• Cool Solutions

Many of you have been following the five part blog series that has spelled out some of the technical decisions and choices that have been made or considered regarding the next major release of GroupWise. As you all know, the code name for that release is Windermere. It is scheduled to release by the end of the year and authorized beta is expected to expand in June. The product has been in an SDK/API beta since January.

A new major release of the product is always exciting! There are always lots of expectations for new functionality and capability. Novell wants to make sure our customers are receiving value for their maintenance investment and that they are continually seeing progress on multiple fronts.

Windermere has been positioned and engineered to deliver a very robust set of functionality that will provide a solid foundation to align our engineering efforts with a more aggressive release cycle as the demands from our customers continue to outpace availability. Here are the main set of features and functionality coming in Windermere:

Active Directory Support

GroupWise will expand directory support to include eDirectory, Active Directory, or no directory. This is actually a return to GroupWise roots. GroupWise was originally designed and delivered as a directory agnostic email solution. Many GroupWise customers will see little impact to their architecture and they will simply continue to use eDirectory. Upgrades to Windermere are expected to be as simple and straight forward as moving from GroupWise 8 to GroupWise 2012.

Allowing GroupWise to leverage Active Directory meshes well with the recently released functionality of the GroupWise Coexistence Solution for Exchange. This change allows our customers the flexibility they need to standardize their directory infrastructure and integrate our applications with other data center requirements.

64-bit Agents

GroupWise will deliver the POA, MTA, GWIA, and other server side components in 64-bit versions only. There will be no 32-bit versions of these server components. This will require that your server OS/platform is running 64-bit. Novell recommends that you upgrade to a 64-bit platform NOW instead of waiting to upgrade both the platform and the version of GroupWise when Windermere ships. This will minimize downtime and increase the confidence that your upgrade will go smoothly. There are more details about 64-bit agents and utilities in this blog post. This puts GroupWise on current hardware/OS configurations and allows our customers to stay current with both their applications and the platforms they run on.

New Admin Console

GroupWise Windermere will no longer utilize ConsoleOne for its administration console. ConsoleOne will not be supported in Windermere. The new Administration service and console will be web based. This will remove several dependencies and allow administrators more flexibility and freedom to manage the GroupWise system from essentially anywhere they have a browser. This move puts GroupWise on current technologies and provides solutions to our customers that can be more easily supported, deployed, and enhanced.

Fresh/New GroupWise Windows Client

The GroupWise Windows client has gone through a very strategic face lift. Modernizing the interface to adhere with more current interface design and practice gives GroupWise a fresh look and feel. While keeping with the underlying familiarity, the client will look like other software products our end users deploy and use. New fonts, softer edges, fewer borders, new icons, softer colors, less harsh contrasts, and eye focusing concepts to allow the user to see and act on the information that is highlighted, selected, and being worked on. The Human Factors and User Design teams have provided significant guidance and excellent design. Customers should find the Windermere Windows Client to be new, but not require training to be able to deploy and enjoy!

Click to view.

New Usability Changes

While large new client side features has not been the goal or objective of Windermere, improving the usability of the high traffic areas of the users experience has been a significant focus. Changes to the compose and read views will delight users as many of the common tasks have been simplified, redesigned, better presented, and are easier to use. Name completion now shows a list of contacts that match as you begin to type a contact name, frequently used contacts can be selected without every using the keyboard, From/CC/BC fields are optional instead of standard and easily toggled on/off. Signatures are added to the message body by default and easily edited or removed. Reply/Forward options can be changed at any time while responding to a message. Decisions made when begining to compose a response can easily be toggled to other options…like reply can easily be changed to reply to all or back again. A reply can change to a forward and easily add or remove the original message text. Forward or Forward as Attachment can also change easily after the fact or at any time before the message is sent. Options will slide in from the right and the attachment control will appear or slide away to allow the user to focus on the message.

Click to view.

Message triage has also been improved. While dragging and dropping messages to other folders may be your method for sorting your inbox, you will now be able to easily move messages to your most recently used folders using just a click of the mouse on the toolbar or menu. Allowing you to not have to continually search for a folder in the folder tree or move your mouse and eyes from one side of the screen to the other.

WebAccess Improvements

The GroupWise WebAccess experience will largely stay the same, but there have been a few significant changes to the WebAccess experience. Auto-refresh has been added to the message list, Calendar, and Contacts. This will allow WebAccess users to see new messages as soon as they arrive and not have to manually refresh the message list. Changes made in other clients will automatically reflect in the WebAccess interface.

IMAP Support

Many of our customers and end users are expanding their use of IMAP to get access to their email. The performance of our IMAP implementation has also gone through some significant changes that will improve the reliability, performance, and overall throughput for IMAP access to your mailbox. A new caching model has been implemented and we expect significant performance and usability improvements.

While not EVERY change or enhancement has been cataloged in this blog, the major areas and themes have been covered. The team is looking forward to Windermere and is very excited to get into beta so that more of you can experience the changes first hand and help us polish any rough edges.

On a personal note, my corporate mailbox has been running on a 64-bit Windermere POA for several months. I was able to update my GroupWise Windows Client to the Windermere version in late March. I run in caching mode and my desktop OS is Windows 8. The experience is very stable and while I admit it has not been ‘crash free’, my productivity has increased and the product we all use and depend upon daily is better than ever!

Dean

• Cool Blogs: Official Novell Bloggers

Montreal, Quebec, Canada – April 24, 2013 — GWAVA announces the release of GWAVA messaging security version 6.5. This latest release of GWAVA includes the all new URL Filtering and Web Content Filtering which monitors incoming and outgoing internet traffic, including URL filtering, social media, search filtering and monitoring.

“Filtering and monitoring Facebook and Twitter is critical functionality for our education and government customers,” said Ken Muir, Chief Executive Officer of GWAVA. “The ability for schools and government to monitor key words that students and employees are using in Facebook and Twitter and on the internet helps prevent potentially harmful situations before they occur. GWAVA is also built to alert administrators about harmful and inappropriate conversations and photos.”

GWAVA Web Content filtering and URL filtering provides the ability for organizations to monitor, filter and block HTTP traffic. GWAVA integrates with compatible ICAP systems and scans HTTP traffic to prevent access based on URL category, reputation, corporate policy and file type, including hidden executable and malignant files. This GWAVA functionality provides the ability to filter content from individual sites. This filtering allows good content, while preventing inappropriate content from any given site, from Facebook or from Twitter.

GWAVA also provides a powerful messaging ‘black and white’ list which empowers end users and reduces administration costs for messaging systems. Additionally, GWAVA provides protection from Denial of Service (DoS) and Distributed DoS (DDoS) attacks and support for PostgreSQL. These additional features add to the already extensive protection offered by GWAVA.

The GWAVA Messaging Security solution protects vital and casual electronic business communications for thousands of organizations in industries such as government, education, financial services, healthcare and business. With these latest additions to GWAVA, organizations now have a total solution to prevent viruses, spam, malware, illicit images, social media filtering, inappropriate content and URLs in addition to protection from DoS/DDoS attacks.

About GWAVA Inc.
For more than a decade GWAVA has built a solid reputation as a leader in messaging security, unified archiving and messaging continuity. Millions of users in over 60 different countries trust GWAVA to secure and protect their messaging and collaboration infrastructure in addition to archiving their email, social, and mobile electronic communication. GWAVA has offices in the United States, Canada, U.K., Australia and Germany and maintains a network of hundreds of authorized partners. Information on GWAVA can be found at www.GWAVA.com
Contact us today VIA Twitter: @GWAVA or questions@gwava.com

• Cool Solutions

Today, Novell announced the release of GroupWise 2012 SP2. This support pack releases eight months after SP1 and contains not only the expected set of fixes, new platform support, and increased reliability, but also contains some significant new functionality. GroupWise 2012 SP2 also includes technology called GroupWise Coexistence Solution for Exchange.

Update Today!

Organizations should follow best practices when deploying SP2 or when upgrading from a previous release of GroupWise. There are not special instructions or procedures to simply update to this version of GroupWise

GroupWise Coexistence Solution for Exchange while embedded in the existing components of GroupWise and part of the GroupWise 2012 SP2 code, this technology does require additional licensing and costs. In addition to purchasing this technology, an administrator must enable and configure Coexistence in order to get the benefits of this solution. If you do have questions, please read this recent blog post that discusses the features, benefits, and reasons that your organization may be interested in this technology and solution.

Security Alert

In addition to the release of GroupWise 2012 SP2, Novell is simultaneously releasing a security hot patch for GroupWise 8. This is called GroupWise 8.0.3 HP3 and contains ONLY these security fixes in the GroupWise 8.0.3 HP2 code base. Both GroupWise 2012 SP2 and GroupWise 8.0.3 HP3 contain the fixes for the following security issues.

Description: The GroupWise Client for Windows is vulnerable to a scripting exploit where by enticing a user to run a malicious script embedded within the body of an email message, a remote attacker could execute arbitrary code on vulnerable Windows workstations running the GroupWise client.

Affected versions: GroupWise Client for Windows 8.0x up to and including 8.03 HP2 GroupWise Client for Windows 2012 up to and including 12.0.1 HP1
Previous versions of the GroupWise Client for Windows are likely also vulnerable but are no longer supported. Customers on earlier versions of GroupWise should, at a minimum, upgrade their GroupWise Windows clients to version 8.0.3 Hot Patch 3 or 2012 SP2 in order to secure their systems.

Resolution: When a user opens a message containing a Javascript or ActiveX script, the GroupWise 8.x and 2012.x clients for Windows display a warning inside of the message window that indicates that GroupWise has blocked a script from running, and which gives end-users the option to allow the script to run by clicking on the yellow warning banner: ("GroupWise has restricted this webpage from running scripts or ActiveX controls that could access your computer. Click here to allow access.")

To allow administrators to prevent potentially harmful scripts from running on their end-users' workstations, the GroupWise 8.0.3 HP3 and GroupWise 12.0 Support Pack 2 clients include support for a new Windows registry key that will configure the GroupWise client for Windows to disable the "Click here to allow access" functionality, which will prevent end-users from running scripts embedded within HTML messages.

To block the ability to run scripts in the GroupWise 8.0.3 HP3 and 2012 SP2 clients for Windows, administrators will need to do the following:

1. Create a new DWORD (32-bit) registry value under HKEY_CURRENT_USER\Software\Novell\GroupWise\Client\Setup\
2. Enter "HTMLScriptsBlocked" (minus the quotes) in the "Value name" field
3. Enter "1" (minus the quotes) in the "Value data" field"
4. Click OK to save the new DWORD value

Administrators can push out that registry setting to their Windows workstation using Novell ZENworks Configuration Management or another workstation-management utility.

With the new HTMLScriptsBlocked registry entry added to Windows, the GroupWise client will still display the yellow script warning, but if the user clicks on the warning message, the script will not run. NOTE, adding this registry key to a Windows workstation will prevent ALL scripts from running within the GroupWise client, not just malicious scripts.

This vulnerability was discovered and reported by Bartlomiej Balcerek at Wroclaw Centre for Networking and Supercomputing

Novell bug 799673, CVE-2013-1087

Related TID 7012063

=========================

Description: GroupWise WebAccess is vulnerable to a cross-site scripting (XSS) issue whereby an attacker could exploit a vulnerability in the "onError" attribute to execute a malicious script in a user's browser session.

Affected versions: GroupWise 8.x WebAccess up to and including 8.03 HP2
GroupWise 2012 WebAccess up to and including 12.0.1 HP1
Previous versions of GroupWise are likely also vulnerable but are no longer supported. Customers on earlier versions of GroupWise should, at a minimum, upgrade their WebAccess servers and associated Domains to version 8.03HP3 or 2012 SP2 in order to secure their system.

Resolution: To resolve this vulnerability, apply GroupWise 8.0.3 HP3 (or later), or GroupWise 2012 Support Pack 2.

This vulnerability was discovered and reported by Bartlomiej Balcerek at Wroclaw Centre for Networking and Supercomputing

Novell bug 802906, CVE-2013-1086

Related TID 7012064

Windermere is Next!

Coming soon will be Windermere! The authorized beta is scheduled to begin in just a few weeks and the team is now code complete on the project. Code validation, cleanup, beta and customer feedback and review, and production ready installations. That is what the team will be doing over the next several months in preparation for an end of year release.

Dean

• End-User Computing

Webinar: What's new in GWAVA 6.5. You are invited to take a first look at the latest release!

Date: May 7, 2013
Time: 1:00 PM Eastern
To Register Click Here

Discover the new features in GWAVA:

Web Content and Traffic Filtering - Monitor, filter, or block incoming and outgoing internet traffic. Protect your organization from threats by preventing access, based on URL category, reputation, corporate policy and file type, including hidden executable and malignant files

DoS/DDoS Protection - Protect your mail system from Denial of Service and Distributed DoS attacks.

End User Black and White Lists - Give users the ability to place individual email addresses or complete domains on their black or white lists. Messages pass through or are blocked based on this list.

PostgreSQL Support - PostgreSQL is now fully supported, in addition to the supported SQL database of SQLite.

Join us!

To Register Click Here

• Cool Solutions

GWAVA is presenting a webinar in which we will weigh the advantages and disadvantages of migrating a company’s messaging and collaboration applications to the cloud. This webinar will give you an overview of the important considerations that both senior business management and IT management should explore as they decide whether or not to migrate.

Please join us!

To Register Click Here
Webinar: The Cloud: Best Practices for Messaging, Collaboration, Security, Archiving and Encryption
Date: April 23
Time: 11:00 AM Eastern

The cloud is a critical consideration for all organizations as they manage messaging and collaboration. Essential applications are now effectively delivered as cloud services--services such as email, malware filtering, spam filtering, real time communications, archiving and encryption. Consequently, companies should give serious consideration as to whether a cloud alternative is more effective for one or more of their existing on-premise applications.

• Cool Solutions

Stay current with the latest discussion between GroupWise administrators, partners and consultants. Free and complete with high speed text search, topics range include GroupWise technical issues to Attachmate/Novell business discussions.

The April 2013 edition of the GroupWise Resource Archive is available from:

http://www.advansyscorp.com/atg-groupwise-resource...

Collated by Advansys since November 1999 and created using Archive To Go, the GroupWise Resource Archive is a rich information resource derived from the GroupWise administrators' NGW List.

If you have collated valuable information in your GroupWise email account, you can also create portable, searchable knowledge archives using Advansys Archive To Go. If you have any questions or comments, please feel free to contact us.

The Advansys Archive To Go Team
www.archive2go.com

• Cool Solutions

As the blog has solicited input regarding decisions that will impact Windermere, there was a need to communicate back to this audience and update each blog affected. Here are a list of decisions that because of your input and feedback, Windermere plans and direction have been adjusted.

Support for Windows XP

Windermere will support Windows XP as a desktop OS. There are several comments, emails, and private discussions that have helped us reconsider our original thinking. While Microsoft will stop supporting Windows XP during the first few months of 2014, Novell and GroupWise will continue to support the GroupWise Windows Client running on Windows XP. You should make sure your desktop OS version is completely patched and that you have a desktop migration upgrade strategy in place as soon as possible. With Microsoft discontinuing support, any issue that is reported to Novell that would require a fix from Microsoft will result in a request by support to the customer to upgrade their OS first.

As a result of supporting Windows XP for Windermere, IE8 running on XP will also be supported. IE9 and IE10 will be the supported browsers for Windows 7/8. Please plan accordingly.

Gateway Links in the Link Configuration Tool

We had communicated that the plan was to remove Gateway Link Types for Windermere. We are reversing this decision and Gateway Links will remain in Windermere and will be administered through the new Admin Console. THANK YOU for your feedback, advice, and technical insight.

Addresssing Rules

It was also communicated that Addressing rules were also under consideration to be removed. After further consideration, Windermere will continue to support Addressing Rules. While the plan continues to lead us to remove this functionality and deem it legacy, the capability will remain for Windermere.

References to this blog and this update will be added to previous blogs to direct readers to this more current message and thinking.

Once again, we want to thank you for your input and participation as we discuss, push the envelope and look for ways to stream line, improve, and push forward the GroupWise platform.

Dean

• End-User Computing

This is Part 5. Engineering will very quickly be winding down the changes and new development that will be in the Windermere release. Engineering continues to find things they want to share and socialize with the GroupWise Community.

This series of Windermere technical updates have served to educate not only GroupWise Administrators, but also Technical Services, Consulting and Dedicated/Premium support personnel. In addition, the discussions have allowed engineering to publicly weigh assumptions and decisions. Thank you for continuing to read along, comment, and participate in these important topics.

Internet Addressing

Internet Addressing has been around for almost two decades. Engineering has decided to make a small change to the default behavior for this capability. Beginning with Windermere, Internet Addressing will be facilitated and encouraged by default. This will only affect systems that are newly created with Windermere code. Existing systems will continue to either have Internet Addressing enabled or disabled depending on the system that is being upgraded. While rare, there are still GroupWise shops who have not enabled Internet Addressing.

Now during the initial configuration process of creating a new GroupWise system, the administrator will be prompted to specify an Internet domain name and the GWIA will be installed in the primary domain. As a result, Internet Addressing is enabled for the new GroupWise system.

You can go through this process *without* specifying an Internet domain name and installing the GWIA . If you do, Internet Addressing is *not* enabled. In other words, these are no longer separate steps and is included in the process of creating a new system.

As a result of this decision, the documentation will change their approach to this subject by representing the idea of "Here's how you set up your Internet domain name" rather than explaining how "default" GroupWise addressing (user.po.dom) works and why it would be a good idea to enable Internet addressing.

This change to the default behavior for Internet Addressing is a precursor to completely removing this option in a future release of GroupWise. This means that in some future release, GroupWise will only support systems with Internet Addressing and therefore an option to enable/disable will become obsolete.

Note: The GWIA will no longer be treated as an optional gateway, but an integral part of GroupWise. The GWIA uses Internet Addressing always. Gateway Links in the Link Configuration Tool

The Gateway Link Types will be removed for Windermere. Flash: We have changed our direction. See latest blog. http://www.novell.com/communities/node/14133/group....

System Maintenance Utilities

As part of Windermere, engineering is making the system maintenance commands available through a command line utility on Windows and Linux. The command line utility will be called "gwadminutil"

Some of the system maintenance commands can be run both from the web-based admin console as well as the command line: validate, recover, rebuild, reclaim space, rebuild indexes, replace primary with secondary

Other commands will only available from the new command line utility: sync primary with secondary, convert secondary to primary, merge external, release secondary, reset admin credentials.

It is this second set of commands that motivated the creation of the new command line utility. Each of these commands (with the exception of reset admin credentials) requires simultaneous file access to two domain databases to run. To implement these through the web console would require the administrator to mount drives on the computer running the admin service to both domain databases before running the command from the web UI. This seems to violate the usefulness of a web interface if the admin has to SSH into the admin service and mount drives before completing an operation.

Here is the usage doc for the new Command Line Interface (CLI):

usage: gwadminutil validate <path>
example: gwadminutil validate /gw/dom1
Validate checks for physical consistency. If problems are found, you
should perform a Recover or a Rebuild.

usage: gwadminutil recover <path>
example: gwadminutil recover /gw/dom1
Recover can be performed even while the database is in use. Any database
inconsistencies will be corrected, but may result in loss of information.

usage: gwadminutil reclaim <path>
example: gwadminutil reclaim /gw/dom1
Reclaiming space may reduce the size of the database by eliminating any
unused space.

usage: gwadminutil reindex <path>
example: gwadminutil reindex /gw/dom1
Rebuild listing indexes reconstructs the indexes used by the Address Book.

usage: gwadminutil rebuild -d <path> -n <name> -o <path>
example: gwadminutil rebuild -p /gw/dom1 -n Dom1.Po1 -o /tmp
Rebuild requires exclusive access. For domains, a new database will be
created from the information in the primary domain. For post offices, a
new database will be created from the information in the parent domain.

-d,--domain <path> Path to domain database that owns object being rebuilt
-n,--name <name> Name of domain or post office object to be rebuilt
-o <path> Output path for rebuilt database

usage: gwadminutil sync -d <path> -p <path>
example: gwadminutil sync -p /gw/dom1 -d /gw/dom2
Synchronize primary with secondary ensures that each record in the
secondary domain has a matching record in the primary domain database.

-d,--domain <path> Path to secondary domain database
-p,--primary <path> Error prompting for password. Please specify password on the command line

usage: gwadminutil convert -d <path> -p <path>
example: gwadminutil convert -p /gw/dom1 -d /gw/dom2
Convert to primary promotes a secondary domain to primary. The existing
primary domain for the system becomes a secondary domain.

-d,--domain <path> Path to new primary domain database
-p,--primary <path> Path to current primary domain database

usage: gwadminutil release -d <path> -p <path> -n <name>
example: gwadminutil release -p /gw/dom1 -d /gw/dom2 -n Released
Release domain removes a secondary domain from the current system and
begins a new system with the released domain as the new primary domain.

-d,--domain <path> Path to database of domain being released
-n,--name <name> Name of new system
-p,--primary <path> Path to the primary domain database

usage: gwadminutil merge [-mergesync] -d <path> -p <path>
example: gwadminutil merge -p /gw/dom1 -d /gw/dom2 -mergesync
Merge brings an external domain into the current system as a new secondary
domain.

-d,--domain <path> Path to external domain database
-mergesync Merge external system synchronization information from the external domain
-p,--primary <path> Path to primary domain database

usage: gwadminutil setadmin -d <path> -p [<password>] -a <name>
example: gwadminutil setadmin -d /gw/dom1 -a admin -p
Set the username and password for the system admin

-a,--admin <name> New system admin name
-d,--domain <path> Path to domain database
-p,--password <password> New system admin password

The gwadminutil will be installed as part of the GroupWise server. On Windows, c:\program files\groupwise server\admin and on Linux /opt/novell/groupwise/admin

Macros

As part of some general clean up that is happening as the Web Admin Console is being created, engineering is removing options and settings that no longer apply. In ConsoleOne, under Client Options > Security Options, there's a Macros tab. This tab and all of its corresponding settings will be removed in Windermere. All current settings already stored in the different databases will be maintained. The administrator will no longer be able to control this setting.

Addresssing Rules

Currently, you can use the Addressing Rules feature to configure GroupWise so that users can enter shortened forms of email addresses for use through GroupWise gateways. However, all of the gateways are currently legacy products and not supported with current versions of GroupWise. Therefore, engineering is considering removing Addressing Rules from the product. The current proposal is that this functionality will eventually be deprecated.

Gateways were the most common reason to configure an Addressing Rule, but they were not the only reason. Addressing rules are applied to all typed in addresses and therefore there may still be GroupWise systems out there with a rule like this: "Change "blah" to "VeryVeryLongDomainNameThatIHateToType". This is so that the user can shorthand Joe@blah.com and have GroupWise properly send – for example.

Flash: We have changed our direction. See latest blog. http://www.novell.com/communities/node/14133/group....

Thank you for continuing to read, provide feedback and ask clarifying questions regarding Windermere. As you should be able to tell, Product Management and Engineering are taking a bigger step forward with Windermere in order to set our product, technology and customers on more sure footing and prepare them for the ever changing landscape ahead. We hope you understand the changes we are making and while there may be some pain associated with these changes for some customers, we certainly believe that all customers will benefit.

As always, please submit your feedback for all to see so that all can benefit.

Dean

GroupWise: Windermere Changes Series:

• GroupWise: Windermere Changes – Part 1
• GroupWise: Windermere Changes – Part 2
• GroupWise: Windermere Changes – Part 3
• GroupWise: Windermere Changes – Part 4
• GroupWise: Windermere Changes – Part 5

• End-User Computing

You are invited to attend this month’s Technical Solutions Training Webinar. In this webinar, learn about identity and access management in the cloud, multiplatform instant single sign-on, a new Mac client for GroupWise, and how to avoid being the next social media scandal. This webinar is part two of a two-part series featuring the best of BrainShare 2013.

The March webinar will be:

Date: March 27, 2013
Time: 11:00 am to 3:00 pm Eastern (GMT -4)
Link to register: http://www.grouplink.com/event/178

The agenda will be as follows. You have the choice to attend one or more of the sessions:

11:00- 11:45 am “Identity and Access Management in the Cloud: NetIQ Cloud Access” – Don DaRe & Mike Weaver, Concensus Technologies

12:00- 12:45pm “WSTrust: Multiplatform Instant SSO at a Glance” – Vaclav Samsa, WSTrust

1:00- 1:45pm “A New Mac Client for GroupWise” – Daniel Shelley, Ghost Pattern Software

2:00- 2:45pm “Avoid Being the Next Social Media Scandal” – Que Mangus, GWAVA

*Announcement* - A new, third-party Mac client is being developed by Ghost Pattern Software, the makers of iPhone/iPad and Android apps for GroupWise. This new Mac client will be an all-new, native app for OS X. This webinar will be the official launch of the beta for the client. During the webinar, we will publish a link with access to the beta. The 1:00pm session of the webinar will provide an introduction to the GroupWise client, a demonstration of the app, and time for questions.

If you cannot attend during these times, you can still register and we will send you a recorded copy of the sessions.

With the overwhelming response for the last webinar, we anticipate this webinar to fill up fast, so register now!

Follow GroupLink:
In the News http://www.grouplink.com/news.html
On Facebook http://www.facebook.com/everythingHelpDesk
On Google+ https://plus.google.com/111599861763768167702
On LinkedIn http://www.linkedin.com/company/grouplink

These webinars are brought to you FREE of charge by GroupLink’s everything HelpDesk, GroupLinkMDM, and ContactWise CRM. Learn more about these solutions at www.grouplink.com

• Cool Solutions

Stay current with the latest discussion between GroupWise administrators, partners and consultants. Free and complete with high speed text search, topics range include GroupWise technical issues to Attachmate/Novell business discussions.

The March 2013 edition of the GroupWise Resource Archive is available from:

http://www.advansyscorp.com/atg-groupwise-resource...

Collated by Advansys since November 1999 and created using Archive To Go, the GroupWise Resource Archive is a rich information resource derived from the GroupWise administrators' NGW List.

If you have collated valuable information in your GroupWise email account, you can also create portable, searchable knowledge archives using Advansys Archive To Go. If you have any questions or comments, please feel free to contact us.

The Advansys Archive To Go Team
www.archive2go.com

• Cool Solutions

This document covers the tools and process for moving entries from GroupWise Document Management to Novell Vibe.

Information and expertise provided by Rob Luhrs, Bill Ramsey, Bob Hannan

System Requirements

GroupWise 8.x or GroupWise 2012.x
Vibe 3.3

Prerequisites

Vibe 3.3 Installation.

• Vibe must access the same LDAP user store that GroupWise uses. An LDAP sync must be run. Choose the option to Register LDAP User Profiles automatically. This ensures that the users are the same in Vibe as in GroupWise.
• You must enable SSL on SOAP for all POAs involved if you intend to use SSL. Note: HTTP is an option just for the export.
• Clean up all documents by using Mass Document Operations. In the process of running these procedures, you might find a number of orphaned documents and you might also find that some users have been deleted and re-created or lost access to some of their documents. These documents and situations should be cleaned up as much as possible before the migration begins. Handling these situations is easier in GroupWise and then you will avoid having to fix these problems after the migration.
• To ensure that the groupsWiseDistributionLists are moved over to Vibe (because some permissions are based on that), you need to add the following value to the group filter section of the LDAP configuration: objectClass=groupWiseDistributionList. Then re-run the LDAP synchronization.
• Any orphaned documents still in the system are moved to the Admin user in Vibe.

General Overview

Novell has developed a set of scripts to assist in the migration of GroupWise Document Management to Novell Vibe. The feature set between the two products are quite different. GW DMS allows users to create, edit and share documents individually as well as through the folder hiearchy. A user has full control of the access rights for each document. Novell Vibe allows users to share documents through global, team, and personal folders. In order to migrate GW DMS documents, each user's personal documents are copied to a Vibe folder within the Vibe user's workspace. Users who originally had access to those documents (essentially a link) now have an entry in their personal workspace that links to the owner's documents. Access controls are maintained via the provided set of scripts.

GroupWise DMS

A GroupWise user creates DMS entries by uploading documents into GroupWise. The user then shares a folder or file to relevant users while granting access controls. When the GroupWise user updates a document, those changes are either immediately available to users on the same post office or replicated automatically to all necessary post offices throughout the GroupWise system.

Novell Vibe

A user or admin creates a personal/team/group area, depending on the use case. The creator decides access controls at that time, and then begins uploading entries and documents. The folder structure is usually built to mimic organization structure and teams. Search and structure are essential, allowing users to find their desired document areas.

Vibe migration is not intended to duplicate the features of GW DMS, but to move documents en masse, maintaining access controls and folder structure. Moving forward, a successful migration will likely include the rearrangement of the documents into a more coherent structure with team/group/user access. This can be manually accomplished with the copy/move functionality within Vibe.

Migrated Documents

Each migrated document is owned by the original creator. If the original creator shared the document with other users, that link is preserved and access control is maintained.

Export Process

Overview

The migration process begins with an export of files. You run an export that communicates to the GroupWise system via web services. You can define a specific user or request all users. Once the export is complete, each user will have an individual XML file that includes all documents and their properties. Files are stored in the file system in a directory structure based on the post office.

After the users and their documents are exported, you will need to execute the import utility. This script reads the exported XML files/documents and uploads the documents into Vibe via web services. After all the users are imported, the import script process then creates links in each document area to the documents you previously had access to.

Export

The export tool exports user's documents and document information from GroupWise. The tool for this is gwdmsexport.exe. The script can be run from anywhere that can connect to the GroupWise POA. Be aware that since large amounts of information and documents are downloaded, using a machine that has close proximity to the GroupWise machine greatly increases performance.

To export all users at once, you need to create a Trusted Application and Key. The GroupWise instructions are here.

1. Leave the Requires SSL and TCP/IP Address fields blank.
2. Remember the application name and note the directory and file name you want.
3. Location for the Key File: Browse to and select the directory where you want to create the trusted application key file.
4. Name of the Key File: Specify the name of the trusted application key file to create. The third-party program must be designed to successfully access the trusted application key file where you create it.
5. Find the file you just created, and edit it in a text editor.
6. Put the application name on the first line, and move the key to the second line. Make sure there is no third line.

The trustfile.txt file might look like this:

DMSTrust 3657C60118B10230444998877B346CDFD5B3657C60218B10000B35331FC4A7GB91B

Place this file in the GwMigrateDMSToVibe directory.

The options for gwdmsexport.exe are as follows:

/host | h /port /user | u /out | o (output directory) /export (include documents) /alias (transforms one user's docs to another; not recommended for this project) /dumpusers (dumps a list of users including uid and email. Used for debugging) /proto (by default it is HTTPS. , If you want HTTP, use /proto=http) /all /trust (this points to the trusted key file)

Here is a sample command line to export a single user:

gwdmsexport.exe /user=jsmith /host=192.168.1.1 /port=7194 /export /trust=trustfile.txt

The system creates an export.log and a jsmith.xml file. If export was chosen, a directory with the post office name containing the exported files is also created.

For exporting all users, it is still required to put in an existing user. We recommend trying a single user first to test the trust file. When you are satisfied that works, run a command like the following:

gwdmsexport.exe /user=jsmith /host=192.168.1.1 /port=7194 /export /trust=trustfile.txt /all Import Process

The import process can be run on any machine, but the recommendation is to run it on the Vibe server.

The script to migrate is called: migrate.bat (or migrate.sh on Linux). Most configuration settings are done in the migrate.properties file. The common configuration items are:

dataRoot=C:/install/data hiddenRoot=C:/install/data/zone1/entry_data

Configure the properties before running migrate.bat. Any changes to the directories below require removing the configuration and then reinstalling it.

The dataRoot contains all the exported information XML files. The dataRoot directory contains default directories:

• Binders (Copy all the username.xml files to here)
• entry_data (copy the SDCS.DistLibPo.DLIB19 etc directories containing the files from the export to here)
• Users_Groups (leave empty)
• The hiddenRoot directory points to where the documents were exported. This directory contains directories such as SDCS.DistLibPo.Lib42

To run this tool, you must first change permissions on the migrate.sh file in Unix. Then run migrate.bat in Windows or migrate.sh in Unix. Please check with your System Administrator, but the most commonly used command is chmod 744 migrate.sh.

The command line looks like this:

######## Welcome To DMS to Vibe Migration Select one of the following: 0. Quit 1. Vibe Configuration (Must be done before Migration) Enter Your selection: ########

The first choice is to run option 1. This installs the required Web services to the Vibe installation. The application walks you through stopping Tomcat and then restarting after installation of the migration-specific tools.

The next step is to run the migration.

######## Welcome To DMS to Vibe Migration Select one of the following: 0. Quit 1. Migrate DMS 2. Delete Migrated Data 3. Undo Vibe Configuration (Do this after Migration is complete) Enter Your selection:########

Choose Option #1.

When you have completed the migration, you have the choice to remove the custom migration code from your Vibe installation.

######## Welcome To DMS to Vibe Migration Select one of the following: 0. Quit 1. Migrate DMS 2. Delete Migrated Data 3. Undo Vibe Configuration (Do this after Migration is complete) Enter Your selection: ########

Deleting migrated data might not get all artifacts.

Finally, copy the Install/teaming-library/definitions/dms directory to the /opt/novell/teaming/apache-tomcat/webapps/ssf/jsp/custom_jsp directory.

Usage Notes

1. Duplicates. During this process, we have found that users might have many duplicate files in their document directories. Because of the way DMS handled documents, these are actually links to a single document.

   For example, in my home directory I might have the following files:

   John's Documents
        Documents
             Document1.doc
        Schedule
             Subfolder
                  Document1.doc

   The migration process deletes a duplicate reference if it is in the same folder.

   If the duplicates are in a different folder, you need to create a link to the first entry:

2. Links. In the documents, you will see a number of places where a user has shared a document with another user:

   User1 Documents
        Documents
             User1sDocument.doc

   User2 Documents
        Documents
             User1sDocument.doc

   The migration process, creates the document under User1's documents, and creates a link to the document from User2's documents. When User2 clicks his version of the document, it loads the original (if he has permissions). All permissions should be migrated.

   When you have a link to an entry in another user’s directory, you see the title link as follows:

   Link->User1sDocument.doc

   Clicking that entry redirects you to the actual document if you have permissions.

3. Any orphaned documents still left in the system after your cleanup that are referenced by other users are placed in the Admin Home directory under the admin personal workspaces. All the files are hidden, but any user who had access to them before can see them through their links.

4. Vibe does not support linked documents natively. Moving forward, the best thing to do is to create a new structure to stored documents based on business needs and access controls. Documents should be moved to where they belong in this new structure. Links can then be deleted by the user by going to the folder containing the links and clicking the check box to the left of the link, then clicking the Delete button above the folder. Duplicates should be handled in the same way, by moving them to the appropriate area and removing the duplicate links.

This information was provided by our Engineering and Services organization as they developed these tools/utilities and executed them for a Government customer in the US. Please let us know if you use this information and if you find anything that would be useful to share. The article and best practices will be updated accordingly. We would love to hear your successful or unsuccessful implementations and migrations.

• Vibe Cool Solutions

While BrainShare has been a personal distraction for a few weeks and the GroupWise blog has suffered, the engineering team has steadily made progress in a variety of areas. Here is an update!

Novell Data Synchronizer Mobility Pack 1.2.5 has been released in the Patch Finder.

GroupWise Mobility Service 1.2.5 Releases

There are several important new capabilities and device support included in this regularly scheduled Mobility update. I have listed as many as possible here.

• Additional Device Operating Support: Windows Phone 8 is now supported.
• Improved User/Group Management: Users and groups are now managed on a Synchronizer system level, rather than being associated with individual connectors.
• Global Status Monitor: A preview version of the new Global Status Monitor is available for monitoring all aspects of your Synchronizer system in a single Web interface.
• Device Quarantine: New devices can be automatically quarantined, so that they do not automatically connect to your Synchronizer system until you release them from the quarantine.
• Automatic Device Removal: Unused devices can be automatically removed from your Synchronizer system.
• Maximum Item Synchronization: You can control how much data synchronizes to mobile devices when users configure their devices to request synchronization for all email and calendar items.
• MCheck Utility: The new MCheck utility helps you diagnose synchronization problem. MCheck gathers configuration settings for your Synchronizer system and verifies that the contents of the GroupWise Address Book and users’ mailboxes have synchronized to the Mobility Connector database.
• Resource Mailbox Synchronization: You can synchronize resource mailboxes to your mobile device along with your own mailbox.
• Simplified Logging Levels: The Info logging level now provides sufficient logging information for day-to-day usage. The Debug logging level should be used only for short-term periods of troubleshooting.
• Synchronizer Web Admin Access by root User: If the LDAP server associated with your Synchronizer system is unavailable, you can log in to Synchronizer Web Admin using the root user name and password.
• Anonymous Feedback: You can submit anonymous feedback about your Synchronizer system to Novell, in order to assist in ongoing efforts to improve Synchronizer performance.
• WSTrust: The WSTrust single sign-on solution is now supported for use with Synchronizer Web Admin.

See the Readme for additional details and information.

Increased Scalability

Recommended Number of Devices

A single Synchronizer server can comfortably support approximately 750 devices.

The performance of your Synchronizer system depends on many variables including server configuration, system configuration, and the level of user activity, both in GroupWise and on their mobile devices. This statement of support is based on the following testing parameters:

Server Configuration

• Virtual machine
• 2.8 GHz processor
• 4 CPUs
• 8 GB RAM

Synchronizer System Configuration

• 500 users
• 750 devices

User/Device Traffic

• Average of 181 GroupWise events/minute
  
  • Email send / read/ move to folder / delete
  • Appointment send / accept / decline / delete
  • Folder create
• Average of 474 events/user in a 24-hour period
• Average of 165 device requests/minute
  
  • Email send / read
• Average of 427 emails from devices in a 24-hour period
• Average of 2479 KB/minute of attachment data transfer
  
  • 97% under 1MB
  • 2% between 1MB and 2 MB
  • 1% above 2 MB

Additional Details –>

BES, RIM, Blackberry 10

A couple of weeks ago, Novell finished its initial certification and testing of Novell Mobility Service with BlackBerry 10 devices. The Device Wiki has been updated with the current status, known issues, and expectations. Making sure the GroupWise works with the latest Mobile devices is top priority and will continue to update, validate, and certify devices and services as our partners and other vendors release new solutions.

RIM continues to be an excellent partner . Slav Koziarski, Enterprise Product Manager with RIM, presented once again this year at BrainShare 2013. RIM has released BlackBerry Enterprise Service 10, which is supported by RIM/Novell. In addition, BlackBerry 10 devices are supported via Novell Mobility Service, BlackBerry Device Service and BlackBerry Enterprise Service 10.

GroupWise 2012 SP2 – Authorized BETA

About three weeks ago, Novell released GroupWise 2012 SP2 to its authorized BETA sites. As is customary with our support packs, GroupWise 2012 SP2 includes a number of fixes to customer-reported issues.

GroupWise 2012 SP2 also introduces what we are calling our "Coexistence Solution," which provides improved support for mixed GroupWise 2012 and Exchange 2010 environments. The GroupWise Blog recently published an article relating to this technology and solution.

Novell expects to run the authorized beta for a few more weeks to make sure the code is adequately run through its paces and then engineering will release the product publicly. Judging by beta site response and other indicators – I expect the release to happen before May.

Dean

• End-User Computing

license:  UC1522507

download url: http://www.messagingarchitects.com/netmail-platform/free-gw-tools/email-essentials/cleanit-for-groupwise-80.html
home page url: www.messagingarchitects.com

CleanIt for GroupWise 7.0, 8.0 & 2012 (now in beta)

Are you interested in trying the latest version of our very popular free tool CleanIt? We've recently retooled this cool little tool to support GroupWise versions 7.0, 8.0 and 2012. Make sure you have a fresh and clean desktop before upgrading to GroupWise 2012. CleanIt removes old GroupWise client files and registry settings, including those for GroupWise Messenger.

CleanIt runs as a single executable file - no installation required.

Help us make sure the latest version of CleanIt for GroupWise is rock solid by testing it out for us.

• Cool Solutions