Schikitar

It's because the Store apps have updated and this breaks Sysprep. I was speaking with a MS rep at a conference yesterday and they said you've got a few options; 1. Install W10 without a network connection and build the image in this state until the capture 2. Install W10 and set local policy (or registry) to disable the Windows Store (so it doesn't update itself and the built-in apps), then connect it to the network, build the image and remove the GPO/regedit just before capture 3. Nuke the Store and apps by running the steps shown here - https://www.windows-noob.com/forums/topic/5070-how-can-i-capture-an-image-using-capture-media-in-configmgr-2012/?p=38663 Once you capture and then deploy the Store and its apps will automagically reappear in the deployment. I tested this and replicated the results, it's really annoying and I hope MS fix it, legacy meets modern in craptacular fashion once again! Would love to see anyweb replicate the issue and post a more thorough writeup on the problem! ;D

How do you do this in Windows 10 because it simply doesn't work and errors out with 0x0004005 at the sysprep stage. Seems you have to remove all MS apps - but what if you don't want to remove all or any of those apps?!!

Okay, here is the ccmsetup.log from a failed images machine. When I was imaging it I took note that the ccmclient started it's install at around 12.57pm, then at 1.01pm it finished and about 15 seconds later it began the Office install (which then fell over as expected. Looking at this log it seems like the client is installing, then reports "An MP does not exist on this machine" followed by "No client is currently installed" and then it begins the installation again. Then right at the end it states "A Fallback Status Point has not been specified" and then it starts deleting all the ccmsetup files (which, oddly, are there and the client is installed). Does this sound right/normal?? I think I need some help with rebuilding the client source files and configuring the install... I have also attached the smsts-20140826-191650.log file which shows the 6 hour failover time between approximately 1pm and 7pm. I hope someone can assist! ccmsetup.log smsts-20140826-191650.log

Hi rddvls1999, Well it's been a few days but I have had a breakthrough, of sorts. Infact, the breakthrough may have me on the path of resolving three major issues which has plagued me for MONTHS! I don't quite know what I've done (scary, I know) but here's the basic breakdown; It occurred to me that I had been too obsessed with capturing log files whilst the 'hang' was happening. I let a machine image overnight because we had noticed that occasionally the install would timeout and then the machine would complete the TS (sans applications). I grabbed the log files from there and inside the smsts-XXXXXXXX-XXXXXX.log file was a sudden jump from the previous entry at 2.18pm (around the time it was imaging) to about 6 hours later at 8.18pm Waiting for job status notification... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) AppMgmtSDK handler is invalid. Trying to reconnect... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) GetAppMgmtSDKInterface successful InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Reconnecting to existing jobID '{682B9098-4ED7-4F9E-BBFE-61E30918C2F1}'.. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) spAgent->GetJob(jobId, &spAgentJob), HRESULT=87d00215 (e:\qfe\nts\sms\dcm\sdk\cisdkclass.cpp,1756) DCMAgent 25/08/2014 8:18:15 PM 2724 (0x0AA4) spAppMgmtSDK->SetEvaluationCallback( guidJobID, spNotifyCompPtr ), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,456) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Failed to Reconnect to existing job, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Reconnect Job request failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) ReconnectJob(spAppMgmtSDK, spCallback, guidJobID), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1233) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) WaitforJobCompletion(spAppMgmtSDK, m_guidAppInstallJobID, ulAppInstallTimeout, nAppInstallRetryAttempts), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1122) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Step 2 out of 2 complete InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Install application action failed: 'Microsoft Office Professional Plus 2013 with SP1'. Error Code 0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Sending error status message InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting URL = http://SCCM-SVR.lcgs.local, Ports = 80,443, CRL = false InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting Server Certificates. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting Authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Set authenticator in transport InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting Media Certificate. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Sending StatusMessage InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting message signatures. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Setting the authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80 CCM_POST /ccm_system/request InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Request was successful. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Install application action cannot continue. ContinueOnErrorFlag is set to false. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) hrInstallation, HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,914) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\main.cpp,277) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Install Static Applications failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4) Process completed with exit code 2278556181 TSManager 25/08/2014 8:18:15 PM 2312 (0x0908) !--------------------------------------------------------------------------------------------! TSManager 25/08/2014 8:18:15 PM 2312 (0x0908) Failed to run the action: Install Office. Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:15 PM 2312 (0x0908) MP server http://SCCM-SVR.lcgs.local. Ports 80,443. CRL=false. TSManager 25/08/2014 8:18:15 PM 2312 (0x0908) Setting authenticator TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Set authenticator in transport TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Sending StatusMessage TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Setting message signatures. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Setting the authenticator. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80 CCM_POST /ccm_system/request TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Request was successful. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Set a global environment variable _SMSTSLastActionRetCode=-2016411115 TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Clear local default environment TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Let the parent group (Setup Operating System) decides whether to continue execution TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Failed to run the last action: Install Office. Execution of task sequence failed. Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908) Looking at the error codes I did a search on 0x87d00215 which turned up a few bits and pieces, but eventually a post, within a post within a post (Inception!) lead me to this article which I had to use Bing Translator to read - http://adminsccm.blogspot.com.br/2013/06/failed-to-get-dp-locations-as-expected.html This article goes on to describe a problem with the original CM Client installation, which is something I have had problems with for a long time. Using the steps in the article I manually created a new client package as outlined, then I ran some SQL queries to clean things up... select * from ClientDeploymentSettings - to return the reference to the ccm client install and upgrade packages update ClientDeploymentSettings set UpgradePackageID = '' where UpgradePackageID = 'LCG00003' - LCG00003 was an update package that was constantly showing up in distmgr.log with problems, I used this to remove it from the current client package 'LCG00002' (which also had problems) update ClientDeploymentSettings set FullPackageID = 'LCG0011E' where FullPackageID = 'LCG00002' - to associate my new manually created package (LCG0011E) in place of the originally automatically generated package (LCG00002) At this point I edited the TS, added my new package to the "Setup Windows and Configuration Manager" step and set off imaging the same machine I've been using so far, then I went to lunch Upon returning from lunch (about 30mins) the OSD was nearly finished and shortly completed thereafter without incident. I logged in and Office was installed as was the most current version of the ccm client (5.00.7958.1303) I did a little dance Next I thought I would add all the other application installs back into the OSD TS (about 8 in total), so I went back and edited it This time I got an error complaining that the previous Config Manager setup package was no longer available - what the flip? I browse to the root of the Packages folder in the console and my manually created package has mysteriously disappeared In its place was a new automatically generated package (it had a new package ID as well) I decide to rerun the SQL query select * from ClientDeploymentSettings which returned the following; FullPackageID UpgradePackageID UpgradeProgramName UpgradeAdvertisementID UpgradeVersion EnablePeerCache LCG0011F LCG00120 Configuration Manager Client Upgrade Program LCG20058 5.00.7958.1000 1 This is not what I had changed it to before lunch so ConfigManager has done it's own bit of magic here (obviously not happy with my manual package and tinkering) Okay, well I decided to then associate this newly automagically created package to the TS and set off another re-image of a machine Sadly, this has now resulted in the 'hang' happening in exactly the same spot as before Whilst I'm no further ahead in terms of imaging machines I feel there is some insight to be gained here. I hope someone reading this might have a light-bulb moment, I'm not entirely sure what to do next...

I've had this problem before, had to run this command on the server where you are attempting to do the servicing: dism /cleanup-wim

Texasit, I think I am having a similar issue, how exactly did you correct this? I can't see how to tell my TS to use 'the latest' client version...

Hi guys, Had a machine do this today that we were imaging using PXE (also have another machine that is skipping some app installs, that's using TS media). First time through it imaged but just seemed to skip a bunch of applications (Office and a few others), so we kicked it off again and second time round it hung sometime after it started installing the second application in the list (see attached image of the TS). I did find the smsts.log file this time, it was as suggested in C:\_SMSTaskSequence\Logs - I have attached all the log files I could find. Appreciate your assistance, I've got other problems with my SCCM install as well, I figure I should mention it, but I have packages stuck in my distmgr queue which is also driving me crazy (have separately attached that, ignore if not relevant). About to give up on SCCM, it's a full time job for me at the moment and I can't afford the amount of time it sucks out of me, I have too many other things to deal with and my boss is getting quite shirty! Cheers! logs.zip distmgr.log

Hi Guys, apologies for the late reply, I had kinda given up hope that no one would respond due to this being a bit of an odd issue! rddvls1999, normally I would agree, however, I have tried changing the order of the application installs and it seems to be a problem that trikes after a certain amount of time has passed since the last reboot (after the ccm client install), it's not stuck on a particular application. Also, as I mentioned, it might hang on the 1st, 2nd, 3rd attempts (or more) but then on the next attempt goes through without issue with all applications installed. When it happens it definitely seems to be 'waiting' for something, or after that fixed time another process is, or isn't, happening in the background interrupting the whole OSD process (ccm client policy processing maybe??). I will try and capture the smsts.log, didn't think to view it in realtime, will also try that... giftedwon, no, not across a WAN, clients are connected via 1gb Ethernet. This is still an ongoing and intermittent issue, usually happening at the most inconvenient times (like when reimaging a senior staff members machine, gah)!

Attached are all the log files from the client... _LOGS.zip

Hi all, I have an error that has plagued me since, I think, upgrading to SCCM 2012 R2. I have a handful of OSD's which I have setup and generally, they all exhibit the same issue at seemingly random times. I could have multiple machines on my bench all using the same OSD and a couple of them will hang during the installation of applications. So, it installs the Windows image, sets up the CCM client, reboots and finishes the client install and then starts installing applications. When it hits about the third or fourth application it just sits there and does nothing for as long as the machine stays on (no error). It seems to be something that happens after a fixed amount of time (not sure how long), probably ~10 minutes after the last reboot. It makes no difference how I order the apps to install. I've sorted the log list by date and time to try and find an error somewhere but I can't see anything. The really frustrating thing is, if I have a machine that is failing it will usually keep failing repetitively but then suddenly it might start working and completed the TS all the way through. Can anyone give me any advice as to what logs I should keep a closer eye on (client/server) or if anyone has heard of anything similar. It's really frustrating when you have hundreds of machines to do! Sorry if I'm a bit light on info, I'm not sure what to provide as I'm still learning! Cheers!

Hi Niall, Apologies for the tardy reply, have had a hell of a week with our new internet filtering server and so many other things going on (that's the problem with effectively running an IT dept in a school on your own)! Anyway, I did manage to squeeze in a few more tests etc., Before I start on that I'll just cover off on your points/questions; ccmcean is not supported, use ccmsetup.exe /uninstall if you want to uninstall the ccm client for whatever reason ccmsetup.exe /uninstall in my testing didn't seem as thorough as ccmclean - however, more on this in a moment wmi getting corrupted on a windows 8.1 device sounds unlikely unless you are somehow pushing some odd settings to the computer via gpo/gpp/script I agree about WMI, although we do push a quite a few GPO's out for basic config stuff in a school environment so starting from the beginning how are these systems imaged The systems are imaged using a fairly basic task sequence that installs an unmodified (except for offline servicing) Windows 8.1 x64 image (taking the image.wim directly from our VL ISO). Through the task sequence I then layer in the drivers and applications, I've uploaded a screenshot of how the TS is structured - http://1drv.ms/1nfIlhY what client version do they have installed initially ? When I first log into a freshly imaged machine they are sitting at version 5.00.7958.1203. Without any intervention they start getting policy and software starts appearing in the Software Centre, everything looks fine. I'm assuming it's deploying from SMS_XXX, here in the "Client" folder I have a "ClientPatch" folder (for each architecture) with only the latest hotfix contained within it (kb2938441) - I'm led to believe this will then deploy the standard client (.1000) and then roll it up to .1203 how long before they start to repair the client ? I haven't caught it in the act but seemingly by the next day they begin and then it's pretty regular (like every 15-30 minutes) after each repair, continually draining resources and frustrating the heck out of end users (and me!) In the interim I have turned off Client Push Installation and Software Update-Based Client Installation, I have also disabled Automatic Client Upgrade. Even when I first posted I thought I had a manual fix, I would run ccmclean.exe (yes, I know), clear out the ccm and ccmsetup folders from c:\windows, reboot, reinstall the client from the SC console and then everything would tick along nicely for the day without further issue. However, sometime after that work day the clients started auto repairing again, my own machine just today as well as a few others. I had to image a couple machines today and a separate issue with a failed Office 2013 install (that's another problem I have) from my TS led me to a search result which suddenly sounded very familiar - - it's an older artcile and I haven't dug deep enough into logs just yet but it sounds a lot like what I'm experiencing. So that's where I'm at, I will update if I find anything else!

Hi, they are all running WIndows 8.11 x64. Your search turned up the same one I've been spending a bit of time on. The only thing I haven't been able to establish is whether or not CCMCLEAN.exe from the SMS Toolkit 2003 is still a valid option for 2012 R2 clients!? I have also just started testing repairing/rebuilding the WMI repository on some machines with mixed results. As the clients are constantly looping I'm finding it difficult to identify where in that process I can execute commands etc., Very frustrating, would love to wipe the slate clean and start again but I can't, have to try and undo the damage somehow! Thanks for your time, appreciate it.

Cool, thanks for the help. So, I have a machine here, it is constantly looping between installed and repairing. Currnetly it is installed and it is running 5.00.7958.1203. I've uploaded some log files from this client here - http://1drv.ms/1nfIlhY I've noticed the ccmsetup.log file resets at some point, hopefully I've caught it with enough info in it. I've begun looking at things such as resetting the WMI repository etc., on a couple test machines but I don't know enough about what's going on to really hone in on the issue(s). Very frustrating as it was working nicely, now I get students coming up constantly saying that they can't get to the Software Centre. I'm depserately trying to get apps and updates deployed but there is little point if the clients aren't working properly. Please let me know if there is anything else you can think of! Cheers!

Hi all, Bit of a SSCM noob here, I'm an IT Manager (or IT GP) at a school with a deploymnent of about 800 clients. Since, I believe, I updated our site to CU1 (for SCCM 2012 R2) most of my clients have been stuck in some sort of install/repair loop. I have machines sitting in front of me, checking Task Manager I can see "CCM Insttallation Repair" and "ccmsetup.exe" both running for sometime, then once these clients are done and start getting policy I start seeing some notifications from the Software Centre for various programs etc before it all dissappears and starts the repair process again. I can't find anything useful in the logs (not 100% which logs to check in this instance but have been inspecting the ones most recently modified). Has anyone seen behaviour like this, how can I stop it without pulling every client in and manually uninstalling!? I have disabled Client-Push Installations (clientsd are usually installed as part of Task Sequence when we image machines) and any client upgrade deployments, not sure what to try next. Cheers

Hi guys, I'm having some real problems with this. I'm currently using Config Manager 2012 R2, fully patched. I have a TS setup which deploys to pre-existing clients no problems (it uses their existing computer names), however, unknown computers keep failing. What I've noticed on a new machine when deploying Winodws 8.1 is the following; PXE Boot Select TS Get prompt for OSDComputerName (as previously setup and working in 2012 SP1) Manually specify the machine name TS begins (partitions, applies the image) An 'unknown' device then appears in the All Systems collection After driver packagesare installed I see a screen displaying the Win8 logo and a message saying "Getting Ready" This screens sits there for a long time (on a known machine it goes through very quickly) At some point the machine reboots and displays the "Get Online" screen (as normally shown in OOBE), not a part of the usual TS I click through that and the TS resumes and seemingly completes, however, the machine is not joined to the domain (and I cannot log into it) On a known machine, using the same TS, it all goes through without issue. I have tried the method used in this article, as well as the vbs script mentioned by Rocket Man as well as the TS variable method mentioned by djkarl - all result in the same failure. I have experienced this on a number of different new machines (we are a school and had a few new models come in this year). Any tips or suggestions would be greatly appreciated!

Hi all, Just wondering if anyone else has experienced memory leaks in Windows Server 2012 with related products SCCM 2012 or SQL 2012 installed? We have two Windows Server 2012 installs, one is our PDC which chugs along fine, the other is my SCCM server. This server constantly locks up every few days, but now it peaking (read: leaking) more frequently which is making it painful to use! I've attached a screenshot of Task Manager just after doing a reboot. It just doesn't add up (literally). I have done the following; WS is running the latest updates SQL is running SP1 with CU4 and has its memory capped at 8gb SCCM is running SP1 with CU2 I've come across a couple MS articles pointing to memory leak with the Server Manager console but my server already has the patch applied which addresses that issue. Some of the CUs for SQL and SCCM were also meant to address potential memory leak issues but I haven't noticed any improvement. Anyway, before I hassle MS I was just curious to see if anyone else has experienced anything similar and/or has any good tips for isolating the cause. Cheers!

We just received 8 of these devices as part of a trial. As I'm only half way through building our CM2012 server I hadn't got round to building and deploying an image to the tablets as yet. When I do I'll see how things go down for us, otherwise, I'll be keeping an eye on your thread. I hope a simple solution is around the corner... Other links: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/3a91050c-b5fc-4f4c-8e0f-e96e7bfe6f3f https://forums.lenovo.com/t5/ThinkPad-slate-tablets/Table-2-How-to-PXE-Boot/m-p/1039779