Skip to content

Commit 2b82ff8

Browse files
authored
Merge pull request #8342 from MicrosoftDocs/main
Publish main to live on 8/29 @ 10:30 am
2 parents 1d048fb + 884d506 commit 2b82ff8

22 files changed

Lines changed: 4031 additions & 2505 deletions

.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,15 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "memdocs/intune/developer/app-sdk-android.md",
5+
"redirect_url": "/mem/intune/developer/app-sdk-android-phase1",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "memdocs/intune/developer/app-sdk-android-testing-guide.md",
10+
"redirect_url": "/mem/intune/developer/app-sdk-android-phase1",
11+
"redirect_document_id": false
12+
},
313
{
414
"source_path": "memdocs/intune/fundamentals/end-user-company-portal-messages.md",
515
"redirect_url": "/mem/intune/user-help/sign-in-to-the-company-portal",
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Connected cache update for Microsoft Endpoint Configuration Manager version 2203
3+
titleSuffix: Configuration Manager
4+
description: Console update for 2203
5+
ms.date: 8/29/2022
6+
ms.prod: configuration-manager
7+
ms.technology: configmgr-core
8+
ms.topic: reference
9+
ms.assetid: 006f3396-a9d0-44f8-9db1-6408259e405ef
10+
author: bhuney
11+
ms.author: brianhun
12+
manager: dougeby
13+
---
14+
15+
# Connected cache update for Microsoft Endpoint Configuration Manager versions 2103 - 2207
16+
17+
*Applies to: Configuration Manager (current branch, versions 2103 - 2207)*
18+
## Summary of KB14978429
19+
20+
An update is available that fixes the following issues with the Microsoft Connected Cache feature in Configuration Manager current branch, versions 2103 - 2207.
21+
22+
- Incorrect access control list (ACL) set on the cache folder prevents installations from completing in some environments.
23+
- Uninstall race condition that prevents a scheduled task from being cleaned up as expected.
24+
- An incorrect failure state can persist after installation in some cases.
25+
26+
In addition, the following enhancements are included in this release.
27+
28+
- Added general supportability enhancements to improve logging, troubleshooting, and discoverability of error conditions.
29+
- Added support for the latest Office Click-to-Run (C2R) host.
30+
- Decreased installation time by approximately 30 percent.
31+
32+
## Update information for Microsoft Endpoint Configuration Manager
33+
The following hotfix to resolve this problem is available for download from the Microsoft Download Center:
34+
35+
[Download this hotfix now](https://download.microsoft.com/download/8/e/d/8ed826e2-0a9d-4160-a1a0-725efa0d0971/1.5.5.14088/DoincInstall.exe).
36+
37+
After you download this hotfix, refer to the following installation instructions.
38+
39+
## Installation instructions
40+
1. Confirm there is not currently an installation of the MCC component in progress. This is done by checking for status message **9522**, generated by the `SMS_DISTRIBUTION_MANAGER` component. The 9522 message indicates that installation is no longer being retried.
41+
2. Copy the new version of `DoincInstall.exe`, version **1.5.5.14088**, to the `{SMSInstallDir}\bin\x64` folder on all site servers, including the Central Administration Site (CAS) if present, and any passive sites.
42+
3. Uncheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option in the affected distribution point’s properties.
43+
4. Wait for the uninstall of MCC to complete on the distribution point. This can be confirmed by looking for a **9152** success status message, combined with the following entry in `distmgr.log`.
44+
```text
45+
Finished waiting for DoincInstall. InvocationState: UninstallCompleted. InvocationExitCode: 0. InvocationMessage: .
46+
```
47+
5. Recheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option for the affected distribution point.
48+
49+
> [!TIP]
50+
> For sites with a large number of distribution points, replace steps 3 - 5 above with the following.
51+
> - Create an empty file named `resetdps.trn` and place it in the `{SMSInstallDir}\inboxes\distmgr.box` folder. This will reinstall all distribution points for that site using the latest version of `DoincInstall.exe` copied in step 2. above.
52+
53+
## Prerequisites
54+
To apply this hotfix, you must be using Microsoft Endpoint Configuration Manager, versions 2103 through versions 2203.
55+
56+
## Restart information
57+
You don't have to restart the computer after you apply this hotfix.
58+
59+
## Hotfix replacement information
60+
This hotfix replaces the following previously released hotfix.
61+
62+
[KB12819689 Connected cache update for Microsoft Endpoint Configuration Manager version 2111](../../hotfix/2111/12819689.md)
63+
64+
## File information
65+
File information is available in the downloadable [KB14978429_FileList.txt](https://aka.ms/KB14978429_FileList) text file.
66+
67+
## Release history
68+
- August 29, 2022: Initial hotfix release

memdocs/configmgr/hotfix/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
items:
22
- name: Hotfix documentation
33
href: index.yml
4+
- name: Version 2207
5+
items:
6+
- name: KB 14978429 Connected cache update for Microsoft Endpoint Configuration Manager version 2207
7+
href: 2207/14978429.md
48
- name: Version 2203
59
items:
610
- name: KB 13174460 Summary of changes in 2203

memdocs/intune/configuration/vpn-settings-windows-10.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: MandiOhlinger
88
ms.author: mandia
99
manager: dougeby
10-
ms.date: 05/12/2022
10+
ms.date: 08/22/2022
1111
ms.topic: conceptual
1212
ms.service: microsoft-intune
1313
ms.subservice: configuration
@@ -108,6 +108,9 @@ The following settings are shown depending on the connection type you select. No
108108

109109
- **Derived credential**: Use a certificate that's derived from a user's smart card. If no derived credential issuer is configured, Intune prompts you to add one. For more information, see [Use derived credentials in Intune](../protect/derived-credentials.md).
110110

111+
> [!NOTE]
112+
> Currently, derived credentials as an authentication method for VPN profiles isn't working as expected on Windows devices. This behavior only impacts VPN profiles on Windows devices and will be fixed in a future release (no ETA).
113+
111114
- **EAP** (IKEv2 only): Select an existing Extensible Authentication Protocol (EAP) client certificate profile to authenticate. Enter the authentication parameters in the **EAP XML** setting.
112115

113116
For more information on EAP authentication, see [Extensible Authentication Protocol (EAP) for network access](/windows-server/networking/technologies/extensible-authentication-protocol/network-access) and [EAP configuration](/windows/client-management/mdm/eap-configuration).
@@ -239,7 +242,7 @@ Example:
239242
240243
- **DNS suffix search list**: In **DNS suffixes**, enter a DNS suffix, and **Add**. You can add many suffixes.
241244
242-
When using DNS suffixes, you can search for a network resource using its short name, instead of the fully qualified domain name (FQDN). When searching using the short name, the suffix is automatically determined by the DNS server. For example, `utah.contoso.com` is in the DNS suffix list. You ping `DEV-comp`. In this scenario, it resolves to `DEV-comp.utah.contoso.com`.
245+
When using DNS suffixes, you can search for a network resource using its short name, instead of the fully qualified domain name (FQDN). When you search using the short name, the suffix is automatically determined by the DNS server. For example, `utah.contoso.com` is in the DNS suffix list. You ping `DEV-comp`. In this scenario, it resolves to `DEV-comp.utah.contoso.com`.
243246
244247
DNS suffixes are resolved in the order listed, and the order can be changed. For example, `colorado.contoso.com` and `utah.contoso.com` are in the DNS suffix list, and both have a resource called `DEV-comp`. Since `colorado.contoso.com` is first in the list, it resolves as `DEV-comp.colorado.contoso.com`.
245248

0 commit comments

Comments
 (0)