Deployment of an application task sequence after the initial OS deployment task sequence is working fine, but several application deployments that is deployed to a role collection does not
install even if they are deployed required and deadline is passed. As you can see from print screen all the jobs is received by the agent, so the question is, why do they not start
installing automatically?
Checked the Computer Agent settings and all the settings were also intact including “Additional Software manages the deployment of application” setting was set to No so there
is something else due to which this is not installing.
as per it issue may be with Incorrect revision number within any of the task sequences
targeted to a machine. Now how do I find the application with the incorrect revision number in any of the task sequences targeted to the machine?
Also not sure how to go about verifying the correct revision numbers in the task sequences if this is the issue in my case
I am using SCCM 2012 sp1 cu5 and my clients are running W7 sp1 x64
I have installed Lync 2010 x64 RTM version 4.0.7577.0 to the clients (it also uses a transform to set the lync server name). The installation went fine and sccm client detected the presence of the applicaton (set as by MSI product code and file version number),
and it showed as installed in software center and displayed as detected in the appenforce log.
Then I let windows update (from SCCM) patch lync to bring it up to 4.0.7577.4419 and the app upgrades and shows the correct updated version number and everything works. However when the application evaluation scan runs again, it shows the application
as failed with a Status of 'Past due - Will be retried' in the software center (i.e. the orig deployment of 4.0.7577.0), and the appenforce log shows as this is not now detected. Which makes sense since it has been upgraded, but is there anyway of telling
sccm that it is now an upgraded version so that it will not show as failed, and will stop telling the users that there is a package waiting to be installed?
I did try to add the lync 2010 4419 rollup as a deployment and used the detection as the new MSI product code and file version, and the app had a dependency on the RTM version. This all worked fine and displayed as installed and as detected in appenforce,
until the detection process ran again and it then showed as failed in software center and not detected in appenforce log.
Has anyone else seen this strange detection process for lync 2010 x64? Could it be the transform is trying to repair itself, although I can't see that in any of the logs or on the screen.
I've checked and doubled checked that the product code and file versions are correct, and it does say installed and detected on first installation, so I'm not sure of the process to fix this.
Letting windows update patch is the preferred way to go for me, since there will be updates in the future, but how do I stop it from detecting the original deployment now that it is patched and at a higher version?
I need to deploy an update of an app in my company using the sideloading mechanism and sccm 2012.
If I choose Supersedance, select the installed app version and check the uninstall option, the app is installed, but unfortunately all permissions need to be re-authorized by the user.
If I don't select the uninstall option, the deployment fails saying package with same identity is already installed..
How can I update my enterprise app, keeping the registered permissions by using sccm?
I've set up the Application Catalog for SCCM 2012 a few times before and never really had an issue. Today, I tried setting something up and can't get it to appear. I've poured through log after log and am either missing something simple or there's
some type of corruption. I was hoping I could post here and see if anyone had ideas.
What I'm Trying to Do
Advertise 2 applications to the Application Catalog for "Proof of Concept" to show my manager how it works and what it looks like.
The Issue
Any application that I advertise does not show up in the Software Center.
The Set-Up
We are using SCCM 2012 SP1 CU4. Below are the details about how the one of the applications is set up as an example, the advertisement, system, and computer(s)
The ApplicationI've tried 5-6 different applications, but this is just an example
- Adobe Reader 10.1.9
- Filled out all App Catalog info (even though not needed)
- User Experience: Install for User (Originally for system - tried both) / Hidden Installation
- Everything else defaul
The Collection
- User-based collection (Plain-jane - no queries)
- Created new, empty one then added my AD account to it, another IT person's and a test account
- No Security Group members - Only direct members
The Advertisement
- Deployed from the Application to the User Collection above
- Action: Install / Purpose: Available
- Scheduling: ASAP (UTC) (Tried setting to current time and week ago, too)
- User Experience: Display in Software Center and only show notifications doe restarts (Tried Show All, too)
Custom Client Settings Policy
Our default Client Settings Policy wasn't configured for Application Catalog yet as it wasn't implemented at first. I created a new custom policy with the below settings and deployed it to a collection of a few computers including the ones I'm testing
on
- Computer Agent Settings
- Default App Catalog Website Point: NetBIOS of primary server (Tried FQDN, too)
- Add site to Trusted Site: Yes
- Allow Silverlight: Yes
- Install Permissions: All Users
Software Center
Shows nothing that I've advertised
Log Files
No events were flagged in the console which seemed to be related. I checked log files, but nothing really stood out, either. Using NotePad+, I searched through all my computer's local CCM log files for the package ID (according to the advertisement
view) and names of some of the applications The only traces of them I could find was in distribution logs and SMSProv.log.
The Kicker
Here's the kicker... Another Application (Cisco Jabber) was advertised the same way by someone else a few days ago and currently shows up in the Application Catalog of all people it was advertised it. It did a side by side comparison of all settings
in everything and the only difference was that it was Required, not Available. Obviously, the user collection and advertisement for it still exist so tried advertising a couple of apps to the same User collection as well as adding my AD user to the collection.
After refreshing policy and waiting; the app I advertised still won't show up on machines which still see the old advertisement PLUS my Application Catalog doesn't show the old app. This is why I think there
may be an issue.
On my machine (and other test ones I'm logged into currently,) I should see Cisco Jabber, Adobe Reader, and a couple other apps in Software Center and Application Catalog. Where people who were in the collection before can see it (And only it) in Application
Catalog, I only see it in Software Center
Image may be NSFW. Clik here to view.
Image may be NSFW. Clik here to view.
What Next?
I know this may be a lengthy post and if you have stuck with it this far, Thanks. :) What do you suggest I do next? See anything I missed?
First off, I have seen this "issue" since ConfigMgr 2012 RTM and I have seen it continuously through the various upgrades done on the way to ConfigMgr 2012 R2. The environment consists of a single AD domain, one ConfigMgr Primary site with 30 DP's
and 1500 computers.
Application B is created and it should supersede application A. The application is present on all computers throughout the environment. The application is distributed to all DP's. The deployment of application A is targeted to a collection containing all
computers. Then the deployment of application A is deleted. Application B is then configured to supersede application A with an uninstall of application A and the deployment type is replaced with the deployment type of application B. The option that Allows
users to see older deployment types is not selected. Now application B is deployed to the same collection as application A was. The deployment settings are configured with a deadline date in the future (to match the corporate maintenance window - not a ConfigMgr
maintenance window), but the application should be visible for users who want to upgrade before the deadline is reached. The option of automatically upgrading any superseded versions of the application is selected. The deployment is not created as a required
deployment, but only available.
What happens after the above is done is a bit odd. If I compare a application deployment that is superseded, to the Software Updates that normally have the same psychological effect on users (for anyone in IT this is common knowledge to be: Postpone and
don't bug me again until deadline has passed and then becomes a forced installation/update, for about 70% of the user mass) this is not the case. After about 24 hours about every single computer that is online has received the deployment of application B and
has been successfully installed. I refuse to believe that close to a 100% of the users actually select the option to upgrade application B before the deadline has been passed.
I have checked the above and it looks like it does not honor the deadline given and finds out that when it can kick of the deployment, it does.
This also happens if I don't delete the deployment of application A and leave it deployed to the same collection as the superseding application B is deployed to.
Any ideas on why I'm seeing this behavior would be greatly appriciated.
Ive deployed a customized Office 2013 package to a number of test machines, all with Win7 Ent 64bit.
A couple installed sucessfully but a couple failed with the error "Past Due - Will be installed".
On SCCM Monitoring, the failure message is "No current or future service window exists to install software updates" 0x87D00667 is the error code
If I choose "install" from Software Centre the installation completes sucessfully, though it is visible rather than silent.
A pop up message on one of the failed machines stated "Software changes must be applied to your computer after 05/02/2014 at 15:45" This give me the option to install also.
Ive seen a number of posts with the same error code, but none with quite the same issue. Im using SCCM 2012 with the latest SP and updates.
I have no maintenance windows set on anything, so my question is what is causing some to install and some to fail?
I am having trouble deploying packages to my environment. From what I can tell with the trouble shooting I have done so far. The run with admin rights is not passing through to the clients. If I use a standard software package .exe or .msi (like adobe, MS
Office) the package or application installs fine. However if I use, powershell, vb, .bat, straight command line
MsiExec.exe, They all fail to what seems like it’s not passing the admin right through because I get the UAC prompt and install fails. How do I get the admin rights to work with the other forms of installs so I can push them out silent like I do with .exe and
.msi applications?
Our ConfigMgr 2012 instance has stopped deploying software since the last round of MS Patches was applied on Feb 18 (could be coincidence); all the machines come up as "Unknown" in the Deployment status, but they also are showing as Active under
Devices. We've restarted the server with no change.
Anyone else having issues with the February patches on CM12? Anyone have any ideas where to start looking (e.g. which of the dozens of logs to start analyzing)?
So, I suspect I know the answer to this question, but I'm going to ask it anyway, and maybe solicit some thoughts on the best approach to this.
It's not hugely relevant, but as some background, we've come from LANDesk, which has a very different approach to deploying software to computers. I favour many of the approaches in SCCM, notably user-based deployments, but I'm struggling to work out how
to fit some of them in without causing myself, and my team, excessive administration.
Let's say Software X is freely, optionally installable by any user on any computer (it's freeware, or we have a company license). We have aUser-based Available deployment which puts it in the Application Catalog. They can install it on their own computer, or they can install it on a meeting room PC. Heck, IT can go all old-school, walk over to user's PC, log in
and install it on the user's behalf (assuming it's a System install). Nice. Flexible.
A need is identified for an IT team to "push" (LANDesk term) that software to the primary computer of allUsers in AD Group Y. This will need to be free of user-interaction. To reiterate: in this scenario, it's not satisfactory for users to be told to go install it themselves from the catalog - it needs to be automatic.
If we create a User-based Required deployment, the software will end up on every computer they log into, not necessarily their primary computer.
I know the documented solution to that is to define user device affinitiesand then set a deployment type requirement for primary devices. However, the moment you do that, you prevent the Application from ever being used in adevice-based deployment, and you also prevent my first scenario, where users are free to install it wherever they like from the Catalog.
Microsoft seem to have designed the user-centric model around the notion that if software is assigned/deployed to a user, it absolutely has to be available to themwherever they are, and that simply isn't the case in our business, and I'd wager in others as well.
I've seen a few discussion here where the workaround is to create a second Applicationwithout the affinity requirement, but that doubles
the amount of administrative work for any application we wish to deploy in this way (we have some apps with 6 deployment types!), and introduces the possibility of human error, where the wrong Application is deployed and it either doesn't work at all (affinity
app to device deployment), or works too well and ends up on the wrong machines (no affinity app to user deployment).
So, has anyone encountered these requirements in their, or a client's environment and come up with a satisfactory solution to this conundrum? Are we just being really odd in approaching things this way?
I know what I'd change about SCCM to accommodate this: allow the user-device affinity requirement to be applied to thedeployment instance rather than (or as well as) the application deployment type and I may hit up a Connect suggestion to that end, but I've got to come up with something in the meantime!
some Clients have Problems to show Application Deployments in Software Center. In Deployment Monitoring Tool I can see the Deployments. But if you select the Deployment I get the Error "DT cannot be empty". So I think the
Policy isn't downloaded correctly.
CIDownloader.log.
CCIDownloadItem::AddToManifest - Starting download of DocumentType 2 for ModelName Windows/x64_Windows_Server_2008_R2_Core, Version 1 CIDownloader 24.01.2013 11:00:54 5068 (0x13CC)
CCIDownloadItem::AddToManifest - Starting download of DocumentType 1 for ModelName Windows/x86_Embedded_Windows_7, Version 2 CIDownloader 24.01.2013 11:00:54 5068 (0x13CC)
CCIDownloadItem::AddToManifest - Starting download of DocumentType 2 for ModelName Windows/x86_Embedded_Windows_7, Version 2 CIDownloader 24.01.2013 11:00:54 5068 (0x13CC)
CCIDownloadItem::AddToManifest - Starting download of CI content document with DocumentName urn:policy-platform:policy.microsoft.com:smlif:ms.dcm.Windows.x86_Windows_7_Client:1:VL, DocumentVersion 1 (VL) CIDownloader 24.01.2013 11:00:54 5068 (0x13CC)
CCIDownloader::ParseDtsMessage - Dts failed with error code: 0x80070002. CI Downloader will retry. CIDownloader 24.01.2013 11:00:54 4008 (0x0FA8)
CIDownloaderJob({CFEBCEF0-7D16-421D-A53A-2A26F82CE5BF}): Received Dts failure message during CI download. CIDownloader 24.01.2013 11:00:54 4008 (0x0FA8)
CIDownloaderJob({CFEBCEF0-7D16-421D-A53A-2A26F82CE5BF}): CCIDownloaderJob::QueueRetry - Consumed 5763 seconds of 172800 second download window. CIDownloader 24.01.2013 11:00:54 4008 (0x0FA8)
CIDownloaderJob({CFEBCEF0-7D16-421D-A53A-2A26F82CE5BF}): CCIDownloaderJob::QueueRetry - Retrying package download in 2880 seconds... CIDownloader 24.01.2013 11:00:54 4008 (0x0FA8)
CCIDownloader::CreateJob CIDownloader 24.01.2013 11:21:50 44 (0x002C)
CCIDownloader::StartJob CIDownloader 24.01.2013 11:21:50 44 (0x002C)
CIDownloader job empty. CIDownloader 24.01.2013 11:21:50 44 (0x002C)
CCIDownloader::DeleteJob for job {D10C1E70-D480-4C05-9C95-D4BCBECFD4F1} CIDownloader 24.01.2013 11:21:50 44 (0x002C)
CIDownloader job deleted. CIDownloader 24.01.2013 11:21:50 44 (0x002C)
CIAgent.log
CAgent::EvaluateCIs CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=Transition, CurrentState=Init) CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): Client requesting CIAgentJob context info for key: StateMessagePriority CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): TransitionState(From=Init, To=WaitingForAssignedCI) for Event=Transition CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): QueueDebug - Executing Event. CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=Transition, CurrentState=WaitingForAssignedCI) CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore DownloadCIs CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): QueueDebug - Executing Event. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=DownloadCIs, CurrentState=WaitingForAssignedCI) CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): TransitionState(From=WaitingForAssignedCI, To=DownloadingCIs) for Event=Transition CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): QueueDebug - Executing Event. CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=Transition, CurrentState=DownloadingCIs) CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): Client requesting CIAgentJob context info for key: PostRebootDetect CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): Nothing to be downloaded. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore PersistCIs CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): QueueDebug - Executing Event. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=PersistCIs, CurrentState=DownloadingCIs) CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): TransitionState(From=DownloadingCIs, To=PersistingCIModels) for Event=Transition CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::Execute [GlobalSemaphore] Trying to aquire global semaphore CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::Execute [GlobalSemaphore] Queued for global semaphore acquisition. CIAgent 24.01.2013 11:21:50 1336 (0x0538)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): GlobalJobEvent() called [GlobalSemaphore] CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::Execute [GlobalSemaphore] Acquired global semaphore. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): CAgentJob::HandleEvent(Event=Transition, CurrentState=PersistingCIModels) CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_0ddc3eb7-5ee3-41eb-9fed-646d28a06bcf:11. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_0ddc3eb7-5ee3-41eb-9fed-646d28a06bcf:11 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_0e9a8348-0ad5-44ee-bf81-82dfd44f0699:11. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_0e9a8348-0ad5-44ee-bf81-82dfd44f0699:11 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_10203df1-4fe4-49ef-8ab3-e8030e6a2cef:22. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_10203df1-4fe4-49ef-8ab3-e8030e6a2cef:22 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_1fc34d72-440d-4f6f-9a50-604e421f3c04:13. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_1fc34d72-440d-4f6f-9a50-604e421f3c04:13 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_2191a582-1987-40fd-b8ec-cbee1a2ba590:4, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_22778347-5967-4ee1-bdc0-3fce578b7ee1:2. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_22778347-5967-4ee1-bdc0-3fce578b7ee1:2 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_278d8ebe-16bc-49b7-a806-42025d921f84:6. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_278d8ebe-16bc-49b7-a806-42025d921f84:6 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_27c341d0-a38e-43c9-aeef-a82be7e1f664:1. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_27c341d0-a38e-43c9-aeef-a82be7e1f664:1 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_2bf3a7d7-27fc-4fe6-80ff-80c9adee89a8:5, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_33aa078b-9afa-48b3-9550-8d926c07721e:5. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_33aa078b-9afa-48b3-9550-8d926c07721e:5 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_3a41042c-4feb-421b-8b55-42334654681e:15, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_3be6a762-f993-4fe5-aca5-1989551d5a88:5. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_3be6a762-f993-4fe5-aca5-1989551d5a88:5 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_3c0b214a-2258-4765-be5d-d2a9fd754bc6:2. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_3c0b214a-2258-4765-be5d-d2a9fd754bc6:2 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_46f5d091-992c-4e24-b0a2-3de657c0b8c7:16, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_49337598-4c68-401e-8c39-a415288cd7d6:11. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_49337598-4c68-401e-8c39-a415288cd7d6:11 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_4da67baa-ac51-4327-bfdc-c8f81781ae62:20, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_4f0df4d7-e1d0-4717-b9e2-5f9cb6f1dd9b:8. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_4f0df4d7-e1d0-4717-b9e2-5f9cb6f1dd9b:8 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_5d895d54-10ea-447d-8b45-123b77e89721:4. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_5d895d54-10ea-447d-8b45-123b77e89721:4 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_636ad5b2-da09-439b-ac7c-d7895d728131:2. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_636ad5b2-da09-439b-ac7c-d7895d728131:2 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_665c56e0-626a-4d8d-9378-48a8c8546846:1. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_665c56e0-626a-4d8d-9378-48a8c8546846:1 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_666d662e-66f7-4e53-b4fd-06ccd55239bf:4. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_666d662e-66f7-4e53-b4fd-06ccd55239bf:4 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_6a39d117-9e22-4e11-8fcd-ebbf35b00688:3. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_6a39d117-9e22-4e11-8fcd-ebbf35b00688:3 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_6da53bf1-ab56-4a96-9af8-6df6d4b9972e:10. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_6da53bf1-ab56-4a96-9af8-6df6d4b9972e:10 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_70d0451a-94c0-4372-b19b-dd9e4246788f:3. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_70d0451a-94c0-4372-b19b-dd9e4246788f:3 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_716e6646-2efd-4d3a-9441-5563de429a01:3. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_716e6646-2efd-4d3a-9441-5563de429a01:3 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get dependency chain for App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_77493905-3008-4862-bd89-d5fad3318cfc:41, will not be included in evaluation. CIAgent 24.01.2013 11:21:50 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_77c479ff-bef7-456d-9bae-47ea1513e56f:4. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_77c479ff-bef7-456d-9bae-47ea1513e56f:4 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_7925a429-49b4-4b04-8094-4987ca70a35b:7. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_7925a429-49b4-4b04-8094-4987ca70a35b:7 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_79516c6a-a815-4c31-99fe-9ab4e4024e4e:1. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_79516c6a-a815-4c31-99fe-9ab4e4024e4e:1 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_7af21e61-ffe4-4791-85ba-86d83cc9cf31:3. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_7af21e61-ffe4-4791-85ba-86d83cc9cf31:3 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_7d5204c1-26e4-489e-addb-1401d965153f:8. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_7d5204c1-26e4-489e-addb-1401d965153f:8 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_7e5660da-b7c7-49dd-8940-7c751389f61a:3. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_7e5660da-b7c7-49dd-8940-7c751389f61a:3 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_85f4af90-a3f1-4d7e-bb6a-b079c20fa2d5:14. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/RequiredApplication_85f4af90-a3f1-4d7e-bb6a-b079c20fa2d5:14 chain will not be included in evaluation. CIAgent 24.01.2013 11:21:51 44 (0x002C)
CIAgentJob({5BCCC0E4-C16C-4F1D-85A7-F62515232072}): [JOB SCOPE] Failed to get digest for ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/Application_8908c4aa-5c4e-41fd-a111-e4be0780e6bb:2. App policy ScopeId_CF43FADB-8569-46DF-ADB2-984C3AA1E7B1/
I don't know what is happening, but I have had SCCM 2012 decide to remove some applications from computers. The bad thing about this is one, that I know of so far, application is patient care. In the AppEnforce.Log on the client it looks like it removes
it, then reinstalls it:
+++ Starting Uninstall enforcement for App DT "Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e, Revision - 2, ContentPath - C:\Windows\ccmcache\1n, Execution Context - System AppEnforce 12/7/2013 4:19:57 AM 3468 (0x0D8C)
A user is not logged on to the system. AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Performing detection of app deployment type Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)(ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e, revision 2) for system. AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)+++ Discovered application [AppDT Id: ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e, Revision: 2] AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
App enforcement environment:
Context: Machine
Command line: msiexec /x {B0BE2D80-F89F-4AEC-8ED3-52913B7CF027} /q
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\1n
Working directory: AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Prepared working directory: C:\Windows\ccmcache\1n AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Prepared command line: "C:\Windows\system32\msiexec.exe" /x {B0BE2D80-F89F-4AEC-8ED3-52913B7CF027} /q /qn AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Post install behavior is NoAction AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Waiting for process 3784 to finish. Timeout = 120 minutes. AppEnforce 12/7/2013 4:19:59 AM 3468 (0x0D8C)
Process 3784 terminated with exitcode: 0 AppEnforce 12/7/2013 4:20:03 AM 3468 (0x0D8C)
Looking for exit code 0 in exit codes table... AppEnforce 12/7/2013 4:20:03 AM 3468 (0x0D8C)
No action needed after successful enforcement AppEnforce 12/7/2013 4:20:03 AM 3468 (0x0D8C)
Performing detection of app deployment type Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)(ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e, revision 2) for system. AppEnforce 12/7/2013 4:20:04 AM 3468 (0x0D8C)+++ Application not discovered. [AppDT Id: ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e, Revision: 2] AppEnforce 12/7/2013 4:20:04 AM 3468 (0x0D8C)++++++ App enforcement completed (6 seconds) for App DT "Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)" [ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_d6c162e0-8de8-45d5-90ce-8a20f0602f6e], Revision: 2, User SID: ] ++++++ AppEnforce 12/7/2013 4:20:04 AM 3468 (0x0D8C)+++ Starting Install enforcement for App DT "Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_e1e72a94-ca75-45c8-be23-f4c0751c2682, Revision - 3, ContentPath - C:\Windows\ccmcache\1l, Execution Context - System AppEnforce 12/7/2013 4:20:05 AM 3468 (0x0D8C)
A user is not logged on to the system. AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Performing detection of app deployment type Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)(ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_e1e72a94-ca75-45c8-be23-f4c0751c2682, revision 3) for system. AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)+++ Application not discovered. [AppDT Id: ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_e1e72a94-ca75-45c8-be23-f4c0751c2682, Revision: 3] AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
App enforcement environment:
Context: Machine
Command line: cscript.exe template.vbs
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\1l
Working directory: AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Prepared working directory: C:\Windows\ccmcache\1l AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Found executable file cscript.exe with complete path C:\Windows\system32\cscript.exe AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Prepared command line: "C:\Windows\system32\cscript.exe" template.vbs AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Post install behavior is NoAction AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Waiting for process 2456 to finish. Timeout = 120 minutes. AppEnforce 12/7/2013 4:20:06 AM 3468 (0x0D8C)
Process 2456 terminated with exitcode: 1 AppEnforce 12/7/2013 4:20:12 AM 3468 (0x0D8C)
Looking for exit code 1 in exit codes table... AppEnforce 12/7/2013 4:20:12 AM 3468 (0x0D8C)
Unmatched exit code (1) is considered an execution failure. AppEnforce 12/7/2013 4:20:12 AM 3468 (0x0D8C)++++++ App enforcement completed (7 seconds) for App DT "Spacelabs Healthcare Clinical Access - Windows Installer (*.msi file)" [ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_e1e72a94-ca75-45c8-be23-f4c0751c2682], Revision: 3, User SID: ] ++++++ AppEnforce 12/7/2013 4:20:12 AM 3468 (0x0D8C)
Starting last night with a different application:
+++ Starting Uninstall enforcement for App DT "Google Chrome - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337, Revision - 2, ContentPath - C:\Windows\ccmcache\x, Execution Context - System AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
A user is logged on to the system. AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
Performing detection of app deployment type Google Chrome - Windows Installer (*.msi file)(ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337, revision 2) for system. AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)+++ Discovered application [AppDT Id: ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337, Revision: 2] AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
App enforcement environment:
Context: Machine
Command line: msiexec /x {61D1D65D-76AF-37E3-A2AC-006AACB51587} /q
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\x
Working directory: AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
Prepared working directory: C:\Windows\ccmcache\x AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
Prepared command line: "C:\Windows\system32\msiexec.exe" /x {61D1D65D-76AF-37E3-A2AC-006AACB51587} /q /qn AppEnforce 12/12/2013 12:12:38 AM 7028 (0x1B74)
Post install behavior is NoAction AppEnforce 12/12/2013 12:12:39 AM 7028 (0x1B74)
Waiting for process 9480 to finish. Timeout = 120 minutes. AppEnforce 12/12/2013 12:12:39 AM 7028 (0x1B74)
Process 9480 terminated with exitcode: 0 AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)
Looking for exit code 0 in exit codes table... AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)
No action needed after successful enforcement AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)
Performing detection of app deployment type Google Chrome - Windows Installer (*.msi file)(ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337, revision 2) for system. AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)+++ Application not discovered. [AppDT Id: ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337, Revision: 2] AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)++++++ App enforcement completed (27 seconds) for App DT "Google Chrome - Windows Installer (*.msi file)" [ScopeId_07BE0050-1DAB-4F0B-BE99-524582FE38AF/DeploymentType_0921d804-9398-4c05-a35e-a2fc70683337], Revision: 2, User SID: ] ++++++ AppEnforce 12/12/2013 12:13:06 AM 7028 (0x1B74)
For Spacelabs there is only 1 collection to instsall the application. No collection, or deployment to remove it. For Chrome I have a Collection for Deployment and removal. The deployment is based on an AD group membership, if you arent in it and you have
chrome installed SCCM will remove it. Problem is, in the case of chrome, the computers are in that membership and show in the collection to install Chrome, but do not show to remove Chrome. The spacelabs collection is currently just a manual add collection,
so if you are in it, you should have the software.
Why would these computers be removing the software?
im really banging my head here so i hope someone can help. i am trying to set up an unattended deployment of vs 2013 test professional through sccm 2012. i am using the following command:
i have the user experience set to install for system whether or not a user is logged in. this works fine when a user is logged in and clicks the Install button in SCCM Software Center. however, when it attempts to run with no user logged in, it fails. AppEnforce
log from SCCM shows failure with exit code 1603.
the log created from the VS installer shows the following errors:
[1364:1108][2013-11-19T15:39:32]e000: Error 0x80074005: Failed to execute EXE package.
[05BC:0CC0][2013-11-19T15:39:32]i351: Removing cached package: netfxfullredist_43, from path: C:\ProgramData\Package Cache\5934DD101414BBC0B7F1EE2780D2FC8B9BEC5C4D\
[05BC:0DB0][2013-11-19T15:39:32]i304: Verified existing payload: cab451882C43592103885E4162B40BCCCA0 at path: C:\ProgramData\Package Cache\{65C91666-C3E8-3A42-BDA8-87932DD34F89}v12.0.21005\packages\TFSObjectModel\x64\cab1.cab.
[1364:0E90][2013-11-19T15:39:32]e000: Error 0x80070642: BA aborted verify of payload: cab451882C43592103885E4162B40BCCCA0
[1364:0E90][2013-11-19T15:39:32]e314: Failed to cache payload: cab451882C43592103885E4162B40BCCCA0 from working path: C:\WINDOWS\TEMP\{9e363c49-1af0-4e55-a0f8-5aadcfb3a8c5}\cab451882C43592103885E4162B40BCCCA0, error: 0x80070642.
it looks like the .net 4.5.1 install is failing somewhere but i cant really figure out why. we also have deployments of vs 2013 premium and ultimate that are set up the same in sccm (though with IE10 added as a dependency) and they work exactly as they should.
any help or idea would be greatly appreciated. OS is windows 7 SP1 64bit. please let me know if you need any more info.
I am having a very strange problem with the App Catalog. It has been working flawlessly ever since we set it up. We have several applications deployed to All Users, some requiring admin approval and some available to everyone. It was even working earlier
today. All of a sudden, for no reason that I can think of, the App Catalog is not displaying any applications - I just get "No applications are available at this time". I am perplexed.
Site status has some errors that it's not responding to HTTP requests, however these are irrelevant because we've always had those errors and the App Catalog point is obviously responding to HTTP and HTTPS requests because the App Catalog is displaying,
it's just not showing our apps.
The only results Google has given me are for n00bs that didn't understand that you needed to deploy apps to user collections in order for apps to display, that is not the case here. Anybody experience this before?
Do any of you Guys/gals have any experience with creating detection checks on mac.
I know that making detection checks for .App's isn't that hard, i could simply do "Application Bundle" - "Version", which i can find the information in the Info.plist file.
And then it uses "CFBundleIdentifier" and "CFBundleVersion" sections in the Info.plist file. (at least this is how i think it Works, if someone knows elsewise, feel free to clerify my mistake)
But now i am in the situation i need to create a detection check for a .pkg file, which installs "jre7update51" - and this application does not use CFBundleVersion - the CMAppUtil can't create the detection.XML file for me.
This Means i don't know how to create the detection check, are there anything i can do to find this information?
I'm new to SCCM 2012 and have very little exprience with this software. I'm trying to deploy project 2010 as an application.
I've created the MSP file within SCCM "Content tab" I have chosen the source folder for project.
Programs tab - I have tried it one of two ways one by just typing in "setup.exe" Within Software centre the display status is installing and the status does not change.
2) Tried to point it ot the MSP file setup.exe/adminfile setup.msp. Software centre display shows as past due - will be retried status never changes.
I have an application that I'm trying to deploy that copies two files into %AppData%\Trelligence. The detection rule checks for these files. The deployment type is set to Install for User and the detection method is a VBscript. The script
checks for both files and then returns. For testing, it also outputs the value of %appdata% to a text file on my desktop. That output shows it's checking C:\WINDOWS\system32\config\systemprofile\AppData\Roaming and not C:\Users\<username>\AppData\Roaming. Can anyone tell me how to get this detection method working? It seems like SCCM is installing as the user but detecting as system. How can I have it detect a file in %appdata%?
I'm trying to deploy some executables files in a collection of 900 pc, but for some reason, some pc takes until 4 days to show the deployment as Succeded, the other 896 pc takes the deploymen in the next 2 hours I created it.
I am trying to deploy the following command line via a package to my servers but for some reason the results are as expected. The command I am trying to run is:
Office 2010 package with three seperate MSP based on their location. Therefore created three deployment types with the relevant command line i.e. setup /adminfile location1.msp
I have added requirements based on OU i.e. OU one of ..... but the application which is called from OSD build does not detect it
I'm looking in appdiscovery.log and all I see is did not detect app type ...
How can I nail down why it is not detecting correctly?
Failing that what else could I use to determine different location - I did previously try Active Directory Site as the requirement but again same problem
that confirms that OU requirement won't work in OSD which is where I'm installing Office because a GPUpdate hasn't yet been run. In the Task Sequence I know the location because I'm using the MDT database but how could I associate a deployment type
of the application with the TS Variable ?? (without creating a new/separate application)