It turns out that downgrade didn't help, and as soon as I tried to print again, the DCP directory expanded again. I had to delete network printer and Global Print drivers completely, then install printer specific drivers (in my case Versalink C7030), and connect printer again by IP, so it will use C7030 drivers instead of installing Global Print driver by default.
Has anyone found a good solution to this? We are having this issue in one of our sites and they have 2 Xerox 7830 devices, printing via a Windows 2008 Print Server. The driver installed on the printers on the print server are the Xerox 7830 PCL6 driver, NOT the global print driver.
I can only think that maybe, at some point, the global print driver was installed, and is remaining on the user's drive? How do we delete them?
Just noticed that too and then found this thread. This is really outrageous! A driver that copies all the user / computer data from the C drive to its own folder is somewhat scarry... Has the look of a malware infected driver.
Same thing here 10 to 15 GB on 2008 R2 server running Xenapp. We also found that after the DCPs are downloaded that we are running into issues with Excel crashing if you try and expand the margins. (WMI was a good catch too also see that too) Xerox has an article that I found explaining the DCPs and how to point it to a location on your network so you can manage what DCPs are install. This weekend I am going to try and point a couple of the Xenapp hosts out to a dummy folder and see if it stops the DCPs from doing whatever it is that they are doing.
Here is the article that I was referencing.
This problem is still present as of version 5617.700.0.0 of Xerox Global Print Driver. All the computers in our organization that have the Xerox drivers installed have this issue, we have discovered it because many users had they workstations locked due to missing free disk space on C: driver, the C:\Windows\System32\spool\drivers\x64\3\Xerox\Product Data\Public\DCPs can grow to 20 or more GBs.
After every boot I see WmiPrvSE (a system Windows process that among other things runs the printer drivers) using a full CPU core and writing to C:\Windows\System32\spool\drivers\x64\3\Xerox\Product Data\Public\DCPs
Please fix this as soon as possible or provide a workaround.
i think this is an issue with a older version of the driver
have you guys updated to the recent driver thay you can download on the xerox.com site?
I deleted the extra files yesterday. Today those extra folders were recreated , according to the timestamps this happend between 09:57-10:00 AM. I did not add any Xerox printer, did not restart or relogin during this time. What is happening here???
And on another note:
I found the same problem on our Windows Server 2008R2 terminalserver. Here the folder containing the extra files is:
So another Xerox driver, same problem. Something is going seriously wrong here.
We ran across a similar issue. The Client is running Windows 7 SP1 64bit, installed Xerox printer drivers are:
- Xerox ColorQube 9303 PS 5295.1700.0.0
- Xerox ColorQube 8900X PS 5351.500.0.0
The folder c:\windows\system32\spool\drivers\x64\3\xerox\Product Data\Public\DCPs\x2DMAMPZ\ was 15 GB in size, filling up the client´s harddrive.
It seems that during driver installation each and every non-standard folder was copied from the root of the PC´s C:\ drive to c:\windows\system32\spool\drivers\x64\3\xerox\Product Data\Public\DCPs\x2DMAMPZ\V5\ in addition to the folder "DMAM", which should have been the only folder to resize under this path.
What went wrong, why is this happening?
I know this topic is old, but we ran across a similar issue yesterday and I wanted to provide some additional information, although we don't yet know why exactly this is happening. We run Windows Server 2003 Terminal Services and noticed a few days ago that the C: drive was filling up. Investigation revealed that the folder getting all of the files was C:\WINDOWS\system32\spool\drivers\w32x86\3\Xerox\Product Data\Public\DCPs\x2UNIVSJ\V5.0. Files seemed to show up in there at random from a variety of different staff members. Today, we realized that the people whose files were winding up there were people who were logging on to the terminal server. We then realized that the files were copied while we were running a VBscript at logon that connects two Xerox printers to the local session. Our VBscript looks like this:
Set objNetwork = CreateObject("Wscript.Network")
objNetwork.AddWindowsPrinterConnection "\\ps\Xerox WorkCentre 7345 PS"
objNetwork.AddWindowsPrinterConnection "\\ps\Xerox EXi 570 Print Server"
That VBscript has been in place for months with no issues, so we're stil not sure what is going on, but preventing the script from running at user logon prevents the problem from happening.