Skip to main content

SCCM Task Sequence Fails on SSD Drives Error Error: 87D00267


If you get the error code 87D00267 in a task sequence when deploying an Operating System it 
basically means the machine is unable to talk to the DHCP server. From a bit of investigation it 
seems that some machines with SSD's actually boot up into the task sequence quicker than it 
gets an IP Address! The get around this problem you need to put some pauses in the task 
sequence. The best way is to put the pause in the task sequence just before the point where it 
fails. There is some further reading into this issue below, the sites credited with links. 


Part 1
Source: http://ericsccm2012.blogspot.com.au/2013/04/applications-fail-to-install-on-ssd.html

We received several of the new Dell Latitude 6430U models with SSD drives.  Very nice laptops in a small case.  Easily found drivers for them and loaded into SCCM.  Started the task sequence on one and all looked like it went ok until we realized that none of the Application tasks in the Task Sequence worked.  They all had an error in the smsts.log of failed to download. ("Policy evaluation failed, hr=0x87d00267" followed by "Failed to run the action: Install App123.  Download Failed (Error: 87D00267; Source: CCM)")  Strange error since ever other model worked just fine with the same TS.  Reviewed the TS looking for anything that might act different based on model and found nothing other than drivers.

Started searching for that error code and immediately found this forum post (http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/221bcfe8-4c1e-4766-be5b-fbf54fe0e66c).

The last post in the thread referenced the scenario we were seeing and showed that the cause was related to the Samsung SSD drives that this model has.  Following the suggestion in that thread I placed the laptop on a 100MB line and it imaged just fine.  Then I added a 5 minute pause into the TS just prior to the Application installs.  Placed the laptop back on a GB line and it imaged just fine.

Seems to be yet another bug in SCCM 2012 SP1.

Part 2
Source:https://sccmfaq.wordpress.com/2013/11/21/sccm-2012-install-windows-7-on-ssd-fails-with-error-0x87d00267/

SCCM 2012 – Install Windows 7 on SSD fails with error 0x87d00267

Hi there, here’s Martin again, today I hopefully found the solution for the annoying Problem with devices that has a SSD for the System drive.
The Problem was, that the Task sequence stops at different Install Application steps. The smsts.log Shows the following Errors:
Policy Evaluation failed, hr=0x87d00267
Install application action failed: 'App-V Client 4.6 SP2 Only'. Error Code 0x87d00267
Install Static Applications failed, hr=0x87d00267
Failed to run the action: App-V 4.6 SP2 Only.
Download failed (Error: 87D00267; Source: CCM)
smsts.log error

This leads me to check the CAS.log for any Errors, and there were nothing Special to find. Thus I assumed that there has to be a Network issue. But why should only the devices with SSD have this Problem. I googled around a bit, and found suggestions to add a delay to the Task sequence, but this didn’t resolve the Problem.
See this TechNet Blog post for those suggestions:
http://social.technet.microsoft.com/Forums/en-US/221bcfe8-4c1e-4766-be5b-fbf54fe0e66c/specific-model-suddenly-fails-on-any-application-install-packages-work-fine?forum=configmanagerosd
I then checked the Event log for particular Messages, and found just at the time of the TS error a eventlog entry, that the System cannot find a Domain Controller:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: Date
Time: Time
User: N/A
Computer: Server
Description:
No Domain Controller is available for domain due to the following: There are currently no logon servers available to service the logon request. Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.
This was leading me to the following KB article:
http://support.microsoft.com/kb/938449/en-us
This first 3 Resolutions didn’t resolve the Problem, but the forth did. Adding the Hotfix KB2459530 (http://support.microsoft.com/?kbid=2459530) to the wim or inside the Task sequence, the Task sequence will now be processed even on SSDs.
This hotfix is also included in the “Enterprise hotfix rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1″ (http://support.microsoft.com/kb/2775511/en-us)
Hope this helps some other People :)


Comments

Post a Comment

Popular posts from this blog

SCCM - Required Application Not Installing to a collection based on an Active Directory Security Group I recently had an issue where I was trying to install Office 2013 as a required application to a collection based on an AD Security group. This would work fine if I was advertising the install as  'available', however when I set as 'required' it would not install and not even show up in Software Centre. After looking through the Monitoring section in SCCM and had a look at the deployment status I noticed it said success however the Message ID was 10040 and the description was "program will not rerun" I managed to fix this by going to the deployment settings for this collection and then going to scheduling and altering the "Rerun behaviour" to always rerun program.
Post a Comment
Read more

Office 2013 Silent Install

Office 2013 Silent Install Setup To setup a silent install of Office 2013 follow the below steps. If you have an ISO mount the file and then copy all the files out to a folder.  Run the command \\locationoffolder\setup.exe /admin. This will bring up the Office 2013 customisation tool.  You can apply which settings you require. The main ones you probably need to apply are  Licensing and user interface - choose here if you want to use a KMS key or a MAK key. In the options for the licencing agreements it is best to Tick "I accept the terms of the license agreement" Display level - none Suppress modal - ticked Set feature installation states. Tick the appropriate install options and features which you want. Configure shortcuts. I came across an issue in here which appears to be a known bug. If you try to create desktop shortcuts for any of the applications it would try to force you to enter something in the "start in" field saying this is required. ...
1 comment
Read more