Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1681 views

moving NDPS print services to new server

Someone want to check me on this theoretical plan? I've read TID
10016871.

Situation: I have an NW 6.5.4a system running both the Broker and NDPS
Manager supporting 140 printer agents. I have a new server (NW 6.5.5
with most post release patches) installed into the tree and want to move
all print services to the new server.

Plan:
1. unload the NDPS manager on the old server
2. unload the broker on old server
3. copy the NDPS folder to the new server
4. manually modify the HOST DEVICE and RESOURCE MANAGER DATABASE PATH
attributes of the broker in edir (found in Other tab of broker properties)
5. load broker on new machine
6. load print manager on new machine and follow prompts to move files to
the new location
7. verify broker and manager are only loading on new location

What concerns me is the potential for edir coruption if both old and new
servers don't have matching SP levels, ndps versions, and edir versions.
Anyone done the above steps with two servers so close in versions?

I'd considered using the consolidation utility, but that doesn't seem to
address my need to move the broker as well.

andrew
0 Likes
2 Replies
Absent Member.
Absent Member.

There is no risk in eDirectory corruption. The only possible problem you
might get with different NDPS/iPrint versions is problems with the NDPS
Manager database which may change from version to version. However an
upgrade in version is not a problem either. This just amounts to the same
as if you upgrade your source server to SP5.

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

The consolidation tool works nice for moving the PAs from one manager to
the other. However, I've run into a couple issues that I haven't been
able to resolve without doing some manual work on the printer agents.

When the PA is assigned to the new manager, the PA is still referencing
the old broker. There are switches to add to the NDPSM load statement
that will force your PAs to use a different broker, or you can
manipulate them with your favorite too. I considered generating a large
LDIF file to do this, until I found the command line switches.

The other problem is when you point at the new broker, the PA still
tries to reference the driver path which existed on your old server, but
may not exist on the new one. I haven't really figured out if this can
be fixed or not. Since I had a small number of PAs, I just went in and
unassigned printer drivers (set to none), save, then reassign the
driver. The errors I saw on the broker were about the RMS could not
open the data file
PRINTVOL:/ndps/resdir/ENGLISH/prndrv/win2000/XXXXXXXX/ARCHIVES/NDPSDRVR.ZIP.
Error code 1. Make sure the file exists, is not protected and has not
been corrupted, then try the task again.

XXXXXXXX is some random Hex string that the broker generated on your old
system when you uploaded the printer drivers. Again, because this is
all generated by the broker when the drivers are uploaded, I don't know
if you can successfully move the resdir from one system to another and
have it work. I moved from a stand alone system to a cluster, so my
volume name is a shared cluster resource. Your's should reference SYS:.

I'd be curious to know if Novell knows of a way to move the resdir so
that this type of problem can be avoided. I haven't dug too far on
this, so I'm sure others may have solved this problem. There is only so
much time in a day. 🙂

-Tim


awilkinson@bemidjistate.edu wrote:
> Someone want to check me on this theoretical plan? I've read TID
> 10016871.
>
> Situation: I have an NW 6.5.4a system running both the Broker and NDPS
> Manager supporting 140 printer agents. I have a new server (NW 6.5.5
> with most post release patches) installed into the tree and want to move
> all print services to the new server.
>
> Plan:
> 1. unload the NDPS manager on the old server
> 2. unload the broker on old server
> 3. copy the NDPS folder to the new server
> 4. manually modify the HOST DEVICE and RESOURCE MANAGER DATABASE PATH
> attributes of the broker in edir (found in Other tab of broker properties)
> 5. load broker on new machine
> 6. load print manager on new machine and follow prompts to move files to
> the new location
> 7. verify broker and manager are only loading on new location
>
> What concerns me is the potential for edir coruption if both old and new
> servers don't have matching SP levels, ndps versions, and edir versions.
> Anyone done the above steps with two servers so close in versions?
>
> I'd considered using the consolidation utility, but that doesn't seem to
> address my need to move the broker as well.
>
> andrew

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.