apps not installing in UDI task sequence

[eddyballs]

Hi AnyWeb,

 

Just wanted to say real quick that I've lurked these forums for a couple of years now and have always appreciated your work.

 

But I finally do have one, hopefully simple, question I would like answered:

 

How does sideloading applications work with Windows 8/10? I have an MDT integrated task sequence for UDI deployments in my environment. I have applications installed at the end of the task sequence for Windows 7 and it doesn't work with Windows 8 or Windows 10.

 

Is this happening because I need to update my MDTToolkit to update 1? I've already upgraded my MDT server to the latest build (8298), but haven't updated the MDTToolkit package in SCCM.

 

Thoughts?

 

Thanks in advance!

[anyweb]

hi Eddy,

what are these applications exactly ? are they actual store apps that your company has created or apps available in the Windows store ?

[eddyballs]

Hi! Thanks for the reply.

 

I sideload applications like Firefox, Adobe Acrobat Pro, Java, and Flash Player to name a few.

[anyweb]

when you say 'sideload' are you referring to Windows Store apps, or are you just calling it 'sideloading' and they are normal apps/packages ?

 

sideloading is normally the term provided for installing Windows store apps.

[eddyballs]

Oh sorry! I didn't know that 'sideloading' was specific just for Window Store apps. I'm talking about normal apps/packages in SCCM that are selected in the MDT UDI process.

 

In our UDI wizard, I have added these applications that get installed automatically during the imaging process. These applications get installed fine in Windows 7, but with Windows 8 and Windows 10 it doesn't work. They're all applications (some msi and some exe) in SCCM.

 

So my questions is if this is possible? Or is it just .appx packages that are able to be installed during the UDI imaging process?

[anyweb]

they should work, ,can you attach your smsts.log so we can see what's failing and why

[eddyballs]

Here's the log. Oddly enough, it was hard to find the log file. Because the task sequence just stops after it installs Windows 10, there was no CCM directory anywhere.

 

Luckily I found it in C:\users\ADMINI~1\appdata\local\temp

 

There's a couple of errors that stand out, but I've never seen this one before:

 

Non fatal error 0x80070057 in sending task sequence execution status message to MP

 

smsts.log

[anyweb]

no apps are installing because the ConfigMgr client is failing to install

<![LOG[Failed to install SMS Client (0x80004005)]LOG]!><time="12:21:10.160+420" date="10-02-2015" component="OSDSetupHook" context="" type="3" thread="2368" file="basesetuphook.cpp:1517">

so.. what does the ccmsetup.log file tell you ?

 

and as your post is really not inline with this overall topic i'm going to create a new thread (this one.)

[eddyballs]

I have attached the ccmsetup.log which does highlight a couple of errors I've never seen before.

 

It's also failing during that step, so I'm going to assume that it's the issue?

 

File 'C:\WINDOWS\ccmsetup\WindowsUpdateAgent30-x64.exe' returned failure exit code 775. Fail the installation. ccmsetup 10/2/2015 12:21:09 PM 2496 (0x09C0)

ccmsetup.log

[anyweb]

this tells me you are using the old version of the ccm client, which doesn't work properly with SCCM 2012 R2 SP1 (cu1),

so have you updated your infrastructure yet ?