Please note that in a recent update published by Novell, they have opted to lengthen Extended Support for Novell NetWare 6.5 and Novell ZENworks 7 Suite by a year, to 30 September 2013. In addition, Novell BorderManager and Novell GroupWise 8 are extending General Support, and will be supported on NetWare 6.5 for the same time period.

Product Previous Support End Date New Support End Date

• NetWare 6.5 30 Sept 2012 (Extended Support) 30 Sept 2013 (Extended Support)
• ZENworks 7 30 Sept 2012 (Extended Support 30 Sept 2013 (Extended Support)
• GroupWise 8 1 May 2013 (General Support) 30 Sept 2013 (General Support)
• BorderManager 3.9 30 Sept 2012 (General Support) 30 Sept 2013 (General Support)

For the best value, Novell encourages upgrades to the latest release of Novell Open Enterprise Server and Novell ZENworks Configuraiton Management, but is offering Extended Support on these older releases to provide more deployment time for customers who need it.

The Extended Support phase of Novell's Product Support Lifecycle offers installation and configuration technical support and critical security fixes for customers with current maintenance on the replacement products - in this case Novell Open Enterprise Server 2 and Novell ZENworks Configuration Management 11.

Free Unlimited Extended Support on ZENworks 7 Suite

Current Novell Open Enterprise Server maintenance customers already realize free, unlimited 12x5 technical support during the Extended Support phase for NetWare. Effective 1 January 2012, Novell is offering this same free, unilmited 12x5 technical support benefit on ZENworks 7 Suite for all customers with current maintenance on Novell's ZENworks Configuration Management.

Product Information

• Novell NetWare 6.5 and Novell ZENworks 7 Suite Extended Support brings the following benefits through 30 September 2013:
• Continue to receive installation support while you plan and execute your upgrade from NetWare 6.5 to Open Enterprise Server on Linux, and from ZENworks 7 Suite to ZENworks 11
• Receive unlimited service requests 12 hours a day, 5 days a week from a Novell technical support engineer

Customers who are not current with maintenance may purchase Standard or Priority maintenance for licensed users and take advantage of Extended Support on ZENworks 7 Suite or NetWare 6.5 for free.

For further information

For detailed information on Novell's Support lifecycle, visit http://support.novell.com or contact Cindy DeHart, Novell & Virtualization Practice Manager at (540) 443-3392 or This e-mail address is being protected from spambots. You need JavaScript enabled to view it

The HP Proliant G6-generation (and newer) servers have a new type of high-efficiency power supply that is sensitive to the waveform output of UPS units.  If you find your UPS is not carrying the new G6 server (it immediately shuts down upon power loss), check the specifications of the UPS unit(s).  The output must be True Sinewave.  If it is anything else (Stepped Approximation to Sinewave is the usual alternative), then the server will not run on it.

Contributed by Brian Ogden
2011-08-30

The Verizon Droid 3 phone is not supported by Novell Data Synchronizer due to the change in the phone software.

When you setup an account on the device, the certificate setting isn't visible on the initial screen. However, "Use a secure connection" and "Verify Certificate" is automatically enabled. Since we always use a self-signed certificate, this cert is not part of the trusted authority on the device. If you use the workaround below, you can setup an account that works, then uncheck verify certificates and switch to the config of the customer Novell Data Synchronizer.

Here is a workaround:

1. Set-up a corp-sync or Exchange Activesync account
2. Use your google account to create a corporate sync account . The prompt for server name should be “m.google.com” and the prompt for user name is your gmail address (the entire email address, not simply the first half/user part). So, as an example:
3. Server: m.google.com
4. Username: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
5. After the account is created, go into settings -> accounts and select the EAS account created
6. In the first screen, un-check the option "Verify Certificate"
7. Change the credentials to the account needed

If you find you need more assistance with this issue, please don't hesitate to contact us!

ALI Technical Assistance Center
(540) 443-3398
This e-mail address is being protected from spambots. You need JavaScript enabled to view it

1. Click Start, and then click Run.
2. In the Open box, type regedt32, and then click OK.
3. Locate and click the following registry key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler
4. Click Add Value on the Edit menu.
5. Type DependOnService in the Value Name box.
6. Click REG_MULTI_SZ in the Data Type box, and then click OK.
7. Type LanmanServer in the Data box, and then click OK.
8. Click Exit on the Registry menu to quit Registry Editor.
9. Restart your computer.

On HP workstations and laptops that use high-density (750GB-1TB) hard drives and are running Windows, older versions of the Intel Rapid Storage Technology driver can cause various problems including the inability to run Windows Update. 

The error message will state that the Windows Update service is not started, but if you check it, it is running. 

The solution is to download version 9.5.6.1001 (software package SP47845) or newer of the Intel Rapid Storage Technology driver from HP's support website.  

If you need help with this or any other support issue, please don't hesitate to contact me at the ALI Technical Assistance Center at (540) 443-3398.

Brice Stevens    
Advanced Logic Industries
Technical Assistance Center (TAC)
This e-mail address is being protected from spambots. You need JavaScript enabled to view it

GroupWise 8 & 7 users should check their security patches RIGHT AWAY! 
The GroupWise Internet Agent (GWIA) has a vulnerability.

If you need assistance with resolving this GWIA issue, please do not hesitate to contact our TAC.

Are you running DHCP on your OES 2 server?
Would you like to view the DHCP leases in use?
Well, now you can in OES 2 SP3!

Please contact the ALI TAC to schedule the upgrade and configure DHCP for this feature!

This document (7006450) is provided subject to the disclaimer at the end of this document.

Environment

Situation

• Configure the "DHCP server IP address" to view the leases
• Configure the "omapi-key" setting of the DHCP server object to view the leases
• Configure the following DHCP server settings to view the leases: DHCP Server IP address, omapi-key
• ERROR: EOMAPI1
• ERROR: DHCP server connection failed

Resolution

To address the "DHCP server IP address" portion of the message(s), do the following:

1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
2. Click on the 'DHCP (OES Linux) tab toward the top of the console
3. Find the DHCP Server object at the bottom of the console and select it
4. Toward the top-right hand side of the console select the GENERAL tab and find the section called DHCP SERVER
5. Click the ADD button and enter the IP address of the DHCP server
   • NOTE:  If doing this step on OES 2 SP 2 the buttons may be greyed out.  This is due to the schema not being extended.  This option is officially supported on OES 2 SP 3
6. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)

1. The first step in addressing this issue is to create a TSIG key if one has not already been created.
   • NOTE:  At the time this TID (Technical Information Document) was created, the secret for the TSIG key must be divisible by four (4).  If it is not DHCP will not load.  For instance, if the key's secret is set to SECRET then DHCP will fail to load as the secret is not divisible by four; however, if SECRET12 is used instead, then DHCP will load as the secret is now divisible by four.
     1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
     2. Click on the 'DHCP (OES Linux) tab toward the top of the console
     3. Highlight the SERVICE object (assuming it has already been created) and click on the CREATE button located at the top, left-hand side of the console (looks like a 3-dimensional box)
     4. Select 'TSIG Key" and assign the KEY NAME and SECRET.  Keep in mind the note above regarding the secret to make sure the number of characters used in the secret is divisible by four
     5. After hitting CREATE on the key the key should show up under the service object that was highlighted
2. The second step in addressing this issue is to add the omapi-key setting itself
   1. While in the DNS/DHCP management console, and with the 'DHCP (OES Linux)' tab selected, highlight the DHCP SERVER object toward the bottom of the console
   2. Select the SETTINGS tab toward the top, right-hand side of the console (next to the GENERAL tab)
      • NOTE:  At this point the administrator should see a setting for the OMAPI-PORT already configured for port 7911.  If it is not there, the click the MODIFY button, find the setting, add it and assign it a port of 7911 (which is the default)
   3. Click on MODIFY and find the OMAPI-KEY setting (likely at the bottom of the list).  A drop down menu should appear after adding it, and a list of found TSIG keys should be presented.  Select the appropriate key
      • NOTE:  If the key doesn't show up at this point, review the steps above and create the key as specified
   4. Review the settings and make sure there is an OMAPI-PORT and OMAPI-KEY setting, each assigned a valid value
   5. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)

At this point it may be necessary to hit the TREE REFRESH button located at the top, left-hand side of the console.  It is found next to the SAVE button.  Once the tree refresh is complete, expand the SUBNET and then the POOL to view any current leases that may be assigned out.  If one of the following errors is encountered, it is likely due to the fact that the leases file has not yet been populated with any leases.  This error should resolve itself once there is a lease to be found in the dhcpd.leases file on the server:

• ERROR: EOMAPI1
• ERROR: DHCP server connection failed

NOTE: The 'omapi-port' and 'omapi-key' settings cannot be added, modified, or managed from iManager in any way at the time this TID was written.  This has been reported to Engineering.   The steps described in this TID should be completed from the DNS/DHCP Management Console.

Our TAC support desk has seen some recent instances of HP notebooks having CPU usage spikes that drive overheating because the HP Wireless Assistant service gets hung up. 

If, on an HP laptop, the WMIPrvSE.exe process is causing repeated excessive CPU usage spikes (25% or more every few minutes) and thus overheating, try disabling the HP Wireless Assistant service.

(Start menu -> Control Panel -> Administrative Tools -> Services)

Some older versions of this software have this issue, though HP indicates the latest version is fixed for this bug.

The HP Wireless Assistant's only purpose seems to be to inform the user whether the wireless is on or off. However, if you find your wireless switch on your keyboard no longer works with the HP Wireless Assistant disabled, obtain the latest version from HP's website, uninstall the old first, then install the new.

If you need more help with this issue or would like other help with your technical support issues, please don't hesitate to contact us in the Technical Assistance Center!

Brice Stevens
ALI TAC Support Lead
(540) 443-3398
This e-mail address is being protected from spambots. You need JavaScript enabled to view it

Important LiveUpdate Certificate Expiration Notice

 Problem

An older Symantec root certificate, SymRoot1, will expire on April 30, 2011. With an expired certificate, older LiveUpdate clients would no longer authenticate, download, or install content such as AntiVirus definitions or product updates.

Solution

To allow customers additional time to plan migrations, Symantec has introduced a workaround that allows LiveUpdate to continue to successfully authenticate valid content from Symantec through July 4, 2012. This date may be extended if needed on a product-by-product basis.

In addition, a newer Symantec root certificate, SymRoot2, will expire on August 23, 2020. Newer Symantec products and recently patched products are compatible with SymRoot2. All customers utilizing SymRoot1-based products are recommended to upgrade to SymRoot2-based products.

What is the impact of using SymRoot1 definitions after the certificate expiration?

The product will continue to download and install new updates, such as AntiVirus definitions and product updates. You do not need to do anything to continue to receive definitions for these products after the certificate expiration, but you are encouraged to upgrade to a version that supports SymRoot2 as soon as feasible.

Will products without SymRoot2 support still be able to use Intelligent Updater or Rapid Release to update definitions?

Yes, Intelligent Updater and Rapid Release definition packages will be signed by both SymRoot1 and SymRoot2.

Which products are affected?

The following table shows which product versions support SymRoot2 in green, which product versions will continue to receive SymRoot1 definitions after the certificate expiration in orange, and which product versions require an upgrade in red.

 My product version will not be updated. How do I upgrade?

If possible, Symantec recommends that you upgrade to a version that supports SymRoot2. SymRoot2 compatible products appear in green in the table above. You can download the latest version of your product from File Connect or from the Business Critical Services Web site.

For some products, you may need to apply patch instead of upgrading. For additional assistance, the Technical Assistance Center line is available to provide support (540) 443-3398 or contact your ALI representative for further assistance.