mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 19:33:37 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-10574249
This commit is contained in:
@ -844,17 +844,16 @@ The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to
|
||||

|
||||
|
||||
19. Click **File**, click **Save As**, and save the commands as **c:\VHD\pc1.ps1** on the Hyper-V host.
|
||||
20. In the (lower) terminal input window, type the following command to copy the script to PC1 using integration services:
|
||||
20. In the (lower) terminal input window, type the following commands to enable Guest Service Interface on PC1 and then use this service to copy the script to PC1:
|
||||
|
||||
<pre style="overflow-y: visible">
|
||||
Enable-VMIntegrationService -VMName PC1 -Name "Guest Service Interface"
|
||||
Copy-VMFile "PC1" –SourcePath "C:\VHD\pc1.ps1" –DestinationPath "C:\pc1.ps1" –CreateFullPath –FileSource Host
|
||||
</pre>
|
||||
|
||||
>In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not installed, you can try updating integration services on the VM by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server 2012 and 2012 R2 operating systems that are running the Hyper-V role service. You can also try running the following command from an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
<pre style="overflow-y: visible">Enable-VMIntegrationService -VMName PC1 -Name "Guest Service Interface"</pre>
|
||||
>In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not enabled in this step, then the copy-VMFile command will fail. In this case, you can try updating integration services on the VM by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server 2012 and 2012 R2 operating systems that are running the Hyper-V role service.
|
||||
|
||||
If the copy-vmfile command does not work and you cannot properly enable or upgrade integration services on PC1, then create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. The copy-vmfile command is only used in this procedure as a demonstration. After typing the script file manually, be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file.
|
||||
If the copy-vmfile command does not work and you cannot properly enable or upgrade integration services on PC1, then create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. The copy-vmfile command is only used in this procedure as a demonstration of automation methods that can be used in a Hyper-V environment when enhanced session mode is not available. After typing the script file manually, be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file.
|
||||
|
||||
21. On PC1, type the following commands at an elevated Windows PowerShell prompt:
|
||||
|
||||
|
@ -29,8 +29,8 @@ You can use these tools to configure access to Windows Store: AppLocker or Group
|
||||
|
||||
## <a href="" id="block-store-applocker"></a>Block Windows Store using AppLocker
|
||||
|
||||
Applies to: Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile
|
||||
|
||||
Applies to: Windows 10 Enterprise, Windows 10 Mobile
|
||||
|
||||
AppLocker provides policy-based access control management for applications. You can block access to Windows Store app with AppLocker by creating a rule for packaged apps. You'll give the name of the Windows Store app as the packaged app that you want to block from client computers.
|
||||
|
||||
@ -59,7 +59,10 @@ For more information on AppLocker, see [What is AppLocker?](../keep-secure/what-
|
||||
## <a href="" id="block-store-group-policy"></a>Block Windows Store using Group Policy
|
||||
|
||||
|
||||
Applies to: Windows 10 Enterprise, version 1511
|
||||
Applies to: Windows 10 Enterprise, version 1511, Windows 10 Education
|
||||
|
||||
> [!Note]
|
||||
> Not supported on Windows 10 Pro.
|
||||
|
||||
You can also use Group Policy to manage access to Windows Store.
|
||||
|
||||
@ -89,7 +92,7 @@ When your MDM tool supports Windows Store for Business, the MDM can use these CS
|
||||
For more information, see [Configure an MDM provider](configure-mdm-provider-windows-store-for-business.md).
|
||||
|
||||
## Show private store only using Group Policy
|
||||
Applies to Windows 10 Enterprise, version 1607.
|
||||
Applies to Windows 10 Enterprise, version 1607, Windows 10 Education
|
||||
|
||||
If you're using Windows Store for Business and you want employees to only see apps you're managing in your private store, you can use Group Policy to show only the private store. Windows Store app will still be available, but employees can't view or purchase apps. Employees can view and install apps that the admin has added to your organization's private store.
|
||||
|
||||
|
Reference in New Issue
Block a user