Hello,
We have an AX 2012 R2 CU 6 environment, with a single virtual AOS running on server 2008 R2, a physical SQL 2012 box for the AX database, and AX clients installed directly on Windows 7 workstations (no RDS).
My question for the group pertains to how the AOS handles printing in batch. Our production scheduler manually releases work orders from his workstation multiple times during the day (Production Orders - select the order to be released - Production order fasttab - 'Release'. When he does this, he prefers to select the option 'Batch processing' on the General area of the Batch tab so as to keep his client from locking up during the release process.
When he releases this way, does the AOS require that the label printer object that the release process is using be installed on the AOS for any reason? I don't believe it does, but the printer is installed on the AOS at this point, and I don't want to affect any other processes if I make changes to it.
The reason for the question is outlined below, if anyone's interested... it's causing me much lost sleep right now.
We've recently been experiencing performance and print issues. Troubleshooting has let me to a problem on our AOS that, if not the cause of our issues, certainly cannot help. In the registry on the AOS, the HKU - .DEFAULT hive has grown to over 8 GB in size.
Analysis of the HKU-.DEFAULT hive showed that the offending keys live in the Software - Seagull Scientific folder, specifically a sub-folder called @CSR|JD-FS2, which corresponds to a network printer that is installed on the AOS (JD-FS2 is our print server). Seagull Scientific makes the drivers that we use for our DataMax label printers.
I contacted Seagull tech support, who state that the problem is resolved with a newer driver set. Unfortunately, this won't solve my AOS registry problem. I've attempted the MS-proscribed registry compression methods, but since the issue isn't whitespace in the registry database, the process doesn't help. I'm going to have to physically delete the key and test like crazy to ensure that nothing went bad.
Scott
