Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We're running Microsoft Dynamics AX 2009 on Windows Server 2008 R2. Users access the rich client via TS Remote App. We have enabled TS Easy Print to avoid issues managing the various required print drivers which would otherwise be required. However, I've been told that when running certain reports in AX there are performance issues caused by AX contacting the client over the WAN to pull across the relevant print settings (prior to the report running, even if there's no intention of printing the eventual output). The proposed solution is to install print drivers onto the TS servers, but this then breaks our TS strategy.Searching the web, I've found that it's possible to setup printers on the AOS server and then configure an option "connect to printers on this server" for the AOS. Could this give us a workaround whereby we could host a PDF printer on this server which reports could use to get their settings instead of pulling data from the users' machines?Has anyone faced this issue before; if so what solutions have you found that work?Do you know where I could read up on this reporting / printing architecture to get a better understanding of what AX is doing under the covers?
AOS printers should in general only be used for batch printing and specialized printing (let say you always want packing slips printed on a specific printer etc.) . Client printing is different though. There is nothing wrong with your TS strategy and you should stick to it. AX will check as you correctly point out what the capabilities are of the printer, even if it is printing to screen. A printer that is not setup correctly on a print server here may cause severe performance ssues. Check bidirectional settings and make sure it is off. Otherwise it may be some advanced features etc. depending on printer model.
We managed to do it by redirecting the print jobs using third party software it's working faster .this is the product
this is my preference and my own opinion .
Business Applications communities