Windows 7 x64 and printers hosted on Windows server 2003

The first obstacle which I've had to overcome that was worthy of a post is regarding network printer installations on a Windows 7 64 bit client. Nice and easy you say, however our printer servers are running Windows server 2003 32bit and when I try to connect to them from a Win7 client, it tells me no drivers are available and that's that.

Well I found an easy solution to allow Win7 clients to install these printers ok and avoid having users go and browse for drivers etc. Users are stupid and if you give them a choice, they will pick the wrong one.

Here's what I did

Jump onto your Windows server 2003 box and open printers and faxes
Right-Click on one of your network printers and properties
Click on the Sharing tab
Click on the Additional Drivers button
Tick the box for x64 (see below)
Now browse for your Windows Server 2003 x64 drivers (which you downloaded in advance!) and let the server install them.

Despite those being drivers for Windows Server 2003 x64, my Windows 7 x64 clients happily installed the printer and are able to print just fine.  We use leased Toshiba e-Studio multi function printers which are a great idea for cost effective communal office printing rather than operating expensive individual laser-jet printers but this is a blog topic for another day.

ThinkPad W510 with unknown device PCI\VEN_8086&DEV_4239

The new Lenovo website launched in the last month or so has been the brain of my working life. I visit that site like 10 times a day and since it has changed it has pretty much made my working life hell.

Today's challenge saw me build a ThinkPad W510 laptop with Win7 x64. All went well until I was left with one ? in device manager and it was the wireless adapter. System update didn't find drivers for it so I was left to visit the wonderful new site and pull the driver manually. This is run of the mill usually and wasn't bothered however after downloading and trying every wireless driver listed for a W510 I still had no joy.

Anyway I googled the device Instance ID of PCI\VEN_8086&DEV_4239 (from device manager) and found the type of wireless adapter in this machine is the Intel Centrino(R) Advanced-N 6200 AGN.
I went to Intel's support website and looked for the drivers - and the latest version listed is currently 14.1.1.0 which i downloaded and installed. Still no driver loaded after running setup.

I then saw in the small print that you needed to use a previous release 13.5.0.6 for win7 x64.

http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=19856

I downloaded this and it picked up my wireless adapter and installed fine!

I've achieved nothing today except this so thought it might help someone else.

But why doesn't system update pick it up nor do they list this driver on their site when i narrow my selection to ThinkPad W510.. because they are clowns I tell you

Installing Printers on a Win7 machine without Admin Rights

OK so you've deployed Windows 7 to your clients and you have not given them local administrator rights (damn right in an enterprise environment).
However non administrator rights means no printer installations without a UAC prompt for admin credentials - which can prove a thorn in the side, especially if your users move around a lot and need to install printers at various locations.

This can be addressed via group policy.
I have managed to allow non-administrators to install network printers on their local machines by applying the following single GPO which apply these two settings:

Computer Configuration -> Policies -> Administrative Templates -> System/Driver Installation
Allow non-administrators to install drivers for these device setup classes = Enabled
     Allow Users to install device drivers for these classes:
          {4D36E979-E325-11CE-BFC1-08002BE10318}
          {8FCEE422-B109-4758-9A6E-5BAB7B37996F}

Computer Configuration -> Policies -> Administrative Templates -> Printers
Point and Print Restrictions = Disabled

How to Configure LDAP on HP LaserJet Multifunction Printers

One of the convenient features of the HP LaserJet Multifunction Printer (MFP) series is the ability to populate the Control Panel with network user email addresses by utilizing ldap. This function is especially useful in Windows Active Directory environments. Once ldap connectivity is established with a domain controller, network user changes are immediately displayed and accessible at the printer. This article will review the minimal steps needed to configure ldap connectivty between an HP MFP and Windows Active Directory.
 

The following screen shots are from a M3035 MFP. The network environment consists of a Windows Server 2003 based domain and Exchange 2003.

First access the MFP web interface and select the "Digital Sending" tab

Then select "LDAP Settings"

Configure "Addressing Settings"  (click image for full size)  

Check off "Allow Device to directly access an LDAP Address Book" then fill in the login credentials. Note the "Username" is in UPN format. Included with the Windows 2003 Support tools is an ldap browser (ldp.exe) that can be used to find the proper UPN path for your environment. The "Find Server" function is optional and can be used to scan the network for ldap servers. You'll need to apply the credentials settings first before using "Find Server." Enter the LDAP Server ip address (your domain controller) manually if you already know it.

Fill out Searching the Database fields (click image for full size)

Enter the UPN path to the Active Directory container where all your users reside in the "Search Root" field. Select "Active Directory Defaults" from the drop down menu then apply your settings and select "Test."

Active Directory user name and email addresses should now be accessible under the Scan to Email function at the printers Control Panel. These settings were successfully configured and tested more recently on a newer HP M4345 MFP printer and should apply to most if not all of the MFP series machines. If you recieve a fail status, re-check your credentials configuration and ldap server address settings. Comments or questions welcomed.