Skip to content

Commit 997beee

Browse files
author
Angela Fleischmann
authored
Merge pull request #9804 from MicrosoftDocs/main
Publish 02/13/2023 3:30 PM PT
2 parents e199c0d + 02e19b9 commit 997beee

File tree

6 files changed

+17
-9
lines changed

6 files changed

+17
-9
lines changed

memdocs/autopilot/windows-autopilot-hybrid.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -152,6 +152,12 @@ Before beginning the installation, make sure that all of the [Intune connector s
152152
> - After you sign in to the Connector, it can take several minutes to appear in the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/). It appears only if it can successfully communicate with the Intune service.
153153
> - Inactive Intune connectors still appear in the Intune Connectors blade and will automatically be cleaned up after 30 days.
154154
155+
After installing the Intune Connector, it will start logging in the **Event Viewer** under the path **Applications and Services Logs** > **Microsoft** > **Intune** > **ODJConnectorService**. Under this path you will find **Admin** and **Operational** logs.
156+
157+
> [!NOTE]
158+
>
159+
> The Intune Connector originally logged in the **Event Viewer** directly under **Applications and Services Logs** in a log called **ODJ Connector Service**. However, logging for the Intune Connector has since moved to the path **Applications and Services Logs** > **Microsoft** > **Intune** > **ODJConnectorService**. If you find that the **ODJ Connector Service** log at the original location is empty or not updating, please check the new path location instead.
160+
155161
### Configure web proxy settings
156162

157163
If you have a web proxy in your networking environment, ensure that the Intune Connector for Active Directory works properly by referring to [Work with existing on-premises proxy servers](../intune/enrollment/autopilot-hybrid-connector-proxy.md).

memdocs/breadcrumb/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,4 +82,4 @@ items:
8282
topicHref: /mem/autopilot/
8383
- name: Solutions
8484
tocHref: /mem/#solutions---scenarios
85-
topicHref: /mem/solutions/
85+
topicHref: /mem/#solutions---scenarios

memdocs/intune/configuration/oemconfig-zebra-android-devices.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Create an [OEMConfig configuration profile](android-oem-configuration-overview.m
5050

5151
On Zebra devices, you can have many profiles on each device simultaneously. This feature allows you to split your Zebra OEMConfig settings into smaller profiles. For example, create a baseline profile that affects all devices. Then, create more profiles that configure settings specific to a device.
5252

53-
Zebra’s OEMConfig schema also uses **Actions**. Actions are operations that run on the device. They don’t configure any settings. Use these actions to trigger a file download, clear the clipboard, and more. For a full list of the supported actions, see [Zebra’s documentation](https://techdocs.zebra.com/oemconfig/about/) (opens Zebra's web site).
53+
Zebra’s OEMConfig schema also uses **Actions**. Actions are operations that run on the device. They don’t configure any settings. Use these actions to trigger a file download, clear the clipboard, and more. For a full list of the supported actions, see [Zebra’s documentation](https://techdocs.zebra.com/oemconfig/) (opens Zebra's web site).
5454

5555
For example, you create a Zebra OEMConfig profile that applies some settings to the device. Another Zebra OEMConfig profile includes an action that clears the clipboard. You assign the first profile to a Zebra devices group. Later, you need to clear the clipboard on those devices. You assign the second profile to the same devices group, without changing the first profile. The device clipboard gets cleared without resending or affecting the configuration settings created in the first profile.
5656

@@ -60,17 +60,17 @@ Multiple profiles will take longer to deploy than a single profile. If the speed
6060

6161
## Ordering
6262

63-
With multiple profiles on each device, the order that profiles are deployed isn’t guaranteed. This behavior is a Google Play limitation. To run operations in sequence, you can use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site).
63+
With multiple profiles on each device, the order that profiles are deployed isn’t guaranteed. This behavior is a Google Play limitation. To run operations in sequence, you can use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site).
6464

65-
To summarize, if order matters, use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site). If order doesn't matter, use multiple Intune profiles.
65+
To summarize, if order matters, use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site). If order doesn't matter, use multiple Intune profiles.
6666

6767
Let's look at some examples:
6868

6969
- You want to turn on Bluetooth for all newly-enrolled Zebra devices before configuring any other setting on these devices. To run operations in sequence, use the **Steps** feature in Zebra’s schema.
7070

7171
Create one Intune profile that has two Transaction Steps. The first step includes Bluetooth settings, and the second step configures the other setting. When Zebra’s OEMConfig app receives the profile, it runs the steps in order.
7272

73-
For more information, see [Zebra's transaction steps](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site).
73+
For more information, see [Zebra's transaction steps](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site).
7474

7575
- You want all Zebra devices to display time in 24-hour format. For some of these devices, you want to turn the camera off. The time and camera settings don't depend on each other.
7676

memdocs/intune/developer/app-sdk-xamarin.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ ms.collection:
3434
# Microsoft Intune App SDK Xamarin Bindings
3535

3636
> [!NOTE]
37-
> The current Xamarin bindings for Android platform only support apps targeting Android 9.0 and lower and Xamarin Forms 4.4 and lower. Microsoft is working on improving support for newer versions on Android starting Q2CY2023. More information on the support plan to be provided in Q1CY2023.
37+
> The current Xamarin bindings for Android platform only support apps targeting Android 9.0 and lower and Xamarin Forms 4.4 and lower. Microsoft is working on improving support for newer versions on Android starting Q2CY2023. We anticipate having a beta release for .NET MAUI support available in March 2023. For more information about migrating your apps from Xamarin Forms to .NET MAUI, see [Migrate your app from Xamarin.Forms](/dotnet/maui/get-started/migrate).
3838
3939
> [!NOTE]
4040
> You may wish to first read the [Get Started with Intune App SDK](app-sdk-get-started.md) article, which explains how to prepare for integration on each supported platform.
@@ -84,7 +84,7 @@ for more information.
8484
* Secure the output directory that contains the Xamarin app. Consider using a user-level directory for the output.
8585

8686

87-
## Enabling Intune app protection polices in your iOS mobile app
87+
## Enabling Intune app protection policies in your iOS mobile app
8888

8989
> [!IMPORTANT]
9090
> Intune regularly releases updates to the Intune App SDK. Regularly check the [Intune App SDK Xamarin Bindings](https://github.com/msintuneappsdk/intune-app-sdk-xamarin) for updates and incorporate into your software development release cycle to ensure your apps support the latest App Protection Policy settings.

windows-365/enterprise/introduction-windows-365-government.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 11/11/2022
10+
ms.date: 02/13/2023
1111
ms.topic: overview
1212
ms.service: windows-365
1313
ms.subservice:
@@ -55,6 +55,7 @@ The following features are not yet supported for Windows 365 GCC or GCCH.
5555
- Windows 365 System based alerting on Microsoft Endpoint Manager for Cloud PCs
5656
- User initiated feedback in End User Portal and Windows 365 Web Client
5757
- Resize VM
58+
- Citrix HDX Plus for Windows 365
5859

5960
## Next steps
6061

windows-365/enterprise/requirements-citrix.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 10/12/2022
10+
ms.date: 02/13/2023
1111
ms.topic: overview
1212
ms.service: windows-365
1313
ms.subservice:
@@ -48,6 +48,7 @@ To use Citrix HDX Plus for Windows 365, you must meet the following requirements
4848
- For Hybrid Azure Active Directory (Azure AD) joined deployments:
4949
- The Azure AD domain must be synchronized from the Azure AD domain that the Cloud PCs belong to.
5050
- Cloud Connectors to allow Citrix Cloud to connect to your Active Directory domain. For more information, see [Citrix Cloud Connector](https://docs.citrix.com/en-us/citrix-cloud/citrix-cloud-resource-locations/citrix-cloud-connector.html).
51+
- Allowlist endpoint required for VDA registation: \*.apps.cloud.com
5152

5253
## Microsoft requirements
5354

0 commit comments

Comments
 (0)