Could not execute the following script C:\WINDOWS\PMCSnap\pushprinterc

[mtnhigh]

I have the following errors showing up:
Could not execute the following script C:\WINDOWS\PMCSnap\pushprinterconnections.exe. The system cannot find the file specified.

This GPO works fine but it is causing userinit on the clients. I have verified that pushprinterconnections.exe is located under C:\WINDOWS\PMCSnap on domain controller

Does pushprinterconnections.exe need to be copied to each desktop

thanks
Pietto

 

[IllogicallyLogical]

Have a look at the following article as it explains thoroughly what you are looking to do.

- Manage Printers with New Group Policy Features in Windows Server 2003 R2

http://technet.microsoft.com/en-us/magazine/2006.08.manageprinters.aspx

Here is an excerpt from the article that would likely pertain to the issue you are experiencing.

Pushprinterconnections.exe is a new R2 command that users or computers need to run. If you’re deploying printers to users, the .exe needs to be run in the user’s Login Script. If you’re deploying printers to computers, it needs to be run in the computer’s Startup Script.

The pushprinterconnections.exe program is found on your R2 server in the \windows\PMCSnap directory along with some other bits associated with the Print Management console (which I’ll talk about in a minute). You can see that in Figure 4. However, this isn’t where you run it. Your job is to take the file and plunk it directly into the GPO itself.

While editing the GPO, drill down to the script type (User Login or Computer Startup). Click the Show Files button. Next, copy pushprinterconnections.exe into the window that opens. Back at the properties of the script, click Add and locate and select the pushprinterconnections.exe file. Then click OK. If you want to enable the logging of troubleshooting information, type –log in the Script Parameters box. A per-user debug log file will be written to %temp% and a per-machine debug log will be written to %windir%\temp (these are totally different directories). It’s worth noting that you shouldn’t use the –log parameter in a production environment—unless you want the utility filling up your client machine hard disks with megabytes of log files.

If you are using Windows Vista™, you’ll see that this utility isn’t required; the ability to push down printer connections is built in. As a result, the first thing that PushPrinterConnections.exe does when you run it is to check if it is running on Windows Vista. If so, the utility simply exits. Network administrators don’t have to worry if Windows Vista clients accidentally ran pushprinterconnections.exe.

At this point, you should see the printers when you log in as the user or restart the computer. Note that these printers won’t change during background refresh after you’re already logged in because the pushprinterconnections.exe utility only runs at login or startup.

Joey
CCNA, MCSA 2003, MCP, A+, Network+, Wireless#