One of the most important parts of check-in is label printing. When labels print without a hitch, your check-in experience stays as fast and easy as it should be. But if your Rock server lives in the cloud, a firewall might keep your server from connecting directly to your label printer. That’s where Cloud Printing steps in! With Cloud Printing, your labels print directly from the server, keeping check-in smooth and frustration-free, no matter where your server is hosted. Options for Printing Labels Before we dive into Rock’s Cloud Printing solution, let's look at all the options you have available. VPN Tunnel One way to get around the firewall is by using a VPN tunnel. This would open a secure pathway between your printer and your server, which would enable the server to print straight to the printer. While this method allows communication through the firewall, it has several downsides: Complex Setup: VPN tunnels can be difficult to configure, requiring technical expertise.Reliability Issues: They can be prone to interruptions, which can cause delays in printing.Cost: VPN services can be expensive, especially when factoring in ongoing maintenance.Security Risks: VPN tunnels, while secure, can introduce vulnerabilities if not properly managed.Maintenance: Regular upkeep and troubleshooting are often required.Possible Delays: Printing may take longer, which isn’t ideal during busy check-in times. Kiosk Printing Another option is printing directly from the kiosk. This method allows you to print labels without needing to connect the printer to your Rock server. While this is a valid and simple solution, it also comes with limitations. You need to download special kiosk software for kiosk printing to work. Local Network Printing If your Rock server is locally hosted (i.e., not in the cloud), you can print labels easily because your server and printer are on the same network. This is another straightforward and easily configured method. However, this approach has its own challenges. Difficult Scaling: As your organization grows, scaling a local network setup can be expensive and complicated.IT Requirements: Running a local network may require dedicated IT staff for maintenance, backups, and support.Physical Risks: Local servers are more vulnerable to physical damage, like natural disasters or power outages.Bandwidth: Your server’s connection to the internet is limited to your local provider’s connection to your building. Cloud Printing: A Better Solution Now that you’ve seen the challenges of other options, here’s the good news: Rock Cloud Printing makes label printing much simpler and more reliable. With Cloud Printing, you don’t have to worry about complex networking setups or direct communication between your server and printers. It’s all managed for you through a proxy device and a proxy service, two components we’ll introduce here. Let’s start with the proxy device. This is a physical device that handles communication between your Rock server and the printers on your internal network, bypassing any need for direct access to your local IP addresses, as pictured below. The proxy device can be any Windows check-in device you already have, or a small, dedicated computer like an Intel NUC. We recommend a dedicated device. Remember, you can always start small with a single device and scale up as needed, adding more based on performance requirements or redundancy goals. Now, what about the proxy service? The proxy service is a small program running on your proxy device that keeps an open line of communication with your Rock server. Think of it like a web browser. When you visit a page, your browser opens a connection to the website. But unlike a typical browser, the proxy service keeps this connection open continuously. This persistent connection allows the server to send commands to the proxy device in real time. Commands like “please print this label on Printer A.” The proxy device then relays the command to the printer(s) on your local network. For example, Rock might send a message to the proxy service saying, “please print this label on Printer A.” Since the proxy service is on your local network, it can reach Printer A, send over the label data, and voilà—your label prints without any direct connection between Rock and your internal printer network. That's a lot of "proxy" talk. It's not critical that you distinguish between proxy device and proxy service. Going forward, we'll simply refer to them both as Cloud Print Proxy. Why Cloud Printing Is a Game-Changer With Cloud Printing, you can say goodbye to complex network configurations. Since the Cloud Print Proxy takes care of all communication, there’s no need for extra VPNs or complicated setups. This feature is flexible and grows with you—one Cloud Print Proxy can handle multiple printers, making it a breeze to expand as your needs increase. And here’s the cherry on top: for larger organizations, adding multiple Cloud Print Proxies builds in a layer of reliability, so if one device goes offline, another jumps right in to keep check-in running without a hitch. How Many Cloud Print Proxies Do I Need? If you’re running a smaller campus with just a few check-in printers, a single Cloud Print Proxy will do the job. But realize that if this device goes down you'll no longer be able to print. For a larger campus with, say, 30 check-in printers, things are a little different. More printers mean more people checking in, which means lots of labels. If the Cloud Print Proxy goes offline in this scenario, all 30 printers stop printing—a much bigger hassle for your staff and volunteers! This is why it’s helpful to have multiple Cloud Print Proxies. With multiple Cloud Print Proxies running, one can pick up the load if another goes down. Rock automatically balances the load across all active instances, so no single proxy has to handle everything on its own. In environments with multiple Rock servers (i.e., a Web Farm setup), Cloud Print Proxies can connect to different servers to create redundancy across the whole setup. If one Rock server fails, Cloud Print Proxies connected to other servers will seamlessly keep things running. So, how many Cloud Print Proxies should you have? There’s no one-size-fits-all answer; it’s a balance of cost and risk. The cost includes any extra hardware and time to maintain it. The risk is the potential disruption in label printing if a Cloud Print Proxy fails. For a small campus, probably not much of a problem. The traffic is probably such that you can just handwrite labels quickly. A larger campus might not have that option, so may want to invest in multiple Cloud Print Proxies. Setting Up Rock Cloud Printing NoteEnsure WebSockets Are EnabledBe sure to review your IIS server configuration if it’s been a while. WebSockets must be enabled for Rock Cloud Print to function. The Internal Hosting guide explains exactly how to configure this. If you're using a Rock Cloud server, WebSockets are already enabled for you. Ready to set up Cloud Printing? Here’s how to get everything up and running. To set up Cloud Printing in Rock, you’ll need to add a Cloud Print Proxy for each campus or network. Multiple instances of a single Cloud Print Proxy can run on different PCs for load balancing and failover, but you only need one Cloud Print Proxy in Rock per network. For example, if you have three campuses, you’ll need three Cloud Print Proxies in Rock—one for each network—even if each campus has multiple PCs running Cloud Print Proxies. To add a new Cloud Print Proxy to Rock, go to Admin Tools > Settings > Check-in > Devices. There, create a new device and set the Device Type to "Cloud Print Proxy." Note, you don’t need to specify an IP address; the Cloud Print Proxy will report its own address to the server. Next, update each printer you’ll be routing through the proxy. Find the proxy device setting in the printer’s configuration and set it to the proxy device you just created. This lets Rock route printing tasks through the proxy for seamless communication with your printers. Finally, confirm that your kiosk configuration is set to use Server printing instead of Client printing. This ensures that all printing requests are handled by the server through the proxy device. Setting Up the Cloud Print Proxy To set up the Rock Cloud Print application on the Windows machine you’ll use as the proxy, start by downloading the installer from Admin Tools > Settings > Power Tools > External Applications in Rock. Run the installer, and once it completes, you’ll find the Rock Cloud Print application in your Start Menu, within the Spark Development Network folder. Open it, select Settings, and complete the information shown below. Server URL - Enter your server's URL, making sure it points directly to your Rock instance and bypasses any CDN that might be configured for your public-facing site. The Cloud Print Proxy requires direct access to Rock to function properly.Proxy ID - Add the Proxy ID, which can be either the GUID or IdKey of the proxy device you created in Rock. You can find these values on the device's detail screen under the Audit panel.b- Finally, choose a name for the Cloud Print Proxy. It’s helpful to make this name descriptive, especially if you plan to use multiple proxies. The name will be displayed when you check the status of your connected proxies, making it easier to identify each service. After saving these settings, navigate back to the Home tab to monitor the connection. It may take a minute or two for everything to sync. Once you confirm the proxy is connected, you can close the Rock Cloud Print application. The Proxy Service will run in the background and automatically start with Windows, so there’s no need to reopen the app unless you need to change configurations.