Quantcast
Channel: TechNet Blogs
Viewing all articles
Browse latest Browse all 34890

Impacto de los nuevos dispositivos UEFI sobre System Center Configuration Manager

$
0
0

Hola,

Últimamente han surgido varias consultas sobre el nuevo método de arranque de los fabricantes, UEFI, y su integración e impacto sobre Configuration Manager.

Configuration Manager se ve impactado por esta tecnología sobre todo en la parte de PXE, se precisa un cambio en la lógica y ficheros del arranque, para que dispositivos con UEFI en modo nativo sean capaces de arrancar por PXE, descargar los ficheros de arranque correctos y comenzar con el despliegue, previamente a tener disponible el ADK Windows Assessment and Deployment Kit (Windows ADK).

Esto se debe a que UEFI modifica la forma de arrancar el hardware, la configuración de disco del hardware, y otros componentes, lo que precisa de un modo diferente de acceso al sistema de arranque, con lo que todo ocurre antes de que el sistema operativo se encuentre disponible, que es la parte que nosotros podemos controlar.

Por esto, hasta que no se ha tenido disponible System Center Configuration Manager 12 SP1, en el cual se ha integrado ADK, no se ha tenido un pleno soporte a esta solución, siendo la opción disponible el arranque del dispositivo en modo BIOS-Compatibility Mode.

En caso de no ser así se puede recibir el mensaje "PXE-E16: No offer received", entre otros eventos.

A continuación adjunto algunos links que amplían esta información.

Information about UEFI support in Configuration Manager:

http://technet.microsoft.com/en-us/library/jj591552.aspx#BKMK_WhatsNewSP1_Clients
Changes to task sequence:
◦ The default task sequences were changed to optimize the deployment of operating systems starting with Windows 7.
◦ Support for computers that are in Unified Extensible Firmware Interface (UEFI) mode. The task sequence sets the SMSTSBootUEFI built-in task sequence variable when it detects a computer that is in UEFI mode.
◦ The default task sequence automatically partitions the computer based on whether it was booted in UEFI mode or BIOS mode (conditioned based on the value of the _SMSTSBootUEFI variable).
http://technet.microsoft.com/en-us/library/jj938037.aspx
UEFI-based computers: Before you install Windows 8 on a UEFI-based computer, note the following.
◦ All computers that are certified for Windows 8 use firmware that meets the UEFI specifications.
◦ For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode. It is not supported to switch from legacy BIOS-compatibility mode to UEFI mode by using a task sequence. For more information, see How to Switch from BIOS-Compatibility Mode to UEFI Mode.
◦ Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode. To provision these computers in UEFI mode, you must start them from boot media instead of using PXE. If the computer performs a PXE-initiated boot, Configuration Manager detects that the computer is in BIOS mode and therefore provisions the computer as such. For more information about how to create boot media, see the How to Create Bootable Media section in the How to Deploy Operating Systems by Using Media in Configuration Manager topic.
◦ UEFI and BIOS have different disk partitioning requirements. UEFI hard disks require the GUID partition table (GPT) partition structure, instead of the master boot record (MBR) partition structure that is used in BIOS. When you use a task sequence to deploy Windows 8, the task sequence detects whether the computer was started in UEFI mode or BIOS-compatibility mode, and the task sequence configures the partitions on the hard disk to accommodate the associated requirements.

 

Un Saludo

 

Raul del Moral


Viewing all articles
Browse latest Browse all 34890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>