Connection group purpose |
-A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other. -Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins. |
-
How the connection group file works |
-When you apply an App-V connection group file, the packages that are enumerated in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups. |
-
Example file path |
-%APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}. |
-
| Field | -Description | -
|---|---|
Schema name |
-Name of the schema. -If you want to use the “optional packages” and “use any version” features that are described in this table, you must specify the following schema in the XML file: -
|
-
AppConnectionGroupId |
-Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group. -You can create a new GUID by typing: [Guid]::NewGuid(). |
-
VersionId |
-Version GUID identifier for this version of the connection group. -When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version. |
-
DisplayName |
-Display name of the connection group. |
-
Priority |
-Optional priority field for the connection group. -“0” - indicates the highest priority. -If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined. |
-
| Field | -Description | -
|---|---|
PackageId |
-Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published. |
-
VersionId |
-Unique GUID identifier for the version of the package. -If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted. |
-
IsOptional |
-Parameter that enables you to make a package optional within the connection group. Valid entries are: -
|
-
| Example | -Example description | -
|---|---|
Virtual application connection group for the financial division |
-
|
-
Virtual application connection group for HR division |
-
|
-
| Package A | -Package B | -
|---|---|
C:\Windows\System32 |
-C:\Windows\System32 |
-
C:\AppTest |
-C:\AppTest |
-
Microsoft Application Virtualization (App-V) apps have typically been configured, deployed, and managed through on-premise group policies using System Center Configuration Manager (SCCM) or App-V server. In Windows 10, version 1703, App-V apps can be configured, deployed, and managed using mobile device management (MDM), matching their on-premise counterparts.
+Microsoft Application Virtualization (App-V) apps have typically been configured, deployed, and managed through on-premises group policies using System Center Configuration Manager (SCCM) or App-V server. In Windows 10, version 1703, App-V apps can be configured, deployed, and managed using mobile device management (MDM), matching their on-premises counterparts.
MDM services can be used to publish App-V packages to clients running Windows 10, version 1703 (or later). All capabilities such as App-V enablement, configuration, and publishing can be completed using the EnterpriseAppVManagement CSP.
@@ -79,7 +79,7 @@ ms.date: 06/26/2017 ## Scenarios addressed in App-V MDM functionality -All App-V group policies will be reflected by having a corresponding CSP that can be set using the Policy CSP. The CSPs match all on-premise App-V configuration capabilities. In addition, new App-V package management capability has been added to closely match the App-V PowerShell functionality.
+All App-V group policies will be reflected by having a corresponding CSP that can be set using the Policy CSP. The CSPs match all on-premises App-V configuration capabilities. In addition, new App-V package management capability has been added to closely match the App-V PowerShell functionality.
A complete list of App-V policies can be found here:
diff --git a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md index 63c22e0fb2..fc0c578410 100644 --- a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md +++ b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md @@ -30,7 +30,7 @@ On the desktop, you can create an Active Directory account, such as "enrollment@ On the desktop and mobile devices, you can use an enrollment certificate or enrollment username and password, such as "enroll@contoso.com" and "enrollmentpassword." These credentials are used in the provisioning package, which you can use to enroll multiple devices to the MDM service. Once the devices are joined, many users can use them. -> **Note** +>[!NOTE] > - Bulk-join is not supported in Azure Active Directory Join. > - Bulk enrollment does not work in Intune standalone enviroment. > - Bulk enrollment works in System Center Configuration Manager (SCCM) + Intune hybrid environment where the ppkg is generated from the SCCM console. @@ -47,7 +47,7 @@ On the desktop and mobile devices, you can use an enrollment certificate or enro Some organizations require custom APNs to be provisioned before talking to the enrollment endpoint or custom VPN to join a domain. -## Create and apply a provisioning package for on-premise authentication +## Create and apply a provisioning package for on-premises authentication Using the ICD, create a provisioning package using the enrollment information required by your organization. Ensure that you have all the configuration settings. diff --git a/windows/client-management/mdm/device-update-management.md b/windows/client-management/mdm/device-update-management.md index f20da5c4c5..2e48c36d75 100644 --- a/windows/client-management/mdm/device-update-management.md +++ b/windows/client-management/mdm/device-update-management.md @@ -630,7 +630,7 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego > [!Important] > Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enteprise and IoT Enterprise. -Allows the device to check for updates from a WSUS server instead of Microsoft Update. This is useful for on-premise MDMs that need to update devices that cannot connect to the Internet. +
Allows the device to check for updates from a WSUS server instead of Microsoft Update. This is useful for on-premises MDMs that need to update devices that cannot connect to the Internet.
Supported operations are Get and Replace. diff --git a/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md b/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md index 9fc4d5138f..6309ac365b 100644 --- a/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md +++ b/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10.md @@ -96,9 +96,9 @@ Example: Export the Debug logs ``` -## Collect logs from Windows 10 Mobile devices +## Collect logs from Windows 10 Mobile devices -Since there is no Event Viewer in Windows 10 Mobile, you can use the [Field Medic]( http://go.microsoft.com/fwlink/p/?LinkId=718232) app to collect logs. +Since there is no Event Viewer in Windows 10 Mobile, you can use the [Field Medic](https://www.microsoft.com/en-us/p/field-medic/9wzdncrfjb82?activetab=pivot%3aoverviewtab) app to collect logs. **To collect logs manually** @@ -168,9 +168,9 @@ The following table contains a list of common providers and their corresponding -## Collect logs remotely from Windows 10 Mobile devices +## Collect logs remotely from Windows 10 Holographic or Windows 10 Mobile devices -For mobile devices already enrolled in MDM, you can remotely collect MDM logs through the MDM channel using the [DiagnosticLog CSP](diagnosticlog-csp.md). +For holographic or mobile devices already enrolled in MDM, you can remotely collect MDM logs through the MDM channel using the [DiagnosticLog CSP](diagnosticlog-csp.md). You can use the DiagnosticLog CSP to enable the ETW provider. The provider ID is 3DA494E4-0FE2-415C-B895-FB5265C5C83B. The following examples show how to enable the ETW provider: diff --git a/windows/client-management/mdm/healthattestation-csp.md b/windows/client-management/mdm/healthattestation-csp.md index 2ebb1b49fe..a08bdd89b6 100644 --- a/windows/client-management/mdm/healthattestation-csp.md +++ b/windows/client-management/mdm/healthattestation-csp.md @@ -138,11 +138,11 @@ The following is a list of functions performed by the Device HealthAttestation C
(DHA-OnPrem)
DHA-OnPrem refers to DHA-Service that is running on premise:
+DHA-OnPrem refers to DHA-Service that is running on premises:
Accessible to all enterprise managed devices via following:
(DHA-EMC)
DHA-EMC refers to an enterprise managed DHA-Service that is running as a virtual host/service on a Windows Server 2016 compatible - enterprise managed cloud service, such as Microsoft Azure.
Accessible to all enterprise managed devices via following:
| New or updated topic | +Description | +
|---|---|
| [Diagnose MDM failures in Windows 10](diagnose-mdm-failures-in-windows-10.md) | +Added procedure for collecting logs remotely from Windows 10 Holographic. + |
| [Mobile device enrollment](mobile-device-enrollment.md) | Added the following statement:
|