8 GB RAM - we’ve been able to deploy a VM with 4 GB RAM and run the publisher comfortably.The real world environment that I’ll cover in this article differs from the system requirements in two ways: The documentation covers the system requirements. The Patch My PC Publisher is a Windows service and console application that must, of course, run on Windows. The customer does have presence in Microsoft Azure to run virtual machines for a number of infrastructure roles, thus the Patch My PC Publisher server is deployed into Azure. Patch My PC is configured to package a relatively high number of application packages and updates, and push these into the Microsoft Intune tenant.
The environment isn’t particularly large in terms of devices however, they do have a wide range of applications deployed across managed desktops, in part due to the technical nature of their business and developers on staff. The example I’m using for this article is a customer environment that is cloud native - all Windows PCs are Azure AD joined and managed with Microsoft Intune, and no Active Directory domain exists.
In this article, I’ll provide an approach to deploying the Patch My PC Publisher into Microsoft Azure, with costs, using a real world example. A virtual machine hosted in Azure is a natural choice for these organisations.
Patch My PC is a great solution for managing Windows application packages for Microsoft Endpoint Configuration Manager and Microsoft Intune.Ĭloud native or cloud hybrid organisations, particularly those who are using Microsoft Intune only to manage Windows desktops, will need to consider where to run the Patch My PC Publisher.
0 kommentar(er)
