Co-Management of Office Click-to-Run apps Workload
This post is about co-managing the Office click-to-run apps workload between Configuration Manager and Intune. A co-managed device gives you the flexibility to use the solution that works best for your organization by allowing it to be managed concurrently with both Configuration Manager and Intune. Lean more about co-management here: http://aka.ms/comanagementTrying Out Autopilot Hybrid Join Over VPN In Your Azure Lab
As an IT admin you plan to ship new devices to end users which can join the on-premises AD (Active Directory) by leveraging Autopilot with Intune for device management. This post is a walkthrough of evaluating the Autopilot Hybrid join over VPN scenario in a lab environment hosted in Azure.Rename Hybrid Joined Computers deployed via Autopilot
Traditionally, IT pros spend a lot of time building and customizing images that will later be deployed to devices. Windows Autopilot introduces a new approach. From the user's perspective, it only takes a few simple operations to make their device ready to use. From the IT pro's perspective, the only interaction required from the end user is to connect to a network and to verify their credentials. Everything beyond that is automated.Update Compliance on Co-Managed Devices
Organizations today are looking for an integrated endpoint management platform which can ensure all devices whether owned by the business or personally owned stay secure, are managed and always up to date. This demands the most secure desktop and mobile experiences without compromising user flexibility. Configuration Manager Co-Management opens the gateway to interconnect the investments made on-premise while attaching it with the power of modern cloud-based solutions like Microsoft 365 & unlock its full potential. A co-managed device gives you the flexibility to use the solution that works best for your organization by allowing it to be managed concurrently with both Configuration Manager and Intune. Lean more about co-management here: http://aka.ms/comanagementRemotely capture ConfigMgr client logs for Troubleshooting
This is a short blog post about remotely capturing ConfigMgr client log files to a file share for troubleshooting purposes. With the ever-increasing security, not all teams supporting endpoints necessarily have Admin access for troubleshooting. Part of which includes analyzing logs. You may experience scenario where the device is not even on corporate network and you need to capture logs.
