yes, this document still applies. you can not chnage the ip address on a running appliance. 

Thank-you, I will try this. Here is what I did:
- Migrated a copy of my current appliance to HyperV

- Followed the upgrade instructions to go from the iprint 4.XX Appliance to a iprnt 23.4 appliance (File up new applaince add secondary production data drive to the new 23.4 appliance)

- Upgrade went smooth
- Now I have fired up a new iprnt 23.4 appliance, and I will follow these instructions, to see if I can change the IP, for the system...Hopefully all goes well.

Okay I tried this and there is something I REALY do not like about this method, I was hoping is:
- Carried over all user and group sync'd objects from the old appliance (It did not)
- As a result, ALL of my User and Group Printer Associations and rights are NOT intact (That's a HUGE JOB)
- As a result of the above, None of the rights for the printers to groups are mapped or associated either....

Does anyone have an answer to this, this is a huge job added for this migration (Where as a migration on the same IP address keeps all of that), as well it would be an even larger job for a larger association suite my print objects are there, but really my Directors user's and the mapping of those users and the groups, should and need to be their as well, this method does NOT address that....

It means I have to populate the printers that are AUTO distributed to those groups for EVERY group, as well it means I have to go to EVERY printer and re-add the groups that have rights to them. So two VERY large jobs.

I am also getting this error, after the sync, all the users are there as they should be, I am only getting this from the Dynamic tab.

Would this solve the issue for the error above?
support.microfocus.com/.../doc.php

Everything else from an LDAP perspective for edir and its objects seems to work, only the Dynamic tab seems to produce this....

Just a little better of a decription, as you can see ALL LDAP objects have synced, Only the dynamic tab produces that:

the simple bind failed only on the dynamic tab for the new address, that is the "New" IP address

yes, you're correct, this method will not migrate the data.
There is still a way to do it.

Once your users and group are already present on the new appliance, take the /var/opt/novell/iprint/print_manager.iPrintAppliance.psm/padbtxt.xml file from your older one. Open the file and change the first entries, hostname and tree, to match the new settings from the new appliance:

<iprintpsm>
<manager>
<hostname>iprint.heaven.com</hostname>
<tree>APPLIANCE_1724933631</tree>

Save the file as padbtxt-mod.xml

Then take a snapshot of the new appliance and follow Option 2 from this document to import the padbtxt-mod.xml into the new appliance:

https://support.microfocus.com/kb/doc.php?id=3006957

On step:

• For OES 2018, run the following:

killall -9 ipsmd;sed -i -e 's/client_delete_not_found_printers=true/client_delete_not_found_printers=false/g' /etc/opt/novell/iprint/conf/iprintconf.properties;/opt/novell/iprint/bin/ipsmd -x /tmp/padbtxt.xml;systemctl start novell-ipsmd.service

the /tmp/padbtxt.xml should be the padbtxt-mod.xml file

This will import all printers configuration with the user/groups assigned to them

Regarding the ldap error, iManager is not involved in this process, you should not do anything in iManager regarding ldap. all is done in the appliance web console, port 9443, on the  identity source tab. There is where you configure the ldap import/sync and you can use /var/opt/novell//log/iprintauth/iprint-auth.log to verify that all went fine

You should not chnage the ldap server in imanager to point ot the external ldap server. This setting in iManager is for the appliance ldap and it should not be changed nor it is not necessary.

Great, I DID NOT change any LDAP settings in iManager, and just specified my Sync server from the Identity Sources tab like I used to, so I'll assume EVEYTHING is fine :)  Just wanted to make sure. As well, I know what you mean about LDAP and imanager. Years ago I had a tech who MANUALLY changed some users in an LDAP group, instead of letting the Sync do it from the Identity Sources from AD....That BROKE the sync :)  

Thank-you for the configuration tip!!!!  Will the padbtxt-mod.xml populate the printers that roll out automatically per group IE This tab:

As well will it populate the rights each group or user has to the printer here again?

"As well will it populate the rights each group or user has to the printer here again?"

# yes

"Will the padbtxt-mod.xml populate the printers that roll out automatically per group IE This tab:"

# no.

this info is stored in edir. the only way to get this info from old appliance is doing a "proper" migration using iprintconfig.zip, but in this case, the new appliance needs to use the same ip and same hostname, what it is not your case.