Installation issues for SCCM 2012 clients on Windows 10 preview

The recent test of win 10 in the process found that SCCM 2012 client is not able to install on win 10, the method used in the test is to use a separate installation package directly on the client installation, but wait for a long time after the client did not change, View Task Manager Discover CCMSetup The process is also run for a while and then automatically disappear, what is this?

Microsoft's own home SCCM incredibly can't be compatible with win 10? Well, given that now is only a beta version, this problem is also can be forgiven, after I found that this is not too much, too much is the SCEP actually hint is a threat of software, directly was ban dropped, this is the SCEP in Win Build 10130 error

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6F/4F/wKiom1WYfW2A-G1bAABrOKekr0Q100.jpg "title=" SCEP error . PNG "alt=" Wkiom1wyfw2a-g1baabrokekr0q100.jpg "/>

In the previous build in the SCEP error is not the case, but the hint is not compatible, and then let the contact vendors, seemingly can be solved by other means, but I did not delve into the problem of SCEP, after all, there are defender carrying it is not.

SCCM client can not be installed, then come to see what is the problem, fortunately, SCCM log is very rich, directly in the C:\WINDOWS\CCMSETUP folder to find the SCCM log, found there are a lot of files here, see the various needs of the components are actually ready to complete, It's just weird why it's not installed?

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6F/4D/wKioL1WYgDXSrdiFAAPSHCtrpBk225.jpg "title=" sccm2. PNG "alt=" Wkiol1wygdxsrdifaapshctrpbk225.jpg "/>

Look at the log know what is the problem, the log error section is as follows:

<! [Log[file ' C:\Windows\ccmsetup\WindowsUpdateAgent30-x86.exe ' returned failure exit code 775. Fail the installation.] Log]!><time= "10:01:02.103-480" date= "06-24-2015" component= "CCMSetup" context= "" type= "3" thread= "6812" file= " manifest.cpp:2239 ">

The original is one of the updateagent problems, resulting in the entire SCCM can not be installed, and then found a way to skip the installation of updateagent, the command is as follows:

Ccmsetup.exe/skipprereq:windowsupdateagent30-x86.exe

It is best to take the updateagent installation files, so that it is more insurance, try again, sure enough this time to install the normal, in the task Manager also saw the process

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6F/4F/wKiom1WYfz6jfcoWAAUqkkbhh9g468.jpg "title=" sccm3. PNG "alt=" Wkiom1wyfz6jfcowaauqkkbhh9g468.jpg "/>

SCCM Client Installation Complete

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/6F/4D/wKioL1WYgTqiNH_6AAFZTY5-Yos799.jpg "title=" SCCM5. PNG "alt=" Wkiol1wygtqinh_6aafzty5-yos799.jpg "/>

After testing the software distribution, asset collection is not a problem, but the patch update because there is no permission so no test, and now also has no win 10 patch, so this piece really is not good to say is not what the problem.

This article is from the "Just Make It Happen" blog, so be sure to keep this source http://mxyit.blog.51cto.com/4308871/1671011

SCCM 2012 Client Installation issues on Windows 10 preview