ShareFile for Android

Supported Localization: German, French, Spanish, Japanese, Simplified Chinese, Korean, Dutch, Russian and Portuguese.

Requirements and Limitations


  • No Related Posts

Collaboration Community Technical Webinar: “Best Practices for upgrading to GroupWise 18” is posted

Mike Bills

If you missed it or just want to watch it again, the latest webinar for the Collaboration Community “Best Practices for upgrading to GroupWise 18”  has been posted and you can view it here! Don’t forget we choose the topics for Collaboration Community Technical Webinar series by you telling us what you want to see. …

+read more

The post Collaboration Community Technical Webinar: “Best Practices for upgrading to GroupWise 18” is posted appeared first on Cool Solutions. Mike Bills


  • No Related Posts

NetWorker 9.x: Unable to select VBA, the VBA list is blank for VMware backups in Workflow>Action

Article Number: 486491 Article Version: 4 Article Type: Break Fix

NetWorker 9.0,NetWorker 9.0.1,NetWorker 9.0.50

After a Policy is created, Policy’s Workflow & Action should be created using the wizard.

But in the second step of Action creation the list of VBAs is blank. Not allowing the policy to be created.

This is seen due to a mismatch of the Hypervisor resource in NetWorker Server and vCenter name in VBA.

For example:


p:type:NSR Hypervisor




Above is the output of printing Hypervisor resource.

But when the VBA is printed:

p type:NSR VBA Server



As shown above, there is a mismatch between the NetWorker Server’s Hypervisor resource(created with a shortname of the vCenter), and VBA resource(has the FQDN of the vCenter).

There can be various configuration changes done to match the configuration between resources. These could involve:

1. Changing the ‘nsr hypervisor’ resource


2. Re-deploying the VBA

NOTE: Below workarounds involve changing your resource database- it is recommended to make copies of ‘nsrresnsrdb’ directory before attempting changes.

Workaround 1: Change the Hypervisor resource:

  1. Delete the groups created with current vCenter name
  2. Delete the current resource:


    > delete type: nsr hypervisor; name: vcenter-name

    Delete? Yes
  3. Create new resource that matches your VBA:

    > create type: nsr hypervisor; name: vcenter-name.test.domain

    create> Yes

    > p type:nsr hypervisor; name: vcenter-name.test.domain

    > update username: abc@test.domain

    update> yes

    > update password: test12

    update > yes

    > update proxy: nw-server-name

    update: yes

    > p type:nsr hypervisor; name: vcenter-name.test.domain
  4. Verify your resource has the right user/password
  5. Refresh the NMC > Configuration > VMware View
  6. Create new groups as needed

    You should now be able to assign policies with these new groups to VBAs

Workaround 2: If you have recently registered a new VBA and have other VBAs working fine- you may not want to remove ‘nsr hypervisor’ resource. In this case- you can choose to re-deploy your new VBA:

NOTE: This involves deleting your new VBA and its backup data from networker. If you have any backups taken through this new VBA- you will not able to restore them after below change

  1. Contact EMC Support for assistance with ‘decommission’ your VBA. See
  2. Deploy a new VBA and during the initial wizard- select the vCenter name that matches your networker’s ‘nsr hypervisor’ resource


  • No Related Posts

“No Syslog box in the dropdown options”.configuring VNX block only array to send logs to syslog server

Article Number: 483920 Article Version: 3 Article Type: Break Fix

Unisphere for VNX

Customer could not get past step 2c in the attached document.

It was determined that they did not have a host agent installed on the appliance or workstation that they wanted to use as the syslog server. (It was also confirmed that they could not install a Host agent on the server due to security considerations.)

Install the appropriate host agent on the syslog server.

You can find the host agent with the following search:

Here’s a link with additional instructions:

Type in Unisphere Host Agent in the (Scope by Product) search box, leave ‘All support’ default in the ‘Scope by resource’ box and most importantly, click on the ‘Advanced Options’ tab over on the lower right. (otherwise a completely different and larger list will populate in findings as it doesn’t do a ‘full text’ search.)

search page screenshot

This search can be modified to find either Windows specific or Unix and other OS versions of the host agents as well. Here are some of the common ones:


Unisphere Host Agent for Windows 32 and 64-bit

Unisphere Host Agent (Linux x64)

Unisphere Host Agent for Linux x86

Unisphere Host Agent (Solaris x64)

Unisphere Host Agent (Solaris SPARC)

Unisphere Host Agent for AIX

Unisphere Host Agent for HP-UX

*Note: Purposely I left out the version number in all of these, and tested search functionality and they all pull up the latest and older versions of each type.

On a block only array, a host agent must be installed on the syslog server.

>> Here’s a questionnaire that you can provide to customer to determine their set up status:

1. Do you have a Host agent installed on the system (workstation) that you are going to be using as the Centralized Monitor station?

2. What is the Host agent type and version?

3. What is the OS and version on the Portal system or workstation (or VNX array) that you have designated?

4. Have you added the Portal IP address(es) to the Host Agent config file?

5. Could you verify that the other systems or workstations that you expect to see in the Available systems dropdown are not already functioning as portals? Can you also verify that they are running Unisphere for Windows?

6. *If* you are using VNX as the portal, do you have more than 20 hosts attached to the array? Note: the attached document states -> IMPORTANT: Do not use as a portal a VNX system that has more than 20 attached hosts.



  • No Related Posts