mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge pull request #3282 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/windows-itpro-docs (branch public)
This commit is contained in:
Gary Moore
GitHub
@ -33,19 +33,22 @@ Organizations that use Windows Server Update Services (WSUS) must take action to
|
||||
|
||||
2. Windows Mixed Reality Feature on Demand (FOD) is downloaded from Windows Update. If access to Windows Update is blocked, you must manually install the Windows Mixed Reality FOD.
|
||||
|
||||
a. Download the FOD .cab file for [Windows 10, version 2004](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab), [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab), [Windows 10, version 1803](https://download.microsoft.com/download/9/9/3/9934B163-FA01-4108-A38A-851B4ACD1244/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), or [Windows 10, version 1709](https://download.microsoft.com/download/6/F/8/6F816172-AC7D-4F45-B967-D573FB450CB7/Microsoft-Windows-Holographic-Desktop-FOD-Package.cab).
|
||||
1. Download the FOD .cab file for [Windows 10, version 2004](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab), [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab), [Windows 10, version 1803](https://download.microsoft.com/download/9/9/3/9934B163-FA01-4108-A38A-851B4ACD1244/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), or [Windows 10, version 1709](https://download.microsoft.com/download/6/F/8/6F816172-AC7D-4F45-B967-D573FB450CB7/Microsoft-Windows-Holographic-Desktop-FOD-Package.cab).
|
||||
|
||||
>[!NOTE]
|
||||
>You must download the FOD .cab file that matches your operating system version.
|
||||
> [!NOTE]
|
||||
> You must download the FOD .cab file that matches your operating system version.
|
||||
|
||||
b. Use `Add-Package` to add Windows Mixed Reality FOD to the image.
|
||||
1. Use `Add-Package` to add Windows Mixed Reality FOD to the image.
|
||||
|
||||
```powershell
|
||||
Add-Package
|
||||
Dism /Online /add-package /packagepath:(path)
|
||||
```
|
||||
```powershell
|
||||
Add-Package
|
||||
Dism /Online /add-package /packagepath:(path)
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> You must rename the FOD .CAB file to : **Microsoft-Windows-Holographic-Desktop-FOD-Package\~31bf3856ad364e35\~amd64\~\~.cab**
|
||||
|
||||
c. In **Settings** > **Update & Security** > **Windows Update**, select **Check for updates**.
|
||||
1. In **Settings** > **Update & Security** > **Windows Update**, select **Check for updates**.
|
||||
|
||||
|
||||
IT admins can also create [Side by side feature store (shared folder)](https://technet.microsoft.com/library/jj127275.aspx) to allow access to the Windows Mixed Reality FOD.
|
||||
|
||||
@ -1550,11 +1550,10 @@ You can control if your settings are synchronized:
|
||||
|
||||
To turn off Messaging cloud sync:
|
||||
|
||||
- Note: There is no Group Policy corresponding to this registry key.
|
||||
> [!NOTE]
|
||||
> There is no Group Policy corresponding to this registry key.
|
||||
|
||||
-or-
|
||||
|
||||
- Create a REG_DWORD registry setting named **CloudServiceSyncEnabled** in **HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Messaging** and set to a **value of 0 (zero)**.
|
||||
- Create a REG_DWORD registry setting named **CloudServiceSyncEnabled** in **HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Messaging** and set to a **value of 0 (zero)**.
|
||||
|
||||
### <a href="" id="bkmk-teredo"></a>22. Teredo
|
||||
|
||||
@ -1642,7 +1641,8 @@ You can turn off **Malicious Software Reporting Tool (MSRT) diagnostic data**:
|
||||
|
||||
- Set the REG_DWORD value **HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\MRT\\DontReportInfectionInformation** to **1**.
|
||||
|
||||
**Note:** There is no Group Policy to turn off the Malicious Software Reporting Tool diagnostic data.
|
||||
> [!NOTE]
|
||||
> There is no Group Policy to turn off the Malicious Software Reporting Tool diagnostic data.
|
||||
|
||||
|
||||
You can turn off **Enhanced Notifications** as follows:
|
||||
@ -1737,11 +1737,11 @@ If you're running Windows 10, version 1607 or later, you need to:
|
||||
> This will only take effect if the policy is applied before the first logon.
|
||||
> If you cannot apply the **Force a specific default lock screen image** policy before the first logon to the device,
|
||||
> you can **Enable** the **Do not display the lock screen** policy under **Computer Configuration** > **Administrative Templates** > **Control Panel** > **Personalization**
|
||||
|
||||
>
|
||||
> Alternatively, you can create a new REG_SZ registry setting named **LockScreenImage** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Personalization**
|
||||
> with a value of **C:\\windows\\web\\screen\\lockscreen.jpg** and create a new REG_DWORD registry setting named **LockScreenOverlaysDisabled** in
|
||||
> **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Personalization** with a value of **1 (one)**.
|
||||
|
||||
>
|
||||
> The Group Policy for the **LockScreenOverlaysDisabled** regkey is **Force a specific default lock screen and logon image** that is under **Control Panel** **Personalization**.
|
||||
|
||||
|
||||
@ -1813,7 +1813,7 @@ By default, PCs running Windows 10 Enterprise and Windows 10 Education will only
|
||||
|
||||
Use the UI, Group Policy, or Registry Keys to set up Delivery Optimization.
|
||||
|
||||
In Windows 10 version 1607 and above you can stop network traffic related to Windows Update Delivery Optimization by setting **Download Mode** to **Bypass** (100), as described below.
|
||||
In Windows 10 version 1607 and above you can stop network traffic related to Windows Update Delivery Optimization by setting **Download Mode** to **Bypass** (99), as described below.
|
||||
|
||||
### <a href="" id="bkmk-wudo-ui"></a>28.1 Settings > Update & security
|
||||
|
||||
@ -1839,7 +1839,7 @@ You can find the Delivery Optimization Group Policy objects under **Computer Con
|
||||
|
||||
-or-
|
||||
|
||||
- Create a new REG_DWORD registry setting named **DODownloadMode** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization** to a value of **100 (one hundred)**.
|
||||
- Create a new REG_DWORD registry setting named **DODownloadMode** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization** to a value of **99 (Ninety-nine)**.
|
||||
|
||||
|
||||
For more info about Delivery Optimization in general, see [Windows Update Delivery Optimization: FAQ](https://go.microsoft.com/fwlink/p/?LinkId=730684).
|
||||
@ -1900,7 +1900,7 @@ For China releases of Windows 10 there is one additional Regkey to be set to pre
|
||||
|
||||
### <a href="" id="bkmk-allowedtraffic"></a> Allowed traffic list for Windows Restricted Traffic Limited Functionality Baseline
|
||||
|
||||
|**Allowed traffic endpoints** |
|
||||
|Allowed traffic endpoints|
|
||||
| --- |
|
||||
|activation-v2.sls.microsoft.com/*|
|
||||
|crl.microsoft.com/pki/crl/*|
|
||||
|
||||
@ -28,7 +28,8 @@ If you define this policy setting, you can specify whether to audit successes, a
|
||||
|
||||
To set this value to **No auditing**, in the **Properties** dialog box for this policy setting, select the Define these policy settings check box and clear the **Success** and **Failure** check boxes.
|
||||
|
||||
> **Note:** You can set a SACL on a file system object using the **Security** tab in that object's **Properties** dialog box.
|
||||
> [!NOTE]
|
||||
> You can set a SACL on a file system object using the **Security** tab in that object's **Properties** dialog box.
|
||||
|
||||
**Default:** No auditing.
|
||||
|
||||
@ -41,10 +42,10 @@ You can configure this security setting by opening the appropriate policy under
|
||||
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| 560 | Access was granted to an already existing object. |
|
||||
| 562 | A handle to an object was closed. |
|
||||
| 563 | An attempt was made to open an object with the intent to delete it.<br>\*\*Note: \*\* This is used by file systems when the FILE_DELETE_ON_CLOSE flag is specified in Createfile(). |
|
||||
| 563 | An attempt was made to open an object with the intent to delete it.<br>**Note:** This is used by file systems when the FILE_DELETE_ON_CLOSE flag is specified in Createfile(). |
|
||||
| 564 | A protected object was deleted. |
|
||||
| 565 | Access was granted to an already existing object type. |
|
||||
| 567 | A permission associated with a handle was used.<br>\*\*Note: \*\* A handle is created with certain granted permissions (Read, Write, and so on). When the handle is used, up to one audit is generated for each of the permissions that was used. |
|
||||
| 567 | A permission associated with a handle was used.<br>**Note:** A handle is created with certain granted permissions (Read, Write, and so on). When the handle is used, up to one audit is generated for each of the permissions that was used. |
|
||||
| 568 | An attempt was made to create a hard link to a file that is being audited. |
|
||||
| 569 | The resource manager in Authorization Manager attempted to create a client context. |
|
||||
| 570 | A client attempted to access an object.<br>**Note:** An event will be generated for every attempted operation on the object. |
|
||||
|
||||
Reference in New Issue
Block a user