Azure AD Registered devices (including devices enrolled via the Company Portal itself) won’t even receive the management extension. $Shortcut.Arguments="shell:AppsFolder\Microsoft.CompanyPortal_8wekyb3d8bbwe!App"Īs another short aside – it’s worth mentioning that this requires an Azure AD Joined or Hybrid Azure AD Joined device because of the Intune Management Extension (the Windows service Intune users to run scripts). $Shortcut = $WScriptShell.CreateShortcut($ShortcutFile) $WScriptShell = New-Object -ComObject WScript.Shell $ShortcutFile = "$env:USERPROFILE\Desktop\CompanyPortal.lnk" Now our updated script will look like: $TargetFile = "C:\Windows\explorer.exe" IconLocation to a publicly available endpoint for the. If you’re interested in this approach, also comment below, and I’ll work on a follow up blog post. One easy answer to the icon problem is deploying the icon as a Win32 app in Intune, copying it to the temp directory, and then running the script. If you’ve found a way to extract the icon during the script let me know! I’ve tried a few methods of extracting the icon on the fly but they simply produce a blank icon. exe) file that can be used as an icon for a shortcut location. The problem is that Microsoft Store apps don’t expose the. To configure the icon location of the shortcut, add an additional line to the PowerShell script: $Shortcut.IconLocation = "c:\LocationOfYourIcon.ico" You’ll probably have noticed that the Icon for Company Portal is set to a File Explorer icon. Make sure that you’re also deploying the Microsoft Store app itself! PowerShell script deployment in intuneĪnd then you should be good to go! Here’s how the desktop shortcut looks on my test device: Deployed Windows 10 App shortcut You can do this by going to the Microsoft Endpoint Manager admin center, selecting Devices > Scripts > Add > Windows 10. Once we have the PowerShell script ready, upload to Intune and deploy to the device. Properties of Microsoft Store app shortcut
0 Comments
Leave a Reply. |