Skip to content

Commit 1593fb3

Browse files
authored
Merge pull request #7857 from MicrosoftDocs/main
Publish 06/21/2022, 10:30 AM
2 parents 06bf080 + 06178c8 commit 1593fb3

8 files changed

Lines changed: 19 additions & 15 deletions

File tree

memdocs/configmgr/core/servers/manage/community-hub.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Community hub and GitHub
33
titleSuffix: Configuration Manager
44
description: Enable and use Community hub in Configuration Manager
5-
ms.date: 01/05/2022
5+
ms.date: 06/20/2022
66
ms.prod: configuration-manager
77
ms.technology: configmgr-other
88
ms.topic: conceptual
@@ -40,7 +40,7 @@ Community hub supports the following objects:
4040
- A supported version of Windows 10 or later
4141
- Windows Server isn't supported before version 2010, so the Configuration Manager console needs to be installed on a supported Windows client device separate from the site server.
4242
- Starting in version 2010, [install the Microsoft Edge WebView2 console extension](#bkmk_webview2) to support Windows Server. <!--3555940, 8625943, 8717639 -->
43-
- The logged-in user account can't be the built-in administrator account
43+
4444

4545
- The [administration service](../../../develop/adminservice/set-up.md) in Configuration Manager needs to be set up and functional.
4646

memdocs/configmgr/core/servers/manage/includes/community-hub-links.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ author: mestew
33
ms.author: mstewart
44
ms.prod: configuration-manager
55
ms.topic: include
6-
ms.date: 01/08/2021
6+
ms.date: 06/20/2022
77
ms.localizationpriority: medium
88
---
99
<!--This file is shared by the community-hub and community-hub-contribute .md files. Headings are context driven by the article-->
@@ -15,7 +15,7 @@ You can navigate to and reference items in the Configuration Manager console **C
1515
Prerequisites for direct links:
1616

1717
- Configuration Manager console version 2006 or later
18-
- You can't use the local built-in administrator account when following a Community hub link.
18+
1919

2020
Share an item:
2121
1. Go the item in the hub and select **Share**.

memdocs/intune/configuration/bundle-ids-built-in-ios-apps.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: 10/19/2020
10+
ms.date: 06/20/2022
1111
ms.topic: reference
1212
ms.service: microsoft-intune
1313
ms.subservice: configuration
@@ -28,7 +28,10 @@ ms.collection: M365-identity-device-management
2828

2929
# Bundle IDs for built-in iOS and iPadOS apps you can use in Intune
3030

31-
When you configure features on iOS/iPadOS devices, you can also add the built-in apps on iOS/iPadOS devices. This article lists the bundle IDs of some common built-in iOS/iPadOS apps. To find the bundle ID of other apps, contact your software vendor. See Apple's list of [iOS/iPadOS bundle IDs](https://support.apple.com/guide/deployment/bundle-ids-for-native-ios-and-ipados-apps-depece748c41/1/web/1.0) (opens Apple's web site).
31+
When you configure features on iOS/iPadOS devices, you can also add the built-in apps on these devices. This article lists the bundle IDs of some common built-in iOS/iPadOS apps. To find the bundle ID of other apps, contact your software vendor. See Apple's list of [iOS/iPadOS bundle IDs](https://support.apple.com/guide/deployment/bundle-ids-for-native-ios-and-ipados-apps-depece748c41/1/web/1.0) (opens Apple's web site).
32+
33+
> [!TIP]
34+
> On macOS devices, you can get the bundle ID using the Terminal app and AppleScript: `osascript -e 'id of app "AppName"'`.
3235
3336
## Bundle IDs
3437

memdocs/intune/configuration/device-restrictions-macos.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
author: MandiOhlinger
99
ms.author: mandia
1010
manager: dougeby
11-
ms.date: 01/20/2022
11+
ms.date: 06/20/2022
1212
ms.topic: conceptual
1313
ms.service: microsoft-intune
1414
ms.subservice: configuration
@@ -437,6 +437,8 @@ This feature applies to:
437437
- **Apps list**: **Add** apps to your list:
438438
- **App Bundle ID**: Enter the [bundle ID](bundle-ids-built-in-ios-apps.md) of the app. You can add built-in apps and line-of-business apps. Apple's web site has a list of [built-in Apple apps](https://support.apple.com/HT208094).
439439

440+
To find the bundle ID of a macOS app, you can open the Terminal app, and use AppleScript (`osascript -e 'id of app "AppName"'`).
441+
440442
To find the URL of an app, open the iTunes App Store, and search for the app. For example, search for `Microsoft Remote Desktop` or `Microsoft Word`. Select the app, and copy the URL. You can also use iTunes to find the app, and then use the **Copy Link** task to get the app URL.
441443

442444
- **App name**: Enter a user-friendly name to help you identify the bundle ID. For example, enter `Intune Company Portal app`.

memdocs/intune/enrollment/windows-enrollment-status.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -230,6 +230,9 @@ The ESP tracks the installation of apps deployed in a device context, and includ
230230
- Offline store apps where installation context = device
231231
- Win32 applications for Windows 10, version 1903 and later, and Windows 11.
232232

233+
> [!NOTE]
234+
> It's preferable to deploy the offline-licensed Microsoft Store for Business apps. Don't mix LOB and Win32 apps. Both LOB (MSI) and Win32 installers use TrustedInstaller, which doesn't allow simultaneous installations. If the OMA DM agent starts an MSI installation, the Intune Management Extension plugin starts a Win32 app installation by using the same TrustedInstaller. In this situation, Win32 app installation fails and returns an **Another installation is in progress, please try again later** error message. In this situation, ESP fails. Therefore, don't mix LOB and Win32 apps in any type of Autopilot enrollment.
235+
233236
### Account setup
234237

235238
During the account setup phase, the ESP tracks apps and policies targeted at users, including:

memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,7 @@ You can manage **Windows 10** and **Windows 11 Enterprise multi-session** VMs cr
4545

4646
## Overview
4747

48-
Microsoft Intune only supports managing Windows 10 or Windows 11 Enterprise multi-session with device configurations. This means only [policies defined in the OS scope](/windows/client-management/mdm/policy-configuration-service-provider) and apps configured to install in the system context can be applied to Azure Virtual Desktop multi-session VMs. Additionally, all multi-session configurations must be targeted to devices or device groups. User scope policies aren't supported at this time.
49-
48+
Microsoft Intune only supports managing Windows 10 or Windows 11 Enterprise multi-session with device configurations. This means only [policies defined in the Device scope](/windows/client-management/mdm/policy-configuration-service-provider) and apps configured to install in the system context can be applied to Azure Virtual Desktop multi-session VMs. Additionally, all multi-session configurations must be targeted to devices or device groups. User scope policies are not supported at this time.
5049

5150
## Prerequisites
5251

memdocs/intune/fundamentals/in-development.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,10 +133,7 @@ Bootstrap tokens allow for non-admin users to have increased MDM permissions, an
133133
- Supervised devices (in Intune, that's all user-approved enrollments)
134134
- Devices enrolled in Intune via Apple automated device enrollment
135135

136-
For more information about how bootstrap tokens work with Intune, see [Set up enrollment for macOS devices](../enrollment/macos-enroll.md).
137-
138-
### UI improvements when Android enrollment is available but not required<!-- 8764312 -->
139-
We're updating the iconography users see in the Company Portal for Android when *Device enrollment* for *End user experiences* on your Intune tenants *Customization* page is set to **Available, no prompts**. The changes will make it easier for users to recognize when enrollment is available to them, but not required.
136+
For more information about how bootstrap tokens work with Intune, see [Set up enrollment for macOS devices](../enrollment/macos-enroll.md).
140137

141138
<!-- ***********************************************-->
142139

memdocs/intune/user-help/rename-your-device-cpapp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Rename a device to make it easier to recognize from other devices. The Company P
3636
* Android
3737

3838
## Rename device from **Device details** page
39-
Complete the following step to remove a device from the Company Portal **Device details** page.
39+
Complete the following step to rename a device from the Company Portal **Device details** page.
4040

4141
1. Open the Company Portal app and go to **My Devices**.
4242

@@ -50,7 +50,7 @@ Complete the following step to remove a device from the Company Portal **Device
5050
![Example screenshot of the Company Portal app for Windows, Device details page, Rename popup field.](./media/1808_RenameApp_Popup.png)
5151

5252
## Rename device from device context menu
53-
Complete the following step to remove a device through the [context menu](/windows/uwp/design/controls-and-patterns/menus) actions.
53+
Complete the following step to rename a device through the [context menu](/windows/uwp/design/controls-and-patterns/menus) actions.
5454

5555
1. On the **Home** page of the Company Portal app, go to **My Devices**.
5656

0 commit comments

Comments
 (0)