MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
633 stars 281 forks source link

log files missing #147

Closed vartaxe closed 4 years ago

vartaxe commented 5 years ago

hi,

i just noticed that lately there seem to be some log files missing...

Invoke-DellBIOSUpdate.log (ok) DellFlashBIOSUpdate.log (empty)

and missing ones are:

ApplyDriverPackage.log ApplyBIOSPackage.log

image

ps: there is only windows 7 driver available for the dell optiplex 780 so it will fail with error code 9... somekinf of fallback to windows 7 driver packages would be nice. also notice the bios flash step exit code is 4294967295 even tough it should be 2

image

vartaxe commented 5 years ago

so no bios upgrade happenned and tried running after windows upgrade finished and now still the same 4294967295 error but 123 exit code instead of 2 when in deployment type = biosupdate

The operating system reported error 123: The filename, directory name, or volume label syntax is incorrect.

and DellFlashBIOSUpdate.log still empty.

ps: manually running the O780-A15.exe successfully completed the flash.

vartaxe commented 5 years ago

btw http://en.community.dell.com/techcenter/enterprise-client/w/wiki/3462.dup-bios-updates.aspx

/s = silent; /r = reboot; /f = forcefully downgrade Code Meaning Description -1 Cancel User manually canceled the update when using the GUI. 0 Successful This value isn’t returned for BIOS updates because they always require a reboot. 0 would be returned from a DUP that doesn’t require a reboot. 1 General failure There are probably many cases when this value is returned. One case when this value is returned is when the hard dependency BIOS version was not already installed on the system. Another common case is when incompatible command line options are used together. 2 Reboot required This value is returned when a successful update happens and just the /s option is used. 3 Soft dependency failure One example when this value is returned is when a system is updated to the same BIOS version that is already installed or a system is rolled back to an older BIOS version. This failure can be overridden with the /f option. 4 Hard dependency failure This value is returned when some required dependency was not met. Try running the update again with the log option (/l="C:\mylog.txt") to get more detailed failure information. This failure cannot be overridden with the /f option. 5 Hard error The update doesn't apply to the system (OS not supported, model not supported, etc). This failure cannot be overridden with the /f option. 6 Rebooting system This value is returned when a successful update happens and both the /s and /r options are used. 7 Invalid password or password validation failure This value is returned when there is a password error. If an administrator uses the /s option and forgets to supply a password, then a password prompt will not be displayed. If an administrator supplies the wrong password, then a prompt is displayed though. 8 Unknown 9 RPM verification failed This value does not apply to Windows operating systems.

vartaxe commented 5 years ago

Nobody with same issue?