Unknownforce

Thanks for the info. This isn't a problem anymore... in fact, it was a real bonehead problem... Our Network Administrator never fully decommissioned our old SMS 2003 server... so it was still broadcasting. And this one WAS set to push clients automatically because we didn't have OSD back then, so the client installed in the background after the AD Discovery and because the client check kept failing, it kept pushing... I should have figured it out easily by seeing the logs mention the old server, but I didn't because the old SMS 2003 server was very similarly named to our current SCCM 2012 server, so when looking at the logs, it just looked like it was coming from the same server... but, in fact, it wasn't. I was also confused by the date on the ccmsetup.exe and the fact that there were two separate ccmsetup.log files... well now it all makes sense... I'm just surprised that it's taken us this long to realize that this was still active, I would have figured it would be causing a LOT more problems across our network... Either way, thanks for the reply.

We recently updated to 2012 R2 CU3 from Non-SP CU2. After the update, I did a manual forced install of the client on our Main collection to get them all up to date, which went fairly well.. there were a few that I had to re-install a couple times to get it to "take" but overall it worked just fine. Now we're reporting about 91% of "active" compliance, client-wise. A little more background on our infrastructure... We have our PxE boot only available on a separate VLAN with an available D block of IP addresses that we use to load computers with, so when we load machines, they tend to get the same IPs that were recently used, which can confuse DNS and SCCM for a bit because there are potentially stale records that still have a freshly loaded computer on that segregated VLAN... So on to the problem here... After any fresh OSD loads, everything works just fine, but ccmsetup.exe keeps re-running, over and over. It uninstalls the client successfully, and then re-installs the client successfully... over and over and over again... Which logs can I look at to see why this is happening? ccmsetup.log doesn't seem to show WHY it was triggered, it just shows that it starts, downloads the package, removes the current version, and then installs it again. Each time is successful with no errors. Client installation is NOT set to push on our site in any way. The only installation of the client is during most of our OSD Task Sequences. (one is setup as just a plain base load without loading the client) It doesn't matter whether or not the CU3 is deployed to it. It will exhibit this same behavior regardless of the CU3 patch deployment. The CU3 patch does work on it as well, but it will just re-install right over it the next time it is triggered. It also doesn't seem to be time dependent, It can re-install within a few minutes and then go for an hour without re-installing, but it eventually does happen again. The devices that exhibit this behavior on are showing that they Pass the client check... so it is checking in properly... It kind of seems like it has something to do with the manual install I pushed to the collection, because it's using the "force install" option as well as the option to uninstall the old version first. It kind of seems like the server is trying to install to a device that perhaps in SCCM's database has the same IP address registered to it, but isn't the same device name... and thus it's not checking in properly because of that, so it's stuck in a loop trying to get the device updated. Over-analyzing is my specialty, but this seems like a fairly reasonable explanation to me. But, if it's true, how do I cancel those "pending" installs? Any help would be greatly appreciated as this is making it difficult to use my test machine for application/package deployment testing because it ends up killing all the SCCM related tasks/services in order to reinstall!

They are Applications. I suppose I could try Packages, but I just don't get why it would be a problem now that we've upgraded when it worked just fine pre-sp1. I'll see if Packages work better, but they aren't as manageable, such as supercedence and whatnot, are they? I'd like to keep superceding things like Java, Reader and flash when we move to new versions so that current clients get the updates as well. I guess I could have them exist in both Applications and Packages, thus retain the manageability. It should still list them as "Installed" even though they weren't originally installed as an Application... I'll play around with Packages and see if that works. Thanks for the suggestion.

VERY similar to this post... http://www.windows-noob.com/forums/index.php?/topic/7802-sccm2012-sp1-big-issues/ Same error number basically (Which seems to be a pretty "generic" error) EXCEPT, my machines ARE domain joined before the application install happens. I've set each application of the task sequence to be deployed to All Desktop Clients as it would likely still be an "Unknown" computer at this point I believe. Regardless of where it would be, All Desktop Clients would hold any Unknown devices and/or Known devices as well, so instead of having this be a possible cause for it to fail, I just set it to All Desktop Clients, but they are only marked as Available, so it doesn't force install on anything we don't want it to be installed on. (Servers, etc.) Here's the current (Basic) Task Sequence for each Sequence: (Group) Restart in PE Format and Partition Disk 0 Apply Operating System Apply Windows Settings (Basically just set name and Admin password (we have an activation server, so we don't use a key here) Apply Network Settings (Joining to Domain) (Each TS has a different OU which they place these new loads) Apply Device Drivers (Group) Setup Windows and Configuration Manager Install Application (Java/Adobe Flash) Install Application (Office/Adobe Reader and a few others) Here's the important bits from AppIntentEval.log from a computer that's failing the load: No dependencies for DeploymentType ScopeId_3FDE2C2B-3430-470E-9299-326559C511B7/DeploymentType_76b5d577-549d-4973-a2ee-3d526460d5cd/8. Evaluating Application policies for Machine Rejecting ScopeId_3FDE2C2B-3430-470E-9299-326559C511B7/RequiredApplication_fbb77ade-84eb-4ec8-a0aa-d592bd528295/8 due to evaluation error ScopeId_3FDE2C2B-3430-470E-9299-326559C511B7/DeploymentType_76b5d577-549d-4973-a2ee-3d526460d5cd/8 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = HP Connection Manager - Windows Installer (Native) ScopeId_3FDE2C2B-3430-470E-9299-326559C511B7/Application_fbb77ade-84eb-4ec8-a0aa-d592bd528295/8 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = HP Connection Manager - SP60031 ScopeId_3FDE2C2B-3430-470E-9299-326559C511B7/RequiredApplication_fbb77ade-84eb-4ec8-a0aa-d592bd528295/8 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy It doesn't seem like an issue with the application. Because it seems to happen with whichever application I set to install first. At first, I thought it was limited to applications that had Superceded other applications. It was originally failing on Java v7u55, which we also had applications out there still for v7u5 v7u13 v7u22, and a few others. But They were all superceded, and I only had v7u55 set for the task sequence, none of the others, but all of the superceded ones showed no clients having them, so I simply deleted the supercedence and the older applications as well. So now there's only Java v7u55. (Which I will update when I fix this problem, but no point in doing that until I can load new machines) Did the same with Flash player and Adobe Reader. This initially didn't resolve the problem, but after rebuilding the task sequence, it worked properly for a load or two, so I assumed it was fixed. Well I go to load another and I'm getting these errors again without even changing anything... A little background here: Similar setup as the other post. Windows Server 2008 R2, SCCM R2 CU3, Only one Primary Site server, no other servers or distribution points or management points or anything. Just a single Server. We just recently updated from SCCM 2012 Vanilla to SP1 and then directly to R2 (and CU3) as well. The upgrades had no major issues, and I planned and performed all the necessary steps involved in each upgrade. (AIK -> ADK, .NET 4.5, etc.) I've also re-distrubuted the Boot Images. (although we only use the 64 bit one, I did both.) But it's booting just fine, the problem isn't until it tries to load an application during the task sequence. BEFORE the upgrade, we could load machines just fine. Add and remove applications from the task sequences without issues. We only have 4 separate Task Sequences for 4 different device types. It wasn't until AFTER the upgrade I started getting this issue. In one of the fixes I read in a link from a reply to the other post I linked above, it mentioned the following: Now, keep in mind we've been loading machines without issue for years now... But... We are dumping them into OU's that do have custom GPO's. Could this be the cause of the problem? And if so, why is it that it worked just fine before (On non-SP1/R2) and now (on R2) it has a problem with it? Is the proper procedure to first start them in the workstations OU (which doesn't have a GPO applied) and then move them after the load or as part of a final task sequence? Any help would be greatly appreciated.