Untitled

1) Export the new CA Certificate as der file. First cd /opt/novell/devman/bin then run following being sure to replace <password> with admin password.

source/opt/novell/eDirectory/bin/ndspath && /opt/novell/java/bin/java -cp certtool.jar:/opt/novell/lib64/npki.jarcom.novell.nids.certmgr.DirCertTool -edirIP 127.0.0.1 -edirUsercn=admin.o=novell -edirPwd <password> -exportCACert -file ca.der

Youan also export by going to Roles and Tasks in AC GUI -> NetIQ CertificateServer Role -> Configure Certificate Authority -> Certificates ->Export Self-Signed without private key as der

*If you can’t get to iManager on Primary AC you can download and use iManager Workstation, which can be extracted on Linux or Windows. See iManageron Netiq Download Site

2) Add exported CAcertificate to NAM keystores.

TheCA der file needs to be added manually through keytool in following locations.

AC: /var/opt/novell/novlwww/devman.cacerts


IDPand AG: /opt/novell/devman/jcc/conf/jcc_devman.keystore

A)For AC devman.cacerts the keystore pass is devman.

Here is an example of importing the ca.der into devman.cacerts

/opt/novell/java/bin/keytool -import -aliasconfigca_2 -keystore devman.cacerts -trustcacerts -file ca.der -storepassdevman

*Do the same on any Secondary Acs.

B)For jcc_devman first you need to get the password for the keystore.

On each IDP and AG…

cd/opt/novell/devman/jcc and run: ./conf/ksinfo.shdump

Exampleof importing cert to jcc_devman.keystore

/opt/novell/java/bin/keytool-import -alias edir_2 -keystore jcc_devman.keystore -trustcacerts -file ca.der-storepass U01eXoV6iyPLVA7

C)For the remaining keystores the ca.der can be added via the Admin Console GUI.

Firstgo to Security -> Trusted roots and import it.

The original one will be calledconfigca. There really is no need toremove that one. Can just import it asconfigca_2 for example.

Nextadd it to:

  • IDPcluster|’s truststore
  • AGESP truststore
  • ProxyTrust store

3) Replace existingcertificates already in use by NAM signed by original CA.

A)Recreate default certificates (Non NAM), however still used for config storeldap etc.


Inadmin Console GUI-> Roles and Tasks -> Netiq Certificate Server ->Create default Certificate.

  • Step1 -> Browse to Admin Console server name and select it. (If secondary Admin Consoles.

  • Step2 -> Click Radio button for “Yes” under Force the generation of new default certificates.

    Ensurethe IP Addresses are correct for “SSL CertificateIP and SSLCertificateDNS”, if not specify in the available field.

  • Step3 -> Click Finish and once done ensure the status of each completesproperly.

    Alternative command line option is to run:

ndsconfigupgrade

Enteradmin user with syntax like “admin.novell” and password when prompted.

B)Recreate Admin-Console Certificate used by tomcat instance that runs iManager.

  • Goto AC GUI -> Security -> Certificates -> New -> Create a new certcalled admin-console_2.

    Ensurethe subject name matches the FQDN name of the Admin Console and I’d recommendsetting months valid to something like 60.

  • Oncecreated click on the new certificate and add it to keystore.

    Thiswill add the new cert to the keystore on the Admin Console filesystem at/var/opt/novell/novlwww/.keystore.

  • Clickthe browse button, then once all the keystores are presented, click on theAdmin-Console keystore.

  • Clickthe “Replace” button and browse to the newly created admin-console_2cert. Ensure alias remains”tomcat”

C) Need to update/replace the Admin Console’s devman.keystore.

The devman.keystore.his keystore is used with device manager and listens on port 8444. NAM devices communicate on this port when sending health info etc to the Admin Console.

  • Export the admin-conssole_2 cert you just recreated.

    Beforewe export we need to see what keystore pass the existing devman.keystore is using. To find this out check the server.xml on the Admin Console at:

    /opt/novell/nam/adminconsole/conf/server.

    Search for “devman.keystore”. This should show up in devman connector section. Just take note of the value of keystorePass .e.

  • Goto AC GUI -> Security ->Certificates -> export public/private key with jks format using the password in the server.xml.

  • Copythis file to Admin Console filesystem at: /var/opt/novell/novlwww/devman.keystore.

    Probablywant to rename the existing one first and ensure new file has same permissionsand ownership as original.

  • After the default certificates are created, need to restart eDirectory and novell-ac on the Admin Console. Execute the following at the terminal to do this.

    ndsmanage stopall && rcnovell-ac restart

    Note: When novell-ac is run it will also start eDirectory

D)Test-* Certificates.

These certificates are meant to be replaced.

If they are currently in use we need to replace them with either externally signed certs or certificates minted with new Certificate Authority. So need to verify if theyare in use.

Check the Security ->Certificates -> and note the test-* certificates that have a device associated withthem and replace them.

E)Take note of any other Certificates that have issuer of original Certificate Authority and replacethem as well.

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

Fixes introduced in the 6.21 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iPrint client asking for authentication, even when Remember Password is checked. (Bug 1172556)

Fixes introduced in the 6.20 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Spoolsv Handles increase when selecting iPrint printer, causing Windows performance problems (Bug )
  • TID 7024095 Windows Apps hang when non-reachable iPrint printer is default. (Bug 1148630)

Fixes introduced in the 6.18 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iCM fails with userPrincipalName (Bug 1113405)
  • iPrint Client hangs spooler listing printers (Bug 1109761)
  • Unable to upload HP Universal PCL 6 (v6.6.5) Driver (Bug 1112601)
  • Authentication fails with dot “.” in AD sAMAccountName (Bug 1126792)

Fixes introduced in the 6.16 FTF iPrint Client

No longer available for download, but the fixes listed here are rolled into future release (as are all fixes with every client version).

  • TID 7023395 6.16 iPrint Client with iPrint Direct printers hangs Windows Print Spooler

Fixes introduced in the 6.16 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iPrintLite prompts for credentials with job submission, even after authentication has occurred. (Bug 1052239)
  • iPrintLite job submission status shows printed successfully with failed jobs. (Bug 1069912)
  • Printing from Edge browser fails. (Bug 1100744)
  • Secure Printing from Edge prompts for credentials, even after credentials already provided. (Bug 1103565)
  • Printer driver not updating with auto driver/profile update feature enabled. (Bug 1105595)

Fixes introduced in the 6.15 iPrint Client

Available through the OES and iPrint Appliance Update channel and through the iPrint Appliance 2.1 Patch 7 download.

  • User printers installed using WSACL rules and shortname could not be removed (Bug 1089861)
  • iPrint Lite: Unsupported files information icon updated (Bug 1081341)
  • iPrint Lite is allowing to print unsupported files through windows context menu open with option. (Bug 1069221)
  • iPrint_lite: Clicking on iprint-lite icon on windows task bar does not minimize it. (Bug 1070780)
  • iPrint_lite: Hitting Enter key after entering server-ip does not click on “Find” button. (Bug 1070925)
  • iPrint Authentications fail with Novell Client installed (userPrincipalName) (Bug 1080884)
  • No error message when user prints to an SSL printer that he has no rights (Bug 1077610)
  • Printer driver download without iPrint provider using CLI. (Bug 116453)
  • iPrint client allowing to print the document even if the copies field is null. (Bug 1070716)

Fixes introduced in the 6.12 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Refresh iCM feature introduced (Bug 1057892)
  • Context menu printing crashes Windows Explorer with files with no extension (Bug 1063863)

Fixes introduced in the 6.11 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Minor cosmetic fixes.

Fixes introduced in the 6.10 iPrint Client

Available through the OES and iPrint Appliance Update channel or through iPrint Appliance 2.1 Patch 5

  • TID 7020136: OES Client nwtray crashes when you login through icon repetitively

Fixes introduced in the 6.09 iPrint Client

Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

  • iPrint Appliance 2.0 Hot Patch 4
  • iPrint Appliance 2.1 Hot Patch 4
  • Error messages flooding NPSMMON.LOG (Bug 1021421)
  • Print dialog within MS Office or Adobe Reader in perpetual error state or spins indefinitely. (Bug 1029529)
  • User Printer installation crashes print spooler if location or description is set. (Bug 1028999)

Fixes introduced in the 6.08 iPrint Client

Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

  • iPrint Appliance 2.0 Patch 4
  • iPrint Appliance 2.1 Patch 2
  • TID 7017101 – 0x00000002 error installing iPrint printers with the EFI Fiery driver (Bug 1019023)
  • TID 7017417 – Direct Printers looses parts of the printed document if bDirectPrintSpoolJobEnabled is enabled (Bug 1021882)
  • TID 7021962 – Hide Document Names for iPrint printer’s Windows Printer Queue
  • Printer driver DLLs are being over-written during iPrint printer installation. (Bug 990474)
  • iprntcmd based printer install and deletion enhanced for new User Printer implementation (Bug 103440)
  • iCM settings only read on log on. Provided message-box in case iCM not enabled. – Added few strings to the string table for User Printer. (Bug 104441)

Fixes introduced in the 6.07 iPrint Client

Available through the OES Update channel

  • Mac driver upload via iManager results in inproper driver name. (Bug 984480)
  • iCM fails to launch when logging in with OES Client. (Bug 1011189)
  • error 0x00000002 installing PS EFI Fiery driver (Bug 1019023)
  • Spooler crashes with Auto driver/profile update on Win 10 x86 (Bug 1020818)

Related:

  • No Related Posts

Untitled

Fixes introduced in the 6.21 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iPrint client asking for authentication, even when Remember Password is checked. (Bug 1172556)

Fixes introduced in the 6.20 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Spoolsv Handles increase when selecting iPrint printer, causing Windows performance problems (Bug )
  • TID 7024095 Windows Apps hang when non-reachable iPrint printer is default. (Bug 1148630)

Fixes introduced in the 6.18 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iCM fails with userPrincipalName (Bug 1113405)
  • iPrint Client hangs spooler listing printers (Bug 1109761)
  • Unable to upload HP Universal PCL 6 (v6.6.5) Driver (Bug 1112601)
  • Authentication fails with dot “.” in AD sAMAccountName (Bug 1126792)

Fixes introduced in the 6.16 FTF iPrint Client

No longer available for download, but the fixes listed here are rolled into future release (as are all fixes with every client version).

  • TID 7023395 6.16 iPrint Client with iPrint Direct printers hangs Windows Print Spooler

Fixes introduced in the 6.16 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • iPrintLite prompts for credentials with job submission, even after authentication has occurred. (Bug 1052239)
  • iPrintLite job submission status shows printed successfully with failed jobs. (Bug 1069912)
  • Printing from Edge browser fails. (Bug 1100744)
  • Secure Printing from Edge prompts for credentials, even after credentials already provided. (Bug 1103565)
  • Printer driver not updating with auto driver/profile update feature enabled. (Bug 1105595)

Fixes introduced in the 6.15 iPrint Client

Available through the OES and iPrint Appliance Update channel and through the iPrint Appliance 2.1 Patch 7 download.

  • User printers installed using WSACL rules and shortname could not be removed (Bug 1089861)
  • iPrint Lite: Unsupported files information icon updated (Bug 1081341)
  • iPrint Lite is allowing to print unsupported files through windows context menu open with option. (Bug 1069221)
  • iPrint_lite: Clicking on iprint-lite icon on windows task bar does not minimize it. (Bug 1070780)
  • iPrint_lite: Hitting Enter key after entering server-ip does not click on “Find” button. (Bug 1070925)
  • iPrint Authentications fail with Novell Client installed (userPrincipalName) (Bug 1080884)
  • No error message when user prints to an SSL printer that he has no rights (Bug 1077610)
  • Printer driver download without iPrint provider using CLI. (Bug 116453)
  • iPrint client allowing to print the document even if the copies field is null. (Bug 1070716)

Fixes introduced in the 6.12 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Refresh iCM feature introduced (Bug 1057892)
  • Context menu printing crashes Windows Explorer with files with no extension (Bug 1063863)

Fixes introduced in the 6.11 iPrint Client

Available through the OES and iPrint Appliance Update channel

  • Minor cosmetic fixes.

Fixes introduced in the 6.10 iPrint Client

Available through the OES and iPrint Appliance Update channel or through iPrint Appliance 2.1 Patch 5

  • TID 7020136: OES Client nwtray crashes when you login through icon repetitively

Fixes introduced in the 6.09 iPrint Client

Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

  • iPrint Appliance 2.0 Hot Patch 4
  • iPrint Appliance 2.1 Hot Patch 4
  • Error messages flooding NPSMMON.LOG (Bug 1021421)
  • Print dialog within MS Office or Adobe Reader in perpetual error state or spins indefinitely. (Bug 1029529)
  • User Printer installation crashes print spooler if location or description is set. (Bug 1028999)

Fixes introduced in the 6.08 iPrint Client

Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

  • iPrint Appliance 2.0 Patch 4
  • iPrint Appliance 2.1 Patch 2
  • TID 7017101 – 0x00000002 error installing iPrint printers with the EFI Fiery driver (Bug 1019023)
  • TID 7017417 – Direct Printers looses parts of the printed document if bDirectPrintSpoolJobEnabled is enabled (Bug 1021882)
  • TID 7021962 – Hide Document Names for iPrint printer’s Windows Printer Queue
  • Printer driver DLLs are being over-written during iPrint printer installation. (Bug 990474)
  • iprntcmd based printer install and deletion enhanced for new User Printer implementation (Bug 103440)
  • iCM settings only read on log on. Provided message-box in case iCM not enabled. – Added few strings to the string table for User Printer. (Bug 104441)

Fixes introduced in the 6.07 iPrint Client

Available through the OES Update channel

  • Mac driver upload via iManager results in inproper driver name. (Bug 984480)
  • iCM fails to launch when logging in with OES Client. (Bug 1011189)
  • error 0x00000002 installing PS EFI Fiery driver (Bug 1019023)
  • Spooler crashes with Auto driver/profile update on Win 10 x86 (Bug 1020818)

Related:

  • No Related Posts