![]() The next step is to create a custom Windows Installer package to deliver the layout file. \LayoutModification.xml -UseDesktopApplicationID To export the Start menu layout, I’ve used the following command - note the use of the UseDesktopApplicationID switch which will make pinning desktop application shortcuts as tiles successful.Įxport-StartLayout -Path. It’s likely you’re familiar with this approach. To package a customised Start menu, we need to create the desired layout and export it with the Export-StartLayout command. Fingers and toes crossed then that this approach works. The Enrolment Status page tracks security policies and line-of-business (MSI) applications, so a custom default Start menu will have to be packaged into an MSI. With the availability of the Windows Autopilot Enrolment Status page in Windand above, plus the recent addition of the feature to ‘ Block device use until these required apps are installed’, we might have an opportunity to deploy a customised default Start menu. Additionally, I’ve had a crack at using PowerShell to pin and unpin tiles from the Start menu, but found that I can’t interact with the shell (or at least the pin / unpin has no effect) when the script is delivered via Intune. PowerShell scripts can be used to remove user and system provisioned Store apps (I have a couple of scripts in my Intune GitHub repository) however, PowerShell scripts in Intune can only be targeted to users and don’t fire until after the first logon. That can be hours after the user has provisioned the PC. Compounding the issue of default apps pinned to the Start menu is that some of them aren’t actually installed, so removal won’t occur until the Store downloads and installs updates. UWP / Microsoft Store apps can be targeted for removal, but those apps won’t be removed until well after login. One size does not fit all, and users should be able to customise the Start menu to suit their style. The administrator can define a Start menu, but that’s a policy, not a preference. Over-the-air provisioning of PCs via Windows AutoPilot & Azure AD, Microsoft Intune (or insert your MDM solution here), limits the possibilities of customising the target PC before the user logs on. The default Start menu, especially on Windows 10 Pro, is far from enterprise ready right? Take a look at this mess: User experience is still important though and a large part of that experience in an enterprise environment, is the default Start menu. ![]() The promise of a modern management approach to deployment and management of Windows 10 is that you no longer create and manage a custom SOE image. Improve the end-user experience on Windows Autopilot provisioned, and Microsoft Intune managed Windows PCs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |