Internet Explorer start tile not working with the PowerShell Import-StartLayout

By | March 26, 2018
Share

Here is a working configuration for importing a “Internet Explorer” tile to the Start screen using the Import-StartLayout PowerShell cmdlet.  This was tested on Win 10 1703.

Here is my exported start layout.  I had to manually switch out the %APPDATA% variable with the %ALLUSERSPROFILE% to get it working.

<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
  <LayoutOptions StartTileGroupCellWidth="6" />
  <DefaultLayoutOverride>
    <StartLayoutCollection>
      <defaultlayout:StartLayout GroupCellWidth="6">
        <start:Group Name="">
          <start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\TeamViewer 12.lnk" />
        </start:Group>
      </defaultlayout:StartLayout>
    </StartLayoutCollection>
  </DefaultLayoutOverride>
</LayoutModificationTemplate>

I also copy the “Internet Explorer.lnk” shortcut to the start menu before performing the Import-StartLayout to ensure the LNK is available.

Here is my PowerShell App Deployment Toolkit scriptlet:

Copy-File -Path "$dirFiles\Internet Explorer.lnk" -Destination "$envProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk"
Import-StartLayout "$dirFiles\Ts12StartLayout.xml" "$envSystemDrive\"

 

3 thoughts on “Internet Explorer start tile not working with the PowerShell Import-StartLayout

  1. Sebastian

    Thanks for your hint. We had the same problem.

    Is Copy-File the right cmdlet? I think it’s Copy-Item.

    Thx
    Sebastian

    Reply
    1. Brian Gonzalez Post author

      Sebastian,

      This example is using the PowerShell App Deploy toolkit’s Copy-File function. If you haven’t tried App Deploy Toolkit, give it a shot. Its extremely useful and free.

      Reply
  2. Juhana Nyman

    Hi Brian, We’ve had problems with the custom Start layout since 1703, we use the customization through Provisioning Package or GPO. What we found is that we should use DesktopApplicationID instead of DesktopApplicationLinkPath in the XML. This is mentioned in some MS documents. It seems that Export-StartLayout has not caught up with the Import-StartLayout or forced Start layout policy requirements…

    We obtain the AUMID (used By DesktopApplicationID) with Get-StartApps. This still requires the shortcut to be in Start menu, but does not care about the correct path to the .lnk file. With this the Start layout seems to work always as supposed.

    Reply

Leave a Reply

Your email address will not be published.

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.