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-10202987
This commit is contained in:
@ -47,9 +47,9 @@ Three features enable Start and taskbar layout control:
|
||||
>[!NOTE]
|
||||
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](https://go.microsoft.com/fwlink/p/?LinkId=623707) cmdlet.
|
||||
|
||||
- [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
||||
- [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
||||
|
||||
- In Group Policy, you use the **Start Layout** settings for the **Start Menu and Taskbar** administrative template to set a Start and taskbar layout from an .xml file when the policy is applied.
|
||||
- In Group Policy, you use the **Start Layout** settings for the **Start Menu and Taskbar** administrative template to set a Start and taskbar layout from an .xml file when the policy is applied. The Group Policy object doesn't support an empty tile layout, so the default tile layout for Windows is loaded in that case.
|
||||
|
||||
>[!NOTE]
|
||||
>To learn how customize Start to include your line-of-business apps when you deploy Windows 10, see [Customize the Windows 10 Start layout]( https://go.microsoft.com/fwlink/p/?LinkId=620863).
|
||||
|
@ -29,7 +29,7 @@ To be able to use WSUS to manage and deploy Windows 10 feature updates, you must
|
||||
|
||||
## WSUS scalability
|
||||
|
||||
To use WSUS to manage all Windows updates, some organizations may need access to WSUS from a demilitarized zone, or they might have some other complex scenario. WSUS is highly scalable and configurable for organizations of any size or site layout. For specific information about scaling WSUS, including upstream and downstream server configuration, branch offices, WSUS load balancing, and other complex scenarios, see [Choose a Type of WSUS Deployment](https://technet.microsoft.com/library/cc720448%28v=ws.10%29.aspx).
|
||||
To use WSUS to manage all Windows updates, some organizations may need access to WSUS from a perimeter network, or they might have some other complex scenario. WSUS is highly scalable and configurable for organizations of any size or site layout. For specific information about scaling WSUS, including upstream and downstream server configuration, branch offices, WSUS load balancing, and other complex scenarios, see [Choose a Type of WSUS Deployment](https://technet.microsoft.com/library/cc720448%28v=ws.10%29.aspx).
|
||||
|
||||
|
||||
## Express Installation Files
|
||||
|
@ -238,7 +238,7 @@ Store for Business is currently available in these markets.
|
||||
<li>Bulgaria</li>
|
||||
<li>Cameroon</li>
|
||||
<li>Canada</li>
|
||||
<li>Cape Verde</li>
|
||||
<li>Republic of Cabo Verde</li>
|
||||
<li>Cayman Islands</li>
|
||||
<li>Chile</li>
|
||||
<li>Colombia</li>
|
||||
@ -267,7 +267,7 @@ Store for Business is currently available in these markets.
|
||||
<li>Greece</li>
|
||||
<li>Guatemala</li>
|
||||
<li>Honduras</li>
|
||||
<li>Hong Kong</li>
|
||||
<li>Hong Kong SAR</li>
|
||||
<li>Hungary</li>
|
||||
<li>Iceland</li>
|
||||
<li>Indonesia</li>
|
||||
@ -304,7 +304,7 @@ Store for Business is currently available in these markets.
|
||||
<li>Norway</li>
|
||||
<li>Oman</li>
|
||||
<li>Pakistan</li>
|
||||
<li>Palestinian Territory</li>
|
||||
<li>Palestinian Authority</li>
|
||||
<li>Panama</li>
|
||||
<li>Paraguay</li>
|
||||
<li>Peru</li>
|
||||
|
@ -94,10 +94,12 @@ Windows 10 volume license editions of Windows 10 will continue to support all
|
||||
| Windows 10 | None |
|
||||
| Windows Server 2012 R2 and Windows 8.1 | [https://support.microsoft.com/kb/3058168](https://go.microsoft.com/fwlink/p/?LinkId=625087) |
|
||||
| Windows Server 2012 and Windows 8 | [https://support.microsoft.com/kb/3058168](https://go.microsoft.com/fwlink/p/?LinkId=625087) |
|
||||
| Windows Server 2008 R2 and Windows 7 | Available by October 2015 |
|
||||
| Windows Server 2008 R2 and Windows 7 | [https://support.microsoft.com/kb/3079821](https://support.microsoft.com/kb/3079821) |
|
||||
|
||||
|
||||
|
||||
Also see: [Windows Server 2016 Volume Activation Tips](https://blogs.technet.microsoft.com/askcore/2016/10/19/windows-server-2016-volume-activation-tips/)
|
||||
|
||||
Additionally, new product keys will be needed for all types of volume license activation (KMS, MAK, and AD-based Activation); these keys are available on the Volume Licensing Service Center (VLSC) for customers with rights to the Windows 10 operating system. To find the needed keys:
|
||||
|
||||
- Sign into the [Volume Licensing Service Center (VLSC)](https://go.microsoft.com/fwlink/p/?LinkId=625088) at with a Microsoft account that has appropriate rights.
|
||||
@ -112,10 +114,8 @@ Note that Windows 10 Enterprise and Windows 10 Enterprise LTSB installations u
|
||||
|
||||
|
||||
[Windows 10 servicing options](windows-10-servicing-options.md)
|
||||
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)
|
||||
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)
|
||||
<BR>[Windows 10 deployment considerations](windows-10-deployment-considerations.md)
|
||||
<BR>[Windows 10 compatibility](windows-10-compatibility.md)
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user