I wanted to throw this out there to see if anyone has seen the same conditions and PROBLEMS with the newer Dymo Connect app. Or, if I am the only turkey cursed with supporting these things :)
We have many other session hosts running both Win10 and Win11 that use the Dymo Label v8 software along with TSPrint and is quite successful. BUT, using the newer Dymo Connect app it just seems to be completely "incompatible" with something on these multi-session hosts.
I have tested it on Win10, Win11, with and without several different apps installed but every time as soon as i install Dymo Connect (all versions so far) the wmiprv and spools processes consume alot of CPU. With just 1 user logged in the CPU usage is only about 2-7% for either but with several people logged in the processes will spike up to nearly 50% sometiems or higher. There does seem to be something funtionally different about this app version the older v8 apps and i even had to find a workaround (disable bi-directional support on the printer) to get the redirected printing to work at all but even that seems to come and go.
Dymo Connect on multi-session hosts
We have one client that uses Dymo Printers. Their custom MS Access based “app” that uses them prints directly to the virtual printer object from TSPrint with bi-directional printer support disabled. We only have the horrible dymo apps on their physical Devices and not on the virtual
I think I have a client with the same issue and found this post while researching Windows 11 Session Host resource issues. I recently created a new Windows 11 session host for this client and I'm constantly getting high CPU alerts from our RMM software. It seems much worse with Windows 11 vs. Windows 10.
I just checked resources on one of the session hosts and Spooler subsystem app and WMI provider host are at the top.
We tried to get them to use Microsoft Word to print labels instead of the Dymo software, but were unsuccessful. I'm now thinking we need to try again.
Phil Long - What model label printers are you using? LabelWriter 550 Turbo here.
Steve Hopler That is the “exact” behaviour we were seeing with Dymo Connect and i couldnt quite figure out what the underlying issue was. We were using the 550 series as well and ultimately switched to the Brother brand of label printers.
The QL-800 is a good fit and works just fine on the Win11 session hosts both with built-in printer redirection and TSPrint.
Phil Long - Thanks. I'm going to see if we can temporarily uninstall Dymo Connect from one the client's Session Hosts to test.
Please sign in to leave a comment.
Comments (4 comments)