Thanks again for your help peter. Just a little background info that I found out yesterday from the vendor. This is a known issue that they have with the VMware View Agent above v. 5.0. The vendor told me they have been working with VMware to resolve the issue since VMware View v. 5.1, but they were not aware of any fix. Their recommendation as a workaround was to create a VMware View environment with the Connection/Compose server running v. 5.1 and have all the agents running v. 5.0. After reading the documentation from VMware, I don't believe that compatibility will work.
While still working with the vendor for some clarification, I came across another thread that you were helping with: https://communities.vmware.com/thread/417217?start=15&tstart=0
After reading this thread, this sounds very much like what we are running into. The printer that we are working with is a Epson TM-U3250. Do you think an upgrade to v. 5.3 and the registry modification would resolve this issue as well? We are a brand new View environment with 5.2, and I would rather go forward than have to go backward and piece things together.