When migrating an SCCM Server to a new server or when updating the ADK on the SCCM server often we end up with old boot images that not only they cannot be customized via SCCM administration console any more but also the information regarding the integrated drivers is not more available. To resolve this issue the following powershell script has been developed. The script should be first rune before ADK Update / SCCM migration so that the information of the imported boot image drivers is exported for each boot image into an xml file named "ExportBootDrivers_[Boot Image Name].xml" in c:\temp folder. After the ADK update /SCCM migration the script should be run one more time in ordert to import the required drivers into the new boot images that have the same name as the old one.
0 Comments
ISSUE:
Software Updates deployment does not work in an SCCM Environment configured for HTTP (no certificates used for client communication). On SCCM clients there is an error “0x800244017” in WUAHandler.log. The following script has been developed to automate the BIOS Upgrade of HP Hardware. The required tools and BIOS versions (.bin and .cab files) can be downloaded from the HP web site (https://support.hp.com/us-en/drivers). The HP tools and BIOS files should be saved in the same folder as the Update-BIOS.ps1 script. When run the scripts first suspends BitLocker then installs the newest BIOS version and finally a RunOnce registry value is created in order to re-enable BitLocker after the computer is rebooted. The script is to be used with SCCM and a SCCM software package should be created.
PROBLEM:
After upgrading our SCCM server to 1710 version our windows 7 task sequence stopped to work for one of our HP hardware models (HP EliteBook 800G1). There were different errors when testing the TS. The error was always when installing software after the "Setup Windows and Configuration Manager" Step. The errors found in the log files on the clients when testing the TS were: Install Software Failed 0x800706ba Install Software failed 0x87d00215 Install Software failed 0x87d01011 By installing an application that has more that 2000 files I have got the famous hash error 0x80091007 on the client (CAS.log). It seems that SCCM has a problem when calculating the hash for a download with too many files. The solution was simply to customize the application so that these 2000 files are downloaded as a single zip file, unzipped on the client and the application is subsequently installed on the client.
The latest version of the Configuration Manager Technical Preview (v1712) makes possible to have a non DP client to respond to PXE requests. In order to configure a client based PXE a Task Sequence for copying boot images to the PXE-enabled client and a custom client setting for enabling the PXE Feature on the PXE-enabled client have to be created and deployed to the PXE-enabled client.
ISSUE
After in-place upgrading of SCCM server to version 1706 all clients in the SCCM administration console are showing as offline. In the Configuration Manager Status Message Viewer there are many Message IDs 4951 and 1020 from the SMS_NOTIFICATION_SERVER component. Furthermore there is 0x80004005 error message in BgbSetup.log file. Having a driver in configuration manager database that that has an invalid7not existing source path can lead to many problems. With the following powershell script you can find all those drivers.
When monitoring software update deployments I have noticed that many Windows 10 v1511 clients haven't reported their update status and that they have been listed in the SCCM administration console with the status "Unknown". The error message both in WUAHandler.log and ScanAgent.log file on the affected clients was "Scan failed with Error==x80240fff".
The solution was simple to install the KB4015219 Update for Windows 10. The update can be downloaded from here: KB4015219 - x64 KB4015219 - x86 Today I installed WSUS role on Windows 2012 R2 Server in order to install Configuration Manager Software Update Point. After the WSUS has been successfully installed there was an issue with the WSUS service. The service wasn't running. By starting the service manually an error 192 0xc1 poped up. Also in event viewer there could be "Event ID 7000 : not a valid Win32 application" errors found. The cause of the problem was, as discribed here, a file named "program" on the system drive (c:\program). The solution was simply to delete/rename this file.
|
Author
Write something about yourself. No need to be fancy, just an overview. Archives
November 2022
Categories
All
|