![]() ![]() The school’s AzureAD subscription needs to be Premium (P1 or P2) (in New Zealand, this is included in the National Schools Agreement between Microsoft and the Ministry of Education) and provides a further compelling reason for organisations to base their identity on Azure AD. An MDM service, such as Microsoft Intune, provisions the client device with policies needed to connect Azure Active Directory to Windows Print service and Discovery service.Windows Print service and Discovery service endpoints are registered with Azure Active Directory to enable the client device to retrieve the required user authentication token to use against these services.Hybrid Cloud Print using Azure Active Directory as the user identity provider.It’s important to recognise that this remains a hybrid cloud solution as it still requires on-premise servers running Discovery Service and Windows Print Service via IIS endpoints. With this announcement there are six new policy CSP in Intune to assist the hybrid cloud printing which enable the client device to know where the IIS service endpoints are and which Azure tenant information to authorize against. This is an important step towards encouraging schools and system integrators to start using Mobile Device Management tools such as Intune in combination with AzureAD as the ability to deliver a cloud printing service remains a critical feature request from schools. And it’s secured by Azure Active Directory, so you and your users still benefit from features like multi-factor authentication, identity protection and single sign-on (SSO). Best of all, your existing printer management scripts, tools, reports, and procedures will continue to work as is. Hybrid Cloud Print is built on top of the Windows Print Server role, so it supports traditional domain-joined devices in addition to Azure AD joined devices. ![]() Ignite 2017 Overview of Hybrid Cloud Print.Here are some important links to get started: I hope this post was helpful and please feel free to reach out to me or correct me in any of the steps.An overview of how AzureAD Hybrid Print works Hybrid Cloud Print is awesome when your machines that are cloud native cannot speak to a Domain Controller Powershell is your friend, take some time to get to know how it ties in with Azure as well as your other technologies. Step 6.2 : What does it look like when I query a Cloud Printer? Step 6.1 : What does it look like when I try and Publish a new Printer? Step 6 : Choose which Administrative task you would like to perform Step 5 : The Script will ask you for the Native Application and will list your available applications to choose from. Step 4 : The Script will ask you for the Enterprise Cloud Print application ( /ecp application) and will list your available applications to choose from. Step 3 : The Script will ask you for the Discovery Endpoint application (Mopria or /mcs application) and will list your available applications to choose from. Step 2 : Execute the script and enter your Azure Account Name that has access to the HybridCloudPrint Azure AD Applications ps1 file so you can run it on a Windows 10 Machine. Step 1 : Get the Powershell script from Github and save it as a. The username and password of the printer. The Google Cloud Print ID of the printer. You will be prompted to enter the following information: 1. Also Ensure you have access to the Print Server as you will need to run a command to query the SDDL for the printer. First, open the Google Cloud Print settings on your computer. ![]() ![]() Benefit from over 13 years of experience in professional printing solutions with more than 3.5 million users worldwide. Please find the code published in GitHub which will hopefully make your life in publishing Printers to your new Hybrid Cloud Print Solution, just a little easier.īefore running this ensure you have the AzureAD and AzureRM, PublishCloudPrint Modules installed. Print on the go with your laptop or at work to your connected printer, e.g. You will see you can only publish Printers from a Windows 10 machine with an account that has permissions to do so. This involves a lot of careful typing and actually knowing each component off by heart(Notepad) and ends up turning Powershell into PowerHell. If you read through the docs article you will see the example Powershell on how to publish, unpublish and query Cloud Printers after the setup. My main issue was not so much with building the solution but the way you publish the cloud printers afterwards. Stay close to our official document – īy not deviating from the above document you not only make your own life easier, but the ones who have to learn the tech after you have left/ passed the technology to someone else. If you have never built this before, it isn’t hard but there are a lot of moving parts. I recently had the opportunity to build a Hybrid Cloud Print Solution. ![]()
0 Comments
Leave a Reply. |