Anonymous_User Absent Member.
Absent Member.
1059 views

Migration questions

Hi,

We are currently running NW6.5 SP8 and NDPS (on NSS volumes) and I have some
options to migrate to OES2 which is largely driven by a desktop move to
Windows7
We are planning to fully migrate all our sites and servers to OES over the
next 12 months or so, however the windows7 migration is likely to be pushed
through a lot sooner.
So, having read and tried to understand the various docs on migrations - I
have two options it seems.....
1.Upgrade current NDPS to iprint (not sure how much change this will incur,
if any) and then do a migration to OES later on after the Windows7 roll out.
2. Hurry the OES migration along ahead of the Windows7 rollout. This however
will mean huge changes as we are also looking at going virtual as well as
new hardware etc so I would realy like a lot more time to research this
approach.

So I guess my questions are:
Which is easier - upgrade current NDPS to iprint and then later migrate to
OES, or migrate to OES straight off?
Bearing in mind that all we really want right now is for Windows7 printing
to work.....

I am also a bit confused.. when I did all my server migrations earlier this
year to new hardware and SP8 I had to install iprint (NDPS, as part of the
migration using the gui) afterwards to get the printing working again, does
this mean that I now have all the main ingredients for iprint on our servers
or is there still more I need to do?

Thanks for your help - Mark



0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Migration questions

Next question....

Is it a "big bang" change i.e NDPS server & client to iprint, or can
old/new server/client co-exist?

Can we roll out the iprint client and connect to the existing NDPS printing
environment or will it be a case of upgrade NDPS to iprint on the server
tonight and tomorrow all the users get the new iprint client as well?

We have many services with imbedded printing currently via NDPS as well as
applications like Citrix, SAP, SQL, Virtual services etc. and if the whole
change could be "staged" it would save a lot of pain....

Mark


0 Likes
Knowledge Partner
Knowledge Partner

Re: Migration questions

Mark Venter;1997842 wrote:
...So I guess my questions are:
Which is easier - upgrade current NDPS to iprint and then later migrate to
OES, or migrate to OES straight off?
Bearing in mind that all we really want right now is for Windows7 printing
to work.....


Your Netware servers should be able to handle iPrint just fine (as NDPS and iPrint are available simultaneously on the same print manager).
Quick check: open a browser and point to : http://<ip ndps server>/ipp.

If Apache is running, you'll see the printers that have been set as iPrint enabled. This is an option you can set/unset using iManager's iPrint module.

As for the Windows 7 Print environment. Instead of getting it to work on the existing Netware base (and have to again migrate later)... You can also setup a new OES2 SP2 server -virtual or not, your choice- that will specifically do iManager & iPrint.
Create the needed printers on that one and have the Windows 7 workstations use it instead of the existing iPrint setup. That way you are using the latest and greatest versions and only have to set this up once. You can add other roles/tasks/services later on if needed/desired. It's good practice to manage iPrint on OES2 using an iManager version running on OES2 (to ensure you are using the correct iPrint modules that handle OES2).

-Willem
0 Likes
Knowledge Partner
Knowledge Partner

Re: Migration questions

Mark Venter;1998333 wrote:
Next question....

Is it a "big bang" change i.e NDPS server & client to iprint, or can
old/new server/client co-exist?

Can we roll out the iprint client and connect to the existing NDPS printing
environment or will it be a case of upgrade NDPS to iprint on the server
tonight and tomorrow all the users get the new iprint client as well?

We have many services with imbedded printing currently via NDPS as well as
applications like Citrix, SAP, SQL, Virtual services etc. and if the whole
change could be "staged" it would save a lot of pain....

Mark

This scenario does warrant setting up a new iPrint OES2 server... gives you the chance to setup/test/iron out the new environment without causing havoc in the existing one.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration questions

Thank you for a concise and clear reply Willem.
This makes sense and I think I understand it now.
The ipp page does come up on the servers but obviously there are currently
no ip enabled printers so none show up. I will enable a test one to
familiarize myself.
Unfortunately we have many sites around the country and overseas so a single
local NDPS server is not very practical, nor a separate additional server at
each site at this stage so I will just have to enable iprinting (printers)
on each server for the W7 roll out.
I will need to migrate again later on anyway as the intention is to replace
our existing remote servers with OES running in virtual environment but that
is at least 12 months of R&D away.

Mark



"magic31" <magic31@no-mx.forums.novell.com> wrote in message
news:magic31.4e6uhz@no-mx.forums.novell.com...
>
> Mark Venter;1997842 Wrote:
>> ...So I guess my questions are:
>> Which is easier - upgrade current NDPS to iprint and then later migrate
>> to
>> OES, or migrate to OES straight off?
>> Bearing in mind that all we really want right now is for Windows7
>> printing
>> to work.....

>
> Your Netware servers should be able to handle iPrint just fine (as NDPS
> and iPrint are available simultaneously on the same print manager).
> Quick check: open a browser and point to : http://<ip ndps
> server>/ipp.
>
> If Apache is running, you'll see the printers that have been set as
> iPrint enabled. This is an option you can set/unset using iManager's
> iPrint module.
>
> As for the Windows 7 Print environment. Instead of getting it to work
> on the existing Netware base (and have to again migrate later)... You
> can also setup a new OES2 SP2 server -virtual or not, your choice- that
> will specifically do iManager & iPrint.
> Create the needed printers on that one and have the Windows 7
> workstations use it instead of the existing iPrint setup. That way you
> are using the latest and greatest versions and only have to set this up
> once. You can add other roles/tasks/services later on if needed/desired.
> It's good practice to manage iPrint on OES2 using an iManager version
> running on OES2 (to ensure you are using the correct iPrint modules that
> handle OES2).
>
> -Willem
>
>
> --
> Novell Knowledge Partner (voluntary sysop)
>
> It ain't anything like Harry Potter.. but you gotta love the magic IT
> can bring to this world.
> ------------------------------------------------------------------------
> magic31's Profile: http://forums.novell.com/member.php?userid=2303
> View this thread: http://forums.novell.com/showthread.php?t=415490
>



0 Likes
Knowledge Partner
Knowledge Partner

Re: Migration questions

Mark Venter;2000130 wrote:
...
Unfortunately we have many sites around the country and overseas so a single local NDPS server is not very practical, nor a separate additional server at each site at this stage so I will just have to enable iprinting (printers) on each server for the W7 roll out.
I will need to migrate again later on anyway as the intention is to replace
our existing remote servers with OES running in virtual environment but that
is at least 12 months of R&D away.

Ah.. A little bigger in scale than I had in mind :)~

In that case, using Netware 6.5 servers is fine. Do make sure they are running the latest NPDS code and patches as also the clients are using the latest iPrint (5.40) clients.

This is important to get it working normally on Windows 7.

Cheers,
Willem
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.