G
Guest
Just thought I'd document a couple of issues I've had with WMI not
working in bare metal situations. The same OSDWinPE.wim works under
Refresh without a problem.
zerotouchinstallation.vbs - log
======================================================
Operating System = WinPE
Is a server OS = False
Warning - Unable to obtain HAL information since WMI is unavailable.
Host name = MININT-GU631JC1
Warning - Unable to obtain asset details (asset tag, serial number,
make, model, product, UUID) since WMI is unavailable.
It seems there's a bug with mechanism that updates the OSDWinPE.wim
file. If you are building a custom OSDWinPE.wim (Update Windows PE in
SMS console) the source must be a CD. It cannot be a UNC or Network
path, as empty dirs aren't copied for some reason. These missing
directories break WMI under readonly (CD/ISO) environments. I suppose
as it cannot create these needed directories.
Hopefully this will be addressed with a patch.
Rob
working in bare metal situations. The same OSDWinPE.wim works under
Refresh without a problem.
zerotouchinstallation.vbs - log
======================================================
Operating System = WinPE
Is a server OS = False
Warning - Unable to obtain HAL information since WMI is unavailable.
Host name = MININT-GU631JC1
Warning - Unable to obtain asset details (asset tag, serial number,
make, model, product, UUID) since WMI is unavailable.
It seems there's a bug with mechanism that updates the OSDWinPE.wim
file. If you are building a custom OSDWinPE.wim (Update Windows PE in
SMS console) the source must be a CD. It cannot be a UNC or Network
path, as empty dirs aren't copied for some reason. These missing
directories break WMI under readonly (CD/ISO) environments. I suppose
as it cannot create these needed directories.
Hopefully this will be addressed with a patch.
Rob