Ok, I figured this out; the application that I was deploying in the task sequence had two deployment types, one for 32bit and one for 64. After removing the 64bit deployment type the task sequence now installs the application. So with that being said, does anyone know how the task sequence evaluates the deployment types?
Thanks
Hello,
In my task sequence, any application that i add fails to install with Error Code 0x87d00215. Outside of the task sequence the applications install with no problems.
A couple things that i have verified already
DP is set to allow clients to connect anonymously
Network Access Account is set and verified
Setting on the application for Allow this application to be installed from the Install Application task sequence action instead of deploying it manually is set
Boundaries are set correctly as software installs correctly outside of the TS
Logs that do not show errors
IIS logs - Check out just fine
Location Services - Does not show any errors and finds the AD Forest/Site and MP successfully
CAS Log - Does not show any errors with the correct date
Data Transfer Log - Does not show any error with the correct date
Any ideas would be greatly appreciated.
Thanks
I´m running ConfMgr 2012 SP1 on customer site, and I have 5-10% failures of apps during XP->Win7 refresh scenario. Error code is always 0x87d00215. This happends usually at the end of TS, last apps are failuring randomly in 5-10% of entire OSD installation ammount. Same computer models, same subnets. Previously I´ve tested this TS like few hundred times and error procentage was 0%. But during rollout, when the install amount of machines grew, this suprised me from behind.
I already came up with temporary solution, I have a collection with a query (app X not installed), which adds missing machines to a collection and distributes whatever app is missing.
Here's two possible solutions I may try.. may work for you
http://www.bpmi.nl/blog/?p=1637
From the link above, the second option given:
"Provide the Site code and Management point during client installation (/MP:<fqdn hostname> SMSSITECODE=xxx)"
A follow up for anyone still trying to work this out...The option given quoted above isNOT VALID. The interface of editing the Task Sequence on step "Setup Windows and Configuration Manager" when you enterSMSSITECODE pops a red exclamation point that when you mouse over it explicitly says, "Installation properties cannot include SMSSITECODE and SMSPROVISIONINGIMAGEMODE."
That suggestion should be disregarded and updated.
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
I had exactly the same problem, with sccm 2012 SP1 on a server 2012R2
I simply enabled anonymous:
Administration -> Site Configuration ->
Select Servers and site system roles
Double-click on the Distribution point
General tab: check the "allow clients to connect anonymously" box then click on OK
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Wanted to circle back on this as it is seems we have resolved our issue.
None of the application level changes related to content downloading on slow or unreliable connections worked.
We had some boundaries that were present but unassigned to a boundary group. Due to the nature of the error we previously had, we deleted all of the unassigned boundaries and haven't seen the issue since and have had 100% success on our OSD builds since cleaning them up.
We had done this type of cleanup in the past, but these were left for some unknown reason.
We don't fully understand why the errors trended up so quickly as the unassigned boundaries were there for quite sometime without any ill effects.
Thinking it was a random issue related to the MP_Location mechanism.
We have battled the "Application Download failed" errors off and on and for a while it was off and now back on.
On our initial t/s efforts and subsequent, albeit, temporary solution, we determined that we had too many boundaries configured ... > 5K, many of them being IP Range boundaries, which is known to be frowned upon. This was due to the Forest Discovery being configured to auto-generate boundaries and even though we didn't have 90% of them assigned to Boundary Groups, this affected the way some stored procs calculated the boundary and content location mechanisms.
Our remediation plan consisted of disabling the auto-boundary creation and doing some cleanup of our boundaries - we got that count down to around 600. In addition to that, we installed SP1/ CU2 (which was the latest available CU at the time) and that included updates to the stored procs to improve the performance and calculations...
the specific stored proc updates that we focused on were:
MP_GetAssignedSite
MP_GetContentDPInfoProtected
MP_GetContentDPInfoUnprotected
MP_GetLocalMPListForSite
MP_GetProxyMPListForSite
MP_GetSiteInfoUnified
After performing the boundary work and applying CU2, we eliminated any Application Download Failed errors.
As far as I know these improvements are also in R2 ( we are on SP1/CU2 still and SP1 alone doesn't have these improvements ).
Fast fwd to now, we are seeing them again and with multiple applications in our task sequence and not consistent at all.
Based on this, we are going to try the suggestion of setting the Download setting for some of the offending apps - even though our boundary group connections are all configured as "Fast", wondering if there is some shenanigans going on from the client/MP side.
Hope some of this helps someone out there.
Because when the task sequence engine was designed and coded there was an inherent latency in all operations that is vastly reduced with SSDs in the process causing the system to reboot and process faster than the TS engine can keep up. Thus, it's a design flaw based on an implication of responsiveness that is not true anymore with SSDs in the mix.
Jason | http://blog.configmgrftw.com | @jasonsandys
Had the exact same problem, then I found this post that provides a root cause and workaround:
Basically, it was the task sequence attempting to execute the wrong application revision. So, every time you update an application that is in a task sequence apply the workaround. The workaround involves editing the task sequence, delete the Install Application step, save the task sequence, recreate the Install Application step. Did it work? Like a boss.
Wanted to circle back on this as it is seems we have resolved our issue.
None of the application level changes related to content downloading on slow or unreliable connections worked.
We had some boundaries that were present but unassigned to a boundary group. Due to the nature of the error we previously had, we deleted all of the unassigned boundaries and haven't seen the issue since and have had 100% success on our OSD builds since cleaning them up.
We had done this type of cleanup in the past, but these were left for some unknown reason.
We don't fully understand why the errors trended up so quickly as the unassigned boundaries were there for quite sometime without any ill effects.
Thinking it was a random issue related to the MP_Location mechanism.
We have battled the "Application Download failed" errors off and on and for a while it was off and now back on.
On our initial t/s efforts and subsequent, albeit, temporary solution, we determined that we had too many boundaries configured ... > 5K, many of them being IP Range boundaries, which is known to be frowned upon. This was due to the Forest Discovery being configured to auto-generate boundaries and even though we didn't have 90% of them assigned to Boundary Groups, this affected the way some stored procs calculated the boundary and content location mechanisms.
Our remediation plan consisted of disabling the auto-boundary creation and doing some cleanup of our boundaries - we got that count down to around 600. In addition to that, we installed SP1/ CU2 (which was the latest available CU at the time) and that included updates to the stored procs to improve the performance and calculations...
the specific stored proc updates that we focused on were:
MP_GetAssignedSite
MP_GetContentDPInfoProtected
MP_GetContentDPInfoUnprotected
MP_GetLocalMPListForSite
MP_GetProxyMPListForSite
MP_GetSiteInfoUnified
After performing the boundary work and applying CU2, we eliminated any Application Download Failed errors.
As far as I know these improvements are also in R2 ( we are on SP1/CU2 still and SP1 alone doesn't have these improvements ).
Fast fwd to now, we are seeing them again and with multiple applications in our task sequence and not consistent at all.
Based on this, we are going to try the suggestion of setting the Download setting for some of the offending apps - even though our boundary group connections are all configured as "Fast", wondering if there is some shenanigans going on from the client/MP side.
Hope some of this helps someone out there.
Here's two possible solutions I may try.. may work for you
http://www.bpmi.nl/blog/?p=1637
From the link above, the second option given:
"Provide the Site code and Management point during client installation (/MP:<fqdn hostname> SMSSITECODE=xxx)"
A follow up for anyone still trying to work this out...The option given quoted above isNOT VALID. The interface of editing the Task Sequence on step "Setup Windows and Configuration Manager" when you enterSMSSITECODE pops a red exclamation point that when you mouse over it explicitly says, "Installation properties cannot include SMSSITECODE and SMSPROVISIONINGIMAGEMODE."
That suggestion should be disregarded and updated.
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
I had exactly the same problem, with sccm 2012 SP1 on a server 2012R2
I simply enabled anonymous:
Administration -> Site Configuration ->
Select Servers and site system roles
Double-click on the Distribution point
General tab: check the "allow clients to connect anonymously" box then click on OK
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
I´m running ConfMgr 2012 SP1 on customer site, and I have 5-10% failures of apps during XP->Win7 refresh scenario. Error code is always 0x87d00215. This happends usually at the end of TS, last apps are failuring randomly in 5-10% of entire OSD installation ammount. Same computer models, same subnets. Previously I´ve tested this TS like few hundred times and error procentage was 0%. But during rollout, when the install amount of machines grew, this suprised me from behind.
I already came up with temporary solution, I have a collection with a query (app X not installed), which adds missing machines to a collection and distributes whatever app is missing.
I had exactly the same problem, with sccm 2012 SP1 on a server 2012R2
I simply enabled anonymous:
Administration -> Site Configuration ->
Select Servers and site system roles
Double-click on the Distribution point
General tab: check the "allow clients to connect anonymously" box then click on OK
I agree partially with what you are saying.
I agree that the domain join could be causing the issue.
But you should be able to join a computer to the domain even if an object with the same name already exists.
So the issue is rather the account that's being used to join the computer to the domain than the existence of the object with the same name.