Windows 7 printer drivers in Server 2003 environment; Problem

[CHiLL]

I've been having a specific problem on Windows 7 clients on our Server 2003 evironment. We have been testing Windows 7, and building a profile to work with it (all of our clients are on XP...but new systems will come with Windows 7). The profiles are all working, except when it comes to printers.

 

We have a vbs script which runs on logon, checks where the user is logged on, and assigns (and defaults) the correct printer for that room. It also deletes printers on log off. On Windows XP, this work flawlessly. However, coming to Windows 7 we encounter massive delays on logon times, caused by this:

 

"Do you trust this printer? Windows needs to download and install a software driver from the \\%servername% computer to print from %printername%. Proceed only if you trust the \\%servername% computer and the network."

 

The vbs scripts run sliently in the background, so the user cannot see this message to click Install driver, so it waits for it to time out and default to Cancel, and then it doesn't install the printer.

 

I have been researching this for a couple of days now, and I can't figure it out. I have tried using group policy for "Point and Print", allowing it in the forest and/or specified trusted servers, but that didn't work. Also tried using another Windows 7 machine to use GPO Management to disable warning messages, and that didn't work either. The messages still appear.

 

Any ideas?

[CHiLL]

Update;

 

Copying the script to the local machine and running it work. The printer installs without this popup message. So it seems to be something about it running from the server. However we have other scripts that run from that server (but don't install software, just change settings) and they work without a hitch.

 

Could it be something about it running from the UNC path? The server in question is classed as a Trusted Site in Internet Explorer because it's part of the local intranet, which is trusted.

[ojhext]

What version of Windows server 2003 are you using? if you have R2 use the print management to deploy your printers using group policy, you should have no problems then.

[3s-gtech]

You can also make the server a Trusted Location in Internet Explorer settings via GP. That may allow it to run properly.

[MYK-IT]

Use Group Policy Preferences to deploy your printers using targeting rules.

 

Works fine with Windows 2003 domain on Windows 7 (and Windows XP with client side extensions update installed)

 

I posted all that was required the other day, so should be easy to find.

 

Update:

Found it:

http://www.edugeek.net/forums/how-do-you-do/65490-install-colour-printer-only-staff-but-flexibly-post589550.html#post589550

[CHiLL]

Well, we aren't using group policy is because of two reasons;

 

1) Our print server is running Server 2003 (NOT R2)

 

2) (The main reason) We have tried it, but it would mean each room in the school having it's own group policy. We have a domain policy, which is inherited to everyone in school. Then a secondary policy (various, but only one is applied depending on the group of the user...such as students, staff or office). Then we'd have to apply a third policy on top of that to deal with printers.

 

Our systems aren't exactly...good. Very old and slow because we can't afford to upgrade them. Loading multiple GPs in sucession really does bring them to their knees.

 

The printers would have to be room specific, so we'd have to apply the GPs on a machine level, because the students and staff move around the school a lot depending on their lessons.

 

That's the reason why we have a centralised vbs script that sets a defined printer and sets defaults, as it doesn't effect system performance much.

[mac_shinobi]

Problem Adding Windows 7 64-bit print drivers to 32-bit Windows 2003 Print Server - Server Fault

 

How to install Windows 7 in-box printer drivers on Windows Server 2003

[MYK-IT]

Well, we aren't using group policy is because of two reasons;

 

1) Our print server is running Server 2003 (NOT R2)

 

2) (The main reason) We have tried it, but it would mean each room in the school having it's own group policy. We have a domain policy, which is inherited to everyone in school. Then a secondary policy (various, but only one is applied depending on the group of the user...such as students, staff or office). Then we'd have to apply a third policy on top of that to deal with printers.

 

Our systems aren't exactly...good. Very old and slow because we can't afford to upgrade them. Loading multiple GPs in sucession really does bring them to their knees.

 

The printers would have to be room specific, so we'd have to apply the GPs on a machine level, because the students and staff move around the school a lot depending on their lessons.

 

That's the reason why we have a centralised vbs script that sets a defined printer and sets defaults, as it doesn't effect system performance much.

 

Our printer server is also Windows 2003 (not R2) so GPP will work fine.

 

If you don't want to create an GPO for each (and every) OU the Computer [account] is located within, you could always have a Printer GPO at the top of the domain with all the printer mappings included (using Targeting Rules for the appropriate connections). Would take a while to set up, but you could then manage printers from one location, similar to your centralised VBS scripts.

[ojhext]

I was in you same position as you, but save your self the headache. Upgrade to 2003 R2 (Educational licence £30ish!!). The upgrade take minutes (if you have no plans to go too 2008 just now). Then use print management and GPO to deploy will save you time, and probably money in the long run. You then don't have to worry about loop back policies and VBscripts to get what you want to acheive. It really is that easy.....

[Reaper]

We managed to fix this with a setting in a GPO.

 

If you go to Computer Configuration > Administrator Templates > Printers and disable 'Point and Print Restrictions'

 

 

That solved it for us