Hi

I am currently running a project to migrate the print
server from the domain controller. It is simple to use
the print migrator to migrate all the printers to another
Windows 2000 box. The problem here is the workstations
needs to remove the existing printers and add the new
connections to the new print server.

I have managed to create a vbs script to run the windows
scripting host to do all the task. But I found that the
script to remove the printers are not able to be run on
some of machines. All the clients are Windows 2000 Pro
with multiple service packs.

The error occurs are below;
The network connection does not exist.

I actually found that I can solve the problem by
upgrading the windows scripting host version XX to the
newest version which is 5.6. What is actually causing the
script not to work properly? Is there any solution to
solve the issue without requiring to upgrade the version
of the windows scripting host as there are 1800
workstations.

Please help!


Cham

Try using con2prt in the logon script. I use it as part
of a VBS script to auto-create network printers for users
as one client uses local profiles on XP (due to WAN
bandwidth limitations).

Anyway, it has several useful switches that may solve your
problem by not having to use a VB Script at all. It is
part of the Win NT 4.0 ZAK that can be pulled down from
MS. It works fine in 2000 server enviroment on 2k and XP
workstations.

Check out http://www.jsifaq.com/SUBA/tip0400/rh0458.htm

Hope that helps. Feel free to email me if you have
questions.

>-----Original Message-----
>Hi
>
>I am currently running a project to migrate the print
>server from the domain controller. It is simple to use
>the print migrator to migrate all the printers to another
>Windows 2000 box. The problem here is the workstations
>needs to remove the existing printers and add the new
>connections to the new print server.
>
>I have managed to create a vbs script to run the windows
>scripting host to do all the task. But I found that the
>script to remove the printers are not able to be run on
>some of machines. All the clients are Windows 2000 Pro
>with multiple service packs.
>
>The error occurs are below;
>The network connection does not exist.
>
>I actually found that I can solve the problem by
>upgrading the windows scripting host version XX to the
>newest version which is 5.6. What is actually causing the
>script not to work properly? Is there any solution to
>solve the issue without requiring to upgrade the version
>of the windows scripting host as there are 1800
>workstations.
>
>Please help!
>
>
>Cham
>
>.
>

Don't know the answer to your specific question, but you may find the
information at http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm useful
for adding the new Network Printers to your client computers.

You may be able to use the /dn optin of the PrintUIEntry function to delete
the printers instead of using a VB script.

At a command prompt, key

rundll32 printui.dll,PrintUIEntry /?

for additional information.

--
Bruce Sanderson MVP

It is perfectly useless to know the right answer to the wrong question.


"Cham" <(E-Mail Removed)> wrote in message
news:01b101c33ed1$a8dabba0$(E-Mail Removed)...
> Hi
>
> I am currently running a project to migrate the print
> server from the domain controller. It is simple to use
> the print migrator to migrate all the printers to another
> Windows 2000 box. The problem here is the workstations
> needs to remove the existing printers and add the new
> connections to the new print server.
>
> I have managed to create a vbs script to run the windows
> scripting host to do all the task. But I found that the
> script to remove the printers are not able to be run on
> some of machines. All the clients are Windows 2000 Pro
> with multiple service packs.
>
> The error occurs are below;
> The network connection does not exist.
>
> I actually found that I can solve the problem by
> upgrading the windows scripting host version XX to the
> newest version which is 5.6. What is actually causing the
> script not to work properly? Is there any solution to
> solve the issue without requiring to upgrade the version
> of the windows scripting host as there are 1800
> workstations.
>
> Please help!
>
>
> Cham
>