Issue:
Task sequence fails with “Failed to Download Policy” and code 0x80004005
This error code typically refers to a certificate validation issue.
The SMSTS.LOG file will show an entry with the following text:
Failed to download policy
Check the certificates under the Site Settings node to if any certificates are blocked or missing. Open the certificates to ensure that the certificates are installed into the certificate store. If not, install the certificates.
Task sequence fails with “Failed to Download Policy” and code 0x80093102 or 0x80004005
This error code typically refers to a certificate validation issue.
The SMSTS.LOG file will show an entry with the following text: CryptDecryptMessage (&DecryptParams, pbEncrypted, EncryptedSize, 0, &nPlainSize, 0 ), HRESULT=80093102
Or
No cert available for policy decoding.
Possible causes are:
Misconfiguration of your domain or a site server, such as DNS not pointing to the site server, or the site server not specifying a valid FQDN (which is referred to by the DNS listing).
If your site server does not specify a FQDN (and only specifies the NETBIOS name), and your DNS server refers to the FQDN, a faulty lookup might cause this error.
The certificate being used for PXE and boot media.
Resolution:
Check the certificates under the Site Settings node and see if any certificates are blocked or missing. Open the certificates and ensure that they are actually installed into the certificate store. If not, install them.
If these actions do not work, try removing the package from the distribution point (via Manage Distribution Points) and adding the package again to regenerate the package hash.
Issue:
NO ASSIGNED TASK SEQUENCE WHEN INITIATING DEPLOYMENTS CAUSED BY DUPLICATE SMBIOS GUIDS
Possible causes are:
This problem can be caused by more than one PC in the environment having the same SMBIOS GUID. ConfigMgr refers to the SMSBIOS GUID as System UUID. Similar to a MAC Addresses being unique to a NIC card, the SMBIOS GUIDs should also be unique on each PC. Two PCs should not have the same SMBIOS GUID. The SMBIOS GUID is stored in the PC's BIOS.
The problem occurs because when the ConfigMgr database is queried for available Task Sequence that are advertised to that PC, it does so first by using the PC's SMBIOS GUID. Each record in the ConfigMgr database records the PC's SMBIOS GUID under the attribute System UUID. If it does not match a record with the SMBIOS GUID, it then uses the MAC Address instead.
However, if multiple PCs have the same SMBIOS GUID in the environment, when the query on the SMBIOS GUID is done on the ConfigMgr database, it may find the record for a PC other than the one that the Task Sequence is advertised to. If the Task Sequence is not also advertised to the PC that it found, it will return back that there are no task sequences available for the computer.
Note Do not confuse the SMBIOS GUID with the SMS GUID. They are two separate, different, and distinct items. The SMBIOS GUID is a unique hardware identifier used universally, whereas the SMS GUID is a unique ConfigMgr client ID used exclusively by SMS/ConfigMgr.
To see if the problem exists in the environment, create a query or collection in ConfigMgr based on the suspected duplicate SMBIOS GUID using the System UUID attribute. If more than one PC has the same SMBIOS GUID, then the problem exists.
To obtain the SMBIOS GUID from a PC having the problem, use one of the below methods:
-
At a command prompt, run the command: wmic.
-
When the prompt wmic:root\cli>.
-
appears, type in the command: csproduct get uuid.
-
The SMBIOS GUID for the PC should be displayed.
Please note that in scenarios where the PC does not have a bootable OS, the PC can be boot into WinPE via PXE or boot media, and then the above commands run from a command prompt window running in WinPE.
-
On most PCs the SMBIOS GUID appears next to GUID: at the PXE boot screen. To pause the PXE boot screen so that the SMBIOS GUID can be copied down, hit the Pause/Break key on the keyboard while at the PXE boot screen. This can be done even if a PXE server does not exist in the environment. However to view the PXE boot screen, PXE booting must be enabled in the BIOS of the PC and either F12 may need to be hit to get to the PXE boot screen or the NIC may need to be temporarily set as the first boot device on the PC.
-
For PCs that successfully boots into WinPE from boot media but fails to receive an advertised Task Sequence, the SMBIOS GUID will be displayed in the SMSTS.log next to the line
Setting SMBIOS GUID =
-
For PCs that do not successfully boot from PXE, the SMSPXE.log on the server hosting the PXE Service Point can be examined for the PC's SMBIOS GUID. The line that contains this information will be something as follows:
MAC=<Mac_Address> SMBIOS GUID=<SMBIOS_GUID> > Device found in the database. MacCount=x GuidCount=y
Note: Ignore the lines in the SMSPXE.log with all Fs for the MAC Address:
MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=<SMBIOS_GUID> > Device not found in the database. smspxe
These lines are the PXE Service Point performing a self-check on itself by performing a PXE request to itself to make sure the PXE Service Point is up and operational.
To create a query based Collection that finds all PCs with a particular SMBIOS GUID:
-
In the ConfigMgr console, navigate to "Site Database" --> "ComputerManagement" --> "Collections"
-
Right click on "Collections" and choose "New Collection"
-
On the "General" page of the "New Collection Wizard", give the Collection a name next to the "Name:" textbox and then click on the "Next >" button.
-
On the "Membership Rules" page of the "New Collection Wizard", click on the yellow Query icon.
-
Under the "General" tab of the "Query Rule Properties" window, give the query a name next "Name:" textbox and then click on the "Edit Query Statement..." button.
-
In the "Query Statement Properties" window, click on the "Criteria" tab, and then click on the yellow starburst button.
-
In the "Criterion Properties" window, make sure that the "Criterion Type:" is set to "Simple value" and then click on the "Select..." button.In the "Select Attribute" window:
-
Next to "Attribute class:", select "System Resource"
-
Next to "Alias as:", leave at the default of "<No Alias>".
-
Next to "Attribute:", choose "System UUID"
-
In the "Select Attribute" window, click on the "OK" button.
-
In the "Criterion Properties" window, make sure that the "Operator:" is set to "is equal to".
-
In the "Criterion Properties" window, next to the "Value:" text box, enter in the full SMBIOS GUID obtained from the PC. Make sure to enter all 32 characters and the 4 dashes that are part of the SMBIOS GUID.
-
In the "Criterion Properties" window, click on the "OK" button.
-
In the "Query Statement Properties" window, click on the "OK" button.
-
In the "Query Rule Properties" window, click on the "OK" button.
-
On the "Membership Rules" page of the "New Collection Wizard", click on the "Next >" button.
-
On the "Advertisements" page of the "New Collection Wizard", click on the "Next >" button.
-
On the "Security" page of the "New Collection Wizard", click on the "Next >" button.
-
When the "New Collection Wizard" completes, click on the "Close" button.
The newly created Collection should display all of the PCs affected by the duplicate SMBIOS GUID. Repeat the above steps if more than one set of duplicate SMBIOS GUIDs exist in the environment.
Resolution:
Please note that this problem is caused by an OEM vendor not adhering to industry standards. It is not an issue with ConfigMgr.
There are two possible solutions to the problem
-
Obtain a BIOS update or utility from the OEM hardware vendor that fixes the duplicate SMBIOS GUIDs and gives each PC a unique SMBIOS GUID.
-
To work around the problem, use the BannedGUIDsregistry entry of WDS as described in the following TechNet articles: Windows
Deployment Services Registry Entries Click here
How PXE Requests Work Click here
The BannedGUIDs registry entry "ignores" any SMBIOS GUIDs that have been entered under the key and instead uses the PC's MAC Address.
Please note that this solution does not actually fix the root cause of the problem and only works around it. When possible, it is recommended to use Solution #1. However in environments where there may be a large amount of duplicate SMBIOS GUIDs or where a BIOS fix or utility is not currently available from the OEM vendor, the BannedGUIDs registry can be used to work around the issue until the duplicate GUIDs issue can be permanently resolved.
For both solutions, use the methods described in the Cause section to discover what PCs are affected by duplicate SMBIOS GUIDs.
Issue:
FAILED TO RUN TASK SEQUENCE" ERROR MESSAGE (0X80070032)
Possible causes are:
Failed to prepare the system partition for staging.
Logfile:
SMSTS.log
In the smsts.log you will see the below errors.
The active system partition on a MBR system must be NTFS and
Failed to prepare the system partition for staging.
The request is not supported. (Error: 80070032; Source: Windows) and
Failed to stage WinPE. Code(0x80070032)
Resolution:
-
Start the machine with CD/DVD boot media.
-
Press F8, after boot media loaded.
-
Type "diskpart" on command prompt.
-
Type " list disk"
-
Type "select disk 0"
-
Type "clean"
-
Restart the machine and image the machine.
Issue:
0x80091007 (The hash value is not correct) error when trying to deploy Windows 7 with SCCM OSD
Possible causes are:
-
When checking the Advertisement Status of the task sequence you see the following error messages:
The task sequence execution engine failed executing the action (Apply Operating System) in the group (Build the Reference Machine) with the error code 2148077575
Action output: zSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031)
TS::Utility::ResolveSource( this->packageID, this->packagePath, TS::Utility::ResolveSourceFlags::PersistContents ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,160)
installer.install(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,632)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\WHATEVER
The user tries to release a source directory C:\_SMSTaskSequence\Packages\WHATEVER that is either already released or we have not connected to it
InstallScripted( g_InstallPackageID, g_ImageIndex, targetVolume, g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,397). The operating system reported error 2148077575: The hash value is not correct.
-
The task sequence execution engine failed execution of a task sequence. The operating system reported error 2148077575: The hash value is not correct.
-
The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned.
Furthermore, if you check C:\SMSTSLog\smsts.log on the deployed computer, you see the following errors:
-
Hash could not be matched for the downloaded content. Original ContentHash = WHATEVER, Downloaded ContentHash = WHATEVER2
-
The user tries to release a source directory C:\_SMSTaskSequence\Packages\WHATEVER that is either already released or we have not connected to it
-
Failed to run the action: Apply Operating System.
The hash value is not correct. (Error: 80091007; Source: Windows)
-
The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
-
Failed to run the last action: Apply Operating System. Execution of task sequence failed.
The hash value is not correct. (Error: 80091007; Source: Windows)
Log file:
SMSTS.log
Resolution:
-
Try to refresh the package's distribution point (refresh, not update):
-
If it doesn't work, try to remove the distribution completely and re-add it (you must WAIT for it to complete the removal before re-adding it, you can use the Package Status to make sure it was removed)
Many Problems, One Place solutions.
Thanks & Regards,
Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr
Twitter: https://twitter.com/hiraniconfigmgr
X
0 Comments
No Comments