I am implementing a driver deployment with Samba. Every possible model of printer found an easy solution, except for Xerox Workcenter.

After browsing the Internet, I found that Xerox printer driver has to change some registry keys in order to work, keys which are changed by the executable downloadable on the manufacturer website. Do you know which key are impacted by the Xerox Workcenter GPD driver?

This corresponds to the error message I get while uploading to Samba, which asks the position of a file named as a registry key.

I browse Samba bug tracker and they did not specify which registry key are impacted.

I contacted Xerox itself, but despite that fact that we have a support contract and really a huge number of workstations, it seems that Xerox is not willing to help us.

  • I have used the freesoftware sourceforge.net/projects/regshot to see that there was a big impact on the windows registry. In addition, some files are deleted after the installation process making it dificult to transmit the driver throught SMB. – MUY Belgium Sep 8 '15 at 7:09

Which registry keys are impacted with Xerox Printer driver installation?

You can use Process Monitor from Microsoft's SysInternals to monitor registry changes.

  1. Start Process Monitor.

  2. Log results to a log file.

  3. Install Xreox Printer Driver.

  4. Stop logging.

  5. Look at the log file for registry changes.

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more.

Source Process Monitor


I am not affiliated with Process Monitor in any way, I am just an end user of the software.


Microsoft offers a tool called Attack Surface Analyzer that you can use to find this out. While it is intended to aid finding security-sensitive changes, it can find others too. It is a free download. I've had the best success running it on Win7, though it should support other OSes too.

What you do is start with a clean system (with ASA installed), and run one scan. This is the "baseline" scan. Then, install the program (or, in this case, driver) that will make changes to the system. Once the system is in the post-install state that you want to look at (i.e. after you first install the driver, or after you reboot post install, or after you configure an actual printer using the driver... or at more than one of these points) run ASA again and do a new scan. Then use ASA to generate a report that compares the new scan to the baseline scan. Registry changes (among many other things) will be in the report. If you do more than two scans, you can also compare them against one another to see the changes that are made from one scan to the next.


I have found the GPL program Regshot that can point modification to registry, see explanation http://www.howtogeek.com/198679/how-to-use-regshot-to-monitor-your-registry/ and download http://sourceforge.net/projects/regshot/ .

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.