We had a signed driver for our printers but due to how we want them to be setup we modiflied the rcf text file (turn of colour printing) which in turn stopped it from being signned. I read somewhere that we should be able to resign these driver within our domian (for use only on our domain) but unsure where we do this as can't find much info on this for a beginning. This is important to us as we don't want to make all our users local adminstrators just to insatll printers.

Hi, What is the model of the printer and the OS? Where did you get the driver? Please first check whether the following links help: Device Installation Types http://msdn.microsoft.com/en-us/library/ff541322.aspx Driver Signing http://msdn.microsoft.com/en-us/library/ff544865.aspx In the meantime, as the driver is provided by the printer manufacture directly, please contact the hardware vendor to ask for the proper driver or assistance on customizing the driver. Thanks for your understanding. Best Regards, NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Nina The driver was a signed driver from Ricoh, the issue is we have 40 odd offices with small network printers but no printer servers and as most of the hardware in the offices are laptops we don't have a local computer we can use as a pritner server. For this reason we install these printers using rundll32 printui.dll and Ip address. Even though the driver is signned to make sure the printer sets up correctly we add extra settings to the driver's RCF file so the printer isn't installed with colour as a default. This in turns increases the size of the RCF file and in turn makes the Offical Ricoh sign volided as the whole package size has changed. To get arround this I beleive we can use a local PKI to resign our changes but just unsure how (very new to PKI).

On Tue, 5 Jul 2011 21:20:44 +0000, Johnw230873 wrote: Even though the driver is signned to make sure the printer sets up correctly we add extra settings to the driver's RCF file so the printer isn't installed with colour as a default. This in turns increases the size of the RCF file and in turn makes the Offical Ricoh sign volided as the whole package size has changed. To get arround this I beleive we can use a local PKI to resign our changes but just unsure how (very new to PKI). While you may be able to sign the driver with a certificate from your internal PKI (though since the original driver is already signed I don't think you'll be able to do so) Windows won't recognize the driver as being signed properly. Drivers from 3rd parties that require a signature are submitted to Microsoft's Windows Hardware Quality Labs (WHQL)for testing and certification. Once the drivers have been certified, Microsoft signs the drivers. The operating system, for obvious reasons, only recognizes the WHQL signature. Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca I am the computer your mother warned you about.