Print Migrator

August 6, 2008

Is there any support for this? I am trying to use version 3.1, and it is

failing, I suspect it is because the cab file gets to large (I have over 300

printers). I know because after the cab is created, I can't mauanlly extract

some files, while I can others. Not sure where to bring this up, in case

there is a fix, or a feature for 3.2

Since it is not working, does anyone know how to backup or migrate printers?

manually??

August 7, 2008

Re: Print Migrator

Hello blankmonkey,

We use it in the past without problems. What error did you get?

http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Is there any support for this? I am trying to use version 3.1, and it

> is failing, I suspect it is because the cab file gets to large (I have

> over 300 printers). I know because after the cab is created, I can't

> mauanlly extract some files, while I can others. Not sure where to

> bring this up, in case there is a fix, or a feature for 3.2

>

> Since it is not working, does anyone know how to backup or migrate

> printers?

> manually??

August 7, 2008

Re: Print Migrator

If runs in an infinite loop. Specifically, I get this in the logs(see below).

When I try to open the cabinet file manually, some files are ok, and others

are either blank (10mb of returns) or the extract asks for the location of

the next cabinet, and never stops asking, unless you cancel, then it extracts

just the one file, and it is bad.

Personally, I think it is a limitation of the printmig program, as there are

300+ printers, and over 500 ports being migrated, the cabinet ends up bing

almost a gig in size.

I did get the printers migrated, I did this;

Ntbackup spool dir

Export hklm\system\currentcontrolset\control\print

Export hklm\software\Microsoft\windows nt\current version\Ports

Restore and import.

But when I was adding a printer later with an existing driver, it said the

print processor was not responding, I replaced the driver with a new one and

it worked, but I am suspicious that all is not well.

((((((((((((())))))))))))))))))

fdintNEXT_CABINET

name of next cabinet where file continued =

name of next disk where file continued =

cabinet path name =

fdintNEXT_CABINET

name of next cabinet where file continued =

name of next disk where file continued =

cabinet path name =

fdintNEXT_CABINET

name of next cabinet where file continued =

name of next disk where file continued =

cabinet path name =

Continued for thousands more lines...

"Meinolf Weber" wrote:

> Hello blankmonkey,

>

> We use it in the past without problems. What error did you get?

> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > Is there any support for this? I am trying to use version 3.1, and it

> > is failing, I suspect it is because the cab file gets to large (I have

> > over 300 printers). I know because after the cab is created, I can't

> > mauanlly extract some files, while I can others. Not sure where to

> > bring this up, in case there is a fix, or a feature for 3.2

> >

> > Since it is not working, does anyone know how to backup or migrate

> > printers?

> > manually??

>

August 7, 2008

Re: Print Migrator

the replacement for printmig is printbrm which ships in Vista +

--

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.

"blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

>

> If runs in an infinite loop. Specifically, I get this in the logs(see

> below).

> When I try to open the cabinet file manually, some files are ok, and

> others

> are either blank (10mb of returns) or the extract asks for the location of

> the next cabinet, and never stops asking, unless you cancel, then it

> extracts

> just the one file, and it is bad.

>

> Personally, I think it is a limitation of the printmig program, as there

> are

> 300+ printers, and over 500 ports being migrated, the cabinet ends up bing

> almost a gig in size.

>

> I did get the printers migrated, I did this;

> Ntbackup spool dir

> Export hklm\system\currentcontrolset\control\print

> Export hklm\software\Microsoft\windows nt\current version\Ports

> Restore and import.

>

> But when I was adding a printer later with an existing driver, it said the

> print processor was not responding, I replaced the driver with a new one

> and

> it worked, but I am suspicious that all is not well.

>

> ((((((((((((())))))))))))))))))

> fdintNEXT_CABINET

> name of next cabinet where file continued =

> name of next disk where file continued =

> cabinet path name =

> fdintNEXT_CABINET

> name of next cabinet where file continued =

> name of next disk where file continued =

> cabinet path name =

> fdintNEXT_CABINET

> name of next cabinet where file continued =

> name of next disk where file continued =

> cabinet path name =

> Continued for thousands more lines...

>

> "Meinolf Weber" wrote:

>

>> Hello blankmonkey,

>>

>> We use it in the past without problems. What error did you get?

>> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>

>> > Is there any support for this? I am trying to use version 3.1, and it

>> > is failing, I suspect it is because the cab file gets to large (I have

>> > over 300 printers). I know because after the cab is created, I can't

>> > mauanlly extract some files, while I can others. Not sure where to

>> > bring this up, in case there is a fix, or a feature for 3.2

>> >

>> > Since it is not working, does anyone know how to backup or migrate

>> > printers?

>> > manually??

>>

August 7, 2008

Re: Print Migrator

Will printbrm work on windows 2003? Do i need to copy over any dll files

with it to make it work?

Can I run it against a 2003 server from a vista machine and have it work?

"Alan Morris [MSFT]" wrote:

> the replacement for printmig is printbrm which ships in Vista +

>

> --

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

>

> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

> >

> > If runs in an infinite loop. Specifically, I get this in the logs(see

> > below).

> > When I try to open the cabinet file manually, some files are ok, and

> > others

> > are either blank (10mb of returns) or the extract asks for the location of

> > the next cabinet, and never stops asking, unless you cancel, then it

> > extracts

> > just the one file, and it is bad.

> >

> > Personally, I think it is a limitation of the printmig program, as there

> > are

> > 300+ printers, and over 500 ports being migrated, the cabinet ends up bing

> > almost a gig in size.

> >

> > I did get the printers migrated, I did this;

> > Ntbackup spool dir

> > Export hklm\system\currentcontrolset\control\print

> > Export hklm\software\Microsoft\windows nt\current version\Ports

> > Restore and import.

> >

> > But when I was adding a printer later with an existing driver, it said the

> > print processor was not responding, I replaced the driver with a new one

> > and

> > it worked, but I am suspicious that all is not well.

> >

> > ((((((((((((())))))))))))))))))

> > fdintNEXT_CABINET

> > name of next cabinet where file continued =

> > name of next disk where file continued =

> > cabinet path name =

> > fdintNEXT_CABINET

> > name of next cabinet where file continued =

> > name of next disk where file continued =

> > cabinet path name =

> > fdintNEXT_CABINET

> > name of next cabinet where file continued =

> > name of next disk where file continued =

> > cabinet path name =

> > Continued for thousands more lines...

> >

> > "Meinolf Weber" wrote:

> >

> >> Hello blankmonkey,

> >>

> >> We use it in the past without problems. What error did you get?

> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>

> >> > Is there any support for this? I am trying to use version 3.1, and it

> >> > is failing, I suspect it is because the cab file gets to large (I have

> >> > over 300 printers). I know because after the cab is created, I can't

> >> > mauanlly extract some files, while I can others. Not sure where to

> >> > bring this up, in case there is a fix, or a feature for 3.2

> >> >

> >> > Since it is not working, does anyone know how to backup or migrate

> >> > printers?

> >> > manually??

> >>

>

August 8, 2008

Re: Print Migrator

yes remote. run the tool and target the Server 2003 machine

--

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.

"blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

news:35DE47F7-E942-48EA-9693-75B6401B51FA@microsoft.com...

> Will printbrm work on windows 2003? Do i need to copy over any dll files

> with it to make it work?

>

> Can I run it against a 2003 server from a vista machine and have it work?

>

> "Alan Morris [MSFT]" wrote:

>

>> the replacement for printmig is printbrm which ships in Vista +

>>

>> --

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

>>

>> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

>> news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

>> >

>> > If runs in an infinite loop. Specifically, I get this in the logs(see

>> > below).

>> > When I try to open the cabinet file manually, some files are ok, and

>> > others

>> > are either blank (10mb of returns) or the extract asks for the location

>> > of

>> > the next cabinet, and never stops asking, unless you cancel, then it

>> > extracts

>> > just the one file, and it is bad.

>> >

>> > Personally, I think it is a limitation of the printmig program, as

>> > there

>> > are

>> > 300+ printers, and over 500 ports being migrated, the cabinet ends up

>> > bing

>> > almost a gig in size.

>> >

>> > I did get the printers migrated, I did this;

>> > Ntbackup spool dir

>> > Export hklm\system\currentcontrolset\control\print

>> > Export hklm\software\Microsoft\windows nt\current version\Ports

>> > Restore and import.

>> >

>> > But when I was adding a printer later with an existing driver, it said

>> > the

>> > print processor was not responding, I replaced the driver with a new

>> > one

>> > and

>> > it worked, but I am suspicious that all is not well.

>> >

>> > ((((((((((((())))))))))))))))))

>> > fdintNEXT_CABINET

>> > name of next cabinet where file continued =

>> > name of next disk where file continued =

>> > cabinet path name =

>> > fdintNEXT_CABINET

>> > name of next cabinet where file continued =

>> > name of next disk where file continued =

>> > cabinet path name =

>> > fdintNEXT_CABINET

>> > name of next cabinet where file continued =

>> > name of next disk where file continued =

>> > cabinet path name =

>> > Continued for thousands more lines...

>> >

>> > "Meinolf Weber" wrote:

>> >

>> >> Hello blankmonkey,

>> >>

>> >> We use it in the past without problems. What error did you get?

>> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

>> >>

>> >> Best regards

>> >>

>> >> Meinolf Weber

>> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> >> confers

>> >> no rights.

>> >> ** Please do NOT email, only reply to Newsgroups

>> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>> >>

>> >> > Is there any support for this? I am trying to use version 3.1, and

>> >> > it

>> >> > is failing, I suspect it is because the cab file gets to large (I

>> >> > have

>> >> > over 300 printers). I know because after the cab is created, I

>> >> > can't

>> >> > mauanlly extract some files, while I can others. Not sure where to

>> >> > bring this up, in case there is a fix, or a feature for 3.2

>> >> >

>> >> > Since it is not working, does anyone know how to backup or migrate

>> >> > printers?

>> >> > manually??

>> >>

>>

August 8, 2008

Re: Print Migrator

:( I do not have a Vista workstation. I do have 2k3 R2, will the printbrm

util work from there if I can get it?

is there a way I can import the printbrm util into 2k3?

"Alan Morris [MSFT]" wrote:

> yes remote. run the tool and target the Server 2003 machine

>

> --

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

>

> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> news:35DE47F7-E942-48EA-9693-75B6401B51FA@microsoft.com...

> > Will printbrm work on windows 2003? Do i need to copy over any dll files

> > with it to make it work?

> >

> > Can I run it against a 2003 server from a vista machine and have it work?

> >

> > "Alan Morris [MSFT]" wrote:

> >

> >> the replacement for printmig is printbrm which ships in Vista +

> >>

> >> --

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

> >>

> >> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> >> news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

> >> >

> >> > If runs in an infinite loop. Specifically, I get this in the logs(see

> >> > below).

> >> > When I try to open the cabinet file manually, some files are ok, and

> >> > others

> >> > are either blank (10mb of returns) or the extract asks for the location

> >> > of

> >> > the next cabinet, and never stops asking, unless you cancel, then it

> >> > extracts

> >> > just the one file, and it is bad.

> >> >

> >> > Personally, I think it is a limitation of the printmig program, as

> >> > there

> >> > are

> >> > 300+ printers, and over 500 ports being migrated, the cabinet ends up

> >> > bing

> >> > almost a gig in size.

> >> >

> >> > I did get the printers migrated, I did this;

> >> > Ntbackup spool dir

> >> > Export hklm\system\currentcontrolset\control\print

> >> > Export hklm\software\Microsoft\windows nt\current version\Ports

> >> > Restore and import.

> >> >

> >> > But when I was adding a printer later with an existing driver, it said

> >> > the

> >> > print processor was not responding, I replaced the driver with a new

> >> > one

> >> > and

> >> > it worked, but I am suspicious that all is not well.

> >> >

> >> > ((((((((((((())))))))))))))))))

> >> > fdintNEXT_CABINET

> >> > name of next cabinet where file continued =

> >> > name of next disk where file continued =

> >> > cabinet path name =

> >> > fdintNEXT_CABINET

> >> > name of next cabinet where file continued =

> >> > name of next disk where file continued =

> >> > cabinet path name =

> >> > fdintNEXT_CABINET

> >> > name of next cabinet where file continued =

> >> > name of next disk where file continued =

> >> > cabinet path name =

> >> > Continued for thousands more lines...

> >> >

> >> > "Meinolf Weber" wrote:

> >> >

> >> >> Hello blankmonkey,

> >> >>

> >> >> We use it in the past without problems. What error did you get?

> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

> >> >>

> >> >> Best regards

> >> >>

> >> >> Meinolf Weber

> >> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> >> confers

> >> >> no rights.

> >> >> ** Please do NOT email, only reply to Newsgroups

> >> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >> >>

> >> >> > Is there any support for this? I am trying to use version 3.1, and

> >> >> > it

> >> >> > is failing, I suspect it is because the cab file gets to large (I

> >> >> > have

> >> >> > over 300 printers). I know because after the cab is created, I

> >> >> > can't

> >> >> > mauanlly extract some files, while I can others. Not sure where to

> >> >> > bring this up, in case there is a fix, or a feature for 3.2

> >> >> >

> >> >> > Since it is not working, does anyone know how to backup or migrate

> >> >> > printers?

> >> >> > manually??

> >> >>

> >>

>

August 12, 2008

Re: Print Migrator

No. Print BackUp Restore Migration tool will only run from Vista +

--

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.

"blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

news:7EB51BD1-2A32-4B7E-B077-94B45DC93414@microsoft.com...

>

> :( I do not have a Vista workstation. I do have 2k3 R2, will the

> printbrm

> util work from there if I can get it?

>

> is there a way I can import the printbrm util into 2k3?

>

> "Alan Morris [MSFT]" wrote:

>

>> yes remote. run the tool and target the Server 2003 machine

>>

>> --

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

>>

>> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

>> news:35DE47F7-E942-48EA-9693-75B6401B51FA@microsoft.com...

>> > Will printbrm work on windows 2003? Do i need to copy over any dll

>> > files

>> > with it to make it work?

>> >

>> > Can I run it against a 2003 server from a vista machine and have it

>> > work?

>> >

>> > "Alan Morris [MSFT]" wrote:

>> >

>> >> the replacement for printmig is printbrm which ships in Vista +

>> >>

>> >> --

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

>> >>

>> >> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

>> >> news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

>> >> >

>> >> > If runs in an infinite loop. Specifically, I get this in the

>> >> > logs(see

>> >> > below).

>> >> > When I try to open the cabinet file manually, some files are ok, and

>> >> > others

>> >> > are either blank (10mb of returns) or the extract asks for the

>> >> > location

>> >> > of

>> >> > the next cabinet, and never stops asking, unless you cancel, then it

>> >> > extracts

>> >> > just the one file, and it is bad.

>> >> >

>> >> > Personally, I think it is a limitation of the printmig program, as

>> >> > there

>> >> > are

>> >> > 300+ printers, and over 500 ports being migrated, the cabinet ends

>> >> > up

>> >> > bing

>> >> > almost a gig in size.

>> >> >

>> >> > I did get the printers migrated, I did this;

>> >> > Ntbackup spool dir

>> >> > Export hklm\system\currentcontrolset\control\print

>> >> > Export hklm\software\Microsoft\windows nt\current version\Ports

>> >> > Restore and import.

>> >> >

>> >> > But when I was adding a printer later with an existing driver, it

>> >> > said

>> >> > the

>> >> > print processor was not responding, I replaced the driver with a new

>> >> > one

>> >> > and

>> >> > it worked, but I am suspicious that all is not well.

>> >> >

>> >> > ((((((((((((())))))))))))))))))

>> >> > fdintNEXT_CABINET

>> >> > name of next cabinet where file continued =

>> >> > name of next disk where file continued =

>> >> > cabinet path name =

>> >> > fdintNEXT_CABINET

>> >> > name of next cabinet where file continued =

>> >> > name of next disk where file continued =

>> >> > cabinet path name =

>> >> > fdintNEXT_CABINET

>> >> > name of next cabinet where file continued =

>> >> > name of next disk where file continued =

>> >> > cabinet path name =

>> >> > Continued for thousands more lines...

>> >> >

>> >> > "Meinolf Weber" wrote:

>> >> >

>> >> >> Hello blankmonkey,

>> >> >>

>> >> >> We use it in the past without problems. What error did you get?

>> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

>> >> >>

>> >> >> Best regards

>> >> >>

>> >> >> Meinolf Weber

>> >> >> Disclaimer: This posting is provided "AS IS" with no warranties,

>> >> >> and

>> >> >> confers

>> >> >> no rights.

>> >> >> ** Please do NOT email, only reply to Newsgroups

>> >> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>> >> >>

>> >> >> > Is there any support for this? I am trying to use version 3.1,

>> >> >> > and

>> >> >> > it

>> >> >> > is failing, I suspect it is because the cab file gets to large (I

>> >> >> > have

>> >> >> > over 300 printers). I know because after the cab is created, I

>> >> >> > can't

>> >> >> > mauanlly extract some files, while I can others. Not sure where

>> >> >> > to

>> >> >> > bring this up, in case there is a fix, or a feature for 3.2

>> >> >> >

>> >> >> > Since it is not working, does anyone know how to backup or

>> >> >> > migrate

>> >> >> > printers?

>> >> >> > manually??

>> >> >>

>> >>

>>

August 20, 2008

Re: Print Migrator

But this didn't answer the original question. Is Print migrator capable of

exporting large numbers of printers? Also is it still supported on 2003

servers? Neither Vista or 2008 server are approved yet in our organization

so they are not an alternative. We are getting ready to move 900 printers to

a new server and it will be lot less work if we dont have to recreate all

those printers.

"Alan Morris [MSFT]" wrote:

> No. Print BackUp Restore Migration tool will only run from Vista +

>

> --

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

>

> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> news:7EB51BD1-2A32-4B7E-B077-94B45DC93414@microsoft.com...

> >

> > :( I do not have a Vista workstation. I do have 2k3 R2, will the

> > printbrm

> > util work from there if I can get it?

> >

> > is there a way I can import the printbrm util into 2k3?

> >

> > "Alan Morris [MSFT]" wrote:

> >

> >> yes remote. run the tool and target the Server 2003 machine

> >>

> >> --

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

> >>

> >> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> >> news:35DE47F7-E942-48EA-9693-75B6401B51FA@microsoft.com...

> >> > Will printbrm work on windows 2003? Do i need to copy over any dll

> >> > files

> >> > with it to make it work?

> >> >

> >> > Can I run it against a 2003 server from a vista machine and have it

> >> > work?

> >> >

> >> > "Alan Morris [MSFT]" wrote:

> >> >

> >> >> the replacement for printmig is printbrm which ships in Vista +

> >> >>

> >> >> --

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

> >> >>

> >> >> "blankmonkey" <blankmonkey@discussions.microsoft.com> wrote in message

> >> >> news:68B95385-97DC-45E0-B448-5369441AD918@microsoft.com...

> >> >> >

> >> >> > If runs in an infinite loop. Specifically, I get this in the

> >> >> > logs(see

> >> >> > below).

> >> >> > When I try to open the cabinet file manually, some files are ok, and

> >> >> > others

> >> >> > are either blank (10mb of returns) or the extract asks for the

> >> >> > location

> >> >> > of

> >> >> > the next cabinet, and never stops asking, unless you cancel, then it

> >> >> > extracts

> >> >> > just the one file, and it is bad.

> >> >> >

> >> >> > Personally, I think it is a limitation of the printmig program, as

> >> >> > there

> >> >> > are

> >> >> > 300+ printers, and over 500 ports being migrated, the cabinet ends

> >> >> > up

> >> >> > bing

> >> >> > almost a gig in size.

> >> >> >

> >> >> > I did get the printers migrated, I did this;

> >> >> > Ntbackup spool dir

> >> >> > Export hklm\system\currentcontrolset\control\print

> >> >> > Export hklm\software\Microsoft\windows nt\current version\Ports

> >> >> > Restore and import.

> >> >> >

> >> >> > But when I was adding a printer later with an existing driver, it

> >> >> > said

> >> >> > the

> >> >> > print processor was not responding, I replaced the driver with a new

> >> >> > one

> >> >> > and

> >> >> > it worked, but I am suspicious that all is not well.

> >> >> >

> >> >> > ((((((((((((())))))))))))))))))

> >> >> > fdintNEXT_CABINET

> >> >> > name of next cabinet where file continued =

> >> >> > name of next disk where file continued =

> >> >> > cabinet path name =

> >> >> > fdintNEXT_CABINET

> >> >> > name of next cabinet where file continued =

> >> >> > name of next disk where file continued =

> >> >> > cabinet path name =

> >> >> > fdintNEXT_CABINET

> >> >> > name of next cabinet where file continued =

> >> >> > name of next disk where file continued =

> >> >> > cabinet path name =

> >> >> > Continued for thousands more lines...

> >> >> >

> >> >> > "Meinolf Weber" wrote:

> >> >> >

> >> >> >> Hello blankmonkey,

> >> >> >>

> >> >> >> We use it in the past without problems. What error did you get?

> >> >> >> http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx

> >> >> >>

> >> >> >> Best regards

> >> >> >>

> >> >> >> Meinolf Weber

> >> >> >> Disclaimer: This posting is provided "AS IS" with no warranties,

> >> >> >> and

> >> >> >> confers

> >> >> >> no rights.

> >> >> >> ** Please do NOT email, only reply to Newsgroups

> >> >> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >> >> >>

> >> >> >> > Is there any support for this? I am trying to use version 3.1,

> >> >> >> > and

> >> >> >> > it

> >> >> >> > is failing, I suspect it is because the cab file gets to large (I

> >> >> >> > have

> >> >> >> > over 300 printers). I know because after the cab is created, I

> >> >> >> > can't

> >> >> >> > mauanlly extract some files, while I can others. Not sure where

> >> >> >> > to

> >> >> >> > bring this up, in case there is a fix, or a feature for 3.2

> >> >> >> >

> >> >> >> > Since it is not working, does anyone know how to backup or

> >> >> >> > migrate

> >> >> >> > printers?

> >> >> >> > manually??

> >> >> >>

> >> >>

> >>

>

Sign In

Print Migrator

Recommended Posts

Guest blankmonkey

Popular Days

Popular Days

Guest Meinolf Weber

Guest blankmonkey

Guest Alan Morris [MSFT]

Guest blankmonkey

Guest Alan Morris [MSFT]

Guest blankmonkey

Guest Alan Morris [MSFT]

Guest Dan W

Similar Content

Restore Exchange 03 to 365 migrated mailbox

Migrating NDES templates to a new CA

Live Migration Issues following Upgrades

Windows 11, version 24H2 update - Universal Print is printing characters and printing out reams of paper

Print Server

Browse

Activity

Site Info