TFalconer Absent Member.
Absent Member.
3741 views

Changing initial-web-service file at the server

Hi,

Is there any way to change information in the c:\program files\novell\zenworks\conf\initial-web-service file at the server end?

I have installed ZCM SP2 on a SLES10 XEN-based virtual server for which I was given incorrect DNS info. I have changed the incorrect DNS information on the SLES virtual server from server.organisation.com to server.local. I have also changed the ZAA deployment package so that it now points to the correct DNS name (server.local).

However when I log into a workstation I am unable to log into ZCM - I get a popup telling me to check my credentials (Unable to log into the ZENworks realm because the system has disconnected from the network and the specified credentials did not match with the credentials cached on the system.), etc. Having checked this error message on the forums it all pointed to DNS which has now been sorted - for this workstation anyway. There is no dynamic DNS so this workstation has been setup manually and the name is resolvable by the ZCM server. I am able to register and unregister the workstation from ZCM so there is communication. And according to the agent it's pointing to server.local - this having been changed in the Deployment Package so that's okay.

I have also noticed that when I uninstall the ZAA from the workstation the server address points to server.organisation.com. If I change this to server.local the uninstall does remove every trace of the workstation from ZCM.

Everything I have checked so far points me to the initial-web-service file which, every time I deploy it, still has the incorrect DNS information pointing to server.organisation.com. I'm pretty sure this is the problem. It's not a
workstation issue because the uninstall does remove this file as it should and I have the same issue on other machines.

Is there any way to change this incorrect DNS name in the initial-web-service file so that ZCM deploys it (with the ZAA) with the correct info?

Thanks
T
Labels (2)
0 Likes
2 Replies
TFalconer Absent Member.
Absent Member.

Re: Changing initial-web-service file at the server

Here's how to change the DNS name of your Primary ZCM server:


  1. Backup /etc/opt/novell/zenworks/security - Just In Case.

  2. Recreate your CA on the Primary server - see TID 3911570

  3. Perform the following steps on the Primary Server:
      At the console prompt, run the following command
      novell-zenworks-configure -c SSL -Z
      Follow the prompts.

      Restart all the ZENworks services by running the following command:
      novell-zenworks-configure -c Start
      By default, all the services are selected. Select Restart as the Action.


      Edit the initial-web-service file,found in /etc/opt/novell/zenworks/, and replace the content of the server certificate section with the pem format available in the server.cert file which is found in /etc/opt/novell/zenworks/security/.

      Rebuild the agent packages by running the following commands:
      novell-zenworks-configure -c CreateExtractorPacks -Z
      novell-zenworks-configure -c RebuildCustomPacks -Z (OPTIONAL)

  4. Perform the following steps at the command prompt of each managed device and Satellite registered to the Primary Server where you change the certificate:
      Run the following command to force the device to be unregistered locally:
      zac unr -f

      Clear the cache.
      On Windows: Run the following command:
      delete c:\program files\novell\zenworks\cache\zmd /s
      On Linux: Run the following command:
      rm -rf /var/opt/novell/zenworks/zmd/cache

      Run the following command to register the device in the Management Zone:
      zac reg https://ZENworks_Server_DNS_name
      This replaces the server certificate in the local cache.
0 Likes
TFalconer Absent Member.
Absent Member.

Re: Changing initial-web-service file at the server

Sorry, the Windows cmd should be
del c:\program files\novell\zenworks\cache\zmd /s
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.