Print Management Questions(s).

[Steven L Chan]

Hello All:

Our forest level is Windows 2003 R2, schema version is 31.

# 1).

Installation requirement is for computers running Windows 2003 R2, is x64
allowed?

#2).

Quote: "Print Management can automatically search for and install network
printers on the local subnet of your local print server"

When I tried to execute the "Automatically Add Network Printers" command, it
does not find any printers. I am assuming that's it's searching for
printers on the local subnet, but all printers are located on other
subnets/VLANs. Although, the Windows 2000 print server is located on the
local subnet. How can I expand the search?

#3).

I configued the Group Policy to deploy a printer via User and Computer
settings, but to no avail.

I get an application error stating "Could not execute the following script
pushprinterconnections.exe", what does that mean?


I've triple checked to ensure that I configured Print Management correctly,
any help on this would be greatly appreciated.

If you need additional information, please let me know...

Steven

 

[Alan Morris [MSFT]]

Re: Print Management Questions(s).

Server 2003 R2 is available for x64 machines

Is schema 31 the one that comes with R2?

The search is limited to the local subnet.

Run pushprinterconnections at command line rather that through a logon
script just to verify that it is working. If you are grabbing the exe from
an x64 R2 CD, this file will not run on 32 bit clients. The 32bit
pushprinterconnections.exe will run fine on x64 clients.

PushPrinterConnections.exe -log

will create a ppcuser.log file in %temp%

and when run in computer context ppcmachine.log in %windir%\temp

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

"Steven L Chan" <StevenLChan@gmail.com> wrote in message
news:E242E68B-F9F4-4D08-B012-A86469E4BA41@microsoft.com...
> Hello All:
>
> Our forest level is Windows 2003 R2, schema version is 31.
>
> # 1).
>
> Installation requirement is for computers running Windows 2003 R2, is x64
> allowed?
>
> #2).
>
> Quote: "Print Management can automatically search for and install network
> printers on the local subnet of your local print server"
>
> When I tried to execute the "Automatically Add Network Printers" command,
> it does not find any printers. I am assuming that's it's searching for
> printers on the local subnet, but all printers are located on other
> subnets/VLANs. Although, the Windows 2000 print server is located on the
> local subnet. How can I expand the search?
>
> #3).
>
> I configued the Group Policy to deploy a printer via User and Computer
> settings, but to no avail.
>
> I get an application error stating "Could not execute the following script
> pushprinterconnections.exe", what does that mean?
>
>
> I've triple checked to ensure that I configured Print Management
> correctly, any help on this would be greatly appreciated.
>
> If you need additional information, please let me know...
>
> Steven
>
>

 

[Steven L Chan]

Re: Print Management Questions(s).

Morning,

Yes, Schema 31 came with R2, when we installed new domain controllers to
Windows 2003 Forest level.

I grabbed a copy of the pushprinterconnections.exe from a R2 x86 box and it
worked! Thanks for the tip!

I am assuming that I have to manually removed the printer from our Windows
2000 print server and install it on the R2 box, right?

Steven


"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:%23cMyKeiDJHA.340@TK2MSFTNGP03.phx.gbl...
> Server 2003 R2 is available for x64 machines
>
> Is schema 31 the one that comes with R2?
>
> The search is limited to the local subnet.
>
> Run pushprinterconnections at command line rather that through a logon
> script just to verify that it is working. If you are grabbing the exe
> from an x64 R2 CD, this file will not run on 32 bit clients. The 32bit
> pushprinterconnections.exe will run fine on x64 clients.
>
> PushPrinterConnections.exe -log
>
> will create a ppcuser.log file in %temp%
>
> and when run in computer context ppcmachine.log in %windir%\temp
>
> --
> 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.
>
> "Steven L Chan" <StevenLChan@gmail.com> wrote in message
> news:E242E68B-F9F4-4D08-B012-A86469E4BA41@microsoft.com...
>> Hello All:
>>
>> Our forest level is Windows 2003 R2, schema version is 31.
>>
>> # 1).
>>
>> Installation requirement is for computers running Windows 2003 R2, is x64
>> allowed?
>>
>> #2).
>>
>> Quote: "Print Management can automatically search for and install
>> network printers on the local subnet of your local print server"
>>
>> When I tried to execute the "Automatically Add Network Printers" command,
>> it does not find any printers. I am assuming that's it's searching for
>> printers on the local subnet, but all printers are located on other
>> subnets/VLANs. Although, the Windows 2000 print server is located on the
>> local subnet. How can I expand the search?
>>
>> #3).
>>
>> I configued the Group Policy to deploy a printer via User and Computer
>> settings, but to no avail.
>>
>> I get an application error stating "Could not execute the following
>> script pushprinterconnections.exe", what does that mean?
>>
>>
>> I've triple checked to ensure that I configured Print Management
>> correctly, any help on this would be greatly appreciated.
>>
>> If you need additional information, please let me know...
>>
>> Steven
>>
>>
>
>

 

[Alan Morris [MSFT]]

Re: Print Management Questions(s).

If you have any Vista clients around you can use the Print Backup Restore
Migration Wizard to backup the printers on Win2k and restore to Win2k3.
printbrmui.exe

You can use printmig 3.1 as well. This will run on Win2k and Win2k3.
@microsoft.com. If the new print server is x64 you will need to locate x64
print drivers with the exact names of the x86 print drivers for the
migration to work.

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

"Steven L Chan" <StevenLChan@gmail.com> wrote in message
news:EE5E8A03-5255-41D8-A629-98086AE8F06F@microsoft.com...
> Morning,
>
> Yes, Schema 31 came with R2, when we installed new domain controllers to
> Windows 2003 Forest level.
>
> I grabbed a copy of the pushprinterconnections.exe from a R2 x86 box and
> it
> worked! Thanks for the tip!
>
> I am assuming that I have to manually removed the printer from our Windows
> 2000 print server and install it on the R2 box, right?
>
> Steven
>
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:%23cMyKeiDJHA.340@TK2MSFTNGP03.phx.gbl...
>> Server 2003 R2 is available for x64 machines
>>
>> Is schema 31 the one that comes with R2?
>>
>> The search is limited to the local subnet.
>>
>> Run pushprinterconnections at command line rather that through a logon
>> script just to verify that it is working. If you are grabbing the exe
>> from an x64 R2 CD, this file will not run on 32 bit clients. The 32bit
>> pushprinterconnections.exe will run fine on x64 clients.
>>
>> PushPrinterConnections.exe -log
>>
>> will create a ppcuser.log file in %temp%
>>
>> and when run in computer context ppcmachine.log in %windir%\temp
>>
>> --
>> 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.
>>
>> "Steven L Chan" <StevenLChan@gmail.com> wrote in message
>> news:E242E68B-F9F4-4D08-B012-A86469E4BA41@microsoft.com...
>>> Hello All:
>>>
>>> Our forest level is Windows 2003 R2, schema version is 31.
>>>
>>> # 1).
>>>
>>> Installation requirement is for computers running Windows 2003 R2, is
>>> x64 allowed?
>>>
>>> #2).
>>>
>>> Quote: "Print Management can automatically search for and install
>>> network printers on the local subnet of your local print server"
>>>
>>> When I tried to execute the "Automatically Add Network Printers"
>>> command, it does not find any printers. I am assuming that's it's
>>> searching for printers on the local subnet, but all printers are located
>>> on other subnets/VLANs. Although, the Windows 2000 print server is
>>> located on the local subnet. How can I expand the search?
>>>
>>> #3).
>>>
>>> I configued the Group Policy to deploy a printer via User and Computer
>>> settings, but to no avail.
>>>
>>> I get an application error stating "Could not execute the following
>>> script pushprinterconnections.exe", what does that mean?
>>>
>>>
>>> I've triple checked to ensure that I configured Print Management
>>> correctly, any help on this would be greatly appreciated.
>>>
>>> If you need additional information, please let me know...
>>>
>>> Steven
>>>
>>>
>>
>>
>