Vista previa técnica del Administrador de configuración 2006.
Use the Company Portal app on co-managed devices
The Company Portal is now the cross-platform app portal experience for Microsoft Endpoint Manager. You can now use a preview version of the Company Portal on co-managed devices. By configuring co-managed devices to also use the Company Portal, you can provide a consistent user experience on all devices.
This preview version of the Company Portal supports the following actions:
- Launch the Company Portal app on co-managed devices and sign in with Azure Active Directory (AD azul) single sign-on (inicio de sesión único).
- View available and installed Configuration Manager apps in the Company Portal alongside Intune apps.
- Install available Configuration Manager apps from the Company Portal and receive installation status information.
The behavior of the Company Portal depends upon your co-management workload configuration:
Workload | Configuración | Behavior |
---|---|---|
Client apps | Administrador de configuración | You can see only Configuration Manager client apps |
Client apps | Pilot Intune o Afinado | You can see both Configuration Manager and Intune client apps |
Office Click-to-run apps | Administrador de configuración | You can see only Configuration Manager Office click-to-run apps |
Office Click-to-run apps | Pilot Intune o Afinado | You can see only Intune Office click-to-run apps |
Prerequisites for Company Portal preview
- Contact the Company Portal preview team to get started:
cppreview@microsoft.com
- ventanas 10, versión 1803 o después:
- Enrolled to co-management
- Access to internet endpoints for Intune
- The user accounts that sign in to these devices require the following configurations:
- An Azure AD identity
- Assigned an Intune license
Mejoras en las aplicaciones disponibles a través de CMG
Un basado en Internet, dispositivo unido a un dominio que no está unido a Azure Active Directory (AD azul) y se comunica a través de una puerta de enlace de gestión en la nube (CMG) ahora puede implementar aplicaciones según estén disponibles. El usuario del dominio Active Directory del dispositivo necesita una identidad de Azure AD coincidente. Cuando el usuario inicia el Centro de software, Windows les solicita que ingresen sus credenciales de Azure AD. Luego pueden ver las aplicaciones disponibles..
Configure the following prerequisites to enable this functionality:
- ventanas 10 device
- Joined to your on-premises Active Directory domain
- Communicate via CMG
- The site has discovered the user by both Active Directory and Azure AD user discovery
Los clientes de intranet pueden utilizar un punto de actualización de software CMG
Intranet clients can now access a CMG software update point when it’s assigned to the boundary group. Admins can allow intranet devices to scan against a CMG software update point in the following scenarios:
- When an internet machine connects to the VPN, it will continue scanning against the CMG software update point over the internet.
- If the only software update point for the boundary group is the CMG software update point, then all intranet and internet devices will scan against it.
Mejoras en las secuencias de tareas a través de CMG
Esta versión incluye las siguientes mejoras para implementar secuencias de tareas en dispositivos que se comunican a través de una puerta de enlace de administración en la nube. (CMG):
- Soporte para la implementación del sistema operativo: Con una secuencia de tareas que utiliza una imagen de arranque para implementar un sistema operativo, puedes implementarlo en un dispositivo que se comunique a través de CMG. El usuario debe iniciar la secuencia de tareas desde el Centro de software.
- Esta versión corrige los dos problemas conocidos de la versión actual de la rama de Configuration Manager. 2002. Ahora puede ejecutar una secuencia de tareas en un dispositivo que se comunica a través de CMG en las siguientes circunstancias:
- Un dispositivo de grupo de trabajo que usted registra con un token de registro masivo
- Configura el sitio para HTTP mejorado y el punto de administración es HTTP
Known issue with OS deployment via CMG
If there’s an Install Application step in an OS deployment task sequence to a client via CMG, it fails to download the app policy. To work around this issue, disable this step in the task sequence. Deploy the app separately from the task sequence.
Información de gestión para optimizar para los trabajadores remotos
Esta versión agrega un nuevo grupo de conocimientos de gestión., Optimizar para trabajadores remotos. Estos conocimientos le ayudan a crear mejores experiencias para los trabajadores remotos y reducir la carga en su infraestructura.. La información contenida en esta versión se centra principalmente en VPN.:
- Definir grupos de límites de VPN: Create a VPN boundary and associate it to a boundary group. Associate VPN-specific site systems to the group, and configure the settings for your environment. This insight checks for at least one boundary group with at least one VPN boundary in it. From the properties of this insight, seleccionar Review Actions to go to the Grupos de límites nodo.
- Configure los clientes conectados a VPN para que prefieran fuentes de contenido basadas en la nube: To reduce traffic on the VPN, enable the boundary group option to Prefer cloud based sources over on-premises sources. This option allows clients to download content from the internet instead of distribution points across the VPN.
- Deshabilite el intercambio de contenido de igual a igual para clientes conectados a VPN: To prevent unnecessary peer-to-peer traffic that likely doesn’t benefit the remote clients, disable the boundary group option to Allow peer downloads in this boundary group.
Improvements to VPN boundary type
You can now create more than one VPN boundary, and can detect the connection by the VPN name or description. When you open the Create Boundary página, y seleccione el VPN tipo, choose one of the following options:
- Auto detect VPN: This option is the same behavior as before. The boundary value in the console list will be
AUT:1
. It should detect any VPN solution that uses the point-to-point tunneling protocol (PPTP). If it doesn’t detect your VPN, use one of the other options. - Connection name: Specify the name of the VPN connection on the device. It’s the name of the network adapter in Windows for the VPN connection. Configuration Manager matches the first 251 characters of the string, but doesn’t support wildcard characters or partial strings. The boundary value in the console list will be
NAM:<name>
, dónde<name>
is the connection name that you specify. Por ejemplo, you run theipconfig
command on the device, and one of the sections starts with:PPP adapter ContosoVPN:
. Use the stringContosoVPN
as the Connection name. It displays in the list asNAM:ContosoVPN
. - Connection description: Specify the description of the VPN connection. Configuration Manager matches the first 251 characters of the string, but doesn’t support wildcard characters or partial strings. The boundary value in the console list will be
DES:<description>
, dónde<description>
is the connection description that you specify. Por ejemplo, you run theipconfig /all
command on the device, and one of the connections includes the following line:Description . . . . . . . . . . . : ContosoMainVPN
. Use the stringContosoMainVPN
as the Connection description. It displays in the list asDES:ContosoMainVPN
.
In every case, the device needs to be connected to the VPN for Configuration Manager to associate the client in that boundary.
Tenant Attach: Improvements to Configuration Manager actions in Microsoft Endpoint Manager admin center
This release introduces some improvements to the administration of Configuration Manager devices in Microsoft Endpoint Manager admin center. Improvements include:
- Configuration errors now include links to documentation to help you troubleshoot.
- User available applications now appear in the Aplicaciones node for a ConfigMgr device.
- The application list includes applications deployed to a user currently logged on to the device.
- Multi-user session scenarios aren’t supported.
- Azure AD joined devices aren’t currently supported, only AD joined devices.
Soporte de CMG para políticas de protección de endpoints
Mientras que la puerta de enlace de gestión de la nube (CMG) ha admitido políticas de protección de endpoints, los dispositivos requerían acceso a controladores de dominio locales. A partir de esta versión, Los clientes que se comunican a través de un CMG pueden aplicar inmediatamente políticas de protección de terminales sin una conexión activa a Active Directory..
Importe la aplicación de Azure AD creada previamente durante la incorporación de la conexión de inquilinos
Durante una nueva incorporación, un administrador puede especificar una aplicación creada previamente durante la incorporación al inquilino adjunto. Desde el Tenant onboarding page in the Co-management Configuration Wizard, seleccionar Optionally import a separate web app to synchronize Configuration Manager client data to Microsoft Endpoint Manager admin center. This option will prompt you to specify the following information for your Azure AD app:
- Azure AD tenant name
- Azure AD tenant ID
- Nombre de la aplicación
- Client ID
- Secret key
- Secret key expiry
- App ID URI
Improvements to client upgrade on a metered connection
Starting in Configuration Manager technical preview version 2005, you could install and upgrade the client when you allowed client communication on a metered connection. You can now also configure the client setting Comunicación con el cliente en conexiones a Internet medidas a Límite. This option reduces the client communication on a metered network, but now still allows the client to stay current.
Para más información, ver los siguientes artículos:
- Technical preview 2005: Instalar y actualizar el cliente en una conexión medida
- Acerca de la configuración del cliente: Comunicación con el cliente en conexiones a Internet medidas
Mejoras en la gestión de reinicios del dispositivo.
Configuration Manager provides many options to manage device restart notifications. Basado en sus comentarios de UserVoice, you can now configure client settings to prevent devices from automatically restarting when a deployment requires it. Por defecto, Configuration Manager can still force devices to restart.
Importante:This new client setting applies to all application, actualización de software, and package deployments to the device. Until a user manually restarts the device:
- Software updates and app revisions may not be fully installed
- Additional software installs may not happen
Soporte mejorado para Windows Virtual Desktop
El ventanas 10 Multisesión empresarial La plataforma está disponible en la lista de versiones de sistema operativo compatibles en objetos con reglas de requisitos o listas de aplicabilidad..
NOTA: If you previously selected the top-level ventanas 10 platform, this action automatically selected all child platforms. This new platform isn’t automatically selected. If you want to add ventanas 10 Multisesión empresarial, manually select it in the list.
Direct links to Configuration Manager Community hub items
You can now easily navigate to and reference items in the Configuration Manager console Community hub node with a direct link. The intention for this feature is for easier collaboration and being able to share links to Community hub items with your colleagues. Actualmente, you’ll see these links shared by the Configuration Manager team and in the documentation.
Por ejemplo, use this link to share the Configure Edge Auto Update script (https://communityhub.microsoft.com/item/7200
). If you have the technical preview branch version 2006 console installed, follow that link, y luego seleccione Launch the Community hub. The console opens directly to the script in the Community hub.
NOTA:These deep links are currently only for items in the Community hub node of the console.
General known issues
Azure AD authentication doesn’t work
Configuration Manager’s use of the Azure Active Directory (AD azul) security token service doesn’t work. El CCM_STS.log on the management point contains an entry similar to the following error: ProcessRequest - Exception: System.IO.FileLoadException: Could not load file or assembly 'System.IdentityModel.Tokens.JWT.
It also includes the HRESULT 0x80131040.
Another symptom is issues with a cloud management gateway (CMG). If you run the CMG connection analyzer, it fails testing the CMG channel for management point with the following error: Failed to get ConfigMgr token with Azure AD token. Status code is '500' and status description is 'CMGConnector_InternalServerError'.
This issue is because of a version discrepancy with a supporting library.
To work around the issue, Copiar System.IdentityModel.Tokens.JWT.dll from the \bin\X64 folder of the installation directory on the site server to the SMS_CCM\CCM_STS\bin folder on the management point.