Error 16389 Osd
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home a failure exit code of 16389 was returned. Browse forums users FAQ Search related threads Remove
Sccm Error 16389
From My Forums Asked by: Application fails during OSD Task sequence
Unmatched Exit Code (16389) Is Considered An Execution Failure
with exit code 16389 (RequestContent from CAS failed. Error = 0x87d01202) System Center 2012 Configuration Manager > Configuration Manager
.net Framework Exit Code 16389
2012 - Operating System Deployment Question 0 Sign in to vote We experience a strange behavior when using a task sequence to deploy an OS together with .Net framework (4.5) application. Once that the step kicks in to install sccm 2012 r2 exit code 16389 the application we get the following error: "The task sequence failed to install application Microsoft .NET Framework 4.5(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6) for action (Install Application .NET) in the group () with exit code 16389." Extract from CITaskMgr.log Initiating task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 (WKS_CORP_.NET Framework 4.5_EN_64) for target: , consumer: {B351446F-8FDF-4DD9-AE75-F9E818E79D25} CITaskMgr 1/29/2013 5:53:51 PM 1036 (0x040C) Initiating content download : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) RequestContent from CAS failed. Error = 0x87d01202 CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) Binary content download failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) State transition to (Failure), Error(0x87d01202) : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) State transition to (Failure), Param(-2016407038) : CTaskConsumer(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2.{4FFAD6D2-6F40-4870-96F5-B49B091CA9
Hi Guys , Just something I wanted to share with the operating system reported error 2147500037 you guys around failed application installs during OSD and .net install error 16389 High secure environments. At that specific customer all my apps failed one by one (not error: 0x4005(16389) windows 10 my packages) during OSD with error 16389. At first guess , you would say that your detection methods where not ok , but https://social.technet.microsoft.com/Forums/en-US/b5373b31-e594-4e1b-b6b9-ffecea05531e/application-fails-during-osd-task-sequence-with-exit-code-16389-requestcontent-from-cas-failed?forum=configmanagerosd it worked before when they where targeted in the full OS . So , why would they fail now ? The failure is very clearly visible in the status messages : The issue was also occurring on a specific HW model , a HP 8530P … Strange. Knowing http://scug.be/sccm/2013/02/13/configmgr-2012-rtmsp1-applications-failed-to-install-during-osd-with-error-code-16389-and-denied-logon-for-domain-users-policy/ this is a highly secured environment , my first guess would be policies. However I overruled this thinking strategy because normally during the OSD process , GPO’s aren't applied … However , guess again .. It was indeed a policy , but defined on another level . They deny by GPO that if a computer is not sitting in a specific AD security group , a “Domain user” is denied from logging on to any resource. On Error Resume Next strComputer = "." Set objGroup = GetObject("WinNT://" & strComputer & "/Gebruikers") For Each objUser In objGroup.Members If objUser.Name = "Everyone" or objUser.Name = "Domain Users" or objUser.Name = "Geverifieerde gebruikers" Or LCase (objUser.Name) = "interactief" Then objGroup.Remove(objUser.AdsPath) End was the issue, as it would take the full 120 minutes of time to run, then wouldn't install. I hit F8, ran CMTrace, then opened the AppEnforce.log file and noticed this error: Unmatched exit code http://mikesconfigmgrblog.blogspot.com/2014/07/microsoft-net-framework-45-not.html (16389) is considered an execution failure. It sure is! I had bundled this as an application, and the program was running"NDP451-KB2858728-x86-x64-AllOS-ENU.exe" /q /norestart. This should work. It did not. In fact, besides the error, it ran this https://msitpros.com/?p=1937 step pretty fast. The .NET 4.5 framework tends to take a long time to install, so this was definitely not right. Buried deep in this TechNet article is a response that suggested bundling .NET 4.5 as a exit code package instead. So I did, and created a program inside with the same command line (minus the quotes), and it installed properly! The application that required it also installed properly. Having trouble deploying an app? Try it as a software package instead and see what happens! Posted by Mike Murray at 11:56 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: .NET, Application Deployment, ConfigMgr 2012, OSD No comments: Post a Comment Newer exit code 16389 Post Home Subscribe to: Post Comments (Atom) About this blog... I started this blog for the sole purpose of sharing remedies to problems I've faced in ConfigMgr, and an occasional cool tip or trick. ConfigMgr is complex, and the solutions that worked for me may not work for you. So please don't comment, "didn't work for me". Google your issue, maybe you can find the solution elsewhere. About Mike... I am in no way a ConfigMgr expert. But I have been a ConfigMgr admin since 2006. What I don't know is much more than what I do know, but occasionally I, like the blind squirrel finding a nut now and then, manage to come up with a solution to a problem. Links ConfigMgr Log Reference ConfigMgr Survival Guide ConfigMgr Version Numbers Microsoft AV Exclusions List Microsoft Updates Requiring Multiple Restarts My IT Forum TechNet Script Center TechNet Virtual Labs Blog Archive ► 2016 (2) ► September (1) ► March (1) ► 2015 (5) ► July (1) ► April (1) ► March (1) ► February (1) ► January (1) ▼ 2014 (7) ► November (1) ► October (2) ► September (1) ▼ July (3) Changing the ConfigMgr 2012 size and location Task sequence fails with 0x80004005 - error while ... Microsoft .NET Framework 4.5 not installing during... Simple template. Powered by Blogger. PicturesVideos HomeSCCM 2012Failed to install Applications during Build and Capture Failed to install Applications during Build and Capture November 6, 2013 1 Comment Written by Sem Meijer Issue: You want to install Applications in your thick image, but they fail. Symptoms: During Build n Capture Applications fails to install (but packages installs without a problem) Status messages: The task sequence failed to install application (Install Application) in the group () with exit code 16389. AppEnforce.log is missing on the client Solutions: Check and verify Network Access Account Check you Boundaries they must be memeber of a Boundary Group Since you don't join the domain during build and capture AD Site Boundarys just are not anough. Use IP Address Ranges Best practice is to let them be discovered and let ConfigMgr create them. AD Site and IP Subnet bondaries are still evil in 2012. for more infocheck out Jasons lovely post http://blog.configmgrftw.com/?p=343 Client Installation property adding the SMSMP=myMP.mydomain.com PROPERTY to the client installation properties in the Setup Windows and ConfigMgr task in your TS. This must also be done because it can not get any info about the MP from AD because it doesn't joins the domain Check the applications Try to deploy it to a working workstation (not during OSD) Also Selected the option "Allow this application to be installed from the Install Application task sequence instead of deploying it manually" in the Application Properties. Allow anonymously connections And if it still does not work try enabling "Allow clients to connect anonymously" on the DP Hope that someone will find this little post helpful. Happy Deployment! SCCM 2012 16389, applications, Build and Capture, Configuration Manager User missing IM integration