Q: Why are my Android devices unable to synchronise messages using Google Gmail with GroupWise Mobility Service (GMS) when connection settings are defined by an MDM solution?
A: Open the GMS Admin Console and navigate to the following page:
GroupWise Mobility Service > Config > Device > Enable “Device Security Policy”.
No other settings are needed to be defined in this section.
Q: My QuickFinder indexing is not starting and I see the following error message in the POA logs: “QuickFinder Indexing will not start until the configured DVA is active”. The DVA is running/active on the server. What can I do to resolve this?
A: The most common cause of this issue is a mismatch in the configuration of the DVA between what the DVA has physically been configured with against how the POA has been configured to communicate with the DVA, particularly with regards to the SSL configuration.
By default the DVA does not use SSL. To check this login to the POA Web Console > Configuration > Document Viewer Agent > and see if it is reporting “Offline”. (figure 2).
If it is “Offline” click on the Document Viewer Agent hyperlink > remove the tick in the box by “Use SSL” > select “Update Document Viewer Agent Access Status” and click on Submit.
The status of the DVA, as reported on the POA Web Console should change to Online. If it does change to Online then the configuration mismatch is indeed the SSL settings.
Go to the GroupWise Admin Console > System > Document Viewer Agent > select the agent and remove the tick next to SSL (figure 3). Alternatively configure the actual DVA for SSL.
Q: I’ve renamed a user, removed them from GMS and added them back, yet mail sent from the device still has the old name/email address. How do I update this?
A: I’ve found a combination of restarting the POA to clear the persistent SOAP threads, and then rebuilding the GAL on GMS updates the name/email address.
Q: When I’m installing GMS I get the error “Problem Validating GroupWise Server and credentials”
A: This might be related to the GroupWise admin service certificate in two ways:
The certificate was created in an earlier gw2014 version and does not have the following section in the certificate
X509v3 Subject Alternative Name: DNS:gwserver.company.com, IP Address:1.1.1.1
The GroupWise server has changed hostname or IP number since the certificate was created so the following section doesn’t match the current environment
X509v3 Subject Alternative Name: DNS:gwserver.company.com, IP Address:1.1.1.1
You can verify the certificate and whether the information in there is correct by doing the following:
- On the server hosting the GroupWise primary and secondary domain go to:
/opt/novell/groupwise/certificates/<longhashdir> - Find your domain certificate - admin.domainname.crt3 - and run the following command:
openssl x509 -text -in admin.domainname.crt > cert.txt - You can now open the cert.txt in any text editor and look for the X509v3 Subject Alternative Name
- If this is not correct or missing you can recreate the certificate, to have the correct information with the following command on the primary domain and the domain you are running the GMS installation against:
gwadminutil certinst –db /path/to/dom –ca x.x.x.x:9710 –a adminuser -p adminpassword
Replace the x.x.x.x with the IP number of the primary domain and the -a has the super admin user and -p this user’s password. - Ensure you restart the gwadmin service.
- After this make sure you empty /var/lib/datasync/mobility/ before running the GMS installation again as this holds the certificate before the new certificate was generated and will not be overwritten.
This article was first published in OHM Issue 42, 2018/3, p37-38.