Anonymous_User Absent Member.
Absent Member.
5065 views

move iprint service to new server.

Hi,

I have 150 printers which use iprint as a service. Now, i have plan to
move those printers to run in a new server. But i'm confused that the old
server should or shouldn't have the same name as the new server. But i wish
to use the same name. So what can i do? which tool?

Thank you very much

Thip


Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: move iprint service to new server.

What platform is this? NetWare or Linux?

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: move iprint service to new server.

Netware Platform.

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:OBLzh.687$DN1.189@prv-forum2.provo.novell.com...
> What platform is this? NetWare or Linux?
>
> --
> Marcel Cox (using XanaNews 1.18.1.6)



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: move iprint service to new server.

Are you using it with iPrint or with NDPS clients?

There are different move possibilities:

The "classic" move is to unlaod the Manager from the old server and load
it on the new server using the same NDS object. It will then ask you
whether you want to transfer the database to the new server, and if you
say yes, the manager with all printers will be moved. This works very well
for NDPS clients, but for iPrint clients, there is a problem in that
workstations only know the printer by URL and not by NDS object name. In
that case, you have to make sure that before the move, you make make the
NDPS Manager use a special DNS name for printing so that this special name
will be used in the URLs. Then after moving, you change the DNS entry to
point to the new server and so printers will automatically be pointed to
the new server.

If your system is relatively up to date (I don't know at what point this
was introduced), there is another possibility where you can take advantage
of iPrint redirection. In this case, you create a new empty Manager on the
new server, and form iManager, you select the old server and there in the
pritner list, you have the option to move printers to the new manager. If
you use this feature, the old manager will "remember" where the printers
have been moved to and for each client trying to connect the printer on
the old server, it will be redirected to the new server. The NDPS Manager
will of course have to continue to run on the old server until all
workstations have updated their URLs.

For the broker, in any of the 2 scenarios, the easiest is probably to
simply copy the resdir subdirectory below the NDPS directory to the new
server and create a broker on the new server pointing to that directory.
That will ensure you retain exactly the same drivers. Then, to make sure
your printers use the new broker, use the setens and setrms options when
loading the Manager like described here:

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&sliceId=&externalId=10067688

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: move iprint service to new server.

That's very kind for your answer. Thank you so much.

Thip

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:OO2Ah.195$Vr2.79@prv-forum2.provo.novell.com...
> Are you using it with iPrint or with NDPS clients?
>
> There are different move possibilities:
>
> The "classic" move is to unlaod the Manager from the old server and load
> it on the new server using the same NDS object. It will then ask you
> whether you want to transfer the database to the new server, and if you
> say yes, the manager with all printers will be moved. This works very well
> for NDPS clients, but for iPrint clients, there is a problem in that
> workstations only know the printer by URL and not by NDS object name. In
> that case, you have to make sure that before the move, you make make the
> NDPS Manager use a special DNS name for printing so that this special name
> will be used in the URLs. Then after moving, you change the DNS entry to
> point to the new server and so printers will automatically be pointed to
> the new server.
>
> If your system is relatively up to date (I don't know at what point this
> was introduced), there is another possibility where you can take advantage
> of iPrint redirection. In this case, you create a new empty Manager on the
> new server, and form iManager, you select the old server and there in the
> pritner list, you have the option to move printers to the new manager. If
> you use this feature, the old manager will "remember" where the printers
> have been moved to and for each client trying to connect the printer on
> the old server, it will be redirected to the new server. The NDPS Manager
> will of course have to continue to run on the old server until all
> workstations have updated their URLs.
>
> For the broker, in any of the 2 scenarios, the easiest is probably to
> simply copy the resdir subdirectory below the NDPS directory to the new
> server and create a broker on the new server pointing to that directory.
> That will ensure you retain exactly the same drivers. Then, to make sure
> your printers use the new broker, use the setens and setrms options when
> loading the Manager like described here:
>
> http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&sliceId=&externalId=10067688
>
> --
> Marcel Cox (using XanaNews 1.18.1.6)



0 Likes
aferreira Absent Member.
Absent Member.

Re: move iprint service to new server.

Marcel Cox;517802 wrote:
Are you using it with iPrint or with NDPS clients?

There are different move possibilities:

The "classic" move is to unlaod the Manager from the old server and load
it on the new server using the same NDS object. It will then ask you
whether you want to transfer the database to the new server, and if you
say yes, the manager with all printers will be moved. This works very well
for NDPS clients, but for iPrint clients, there is a problem in that
workstations only know the printer by URL and not by NDS object name. In
that case, you have to make sure that before the move, you make make the
NDPS Manager use a special DNS name for printing so that this special name
will be used in the URLs. Then after moving, you change the DNS entry to
point to the new server and so printers will automatically be pointed to
the new server.

If your system is relatively up to date (I don't know at what point this
was introduced), there is another possibility where you can take advantage
of iPrint redirection. In this case, you create a new empty Manager on the
new server, and form iManager, you select the old server and there in the
pritner list, you have the option to move printers to the new manager. If
you use this feature, the old manager will "remember" where the printers
have been moved to and for each client trying to connect the printer on
the old server, it will be redirected to the new server. The NDPS Manager
will of course have to continue to run on the old server until all
workstations have updated their URLs.

For the broker, in any of the 2 scenarios, the easiest is probably to
simply copy the resdir subdirectory below the NDPS directory to the new
server and create a broker on the new server pointing to that directory.
That will ensure you retain exactly the same drivers. Then, to make sure
your printers use the new broker, use the setens and setrms options when
loading the Manager like described here:

10067688: Setting the RMS and ENS for NDPS Manager

--
Marcel Cox (using XanaNews 1.18.1.6)


I am attempting to execute the same task of moving iPrint services to another server without breaking the configured iprint printers on user workstations. I am not seeing the option you mention, can you explain how to perform:

"You have to make sure that before the move, you make make the
NDPS Manager use a special DNS name for printing so that this special name
will be used in the URLs."

Thanks

A
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.