Untitled

Identify the Appliance Online UpdateRegcode

Depending on the appliance theregcode is different “regcode-zenworks-appliance”

To find the correct regcode at theserver command prompt:

cat /etc/Novell-VA-release |grep regcode

Access to the certs is critical

Option 1:


-Copy valid CA Cert from previous appliance to new appliance

Location: /etc/ssl/certs

<NameOfCert>.pem



At the Appliance Server command prompt, run:c_rchash

Option 2:

Command to create the cert with OpenSSL

true | openssl s_client –connect secure-www.novell.com:443–showcerts > /tmp/www-novell-com-ca-certs.pem

Copy cert to /etc/ssl/certs

Example: www-novell-com-ca-certs.pem

Appliance Server command prompt, run: c_rchash

Online Update Registration

Register Online Updates CreateCert

ZRS Server command prompt andexecute the suse_register command manually

/usr/bin/perl –w /usr/bin/suse_register –d 3 –aemail=<email address> -a regcode-zenworks-appliance=<activationcode> -L <log file path>

Online Update UnRegister

Likewise the command to unregister the appliance from NCCis,


/usr/bin/perl –w /usr/bin/suse_register –E

Related:

  • No Related Posts

Untitled

Identify the Appliance Online UpdateRegcode

Depending on the appliance theregcode is different “regcode-zenworks-appliance”

To find the correct regcode at theserver command prompt:

cat /etc/Novell-VA-release |grep regcode

Access to the certs is critical

Option 1:


-Copy valid CA Cert from previous appliance to new appliance

Location: /etc/ssl/certs

<NameOfCert>.pem



At the Appliance Server command prompt, run:c_rchash

Option 2:

Command to create the cert with OpenSSL

true | openssl s_client –connect secure-www.novell.com:443–showcerts > /tmp/www-novell-com-ca-certs.pem

Copy cert to /etc/ssl/certs

Example: www-novell-com-ca-certs.pem

Appliance Server command prompt, run: c_rchash

Online Update Registration

Register Online Updates CreateCert

ZRS Server command prompt andexecute the suse_register command manually

/usr/bin/perl –w /usr/bin/suse_register –d 3 –aemail=<email address> -a regcode-zenworks-appliance=<activationcode> -L <log file path>

Online Update UnRegister

Likewise the command to unregister the appliance from NCCis,


/usr/bin/perl –w /usr/bin/suse_register –E

Related:

  • No Related Posts

Untitled

In versions 7.1 through 7.7 SP2, you can enable management server connections through a firewall by configuring your management server, firewall, and Administrative Console as follows:

  1. Configure the management server ports:
    1. In a text editor, open the management server properties file. Typical locations are as follows:

Version 7.5 through 7.7 SP2 on 64-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 64-bit Windows: C:Program Files (x86)AttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 32-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Linux/UNIX: /opt/attachmate/verastream/managementserver/conf/container.properties

    1. In the rmi.export.port.ssl line, set a desired port number for encrypted RMI communications. (The default value 0 represents use of arbitrary ports.)
    2. (Optional:) By default, an additional port 33000 is used for encrypted RMI/JMX communication. However, you can configure rmi.port.ssl to use a different value instead.
    3. (Optional:) If you plan to also use third-party JMX tools and need to enable unencrypted JMX communications, set rmi.port to a desired port number such as 33001. (The default value 0 disables non-secure JMX.) Enabling non-secure JMX will also enable unencrypted RMI communications; set rmi.export.port to configure its port number. (The default value 0 represents use of arbitrary ports for non-secure RMI.)
  1. Important: After saving the modified file, restart the management server as described in KB 7021352.

Note: When you upgrade your product installation in the future (major release, service pack, or hotfix), the container.properties file may revert to new defaults. After upgrading, the above steps will need to be repeated.

  1. Configure your firewall:
    1. Refer to your firewall documentation for changing its configuration.
    2. Allow communication to the port you configured in step 1.b. above (rmi.export.port.ssl).
    3. Allow communication to the additional port 33000, or different port you configured in step 1.c. above (rmi.port.ssl).
    4. (Optional) If you plan to also use third-party JMX tools through the firewall, allow communication to the additional non-secure ports configured in step 1.d. above (rmi.port and rmi.export.port).
  2. Configure Administrative Console:

If you configured a different port in step 1.c. above, change the Connection Port in Console > Preferences > Connections. The default value is 33000.

Related:

  • No Related Posts

Untitled

In versions 7.1 through 7.7 SP2, you can enable management server connections through a firewall by configuring your management server, firewall, and Administrative Console as follows:

  1. Configure the management server ports:
    1. In a text editor, open the management server properties file. Typical locations are as follows:

Version 7.5 through 7.7 SP2 on 64-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 64-bit Windows: C:Program Files (x86)AttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 32-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Linux/UNIX: /opt/attachmate/verastream/managementserver/conf/container.properties

    1. In the rmi.export.port.ssl line, set a desired port number for encrypted RMI communications. (The default value 0 represents use of arbitrary ports.)
    2. (Optional:) By default, an additional port 33000 is used for encrypted RMI/JMX communication. However, you can configure rmi.port.ssl to use a different value instead.
    3. (Optional:) If you plan to also use third-party JMX tools and need to enable unencrypted JMX communications, set rmi.port to a desired port number such as 33001. (The default value 0 disables non-secure JMX.) Enabling non-secure JMX will also enable unencrypted RMI communications; set rmi.export.port to configure its port number. (The default value 0 represents use of arbitrary ports for non-secure RMI.)
  1. Important: After saving the modified file, restart the management server as described in KB 7021352.

Note: When you upgrade your product installation in the future (major release, service pack, or hotfix), the container.properties file may revert to new defaults. After upgrading, the above steps will need to be repeated.

  1. Configure your firewall:
    1. Refer to your firewall documentation for changing its configuration.
    2. Allow communication to the port you configured in step 1.b. above (rmi.export.port.ssl).
    3. Allow communication to the additional port 33000, or different port you configured in step 1.c. above (rmi.port.ssl).
    4. (Optional) If you plan to also use third-party JMX tools through the firewall, allow communication to the additional non-secure ports configured in step 1.d. above (rmi.port and rmi.export.port).
  2. Configure Administrative Console:

If you configured a different port in step 1.c. above, change the Connection Port in Console > Preferences > Connections. The default value is 33000.

Related:

  • No Related Posts

Untitled

Identify the Appliance Online UpdateRegcode

Depending on the appliance theregcode is different “regcode-zenworks-appliance”

To find the correct regcode at theserver command prompt:

cat /etc/Novell-VA-release |grep regcode

Access to the certs is critical

Option 1:


-Copy valid CA Cert from previous appliance to new appliance

Location: /etc/ssl/certs

<NameOfCert>.pem



At the Appliance Server command prompt, run:c_rchash

Option 2:

Command to create the cert with OpenSSL

true | openssl s_client –connect secure-www.novell.com:443–showcerts > /tmp/www-novell-com-ca-certs.pem

Copy cert to /etc/ssl/certs

Example: www-novell-com-ca-certs.pem

Appliance Server command prompt, run: c_rchash

Online Update Registration

Register Online Updates CreateCert

ZRS Server command prompt andexecute the suse_register command manually

/usr/bin/perl –w /usr/bin/suse_register –d 3 –aemail=<email address> -a regcode-zenworks-appliance=<activationcode> -L <log file path>

Online Update UnRegister

Likewise the command to unregister the appliance from NCCis,


/usr/bin/perl –w /usr/bin/suse_register –E

Related:

  • No Related Posts

Untitled

In versions 7.1 through 7.7 SP2, you can enable management server connections through a firewall by configuring your management server, firewall, and Administrative Console as follows:

  1. Configure the management server ports:
    1. In a text editor, open the management server properties file. Typical locations are as follows:

Version 7.5 through 7.7 SP2 on 64-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 64-bit Windows: C:Program Files (x86)AttachmateVerastreamManagementServerconfcontainer.properties

Version 7.1.x on 32-bit Windows: C:Program FilesAttachmateVerastreamManagementServerconfcontainer.properties

Linux/UNIX: /opt/attachmate/verastream/managementserver/conf/container.properties

    1. In the rmi.export.port.ssl line, set a desired port number for encrypted RMI communications. (The default value 0 represents use of arbitrary ports.)
    2. (Optional:) By default, an additional port 33000 is used for encrypted RMI/JMX communication. However, you can configure rmi.port.ssl to use a different value instead.
    3. (Optional:) If you plan to also use third-party JMX tools and need to enable unencrypted JMX communications, set rmi.port to a desired port number such as 33001. (The default value 0 disables non-secure JMX.) Enabling non-secure JMX will also enable unencrypted RMI communications; set rmi.export.port to configure its port number. (The default value 0 represents use of arbitrary ports for non-secure RMI.)
  1. Important: After saving the modified file, restart the management server as described in KB 7021352.

Note: When you upgrade your product installation in the future (major release, service pack, or hotfix), the container.properties file may revert to new defaults. After upgrading, the above steps will need to be repeated.

  1. Configure your firewall:
    1. Refer to your firewall documentation for changing its configuration.
    2. Allow communication to the port you configured in step 1.b. above (rmi.export.port.ssl).
    3. Allow communication to the additional port 33000, or different port you configured in step 1.c. above (rmi.port.ssl).
    4. (Optional) If you plan to also use third-party JMX tools through the firewall, allow communication to the additional non-secure ports configured in step 1.d. above (rmi.port and rmi.export.port).
  2. Configure Administrative Console:

If you configured a different port in step 1.c. above, change the Connection Port in Console > Preferences > Connections. The default value is 33000.

Related:

  • No Related Posts