Traditional IT focuses on a single device platform, business-owned devices, users that work from the office, and different manual, reactive IT processes. User computing is going through a digital transformation. User context scripts will be ignored on WPJ devices and will not be reported to the Microsoft Intune admin center. Specifically, device context PowerShell scripts work on WPJ devices, but user context PowerShell scripts are ignored by design. PowerShell scripts, which are not officially supported on Workplace join (WPJ) devices, can be deployed to WPJ devices. For more information, see Intune Management Extensions prerequisites. Like I said though, I haven't specifically tested this with standalone Hyper-V, but PowerShell is not required on the Hyper-V server for this to work, just WMI, so this should work just fine.Once the Intune management extension prerequisites are met, the Intune management extension is installed automatically when a PowerShell script or Win32 app, Microsoft Store apps, Custom compliance policy settings or Proactive remediations is assigned to the user or device. If you want to see a screencast showing how it works first, particularly for Hyper-V, you can watch this one: And you can download the Hyper-V PowerPack here. To use Hyper-V you'll have to download the Hyper-V PowerPack from the PowerPack library (it's an optional component that doesn't come with the core product), but it should allow you to do a lot remotely and the scripts behind it are all open source so you can see how it works. It uses WMI to remotely manage services, processes, Hyper-V servers, event logs, and a bunch of other stuff plus it's completely customizable. PowerGUI is an MMC-like console built on top of PowerShell. I haven't tested this specific scenario, but you should be able to remotely manage this computer using PowerGUI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |