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)
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:
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
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:
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 🙂