mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge branch 'main' into sheshachary-5859198-4
This commit is contained in:
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Change history for MDM documentation
|
||||
description: This article lists new and updated articles for Mobile Device Management.
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dougeby
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/19/2020
|
||||
---
|
||||
@ -174,7 +174,6 @@ This article lists new and updated articles for the Mobile Device Management (MD
|
||||
|
||||
|New or updated article | Description|
|
||||
|--- | ---|
|
||||
|[Mobile device management](index.md#mmat) | Added information about the MDM Migration Analysis Tool (MMAT).|
|
||||
|[Policy CSP - DeviceGuard](policy-csp-deviceguard.md) | Updated ConfigureSystemGuardLaunch policy and replaced EnableSystemGuard with it.|
|
||||
|
||||
## August 2018
|
||||
@ -227,7 +226,6 @@ This article lists new and updated articles for the Mobile Device Management (MD
|
||||
|[WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md)|Added the following node in Windows 10, version 1803:<li>Settings/AllowVirtualGPU<li>Settings/SaveFilesToHost|
|
||||
|[NetworkProxy CSP](networkproxy-csp.md)|Added the following node in Windows 10, version 1803:<li>ProxySettingsPerUser|
|
||||
|[Accounts CSP](accounts-csp.md)|Added a new CSP in Windows 10, version 1803.|
|
||||
|[MDM Migration Analysis Tool (MMAT)](https://aka.ms/mmat)|Updated version available. MMAT is a tool you can use to determine which Group Policies are set on a target user/computer and cross-reference them against the list of supported MDM policies.|
|
||||
|[CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download)|Added the DDF download of Windows 10, version 1803 configuration service providers.|
|
||||
|[Policy CSP](policy-configuration-service-provider.md)|Added the following new policies for Windows 10, version 1803:<li>Bluetooth/AllowPromptedProximalConnections<li>KioskBrowser/EnableEndSessionButton<li>LocalPoliciesSecurityOptions/NetworkSecurity_RestrictNTLM_AddRemoteServerExceptionsForNTLMAuthentication<li>LocalPoliciesSecurityOptions/NetworkSecurity_RestrictNTLM_AuditIncomingNTLMTraffic<li>LocalPoliciesSecurityOptions/NetworkSecurity_RestrictNTLM_IncomingNTLMTraffic<li>LocalPoliciesSecurityOptions/NetworkSecurity_RestrictNTLM_OutgoingNTLMTrafficToRemoteServers|
|
||||
|
||||
|
@ -1,28 +1,28 @@
|
||||
---
|
||||
title: Mobile device management
|
||||
description: Windows 10 and Windows 11 provides an enterprise-level solution to mobile management, to help IT pros comply with security policies while avoiding compromise of user's privacy
|
||||
description: Windows 10 and Windows 11 provide an enterprise-level solution to mobile management, to help IT pros comply with security policies while avoiding compromise of user's privacy.
|
||||
MS-HAID:
|
||||
- 'p\_phDeviceMgmt.provisioning\_and\_device\_management'
|
||||
- 'p\_phDeviceMgmt.mobile\_device\_management\_windows\_mdm'
|
||||
ms.assetid: 50ac90a7-713e-4487-9cb9-b6d6fdaa4e5b
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.topic: overview
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
ms.collection: highpri
|
||||
ms.date: 06/03/2022
|
||||
---
|
||||
|
||||
# Mobile device management
|
||||
|
||||
Windows 10 and Windows 11 provides an enterprise management solution to help IT pros manage company security policies and business applications, while avoiding compromise of the users' privacy on their personal devices. A built-in management component can communicate with the management server.
|
||||
Windows 10 and Windows 11 provide an enterprise management solution to help IT pros manage company security policies and business applications, while avoiding compromise of the users' privacy on their personal devices. A built-in management component can communicate with the management server.
|
||||
|
||||
There are two parts to the Windows management component:
|
||||
There are two parts to the Windows management component:
|
||||
|
||||
- The enrollment client, which enrolls and configures the device to communicate with the enterprise management server.
|
||||
- The management client, which periodically synchronizes with the management server to check for updates and apply the latest policies set by IT.
|
||||
- The enrollment client, which enrolls and configures the device to communicate with the enterprise management server.
|
||||
- The management client, which periodically synchronizes with the management server to check for updates and apply the latest policies set by IT.
|
||||
|
||||
Third-party MDM servers can manage Windows 10 by using the MDM protocol. The built-in management client is able to communicate with a third-party server proxy that supports the protocols outlined in this document to perform enterprise management tasks. The third-party server will have the same consistent first-party user experience for enrollment, which also provides simplicity for Windows 10 users. MDM servers don't need to create or download a client to manage Windows 10. For details about the MDM protocols, see [\[MS-MDM\]: Mobile Device Management Protocol](/openspecs/windows_protocols/ms-mdm/33769a92-ac31-47ef-ae7b-dc8501f7104f) and [\[MS-MDE2\]: Mobile Device Enrollment Protocol Version 2](/openspecs/windows_protocols/ms-mde2/4d7eadd5-3951-4f1c-8159-c39e07cbe692).
|
||||
Third-party MDM servers can manage Windows 10 by using the MDM protocol. The built-in management client is able to communicate with a third-party server proxy that supports the protocols outlined in this document to perform enterprise management tasks. The third-party server will have the same consistent first-party user experience for enrollment, which also provides simplicity for Windows 10 users. MDM servers don't need to create or download a client to manage Windows 10. For details about the MDM protocols, see [\[MS-MDM\]: Mobile Device Management Protocol](/openspecs/windows_protocols/ms-mdm/33769a92-ac31-47ef-ae7b-dc8501f7104f) and [\[MS-MDE2\]: Mobile Device Enrollment Protocol Version 2](/openspecs/windows_protocols/ms-mde2/4d7eadd5-3951-4f1c-8159-c39e07cbe692).
|
||||
|
||||
## MDM security baseline
|
||||
|
||||
@ -37,7 +37,7 @@ The MDM security baseline includes policies that cover the following areas:
|
||||
- Legacy technology policies that offer alternative solutions with modern technology
|
||||
- And much more
|
||||
|
||||
For more details about the MDM policies defined in the MDM security baseline and what Microsoft's recommended baseline policy values are, see:
|
||||
For more information about the MDM policies defined in the MDM security baseline and what Microsoft's recommended baseline policy values are, see:
|
||||
|
||||
- [MDM Security baseline for Windows 11](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/Windows11-MDM-SecurityBaseLine-Document.zip)
|
||||
- [MDM Security baseline for Windows 10, version 2004](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/2004-MDM-SecurityBaseLine-Document.zip)
|
||||
@ -48,37 +48,27 @@ For more details about the MDM policies defined in the MDM security baseline and
|
||||
|
||||
For information about the MDM policies defined in the Intune security baseline, see [Windows security baseline settings for Intune](/mem/intune/protect/security-baseline-settings-mdm-all).
|
||||
|
||||
<span id="mmat" />
|
||||
|
||||
## Learn about migrating to MDM
|
||||
|
||||
When an organization wants to move to MDM to manage devices, they should prepare by analyzing their current Group Policy settings to see what they need to transition to MDM management. Microsoft created the [MDM Migration Analysis Tool](https://aka.ms/mmat/) (MMAT) to help. MMAT determines which Group Policies have been set for a target user or computer and then generates a report that lists the level of support for each policy setting in MDM equivalents. For more information, see [MMAT Instructions](https://github.com/WindowsDeviceManagement/MMAT/blob/master/MDM%20Migration%20Analysis%20Tool%20Instructions.pdf).
|
||||
|
||||
|
||||
## Learn about device enrollment
|
||||
|
||||
|
||||
- [Mobile device enrollment](mobile-device-enrollment.md)
|
||||
- [Federated authentication device enrollment](federated-authentication-device-enrollment.md)
|
||||
- [Certificate authentication device enrollment](certificate-authentication-device-enrollment.md)
|
||||
- [On-premise authentication device enrollment](on-premise-authentication-device-enrollment.md)
|
||||
- [Mobile device enrollment](mobile-device-enrollment.md)
|
||||
- [Federated authentication device enrollment](federated-authentication-device-enrollment.md)
|
||||
- [Certificate authentication device enrollment](certificate-authentication-device-enrollment.md)
|
||||
- [On-premise authentication device enrollment](on-premise-authentication-device-enrollment.md)
|
||||
|
||||
## Learn about device management
|
||||
|
||||
|
||||
- [Azure Active Directory integration with MDM](azure-active-directory-integration-with-mdm.md)
|
||||
- [Enterprise app management](enterprise-app-management.md)
|
||||
- [Mobile device management (MDM) for device updates](device-update-management.md)
|
||||
- [Enable offline upgrades to Windows 10 for Windows Embedded 8.1 Handheld devices](enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md)
|
||||
- [OMA DM protocol support](oma-dm-protocol-support.md)
|
||||
- [Structure of OMA DM provisioning files](structure-of-oma-dm-provisioning-files.md)
|
||||
- [Server requirements for OMA DM](server-requirements-windows-mdm.md)
|
||||
- [Enterprise settings, policies, and app management](windows-mdm-enterprise-settings.md)
|
||||
- [Azure Active Directory integration with MDM](azure-active-directory-integration-with-mdm.md)
|
||||
- [Enterprise app management](enterprise-app-management.md)
|
||||
- [Mobile device management (MDM) for device updates](device-update-management.md)
|
||||
- [Enable offline upgrades to Windows 10 for Windows Embedded 8.1 Handheld devices](enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md)
|
||||
- [OMA DM protocol support](oma-dm-protocol-support.md)
|
||||
- [Structure of OMA DM provisioning files](structure-of-oma-dm-provisioning-files.md)
|
||||
- [Server requirements for OMA DM](server-requirements-windows-mdm.md)
|
||||
- [Enterprise settings, policies, and app management](windows-mdm-enterprise-settings.md)
|
||||
|
||||
## Learn about configuration service providers
|
||||
|
||||
|
||||
- [Configuration service provider reference](configuration-service-provider-reference.md)
|
||||
- [WMI providers supported in Windows 10](wmi-providers-supported-in-windows.md)
|
||||
- [Using PowerShell scripting with the WMI Bridge Provider](using-powershell-scripting-with-the-wmi-bridge-provider.md)
|
||||
- [MDM Bridge WMI Provider](/windows/win32/dmwmibridgeprov/mdm-bridge-wmi-provider-portal)
|
||||
- [Configuration service provider reference](configuration-service-provider-reference.md)
|
||||
- [WMI providers supported in Windows 10](wmi-providers-supported-in-windows.md)
|
||||
- [Using PowerShell scripting with the WMI Bridge Provider](using-powershell-scripting-with-the-wmi-bridge-provider.md)
|
||||
- [MDM Bridge WMI Provider](/windows/win32/dmwmibridgeprov/mdm-bridge-wmi-provider-portal)
|
||||
|
@ -904,6 +904,11 @@ items:
|
||||
items:
|
||||
- name: UnifiedWriteFilter DDF file
|
||||
href: unifiedwritefilter-ddf.md
|
||||
- name: UniversalPrint CSP
|
||||
href: universalprint-csp.md
|
||||
items:
|
||||
- name: UniversalPrint DDF file
|
||||
href: universalprint-ddf-file.md
|
||||
- name: Update CSP
|
||||
href: update-csp.md
|
||||
items:
|
||||
|
110
windows/client-management/mdm/universalprint-csp.md
Normal file
110
windows/client-management/mdm/universalprint-csp.md
Normal file
@ -0,0 +1,110 @@
|
||||
---
|
||||
title: UniversalPrint CSP
|
||||
description: Learn how the UniversalPrint configuration service provider (CSP) is used to install printers on Windows client devices.
|
||||
ms.author: mandia
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: MandiOhlinger
|
||||
ms.date: 06/02/2022
|
||||
ms.reviewer: jimwu
|
||||
manager: dougeby
|
||||
---
|
||||
|
||||
# UniversalPrint CSP
|
||||
|
||||
The table below shows the applicability of Windows:
|
||||
|
||||
|Edition|Windows 11|
|
||||
|--- |--- |
|
||||
|Home|No|
|
||||
|Pro|Yes|
|
||||
|Windows SE|Yes|
|
||||
|Business|Yes|
|
||||
|Enterprise|Yes|
|
||||
|Education|Yes|
|
||||
|
||||
The UniversalPrint configuration service provider (CSP) is used to add Universal Print-compatible printers to Windows client endpoints. Universal Print is a cloud-based printing solution that runs entirely in Microsoft Azure. It doesn't require any on-premises infrastructure. For more specific information, go to [What is Universal Print](/universal-print/fundamentals/universal-print-whatis).
|
||||
|
||||
This CSP was added in Windows 11.
|
||||
|
||||
The following example shows the UniversalPrint configuration service provider in tree format.
|
||||
|
||||
```console
|
||||
./Vendor/MSFT
|
||||
PrinterProvisioning
|
||||
----UPPrinterInstalls
|
||||
--------<GUID> (PrinterSharedID)
|
||||
--------CloudDeviceID
|
||||
--------PrinterSharedName
|
||||
--------Install
|
||||
--------Status
|
||||
--------ErrorCode
|
||||
```
|
||||
|
||||
<a href="" id="PrinterProvisioning"></a>**./Vendor/MSFT/PrinterProvisioning**
|
||||
The root node for the Universal Print PrinterProvisioning configuration service provider.
|
||||
|
||||
<a href="" id="upprinterinstalls"></a>**UPPrinterInstalls**
|
||||
|
||||
This setting will install or uninstall a specific printer to a targeted user account.
|
||||
|
||||
Valid values:
|
||||
|
||||
- Install (default) - The printer is installed.
|
||||
- Uninstall - The printer is uninstalled.
|
||||
|
||||
The data type is node (XML node). Supported operation is Get.
|
||||
|
||||
<a href="" id="guidprintersharedid)"></a>**`<GUID>` (PrinterSharedID)**
|
||||
|
||||
The Share ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share ID in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
|
||||
The data type is node (XML node). Supported operations are Get, Add, and Delete.
|
||||
|
||||
> [!NOTE]
|
||||
> The targeted user account must have access rights to the printer and to the Universal Print service.
|
||||
|
||||
<a href="" id="clouddeviceid"></a>**CloudDeviceID**
|
||||
|
||||
The Printer ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Printer ID in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
|
||||
The data type is string/text (GUID). Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
> [!NOTE]
|
||||
> The targeted user account must have access rights to the printer and to the Universal Print service.
|
||||
|
||||
<a href="" id="printersharedname"></a>**PrinterSharedName**
|
||||
|
||||
The Share Name is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share Name in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
|
||||
The data type is string/text. Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
> [!NOTE]
|
||||
> The targeted user account must have access rights to the printer and to the Universal Print service.
|
||||
|
||||
<a href="" id="install"></a>**Install**
|
||||
|
||||
Installs the Universal Print printer. Supports async execute.
|
||||
|
||||
The data type is string/text (empty string). Supported operations are Get and Execute.
|
||||
|
||||
<a href="" id="status"></a>**Status**
|
||||
|
||||
The result status of the printer installation.
|
||||
|
||||
Valid values:
|
||||
|
||||
- 1 (default) - Installation completed successfully.
|
||||
- 2 - Installation is in progress after receiving execute cmd.
|
||||
- 4 - Installation failed.
|
||||
- 8 - Installation initial status
|
||||
- 32 - Unknown (not used)
|
||||
|
||||
The data type is int. Supported operations is Get.
|
||||
|
||||
<a href="" id="errorcode"></a>**ErrorCode**
|
||||
|
||||
HRESULT of the last installation returned code.
|
||||
|
||||
The data type is int. Supported operation is Get.
|
214
windows/client-management/mdm/universalprint-ddf-file.md
Normal file
214
windows/client-management/mdm/universalprint-ddf-file.md
Normal file
@ -0,0 +1,214 @@
|
||||
---
|
||||
title: UniversalPrint DDF file
|
||||
description: UniversalPrint DDF file
|
||||
ms.author: mandia
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: MandiOhlinger
|
||||
ms.date: 06/02/2022
|
||||
ms.reviewer: jimwu
|
||||
manager: dougeby
|
||||
---
|
||||
|
||||
# UniversalPrint DDF file
|
||||
|
||||
This article shows the OMA DM device description framework (DDF) for the **UniversalPrint** configuration service provider.
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is the current version for this CSP.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN"
|
||||
"http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"
|
||||
[<?oma-dm-ddf-ver supported-versions="1.2"?>]>
|
||||
<MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
|
||||
<VerDTD>1.2</VerDTD>
|
||||
<Node>
|
||||
<NodeName>PrinterProvisioning</NodeName>
|
||||
<Path>./User/Vendor/MSFT</Path>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<Description>Printer Provisioning</Description>
|
||||
<DFFormat>
|
||||
<node />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>com.microsoft/1.0/MDM/PrinterProvisioning</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
<Node>
|
||||
<NodeName>UPPrinterInstalls</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<Description>This setting will take the action on the specified user account to install or uninstall the specified printer. Install action is selected by default.</Description>
|
||||
<DFFormat>
|
||||
<node />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<DDFName></DDFName>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
<Node>
|
||||
<NodeName></NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
<Add />
|
||||
<Delete />
|
||||
</AccessType>
|
||||
<Description>Identifies the Universal Print printer, by its Share ID, you wish to install on the targeted user account. The printer's Share ID can be found in the printer's properties via the Universal Print portal. Note: the targeted user account must have access rights to both the printer and to the Universal Print service.</Description>
|
||||
<DFFormat>
|
||||
<node />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<OneOrMore />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFTitle>PrinterSharedID</DFTitle>
|
||||
<DFType>
|
||||
<DDFName></DDFName>
|
||||
</DFType>
|
||||
<DynamicNodeNaming>
|
||||
<UniqueName>PrinterSharedID from the Universal Print system, which is used to discover and install Univeral Print printer</UniqueName>
|
||||
</DynamicNodeNaming>
|
||||
<TrackedResource />
|
||||
<AsynchronousTracking ResourceInProgressValues="2,8" ResourceFailureValues="4,32" ResourceSuccessURI="UPPrinterInstalls/@#ResourcePlaceholder@/status" ResourceSuccessValues="1" />
|
||||
</DFProperties>
|
||||
<Node>
|
||||
<NodeName>CloudDeviceID</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
<Add />
|
||||
<Delete />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>Identifies the Universal Print printer, by its Printer ID, you wish to install on the targeted user account. The printer's Printer ID can be found in the printer's properties via the Universal Print portal. Note: the targeted user account must have access rights to both the printer and to the Universal Print service.</Description>
|
||||
<DFFormat>
|
||||
<chr />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>Install</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
<Exec />
|
||||
</AccessType>
|
||||
<Description>Support async execute. Install Universal Print printer.</Description>
|
||||
<DFFormat>
|
||||
<null />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>Status</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<Description>1 finished installation successfully, 2 installation in progress after receiving execute cmd, 4 installation failed, 8 installation initial status, 32 unknown (not used).</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>ErrorCode</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<Description>HRESULT of the last installation returned code.</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>PrinterSharedName</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
<Add />
|
||||
<Delete />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>Identifies the Universal Print printer, by its Share Name, you wish to install on the targeted user account. The printer's Share Name can be found in the printer's properties via the Universal Print portal. Note: the targeted user account must have access rights to both the printer and to the Universal Print service.</Description>
|
||||
<DFFormat>
|
||||
<chr />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
</Node>
|
||||
</Node>
|
||||
</Node>
|
||||
</MgmtTree>
|
||||
```
|
Reference in New Issue
Block a user