Remap client printers after migrating to new print server

We have consolidated 3 print servers into one and before switching off the
old print servers we need to remap the client machines to the new server.

In the days of NT4 we used the tool CHGPRINT.exe to do this, which worked a
treat. Anyone know of a tool/script that will run as part of logon script,
search the clients list of connected printers, remap the printer to a
different server and possibly different sharename.

I have tried running chgprint.exe but does not appear to work under W2k3 R2
Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175 printers.

thanks in advance,

Hello,

I am providing a vbscript on my blog do to this:
http://lordoftheping.blogspot.com/20...er-server.html


--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


"Gaza" <> wrote in message
news:1A5E85D5-38BF-4ABE-83C5-...
> We have consolidated 3 print servers into one and before switching off the
> old print servers we need to remap the client machines to the new server.
>
> In the days of NT4 we used the tool CHGPRINT.exe to do this, which worked
> a
> treat. Anyone know of a tool/script that will run as part of logon
> script,
> search the clients list of connected printers, remap the printer to a
> different server and possibly different sharename.
>
> I have tried running chgprint.exe but does not appear to work under W2k3
> R2
> Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
> printers.
>
> thanks in advance,

A nice addition to your script would be to allow for the printer share name
changing too. The old chgprint.exe tool read a list of old
\\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.

As we are also moving from 3 servers to one, and at the same time changing
the printer name standard, the above feature would be beneficial.

regards,
Gary

"Mathieu CHATEAU" wrote:

> Hello,
>
> I am providing a vbscript on my blog do to this:
> http://lordoftheping.blogspot.com/20...er-server.html
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> English blog: http://lordoftheping.blogspot.com
> French blog: http://www.lotp.fr
>
>
> "Gaza" <> wrote in message
> news:1A5E85D5-38BF-4ABE-83C5-...
> > We have consolidated 3 print servers into one and before switching off the
> > old print servers we need to remap the client machines to the new server.
> >
> > In the days of NT4 we used the tool CHGPRINT.exe to do this, which worked
> > a
> > treat. Anyone know of a tool/script that will run as part of logon
> > script,
> > search the clients list of connected printers, remap the printer to a
> > different server and possibly different sharename.
> >
> > I have tried running chgprint.exe but does not appear to work under W2k3
> > R2
> > Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
> > printers.
> >
> > thanks in advance,
>
>

the original one does it, i will include it back after some cleaning

are you in a hurry ?

--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


"Gaza" <> wrote in message
news:8461B149-F0F5-4CDC-858D-...
>A nice addition to your script would be to allow for the printer share name
> changing too. The old chgprint.exe tool read a list of old
> \\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.
>
> As we are also moving from 3 servers to one, and at the same time changing
> the printer name standard, the above feature would be beneficial.
>
> regards,
> Gary
>
> "Mathieu CHATEAU" wrote:
>
>> Hello,
>>
>> I am providing a vbscript on my blog do to this:
>> http://lordoftheping.blogspot.com/20...er-server.html
>>
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> English blog: http://lordoftheping.blogspot.com
>> French blog: http://www.lotp.fr
>>
>>
>> "Gaza" <> wrote in message
>> news:1A5E85D5-38BF-4ABE-83C5-...
>> > We have consolidated 3 print servers into one and before switching off
>> > the
>> > old print servers we need to remap the client machines to the new
>> > server.
>> >
>> > In the days of NT4 we used the tool CHGPRINT.exe to do this, which
>> > worked
>> > a
>> > treat. Anyone know of a tool/script that will run as part of logon
>> > script,
>> > search the clients list of connected printers, remap the printer to a
>> > different server and possibly different sharename.
>> >
>> > I have tried running chgprint.exe but does not appear to work under
>> > W2k3
>> > R2
>> > Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
>> > printers.
>> >
>> > thanks in advance,
>>
>>

Change over is planned for next week .. if you could do this, then that
would be great.

regards,
Gary

"Mathieu CHATEAU" wrote:

> the original one does it, i will include it back after some cleaning
>
> are you in a hurry ?
>
> --
> Cordialement,
> Mathieu CHATEAU
> English blog: http://lordoftheping.blogspot.com
> French blog: http://www.lotp.fr
>
>
> "Gaza" <> wrote in message
> news:8461B149-F0F5-4CDC-858D-...
> >A nice addition to your script would be to allow for the printer share name
> > changing too. The old chgprint.exe tool read a list of old
> > \\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.
> >
> > As we are also moving from 3 servers to one, and at the same time changing
> > the printer name standard, the above feature would be beneficial.
> >
> > regards,
> > Gary
> >
> > "Mathieu CHATEAU" wrote:
> >
> >> Hello,
> >>
> >> I am providing a vbscript on my blog do to this:
> >> http://lordoftheping.blogspot.com/20...er-server.html
> >>
> >>
> >> --
> >> Cordialement,
> >> Mathieu CHATEAU
> >> English blog: http://lordoftheping.blogspot.com
> >> French blog: http://www.lotp.fr
> >>
> >>
> >> "Gaza" <> wrote in message
> >> news:1A5E85D5-38BF-4ABE-83C5-...
> >> > We have consolidated 3 print servers into one and before switching off
> >> > the
> >> > old print servers we need to remap the client machines to the new
> >> > server.
> >> >
> >> > In the days of NT4 we used the tool CHGPRINT.exe to do this, which
> >> > worked
> >> > a
> >> > treat. Anyone know of a tool/script that will run as part of logon
> >> > script,
> >> > search the clients list of connected printers, remap the printer to a
> >> > different server and possibly different sharename.
> >> >
> >> > I have tried running chgprint.exe but does not appear to work under
> >> > W2k3
> >> > R2
> >> > Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
> >> > printers.
> >> >
> >> > thanks in advance,
> >>
> >>
>
>

ok it would be ready soon

--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


"Gaza" <> wrote in message
news:F8ADAB5D-D2CF-4D0D-AF07-...
>
> Change over is planned for next week .. if you could do this, then that
> would be great.
>
> regards,
> Gary
>
> "Mathieu CHATEAU" wrote:
>
>> the original one does it, i will include it back after some cleaning
>>
>> are you in a hurry ?
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> English blog: http://lordoftheping.blogspot.com
>> French blog: http://www.lotp.fr
>>
>>
>> "Gaza" <> wrote in message
>> news:8461B149-F0F5-4CDC-858D-...
>> >A nice addition to your script would be to allow for the printer share
>> >name
>> > changing too. The old chgprint.exe tool read a list of old
>> > \\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.
>> >
>> > As we are also moving from 3 servers to one, and at the same time
>> > changing
>> > the printer name standard, the above feature would be beneficial.
>> >
>> > regards,
>> > Gary
>> >
>> > "Mathieu CHATEAU" wrote:
>> >
>> >> Hello,
>> >>
>> >> I am providing a vbscript on my blog do to this:
>> >> http://lordoftheping.blogspot.com/20...er-server.html
>> >>
>> >>
>> >> --
>> >> Cordialement,
>> >> Mathieu CHATEAU
>> >> English blog: http://lordoftheping.blogspot.com
>> >> French blog: http://www.lotp.fr
>> >>
>> >>
>> >> "Gaza" <> wrote in message
>> >> news:1A5E85D5-38BF-4ABE-83C5-...
>> >> > We have consolidated 3 print servers into one and before switching
>> >> > off
>> >> > the
>> >> > old print servers we need to remap the client machines to the new
>> >> > server.
>> >> >
>> >> > In the days of NT4 we used the tool CHGPRINT.exe to do this, which
>> >> > worked
>> >> > a
>> >> > treat. Anyone know of a tool/script that will run as part of logon
>> >> > script,
>> >> > search the clients list of connected printers, remap the printer to
>> >> > a
>> >> > different server and possibly different sharename.
>> >> >
>> >> > I have tried running chgprint.exe but does not appear to work under
>> >> > W2k3
>> >> > R2
>> >> > Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
>> >> > printers.
>> >> >
>> >> > thanks in advance,
>> >>
>> >>
>>
>>

Mathieu,

I have managed to get "chgprint.exe" to work. The printer definition on the
client were using fully qualified domain name for the old servers.

However, your script is still very useful as chgprint gives no logging or
error detection.

thanks,
Gary

"Mathieu CHATEAU" wrote:

> ok it would be ready soon
>
> --
> Cordialement,
> Mathieu CHATEAU
> English blog: http://lordoftheping.blogspot.com
> French blog: http://www.lotp.fr
>
>
> "Gaza" <> wrote in message
> news:F8ADAB5D-D2CF-4D0D-AF07-...
> >
> > Change over is planned for next week .. if you could do this, then that
> > would be great.
> >
> > regards,
> > Gary
> >
> > "Mathieu CHATEAU" wrote:
> >
> >> the original one does it, i will include it back after some cleaning
> >>
> >> are you in a hurry ?
> >>
> >> --
> >> Cordialement,
> >> Mathieu CHATEAU
> >> English blog: http://lordoftheping.blogspot.com
> >> French blog: http://www.lotp.fr
> >>
> >>
> >> "Gaza" <> wrote in message
> >> news:8461B149-F0F5-4CDC-858D-...
> >> >A nice addition to your script would be to allow for the printer share
> >> >name
> >> > changing too. The old chgprint.exe tool read a list of old
> >> > \\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.
> >> >
> >> > As we are also moving from 3 servers to one, and at the same time
> >> > changing
> >> > the printer name standard, the above feature would be beneficial.
> >> >
> >> > regards,
> >> > Gary
> >> >
> >> > "Mathieu CHATEAU" wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> I am providing a vbscript on my blog do to this:
> >> >> http://lordoftheping.blogspot.com/20...er-server.html
> >> >>
> >> >>
> >> >> --
> >> >> Cordialement,
> >> >> Mathieu CHATEAU
> >> >> English blog: http://lordoftheping.blogspot.com
> >> >> French blog: http://www.lotp.fr
> >> >>
> >> >>
> >> >> "Gaza" <> wrote in message
> >> >> news:1A5E85D5-38BF-4ABE-83C5-...
> >> >> > We have consolidated 3 print servers into one and before switching
> >> >> > off
> >> >> > the
> >> >> > old print servers we need to remap the client machines to the new
> >> >> > server.
> >> >> >
> >> >> > In the days of NT4 we used the tool CHGPRINT.exe to do this, which
> >> >> > worked
> >> >> > a
> >> >> > treat. Anyone know of a tool/script that will run as part of logon
> >> >> > script,
> >> >> > search the clients list of connected printers, remap the printer to
> >> >> > a
> >> >> > different server and possibly different sharename.
> >> >> >
> >> >> > I have tried running chgprint.exe but does not appear to work under
> >> >> > W2k3
> >> >> > R2
> >> >> > Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175
> >> >> > printers.
> >> >> >
> >> >> > thanks in advance,
> >> >>
> >> >>
> >>
> >>
>
>

Hello,

here is the updated script version:
http://gollum123.free.fr/printermigrator.vbs


Now you have to set:
-A folder where a log per username is created:
Set objFile = objFSO.CreateTextFile ("\\fileserver\Logs\printers\" &
UserName & ".log")

-The new print server name in this file
Set objFileServer = objFSO.OpenTextFile (LogonServer &
"\netlogon\printers\default.txt", ForReading)

-A CSV for changing printer name:
Set objfiletable = objFSO.OpenTextFile (LogonServer &
"\netlogon\printers\Convtable.txt", ForReading)
syntax is :
oldname;newname
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


<> wrote in message
news:32ed377d-7237-43e2-bca3-...
> On Nov 23, 1:33 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>> ok it would be ready soon
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> English blog:http://lordoftheping.blogspot.com
>> French blog:http://www.lotp.fr
>>
>> "Gaza" <G...@discussions.microsoft.com> wrote in message
>>
>> news:F8ADAB5D-D2CF-4D0D-AF07-...
>>
>>
>>
>>
>>
>> > Change over is planned for next week .. if you could do this, then
>> > that
>> > would be great.
>>
>> > regards,
>> > Gary
>>
>> > "Mathieu CHATEAU" wrote:
>>
>> >> the original one does it, i will include it back after some cleaning
>>
>> >> are you in a hurry ?
>>
>> >> --
>> >> Cordialement,
>> >> Mathieu CHATEAU
>> >> English blog:http://lordoftheping.blogspot.com
>> >> French blog:http://www.lotp.fr
>>
>> >> "Gaza" <G...@discussions.microsoft.com> wrote in message
>> >>news:8461B149-F0F5-4CDC-858D-...
>> >> >A nice addition to your script would be to allow for the printer
>> >> >share
>> >> >name
>> >> > changing too. The old chgprint.exe tool read a list of old
>> >> > \\printoldsrv\prshare1 tonew\\printnewsrv\prshare99 from a text
>> >> > file.
>>
>> >> > As we are also moving from 3 servers to one, and at the same time
>> >> > changing
>> >> > the printer name standard, the above feature would be beneficial.
>>
>> >> > regards,
>> >> > Gary
>>
>> >> > "Mathieu CHATEAU" wrote:
>>
>> >> >> Hello,
>>
>> >> >> I am providing a vbscript on my blog do to this:
>> >> >>http://lordoftheping.blogspot.com/20...hange-printer-...
>>
>> >> >> --
>> >> >> Cordialement,
>> >> >> Mathieu CHATEAU
>> >> >> English blog:http://lordoftheping.blogspot.com
>> >> >> French blog:http://www.lotp.fr
>>
>> >> >> "Gaza" <G...@discussions.microsoft.com> wrote in message
>> >> >>news:1A5E85D5-38BF-4ABE-83C5-...
>> >> >> > We have consolidated 3printservers into one and before switching
>> >> >> > off
>> >> >> > the
>> >> >> > oldprintservers we need to remap the client machines to thenew
>> >> >> >server.
>>
>> >> >> > In the days of NT4 we used the tool CHGPRINT.exe to do this,
>> >> >> > which
>> >> >> > worked
>> >> >> > a
>> >> >> > treat. Anyone know of a tool/script that will run as part of
>> >> >> > logon
>> >> >> > script,
>> >> >> > search the clients list of connected printers, remap the printer
>> >> >> > to
>> >> >> > a
>> >> >> > differentserverand possibly different sharename.
>>
>> >> >> > I have tried running chgprint.exe but does not appear to work
>> >> >> > under
>> >> >> > W2k3
>> >> >> > R2
>> >> >> > Sp1server& WinXP SP2 clients. I have approx 1800 clients and
>> >> >> > 175
>> >> >> > printers.
>>
>> >> >> > thanks in advance,- Hide quoted text -
>>
>> - Show quoted text -
>
> I took a look at your vbs script, and it looks real good. Did you
> ever get a chance to modify the script so that it will account for the
> queue name changing on the new print server?

Hello,

need to add a "if" statement.

If you have a cluster, you should only and only point to the virtual name,
never the node names.
Do you get where to put the if or do you need help ?

--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


<> wrote in message
news:2e2acc00-3fc9-43d1-9420-...
On Nov 27 2007, 11:13 am, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
> Hello,
>
> here is the updated script
> version:http://gollum123.free.fr/printermigrator.vbs
>
> Now you have to set:
> -A folder where a log per username is created:
> Set objFile = objFSO.CreateTextFile ("\\fileserver\Logs\printers\" &
> UserName & ".log")
>
> -The new print servernamein this file
> Set objFileServer = objFSO.OpenTextFile (LogonServer &
> "\netlogon\printers\default.txt", ForReading)
>
> -A CSV forchangingprintername:
> Set objfiletable = objFSO.OpenTextFile (LogonServer &
> "\netlogon\printers\Convtable.txt", ForReading)
> syntax is :
> oldname;newname
> --
> Cordialement,MathieuCHATEAU
> English blog:http://lordoftheping.blogspot.com
> French blog:http://www.lotp.fr
>
> <tristonhibb...@hotmail.com> wrote in message
>
> news:32ed377d-7237-43e2-bca3-...
>
>
>
> > On Nov 23, 1:33 pm, "MathieuCHATEAU" <gollum...@free.fr> wrote:
> >> ok it would be ready soon
>
> >> --
> >> Cordialement,
> >>MathieuCHATEAU
> >> English blog:http://lordoftheping.blogspot.com
> >> French blog:http://www.lotp.fr
>
> >> "Gaza" <G...@discussions.microsoft.com> wrote in message
>
> >>news:F8ADAB5D-D2CF-4D0D-AF07-...
>
> >> > Change over is planned for next week .. if you could do this, then
> >> > that
> >> > would be great.
>
> >> > regards,
> >> > Gary
>
> >> > "MathieuCHATEAU" wrote:
>
> >> >> the original one does it, i will include it back after some cleaning
>
> >> >> are you in a hurry ?
>
> >> >> --
> >> >> Cordialement,
> >> >>MathieuCHATEAU
> >> >> English blog:http://lordoftheping.blogspot.com
> >> >> French blog:http://www.lotp.fr
>
> >> >> "Gaza" <G...@discussions.microsoft.com> wrote in message
> >> >>news:8461B149-F0F5-4CDC-858D-...
> >> >> >A nice addition to your script would be to allow for the printer
> >> >> >share
> >> >> >name
> >> >> >changingtoo. The old chgprint.exe tool read a list of old
> >> >> > \\printoldsrv\prshare1 tonew\\printnewsrv\prshare99 from a text
> >> >> > file.
>
> >> >> > As we are also moving from 3 servers to one, and at the same time
> >> >> >changing
> >> >> > the printernamestandard, the above feature would be beneficial.
>
> >> >> > regards,
> >> >> > Gary
>
> >> >> > "MathieuCHATEAU" wrote:
>
> >> >> >> Hello,
>
> >> >> >> I am providing a vbscript on my blog do to this:
> >> >> >>http://lordoftheping.blogspot.com/20...hange-printer-...
>
> >> >> >> --
> >> >> >> Cordialement,
> >> >> >>MathieuCHATEAU
> >> >> >> English blog:http://lordoftheping.blogspot.com
> >> >> >> French blog:http://www.lotp.fr
>
> >> >> >> "Gaza" <G...@discussions.microsoft.com> wrote in message
> >> >> >>news:1A5E85D5-38BF-4ABE-83C5-...
> >> >> >> > We have consolidated 3printservers into one and before
> >> >> >> > switching
> >> >> >> > off
> >> >> >> > the
> >> >> >> > oldprintservers we need to remap the client machines to thenew
> >> >> >> >server.
>
> >> >> >> > In the days of NT4 we used the tool CHGPRINT.exe to do this,
> >> >> >> > which
> >> >> >> > worked
> >> >> >> > a
> >> >> >> > treat. Anyone know of a tool/script that will run as part of
> >> >> >> > logon
> >> >> >> > script,
> >> >> >> > search the clients list of connected printers, remap the
> >> >> >> > printer
> >> >> >> > to
> >> >> >> > a
> >> >> >> > differentserverand possibly different sharename.
>
> >> >> >> > I have tried running chgprint.exe but does not appear to work
> >> >> >> > under
> >> >> >> > W2k3
> >> >> >> > R2
> >> >> >> > Sp1server& WinXP SP2 clients. I have approx 1800 clients and
> >> >> >> > 175
> >> >> >> > printers.
>
> >> >> >> > thanks in advance,- Hide quoted text -
>
> >> - Show quoted text -
>
> > I took a look at your vbs script, and it looks real good. Did you
> > ever get a chance to modify the script so that it will account for the
> >queuenamechangingon the new print server?- Hide quoted text -
>
> - Show quoted text -

Hello,

This script is working great! One minor issue that I think I can get
around, but I want to see what you have to say about it.

The script will try to convert all network printers regardless of what
print server that printer is on. In my case there are only certain
printers on one printer server that we are migrating and only the
printers on that one server will be migrated. So for the printers
that were on that server, the script worked beautifully, however, for
printers that were on a different print server, it simply tried to
covert it but failed and the printer was deleted. I know this is
asking much, but is there a way around that. In others words, can we
have the script just look to convert printers that are on one
particular print server. Just to throw a curveball, the print server
is clustered, so it can be referred to by 1 of 3 names. Thanks again
for all of your help.

Regards,
Triston

Hi Mathieu,

Not sure if i'm using the right way to execute the script.

I placed this script on a desktop to try, in cmd, i typed 'cscript printmigrator.vbs'

Nothing seems to happen, no error, no log files, but cscript process took up 100% of usgae and slowed down the entire system.

Did i miss some steps in between ?

> On Thursday, November 22, 2007 5:05 PM Gaz wrote:

> We have consolidated 3 print servers into one and before switching off the
> old print servers we need to remap the client machines to the new server.
>
> In the days of NT4 we used the tool CHGPRINT.exe to do this, which worked a
> treat. Anyone know of a tool/script that will run as part of logon script,
> search the clients list of connected printers, remap the printer to a
> different server and possibly different sharename.
>
> I have tried running chgprint.exe but does not appear to work under W2k3 R2
> Sp1 server & WinXP SP2 clients. I have approx 1800 clients and 175 printers.
>
> thanks in advance,


>> On Thursday, November 22, 2007 5:32 PM Mathieu CHATEAU wrote:

>> Hello,
>>
>> I am providing a vbscript on my blog do to this:
>> http://lordoftheping.blogspot.com/20...er-server.html
>>
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> English blog: http://lordoftheping.blogspot.com
>> French blog: http://www.lotp.fr
>>
>>
>> "Gaza" <> wrote in message
>> news:1A5E85D5-38BF-4ABE-83C5-...


>>> On Thursday, November 22, 2007 5:45 PM Gaz wrote:

>>> A nice addition to your script would be to allow for the printer share name
>>> changing too. The old chgprint.exe tool read a list of old
>>> \\printoldsrv\prshare1 to new \\printnewsrv\prshare99 from a text file.
>>>
>>> As we are also moving from 3 servers to one, and at the same time changing
>>> the printer name standard, the above feature would be beneficial.
>>>
>>> regards,
>>> Gary
>>>
>>> "Mathieu CHATEAU" wrote:


>>>> On Thursday, November 22, 2007 6:09 PM Mathieu CHATEAU wrote:

>>>> the original one does it, i will include it back after some cleaning
>>>>
>>>> are you in a hurry ?
>>>>
>>>> --
>>>> Cordialement,
>>>> Mathieu CHATEAU
>>>> English blog: http://lordoftheping.blogspot.com
>>>> French blog: http://www.lotp.fr
>>>>
>>>>
>>>> "Gaza" <> wrote in message
>>>> news:8461B149-F0F5-4CDC-858D-...


>>>>> On Friday, November 23, 2007 5:08 AM Gaz wrote:

>>>>> Change over is planned for next week .. if you could do this, then that
>>>>> would be great.
>>>>>
>>>>> regards,
>>>>> Gary
>>>>>
>>>>> "Mathieu CHATEAU" wrote:


>>>>>> On Friday, November 23, 2007 1:33 PM Mathieu CHATEAU wrote:

>>>>>> ok it would be ready soon
>>>>>>
>>>>>> --
>>>>>> Cordialement,
>>>>>> Mathieu CHATEAU
>>>>>> English blog: http://lordoftheping.blogspot.com
>>>>>> French blog: http://www.lotp.fr


>>>>>>> On Friday, November 23, 2007 6:54 PM Gaz wrote:

>>>>>>> Mathieu,
>>>>>>>
>>>>>>> I have managed to get "chgprint.exe" to work. The printer definition on the
>>>>>>> client were using fully qualified domain name for the old servers.
>>>>>>>
>>>>>>> However, your script is still very useful as chgprint gives no logging or
>>>>>>> error detection.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Gary
>>>>>>>
>>>>>>> "Mathieu CHATEAU" wrote:


>>>>>>>> On Tuesday, November 27, 2007 11:13 AM Mathieu CHATEAU wrote:

>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> here is the updated script version:
>>>>>>>> http://gollum123.free.fr/printermigrator.vbs
>>>>>>>>
>>>>>>>>
>>>>>>>> Now you have to set:
>>>>>>>> -A folder where a log per username is created:
>>>>>>>> Set objFile = objFSO.CreateTextFile ("\\fileserver\Logs\printers\" &
>>>>>>>> UserName & ".log")
>>>>>>>>
>>>>>>>> -The new print server name in this file
>>>>>>>> Set objFileServer = objFSO.OpenTextFile (LogonServer &
>>>>>>>> "\netlogon\printers\default.txt", ForReading)
>>>>>>>>
>>>>>>>> -A CSV for changing printer name:
>>>>>>>> Set objfiletable = objFSO.OpenTextFile (LogonServer &
>>>>>>>> "\netlogon\printers\Convtable.txt", ForReading)
>>>>>>>> syntax is :
>>>>>>>> oldname;newname
>>>>>>>> --
>>>>>>>> Cordialement,
>>>>>>>> Mathieu CHATEAU
>>>>>>>> English blog: http://lordoftheping.blogspot.com
>>>>>>>> French blog: http://www.lotp.fr
>>>>>>>>
>>>>>>>>
>>>>>>>> <> wrote in message
>>>>>>>> news:32ed377d-7237-43e2-bca3-...


>>>>>>>>> On Thursday, November 29, 2007 1:27 AM tristonhibber wrote:

>>>>>>>>> I took a look at your vbs script, and it looks real good. Did you
>>>>>>>>> ever get a chance to modify the script so that it will account for the
>>>>>>>>> queue name changing on the new print server?


>>>>>>>>>> On Friday, January 04, 2008 3:43 PM Mathieu CHATEAU wrote:

>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> need to add a "if" statement.
>>>>>>>>>>
>>>>>>>>>> If you have a cluster, you should only and only point to the virtual name,
>>>>>>>>>> never the node names.
>>>>>>>>>> Do you get where to put the if or do you need help ?
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Cordialement,
>>>>>>>>>> Mathieu CHATEAU
>>>>>>>>>> English blog: http://lordoftheping.blogspot.com
>>>>>>>>>> French blog: http://www.lotp.fr
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <> wrote in message
>>>>>>>>>> news:2e2acc00-3fc9-43d1-9420-...
>>>>>>>>>> On Nov 27 2007, 11:13 am, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> This script is working great! One minor issue that I think I can get
>>>>>>>>>> around, but I want to see what you have to say about it.
>>>>>>>>>>
>>>>>>>>>> The script will try to convert all network printers regardless of what
>>>>>>>>>> print server that printer is on. In my case there are only certain
>>>>>>>>>> printers on one printer server that we are migrating and only the
>>>>>>>>>> printers on that one server will be migrated. So for the printers
>>>>>>>>>> that were on that server, the script worked beautifully, however, for
>>>>>>>>>> printers that were on a different print server, it simply tried to
>>>>>>>>>> covert it but failed and the printer was deleted. I know this is
>>>>>>>>>> asking much, but is there a way around that. In others words, can we
>>>>>>>>>> have the script just look to convert printers that are on one
>>>>>>>>>> particular print server. Just to throw a curveball, the print server
>>>>>>>>>> is clustered, so it can be referred to by 1 of 3 names. Thanks again
>>>>>>>>>> for all of your help.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Triston


>>>>>>>>>>> On Sunday, January 06, 2008 12:39 AM tristonhibber wrote:

>>>>>>>>>>> On Nov 27 2007, 11:13=A0am, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>>>>>>>>>>> r.vbs
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> er-...
>>>>>>>>>>> g
>>>>>>>>>>>
>>>>>>>>>>> r
>>>>>>>>>>> d
>>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> This script is working great! One minor issue that I think I can get
>>>>>>>>>>> around, but I want to see what you have to say about it.
>>>>>>>>>>>
>>>>>>>>>>> The script will try to convert all network printers regardless of what
>>>>>>>>>>> print server that printer is on. In my case there are only certain
>>>>>>>>>>> printers on one printer server that we are migrating and only the
>>>>>>>>>>> printers on that one server will be migrated. So for the printers
>>>>>>>>>>> that were on that server, the script worked beautifully, however, for
>>>>>>>>>>> printers that were on a different print server, it simply tried to
>>>>>>>>>>> covert it but failed and the printer was deleted. I know this is
>>>>>>>>>>> asking much, but is there a way around that. In others words, can we
>>>>>>>>>>> have the script just look to convert printers that are on one
>>>>>>>>>>> particular print server. Just to throw a curveball, the print server
>>>>>>>>>>> is clustered, so it can be referred to by 1 of 3 names. Thanks again
>>>>>>>>>>> for all of your help.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Triston


>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>> BizTalk: Parallel Processing with Correlation
>>>>>>>>>>> http://www.eggheadcafe.com/tutorials...rrelation.aspx