asked on

Automate Printer install With KIX

I've used KIX scripting as a network administrator for a long time now. Seems that with the release of Windows 7 and Windows Server 2008/(R2) there have been some challenges with the following command:

$Return=AddPrinterConnection("\\server\printer")

Seems as though KIX used to be able to install the printer driver in the Windows XP x86 environment, and now if the Windows 7/Vista account has only "Domain User" rights, and the printer driver needs to be installed, it will prompt for admin credentials. This is ok for one or two workstations, but is a real pain if you have to deploy a new printer to an office of 50 + workstations. Anyone know of a good way around this? I'd really like to stick with the Kix script as I am familiar, but is there a better way?

One great feature with KIX is that you can deploy based on group membershipt and subnet. Any other solution offer this functionality? Thanks fellow admins!!!!!

ProfessorBindokas

Is your OS 64 bit? If so, the problem may be linked to the fact that on 64 bit 7/Vista the drivers\etc directory is excluded from the wow64 File Redirection feature. Your script may simply not be finding the location and issue may not be directly linked to an admin rights problem. Pulled out quite a few of my hairs till found the exception to redirects.

There is a thread on the MSDN library, which covers this: http://msdn.microsoft.com/en-us/library/aa384187(VS.85).aspx

Hope this helps

ProfessorBindokas

Hi, were you able to solve the problem? Is there any additional information you need?

ASKER CERTIFIED SOLUTION

tarkmyler

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial