Merge pull request #8439 from MicrosoftDocs/main

Publish 09/14/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/apps/lob-apps-macos.md

@@ -36,7 +36,7 @@ ms.collection:
 
 [!INCLUDE [azure_portal](../includes/azure_portal.md)]
 
-Use the information in this article to help you add macOS line-of-business apps to Microsoft Intune. You must download an external tool to pre-process your *.pkg* files before you can upload your line-of-business file to Microsoft Intune. The pre-processing of your *.pkg* files must take place on a macOS device.
+Use the information in this article to help you add macOS line-of-business apps to Microsoft Intune. 
 
 > [!NOTE]
 > Starting with the release of macOS Catalina 10.15, prior to adding your apps to Intune, check to make sure your macOS LOB apps are notarized. If the developers of your LOB apps did not notarize their apps, the apps will fail to run on your users' macOS devices. For more information about how to check if an app is notarized, visit [Notarize your macOS apps to prepare for macOS Catalina](https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Support-Tip-Notarizing-your-macOS-apps-to-prepare-for-macOS/ba-p/808579).
@@ -45,42 +45,6 @@ Use the information in this article to help you add macOS line-of-business apps
 > 
 > While users of macOS devices can remove some of the built-in macOS apps like Stocks, and Maps, you cannot use Intune to redeploy those apps. If end users delete these apps, they must go to the app store, and manually re install them.
 
-## Before your start
-
-> [!NOTE]
-> Using the Intune App Wrapping Tool for Mac is not required when uploading *.pkg* files.
-
-You must download an external tool, mark the downloaded tool as an executable, and pre-process your *.pkg* files with the tool before you can upload your line-of-business file to Microsoft Intune. The pre-processing of your *.pkg* files must take place on a macOS device. Use the Intune App Wrapping Tool for Mac to enable Mac apps to be managed by Microsoft Intune.
-
-> [!IMPORTANT]
-> The *.pkg* file must be signed using "Developer ID Installer" certificate, obtained from an Apple Developer account. Only *.pkg* files may be used to upload macOS LOB apps to Microsoft Intune. However, conversion of other formats, such as *.dmg* to *.pkg* is supported. For more information about converting non-pkg application types, see [How to deploy DMG or APP-format apps to Intune-managed Macs](https://techcommunity.microsoft.com/t5/intune-customer-success/how-to-deploy-dmg-or-app-format-apps-to-intune-managed-macs/ba-p/1503416).
-
-1. Download the [Intune App Wrapping Tool for Mac](https://github.com/msintuneappsdk/intune-app-wrapping-tool-mac).
-
-    > [!NOTE]
-    > The **Intune App Wrapping Tool for Mac** must be run on a macOS machine. 
-
-2. Mark the downloaded tool as an executable:
-   - Start the terminal app.
-   - Change the directory to the location where `IntuneAppUtil` is located.
-   - Run the following command to make the tool executable:<br> 
-       `chmod +x IntuneAppUtil`
-
-3. Use the `IntuneAppUtil` command within the **Intune App Wrapping Tool for Mac** to wrap *.pkg* LOB app file from a *.intunemac* file.<br>
-
-    Sample commands to use for the Microsoft Intune App Wrapping Tool for macOS:
-    > [!IMPORTANT]
-    > Ensure that the argument `<source_file>` does not contain spaces before running the `IntuneAppUtil` commands.
-
-    - `IntuneAppUtil -h`<br>
-    This command will show usage information for the tool.
-    
-    - `IntuneAppUtil -c <source_file> -o <output_directory_path> [-v]`<br>
-    This command will wrap the *.pkg* LOB app file provided in `<source_file>` to a *.intunemac* file of the same name and place it in the folder pointed to by `<output_directory_path>`.
-    
-    - `IntuneAppUtil -r <filename.intunemac> [-v]`<br>
-    This command will extract the detected parameters and version for the created *.intunemac* file.
-
 ## Select the app type
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
@@ -91,12 +55,12 @@ You must download an external tool, mark the downloaded tool as an executable, a
 ## Step 1 - App information
 
 > [!NOTE]
-> The **minimum operating system** for uploading a *.pkg* file is macOS 10.14. Upload a *.intunemac* file to select an older minimum operating system.
+> The **minimum operating system** for uploading a *.pkg* file is macOS 10.14.
 
 ### Select the app package file
 
 1. In the **Add app** pane, click **Select app package file**. 
-2. In the **App package file** pane, select the browse button. Then, select an macOS installation file with the extension *.intunemac* or *.pkg*.
+2. In the **App package file** pane, select the browse button. Then, select an macOS installation file with the extension *.pkg*.
    The app details will be displayed.
 3. When you're finished, select **OK** on the **App package file** pane to add the app.
 
@@ -109,7 +73,7 @@ You must download an external tool, mark the downloaded tool as an executable, a
     - **Minimum Operating System**: From the list, choose the minimum operating system version on which the app can be installed. If you assign the app to a device with an earlier operating system, it will not be installed.
     - **Ignore app version**: Select **Yes** to install the app if the app is not already installed on the device. Select **No** to only install the app when it is not already installed on the device, or if the deploying app's version number does not match the version that's already installed on the device.
     - **Install as managed**: Select **Yes** to install the Mac LOB app as a managed app on  supported devices (macOS 11 and higher). A macOS LOB app can only be installed as managed when the app distributable contains a single app without any nested packages and installs to the */Applications* directory. Managed line-of-business apps will be able to be removed using the **uninstall** assignment type on supported devices (macOS 11 and higher). In addition, removing the MDM profile removes all managed apps from the device. The default value is **No**.
-    - **Included apps**: Review and edit the apps that are contained in the uploaded file. Included app bundle IDs and build numbers are used for detecting and monitoring app installation status of the uploaded file. The app listed first is used as the primary app in app reporting. <br>Included apps list should only contain the application(s) installed by the uploaded file in **Applications** folder on Macs. Any other type of file that is not an application or an application that is not installed to **Applications** folder should be removed from the **Included apps** list. If **Included apps** list contains files that are not applications or if all the listed apps are not installed, app installation status does not report success.<br>Mac Terminal can be used to look up and confirm the included app details of an installed app.<br>For example, to look up the bundle ID and build number of Company Portal, run the following:<br> *defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleIdentifier*<br>Then, run the following:<br> *defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleShortVersionString*
+    - **Included apps**: Review and edit the apps that are contained in the uploaded file. Included app bundle IDs and build numbers are used for detecting and monitoring app installation status of the uploaded file. The app listed first is used as the primary app in app reporting. <br>Included apps list should only contain the application(s) installed by the uploaded file in **Applications** folder on Macs. Any other type of file that is not an application or an application that is not installed to **Applications** folder should be removed from the **Included apps** list. If **Included apps** list contains files that are not applications or if all the listed apps are not installed, app installation status does not report success.<br>Mac Terminal can be used to look up and confirm the included app details of an installed app.<br>For example, to look up the bundle ID and build number of a Company Portal, run the following:<br> *defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleIdentifier*<br>Then, run the following:<br> *defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleShortVersionString*
     - **Category**: Select one or more of the built-in app categories, or select a category that you created. Categories make it easier for users to find the app when they browse through the company portal.
     - **Show this as a featured app in the Company Portal**: Display the app prominently on the main page of the company portal when users browse for apps.
     - **Information URL**: Optionally, enter the URL of a website that contains information about this app. The URL appears in the company portal.
@@ -152,8 +116,6 @@ The app you have created appears in the apps list where you can assign it to the
 
 [!INCLUDE [shared-proc-lob-updateapp](../includes/shared-proc-lob-updateapp.md)]
 
-To update a line-of-business app deployed as a *.intunemac* file, you must increment the package `version` and `CFBundleVersion` string in the *packageinfo* file in your *.pkg* file.
-
 To update a line-of-business app deployed as a *.pkg* file, you must increment the `CFBundleShortVersionString` of the *.pkg* file.
 
 Intune will update the app when this schedule elapses, provided that any previous version of the app is still present on the device.

memdocs/intune/remote-actions/remote-help.md

@@ -311,10 +311,13 @@ Remote help logs data during installation and during remote help sessions, which
 
 ## Installation details
 
-Remote help will create the following firewall inbound rules:
-- Quick Assist Firewall Exception
-- Quick Assist RDP Firewall Exception
-- Remote help Firewall Exception
+Automatic firewall rule creation from the Remote help installer has been removed. However, if needed, System administrators can create firewall rules.
+
+Depending on the environment that Remote help is utilized in, it may be necessary to create firewall rules to allow Remote help through the Windows Defender Firewall. In situations where this is necessary, these are the Remote help executables that should be allowed through the firewall:
+
+ - C:\Program Files\Remote help\RemoteHelp.exe
+ - C:\Program Files\Remote help\RHService.exe
+ - C:\Program Files\Remote help\RemoteHelpRDP.exe
 
 ## Languages Supported
 

windows-365/enterprise/in-development.md

@@ -8,7 +8,7 @@ keywords:
 author: ErikjeMS 
 ms.author: erikje
 manager: dougeby
-ms.date: 09/13/2022
+ms.date: 09/14/2022
 ms.topic: reference
 ms.service: cloudpc
 ms.subservice: 
@@ -81,6 +81,9 @@ The resize action will support Cloud PCs that are Azure Active Directory joined.
 <!-- ***********************************************-->
 ## Monitor and troubleshoot
 
+### System alerts and email notifications (preview)<!--40932899-->
+You'll be able to set up system alerts and automated emails to be notified when certain events, warnings, or errors occur in the Windows 365 service. A subset of critical Cloud PC issues will be sent automatically to admins. In addition, you’ll be able to define alert rules, such as target audience (devices, user groups, tenants), thresholds, frequency, and notification channels.
+
 ### Cloud PC utilization report<!--40636545-->
 A new report will be available for Cloud PCs. The **Cloud PC utilization** report will show how many hours users have been connected to their Cloud PCs. Information for individual Cloud PCs and aggregated data will be shown.