Anilrgowda

I have started testing Vista for our network enviroment, and as expecte i have a few problems :-)

I am having problems mapping printers via logon.

On Win2000/XP machines we use the "AddPrinterConnection" in a KIX script, it seems that this wont work anymore...

So i have been playing around with deploying printers via GPO's.

I am using af dansih language Vista Buisness to do the GPO editing, so some of my error messages is in danish, so i am trying to translate as good as possible.

I have created an policy to add printers i have disabled the "point and print restrictions" so there arent any problems with the UAC.

When i try in the "User Configuration\Windows Settings\Deployed Printers" to install a printer i can add the printers from my print server, but when i click OK, i get an error "add failed" and when i press F5 the printer is gone.

I did a lot of googling and i think the reason is that the printer hasent been deployed via the printer manegment found in Vista.

So i went to my vista PC and tried to deploy with gruop policy like this guide shows Microsoft Corporation

But when i try to deploy i get an error sounding like this

"installatoin of printer connection \\name\share for per user group policy opject "test"failed, check that the Active directory schema has been updated to support printerconnection"

And what now.... I am guessing that i need to make some updates to the AD Schema - but which and how, and what will i do with my other policies??

Anilrgowda

The following is extracted from the vista resource kit book.
Deploying printers using Group policy requires you to perform the following preparatory steps:
Your AD schema must be upgraded to R2 level. This means the schema revision number must be 9 (for Windows server 2003) and the schema version number must be 31 (for the R2 schema update) You can determine your current schema version number using the ADSI edit by looking under the Schema node, right clicking the object named CN=Schema,CN=Configuration,DC=forest_root_domain, selecting properties and then examining the value of the objectVersion attribute. The R2 schema update is required so that Print Management can create the following two objects in Active Directory:
CN=Schema,CN=Policies,CN=GPO_GUID,CN=Machine,CN=Pu shPrinterConnections
CN=Schema,CN=Policies,CN=GPO_GUID,CN=User,CN=PushP rinterConnections


If your client computers are running an earlier version of Microsoft Windows, you must first deploy the PushPrinterConnections.exe utility to these clients prior to using Group Policy to deploy printer connections to these computers. The PushprinterConnections utility reads the GPOs that are used to deploy printer connections and adds or removes these connections on the client as needed. The easiest way to deploy PushPrinterConnections.exe is to use a GPO as follows:
As a user logon script for deploying per user printer connections.
As a computer start up script for deploying per-computer printer connections.

The simplest approach is to use the same GPO to deploy both PushPrinterConnections.exe to targeted uses and/or computers using startup/logon scripts, and for deploying the actual printer connections themselves to those users and or computers. With windows VIsta, however you do not need to first deploy PushPrinterConnections.exe to client computers because Windows Vista includes this capability in the operating system.

I think this is more what you were looking for, sorry if I sent you on a goose chase.