This article provides a frequently asked question about using DSCHECK to purge print driver replication in XenApp 5.0 on Windows 2008.
The DSCheck utility is automatically installed as part of XenApp installation. Several new commands were added with each platform and rollup upgrade as part of bug fixes and enhancements. The version number was adjusted to align with the version of each updated platform or rollup binaries.
Q: What does dscheck /full printers /purge_replications do?
A: When you run dscheck /full printers /purge_replications at a command prompt, the following actions occur in the data store:
- The distribution jobs are deleted from the data store. The command searches for the DISTRIBUTION/DistributionJobs node and deletes all the subnodes under it.
- All the replication jobs are deleted from the database. The command searches for the PrinterRoot/PrintrDrivers-Replication node.
Under this node, there is one separate subnode for each driver that is due to be replicated. Each one of these subnodes includes information about how many target servers must be considered for that driver replication and which ones they are. After the command is run, all these subnodes are deleted and no effective driver replication occurs.
- The replication jobs are deleted at the farm level.
Note: In the Distribution Subsystem, to monitor how busy the replicators are, IMA uses the distribution subsystem. The distribution subsystem monitors the load on the XenApp server that is replicating the print drivers while they are distributed across the server farm. If the subsystem detects that the server is getting overloaded, it reduces the speed at which it sends the replication jobs. This can cause very large replication jobs to take several hours.