Hi,

I am trying to install SCCM client version 5.00.7845.1000 on a Windows 10 (build 10061) and get these errors.

-- File 'C:\WINDOWS\ccmsetup\WindowsUpdateAgent30-x64.exe' returned failure exit code 775. Fail the installation.
-- InstallFromManifest failed 0x80070307
-- CcmSetup failed with error code 0x80070307

Both 0x80070307 and error 775 translate to :

The implementation is not capable of performing the request.

I am wondering if it's even possible to install the client on this build?

Thanks

Chanderjeet

It's not officially supported, yet, but this should get you started: http://ccmexec.com/2015/04/sccm-2012-client-fails-to-install-windows-10-build-10049/

Unfortunately OP's issue completely breaks OSD integration as well. That was at least working good enough before to deploy the OS with some creative workarounds for the max runtime issue being interpreted as 0 and all that.

Unfortunately you can't specify /skipprereq in the "Setup Windows and Configuratoin Manager" item - it only accepts MSI properties. So the above article doesn't help OSD at all.

• Edited by jdarg 12 hours 20 minutes ago

I figured out a workaround for OSD. Essentially I create a fake ccmsetup.exe which then executes the normal ccmsetup command line OSD needs but with the /skipprereq:WindowsUpdateAgent30-x64.exe parameter included.

1. Create a copy of your client install package. Move all the install files/folders into a new subfolder named client.

2. Add the new client package and make note of the package ID assigned.

3. Using VS Express 2013, create a new c# console project and name it ccmexec. Paste this code in, replace 10000A53 with the package ID of your new client package, and compile.

using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.Linq;
using System.Text;
using System.Threading;
using System.Threading.Tasks;

namespace ccmsetup
{
    class Program
    {
        static void Main(string[] args)
        {
            var process = Process.Start("c:\\_SMSTaskSequence\\OSD\\10000A53\\client\\ccmsetup.exe", "/skipprereq:WindowsUpdateAgent30-x64.exe /useronly /source:C:\\_SMSTaskSequence\\OSD\\10000A53\\client /config:C:\\_SMSTaskSequence\\OSD\\10000A53\\MobileClient.TCF");
            while (!process.HasExited)
            {
                Thread.Sleep(1000);
            }
        }
    }
}

4. Take the fake ccmexec.exe and add it to the root (the root only - don't overwrite the normal ccmsetup.exe located in the client folder) of your new client source folder and update your new client package.

5. Modify your Windows 10 task sequence(s) and switch the SCCM client package to your new one.

This works for me under SCCM 2012 R2 CU1 w/ WIndows 10 x64 build 10041. This should work for the 10061 build as well. Yeah I know I this could be better (extract package ID from command line, etc.) but I was in a hurry just to make sure this workaround fundamentally works.

• Edited by jdarg 12 hours 13 minutes ago
• Proposed as answer by jdarg 12 hours 12 minutes ago

Unfortunately OP's issue completely breaks OSD integration as well. That was at least working good enough before to deploy the OS with some creative workarounds for the max runtime issue being interpreted as 0 and all that.

Unfortunately you can't specify /skipprereq in the "Setup Windows and Configuratoin Manager" item - it only accepts MSI properties. So the above article doesn't help OSD at all.

• Edited by jdarg Friday, May 01, 2015 7:23 PM

I figured out a workaround for OSD. Essentially I create a fake ccmsetup.exe which then executes the normal ccmsetup command line OSD needs but with the /skipprereq:WindowsUpdateAgent30-x64.exe parameter included.

1. Create a copy of your client install package. Move all the install files/folders into a new subfolder named client.

2. Add the new client package and make note of the package ID assigned.

3. Using VS Express 2013, create a new c# console project and name it ccmexec. Paste this code in, replace 10000A53 with the package ID of your new client package, and compile.

using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.Linq;
using System.Text;
using System.Threading;
using System.Threading.Tasks;

namespace ccmsetup
{
    class Program
    {
        static void Main(string[] args)
        {
            var process = Process.Start("c:\\_SMSTaskSequence\\OSD\\10000A53\\client\\ccmsetup.exe", "/skipprereq:WindowsUpdateAgent30-x64.exe /useronly /source:C:\\_SMSTaskSequence\\OSD\\10000A53\\client /config:C:\\_SMSTaskSequence\\OSD\\10000A53\\MobileClient.TCF");
            while (!process.HasExited)
            {
                Thread.Sleep(1000);
            }
        }
    }
}

4. Take the fake ccmexec.exe and add it to the root (the root only - don't overwrite the normal ccmsetup.exe located in the client folder) of your new client source folder and update your new client package.

5. Modify your Windows 10 task sequence(s) and switch the SCCM client package to your new one.

This works for me under SCCM 2012 R2 CU1 w/ WIndows 10 x64 build 10041. This should work for the 10061 build as well. Yeah I know I this could be better (extract package ID from command line, etc.) but I was in a hurry just to make sure this workaround fundamentally works.

• Edited by jdarg Friday, May 01, 2015 7:30 PM
• Proposed as answer by jdarg Friday, May 01, 2015 7:30 PM

Unfortunately you can't specify /skipprereq in the "Setup Windows and Configuratoin Manager" item - it only accepts MSI properties. So the above article doesn't help OSD at all.

Actually, that is not quite true.

Look at the bottom paragraph of the Details section here: https://technet.microsoft.com/en-us/library/hh846237.aspx#BKMK_SetupWindowsandConfigMgr

Quote (my highlighting):

Installation Properties

Site assignment and the default configuration are automatically specified by the task sequence action. You can use this field to specify any additional installation properties to use when you install the client. To enter multiple installation properties, separate them with a space.

For System Center 2012 Configuration Manager SP1 and later:

You can specify command-line options to use during client installation. For example, you can enter /skipprereq: silverlight.exe to inform CCMSetup.exe not to install the Microsoft Silverlight prerequisite. For more information about available command-line options for CCMSetup.exe, see the CCMSetup.exe Command-Line Properties section in the About Client Installation Properties in Configuration Manager topic.

Note that you have to have SCCM 2012 SP1 or later, but from the version number of the OP's client, he should have that.

I have tested by adding /skipprereq:windowsupdateagent30-x64.exe first in the Installation properties field of the Setup Windows and ConfigMgr TS step (before the MSI properties, not tested adding it after them), and it is working with build 10074 (client version 5.00.7958.1000).

Now I just need to figure out why Software Center crashes when I try opening it...

To avoid this error we have to use this command for skip the installation of
"  WindowUpdateAgent30-x86.exe".

by writing this command:

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x86.exe

or

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x64.exe

Note : this error specific to window 10.

• Proposed as answer by RJ09 Tuesday, September 01, 2015 6:06 PM

To avoid this error we have to use this command for skip the installation of
"  WindowUpdateAgent30-x86.exe".

by writing this command:

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x86.exe

or

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x64.exe

Note : this error specific to window 10.

To avoid this error we have to use this command for skip the installation of
"  WindowUpdateAgent30-x86.exe".

by writing this command:

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x86.exe

or

-- ccmsetup.exe  /skipprereq:WindowsUpdateAgent30-x64.exe

Note : this error specific to window 10.

The above command line, ccmsetup.exe /skipprereq:WindowsUpdateAgent30-x86.exe resolves my issue installing SCCM client on Windows 10 during task sequence in MDT 2013 Update 1. Thank you.