{"id":5468,"date":"2022-08-09T13:33:09","date_gmt":"2022-08-09T17:33:09","guid":{"rendered":"https:\/\/www.uniprint.net\/?p=5468\/"},"modified":"2022-08-11T08:18:49","modified_gmt":"2022-08-11T12:18:49","slug":"client-side-rendering-print-solution","status":"publish","type":"post","link":"https:\/\/uniprint.net\/en\/client-side-rendering-print-solution\/","title":{"rendered":"Client Side Rendering \u2013 Is it a viable Enterprise Print Solution?"},"content":{"rendered":"
Oh man! Client side rendering, who thought this was a great idea?<\/p>\n Ok so you basically turn your entire client machine base into print servers right!?<\/p>\n Well, yes because that\u2019s effectively what you are doing if you adopt a client side rendering print method.<\/p>\n So why is client side rendering so popular in many IT communities<\/a> and why is it pushed so heavily by the printer hardware vendors?<\/p>\n Simply put, it reduces print servers and prevents print traffic from traversing the WAN.<\/p>\n These reasons sound great, but for all intents and purposes it creates more printing issues than you had in the first place.<\/p>\n Let\u2019s look at the scenarios why client side rendering is employed and see what the effect is:<\/p>\n So, we don\u2019t want print servers, like\u2026 anywhere!<\/p>\n Client side rendering solutions have been widely adopted\u00a0in recent years and there are many companies with products that can help achieve the management ‘overhead’.<\/p>\n These solutions are sometimes called Direct IP printing or Serverless Printing<\/a>.<\/p>\n You start by having a centralised server. Ok we failed at the first hurdle, right? Yes, you need a server to implement Server Less Printing *Sigh*.<\/p>\n This server manages all printer and user information like which user wants which printer and the associated information about those printers, drivers, IP addresses etc.<\/p>\n Then a software client is installed on the user\u2019s machine which communicates to the centralised server and is responsible for mapping printers for the user that\u2019s logged in.<\/p>\n When a printer is required to be mapped the software client downloads the driver from the centralised server with which it then installs a direct IP printer.<\/p>\n Printing is now between the user machine and the printer, there is no remote provider involved in this printing process.<\/p>\n To answer let\u2019s look at the Pros and Cons on client side rendering:<\/p>\n 1. No localized print servers to manage either central (if you exclude the management server) or at the local offices for the users.<\/p>\n 2. If you adopt a Cloud architecture, then the print data remains local to the client machine and print traffic does not travel outside of the LAN.<\/p>\n 1. Client OS support. If you must download a printer driver, then the client OS must be compatible with the centralised server. In short, it needs to be a Windows client machine.<\/p>\n 2. With this architecture, all client machines have themselves been transformed into print servers, duplicated print servers at that.<\/p>\n 3. If you adopt a VDI or remote application strategy, then print isn\u2019t generated on your client machine so an additional print management solution is required.<\/p>\n 4. Printing in the cloud will inevitably send print traffic across the WAN which contradicts this implementation in the first place.<\/p>\n 5. Mobile printing in this architecture requires direct line of sight to the printer devices limiting user experience and options.<\/p>\n As you can see, this is no way near an enterprise print solution.<\/p>\n Interested in learning more about software defined printing solutions? Check out this free webinar on consolidating printer servers and reducing costs<\/a>!<\/p>\n <\/p>\n Let\u2019s now introduce the wildest adopted printing strategy; Secure Pull Printing.<\/p>\n If you are attuned with the world of managed print services, then you will undoubtedly be aware that every printer vendor and printer provider wants to lock you into their contracts.<\/p>\n They leverage the IT industries attraction to software by having secure pull printing software solutions<\/a> of their own.<\/p>\n However, they are scared\u2026<\/p>\n For print savvy IT people, you know why they are scared when implementing their MPS solutions in our modern architectures.<\/p>\n We don\u2019t like print drivers, but they need them.<\/p>\n We also don\u2019t like print data swamping our networks and chewing up our compute power for fun, but that\u2019s what their solutions do.<\/p>\n So, to manage their fear they rely on\u2026 you guessed it\u2026 Client Side rendering.<\/p>\n When you hit print using an MPS providers secure pull printing solution, the print job remains on the users client machine.<\/p>\n Only a ticket of the job information is sent to the centralised management software.<\/p>\n Great!<\/p>\n No print data is required to traverse the WAN and print drivers are kept locally on the user\u2019s client machine, genius!<\/p>\n Slight problem\u2026 My client machine is a laptop and you have it turned off in your bag because you are on the way out of the office for a very important meeting and you want to collect my print job as you leave.<\/p>\n What do you do?<\/p>\n You can\u2019t access your print job because your laptop is turned off.<\/p>\n The solution to this that inevitably will come back from the MPS vendor is: \u2018use local print servers\u2019.<\/p>\n OMG!<\/p>\n I am not going to continue to write about the vast amount of issues I get told about the solutions out there as I feel you get the point I am trying to make here.<\/p>\n You see the problem is not; keeping drivers away from centralised IT applications, VDI\u2019s or published web application servers, nor is the problem print data traversing the WAN.<\/p>\n The problem is that when you look to find a solution and start at the hardware you natively end up creating more issues than you started with.<\/p>\n In today\u2019s modern IT we never start building our solutions or strategy from the hardware.<\/p>\n We look at things purely through software nowadays and the hardware is irrelevant.<\/p>\n The solutions we build are omni-channel regarding the user and their user experience should be uniform.<\/p>\n Printing is no different.<\/p>\n To manage a printing problem or to build a printing strategy don\u2019t start with the hardware, start with building a software defined printing strategy.<\/p>\n What you will find is that printer hardware dependencies like drivers and print data become secondary concerns.<\/p>\n
<\/a><\/p>\nWhat is Client Side Rendering?<\/h3>\n
Is Client Side Rendering a Print Solution?<\/h3>\n
Client Side Rendering Pros<\/span><\/h2>\n
Client Side Rendering Cons<\/span><\/h2>\n
\n
\nClient Side Rendering with Secure Pull Printing<\/h3>\n
Software Defined Printing<\/h3>\n