4.7 KiB
title, description, keyboards, ms.prod, ms.mktglfcycl, ms.sitesec, ms.localizationpriority, author, ms.author, ms.date
title | description | keyboards | ms.prod | ms.mktglfcycl | ms.sitesec | ms.localizationpriority | author | ms.author | ms.date | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Enable or block Windows Mixed Reality apps in the enterprise (Windows 10) | Learn how to enable or block Windows Mixed Reality apps. |
|
w10 | manage | library | medium | jdeckerms | jdecker | 11/09/2017 |
Enable or block Windows Mixed Reality apps in the enterprise
Applies to
- Windows 10
Windows 10, version 1709 (also known as the Fall Creators Update), introduces Windows Mixed Reality. Organizations that use Windows Server Update Services (WSUS) must take action to enable Windows Mixed Reality. Any organization that wants to prohibit use of Windows Mixed Reality can block the installation of the Mixed Reality Portal.
## Enable Windows Mixed Reality in WSUSTo enable users to download the Windows Mixed Reality software, enterprises using WSUS can approve Windows Mixed Reality package by unblocking the following KBs:
- KB4016509
- KB3180030
- KB3197985
Enterprises devices running Windows 10, version 1709, will not be able to install Windows Mixed Reality Feature on Demand (FOD) directly from WSUS. Instead, use one of the following options to install Windows Mixed Reality software:
-
Manually install the Mixed Reality software
-
Download the Microsoft Windows Holographic Desktop Feature on Demand package.
-
Open a command prompt as administrator and run the following command to install the package:
dism /online /add-package /packagepath:"path to the cab file"
-
Go to Settings > Update & Security > Windows Update and Check for updates.
-
-
IT admin can create Side by side feature store (shared folder)
You can use the AppLocker configuration service provider (CSP) to block the Mixed Reality software.
In the following example, the Id can be any generated GUID and the Name can be any name you choose. Note that BinaryName="*"
allows you to block any app executable in the Mixed Reality Portal package. Binary/VersionRange, as shown in the example, will block all versions of the Mixed Reality Portal app.
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Add>
<CmdID>$CmdID$</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/PolicyManager/My/ApplicationManagement/ApplicationRestrictions</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
<Type xmlns="syncml:metinf">text/plain</Type>
</Meta>
<Data>
<RuleCollection Type="Appx" EnforcementMode="Enabled">
<FilePublisherRule Id="a9e18c21-ff8f-43cf-b9fc-db40eed693ba" Name="(Default Rule) All signed packaged apps" Description="Allows members of the Everyone group to run packaged apps that are signed." UserOrGroupSid="S-1-1-0" Action="Allow">
<Conditions>
<FilePublisherCondition PublisherName="*" ProductName="*" BinaryName="*">
<BinaryVersionRange LowSection="0.0.0.0" HighSection="*" />
</FilePublisherCondition>
</Conditions>
</FilePublisherRule>
<FilePublisherRule Id="d26da4e7-0b01-484d-a8d3-d5b5341b2d55" Name="Block Mixed Reality Portal" Description="" UserOrGroupSid="S-1-1-0" Action="Deny">
<Conditions>
<FilePublisherCondition PublisherName="CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" ProductName="Microsoft.Windows.HolographicFirstRun" BinaryName="*">
<BinaryVersionRange LowSection="*" HighSection="*" />
</FilePublisherCondition>
</Conditions>
</FilePublisherRule>
</RuleCollection>>
</Data>
</Item>
</Add>
<Final/>
</SyncBody>
</SyncML>