this is what I was looking for. Thanks for including the spooler resource
names. One why to get this to work is create the name without spool, then
change it to the name with spool after the printers have been restored.
http://blogs.technet.com/askperf/arc...s-retired.aspx
Here's five other reasons that Print Migrator 3.1 is not as robust of a
migration solution as it once was:
1.. PrintMig was created before OEM printer manufacturers starting
shipping printer drivers containing .cab files. As a result, PrintMig 3.1
cannot restore printer drivers that have .cab files in them
2.. PrintMig was created prior to Windows Server 2003 SP1 and SP2. For
clustered printing scenarios, the folder structure for the location of Print
Processors changed, and thus PrintMig is unaware of these new locations
3.. PrintMig only recognizes local or NetBIOS path names to separator
pages (.sep files). If you use a fully qualified name (FQDN) for the
location of .sep files it will cause PrintMig to crash with an access
violation
4.. PrintMig cannot restore servers that include the word "Spool" in their
network name, for example Spooler1 or PrintSpool
5.. PrintMig does not work with 64-bit (x64 or IA64) print servers because
x 64 servers were not widely deployed when PrintMig 3.1 was released
So, with PrintMig out of the picture, how should you migrate printers? In
Windows Vista and Windows Server 2008, the Print Migration Wizard within the
new Print Management Console is one option. Alternatively you could also
use the PRINTBRM.EXE command line tool (which effectively replaces PrintMig
3.1). I'll be going over some of the benefits of both of these tools in
future posts, so stay tuned!
Additional Resources:
a.. Microsoft KB 938923: How to back up & restore printers when upgrading
from Windows Server 2003 to Windows Server 2008
b.. Technet: Migrating Print Servers
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no rights.
"Belas" <> wrote in message
news:CDF54265-20BA-48DC-801C-...
>I will try to explain better.
>
> I have one cluster with two nodes: N1 and N2, the cluster name is CLUOC
> and
> the printer spool resource name is CLUSPOOL with 223 printers.
>
> On the other side, I have one cluster with two nodes: N7 and N8, the
> cluster
> name is CLUMD (different to the other), and the printer spool resource
> name
> is SPOOLOC (different to the other).
>
> I use printmig (version 3.1), when I make the bakcup in target I write the
> name os printer spool resource name (CLUSPOOL) and the backup is OK.
>
> I copy this file (*.cab) to N7 and locally launch resore option, writing
> in
> target the name of the node: N7, but it fails. If I put in target the
> name
> of the cluster (CLUMD), also fails, and if I write the name of the printer
> spool resource (CLUSPOOL) also fails.
>
> Then .........
>
> "Alan Morris [MSFT]" wrote:
>
>> Such that both spooler resources are hosted by the same node.
>>
>> If any of the drivers include cab files, printmig will not backup these
>> drivers. Printmig will also not properly backup any x64 print drivers.
>>
>> If you have Vista SP1 around use the printbrmui.exe tool to remotely
>> backup
>> the printer data for each spooler resource.
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Belas" <> wrote in message
>> news:87346066-D817-440B-9A54-...
>> > No, I only have one cluster with two nodes. But how can I do a failover
>> > to
>> > all printers were in node 1??? I don't know how, please, light me!!!
>> >
>> > "Robert Smit" wrote:
>> >
>> >> Belas,
>> >>
>> >> A quick recap here.
>> >>
>> >> you have two clusters 1 and 2 both on two nodes. And you want to
>> >> migrate
>> >> both to a new cluster (3)
>> >> So do a failover from cluster 1 to node 1 so all printer will be on
>> >> node
>> >> 1
>> >> <> export the printers.
>> >> and import it to cluster 3 <> node 1 import.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "Belas" <> schreef in bericht
>> >> news:2E681F04-999D-482C-BCB5-...
>> >> > But, how can I move all printers to one node?? I'd have to use
>> >> > printmig
>> >> > and
>> >> > I'd have the same problem
>> >> >
>> >> > "Robert Smit" wrote:
>> >> >
>> >> >> Hi Belas,
>> >> >>
>> >> >> Did you try to move all printers to one cluster node server and do
>> >> >> the
>> >> >> export based on this node.
>> >> >> Than reimport it to the other site.
>> >> >>
>> >> >> be aware that migrations from x32 to x64 goes wrong and will not
>> >> >> work.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Greetings,
>> >> >>
>> >> >> Robert Smit
>> >> >> Blog : http://fiberman.spaces.live.com/
>> >> >>
>> >> >>
>> >> >> "Belas" <> schreef in bericht
>> >> >> news:517186FC-7F52-4D7C-9137-...
>> >> >> > Hi,
>> >> >> > I'm trying to move a printer spool from a cluster resource to a
>> >> >> > cluster
>> >> >> > resource (in differents servers) using PrintMig. I make a backup
>> >> >> > from
>> >> >> > \\cluspool where I've got 223 printers, when I want to restore it
>> >> >> > on
>> >> >> > one
>> >> >> > of
>> >> >> > the nodes in a new cluster I receive an error: FAILURE: Can't
>> >> >> > restore
>> >> >> > to
>> >> >> > HKLM\Software\Microsoft\Printmig
>> >> >> >
>> >> >> > I'm reading something about this and is possible that the problem
>> >> >> > was
>> >> >> > in
>> >> >> > the
>> >> >> > cab because the path of the backup is a cluster resource not
>> >> >> > C:\windows\system32\..... but what can I do to solve it??? How
>> >> >> > can I
>> >> >> > chage
>> >> >> > the path???
>> >> >> >
>> >> >> > Thank you
>> >> >>
>> >> >> --
>> >> >> Greetings,
>> >> >>
>> >> >> Robert Smit
>> >> >> Blog : http://fiberman.spaces.live.com/
>> >> >>
>> >>
>> >> --
>> >> Greetings,
>> >>
>> >> Robert Smit
>> >> Blog : http://fiberman.spaces.live.com/
>> >>
>> >>
>>
>>
>>