|
You are here |
petervanderwoude.nl | ||
| | | | |
oofhours.com
|
|
| | | | | In the first part, I set up Workspace ONE and integrated it into my existing Entra ID (Azure AD) tenant. In part 2, I set up apps and policies that should be deployed to my devices. That prepares me for the next step, provisioning new devices with Windows Autopilot. Configuring ESP Deep in the Workspace... | |
| | | | |
www.petervanderwoude.nl
|
|
| | | | | ||
| | | | |
jannikreinhard.com
|
|
| | | | | In this blog post I explain how to deploy a Win32 app via Intune. I have choos CMtracert because this tool is useful for troubleshooting and analyzing Intune logs. W32 applications must always be uploaded as .intunewin package. It is not possible to simply upload an .exe file. How to create such an .intunewin package... | |
| | | | |
oofhours.com
|
|
| | | As some of you have noticed, the naming convention allowed for Windows Autopilot Hybrid Azure AD joined devices isn't particularly flexible: You can specify a prefix (e.g. "AD-") and the rest of the computer name will be filled in with random characters and digits to pad the name to 15 characters. So you end up... | ||