After working with one customer, we have included the Sage 50 pre-configured XML in the guidance, which is downloadable in the PolicyPak Portal.

Use this video to see how to get the guidance and use the XML file we’ve pre-created:

https://kb.policypak.com/kb/article/175-installing-applicationsandpreconfiguredrules/

That being said the same customer reported that when opening a report, Sage will hang for several minutes while attempting to “Look for a printer.”

The customer’s own remediation was to elevate the Print spooler also needs to be elevated (c:\windows\splwow64.exe).

However, this is likely more than required, and instead, we would advise to merely attempt to change the integrity level of the spooler using these directions:

https://kb.policypak.com/kb/article/165-09-i-elevated-an-application-but-drag-and-drop-between-the-elevated-and-other-nonelevated-applications-isnt-working-anymore-what-can-i-try/

Both avenues to adjust the spooler service are “use at your own risk.”

We here at PolicyPak no longer have Sage 50 to test, so this is just us passing this information along.