Working on deploying a package and the client seems to have received it just fine, but in the report I see "Failed" and there is no details as to why it failed except for an error code. Isn't there somewhere I can look to see an actual message/error that states why it failed? There is a ton of logs on the client, but one of them must have some sort of message as to why it failed, right?

Hello,

I have one client that when launching Software Center gets "Loading Software Center returned error code 0x80041013." I have tried reinstalling the client, rebuilding the WMI repository (used both winmgmt /resetrepository and stop services renamed wbem\respository folder). The client is SCCM 2012 SP1 with CU1 (had the same problem before CU1 install, was hoping that would fix it). Anyone with any suggestions? This is one in 10 test clients that did it, but I am worried about pushing this to production clients.

Hello,

I need help to find out how to properly deploy an upgraded application using the SCCM 2012 Application supersedence.

What I have

1. One application in production with version 1.0. Let us call it APPL-BLUE1.0
2. New application of the same product with version 2.0. Let us call it APPL-RED2.0

What I want to achieve (the goal)

Users should be notified via the Software Center that a new update is available. The new update should not be installed until the user is ready and manually triggers the installation via the Software Center.

My configuration settings

On application APPL-RED2.0 I have gone to Properties -> Supsersedence and added the APPL-BLUE1.0 to the Supsersdence list. Replacement Deployment Type is configured (set to the Deployment type for the APPL-RED2.0) and the Uninstall checkbox is checked (to uninstall the APPL-BLUE1.0 deployment type first).

Install behaviour for APPL-RED2.0 is "Install for system" and "Whether or not a user is logged on" with Normal visibility.

Then I create the Deployment which I have tried three different ways.

1. Action: Install, Purpose: Available, "Automatically upgrade any superseded versions of this application"unchecked.
2. Action: Install, Purpose: Available, "Automatically upgrade any superseded versions of this application" checked.
3. Action: Install, Purpose: Required, "Automatically upgrade any superseded versions of this application" checked (forced, greyed out).

What happens

1. The application is not automatically made available in the users Software Center at all. No notification is presented and the user has to access the installation by looking in the Application Cataloguefirst. Once found in the Application Catalogue the installation runs without problems but this means that the user must somehow know there is a new version available through other means.
2. The application is automatically installed (without regard to whether or not the application is in use) on the client and a notification is presented on the users machine (Software Center).
3. Exactly the same result as for #2.

This conflicts with what I want to achieve. I want a notification and that the application is automatically made available for installation in the Software Center but I do not want it to automatically upgrade but rather let the user initiate the installation whe he or she is ready (i.e. when the application is not in use).

Please point me in the right direction in order to accomplish this.

Thank you.

Sindre

Upper management would like us to display a message like "Java 7 update 21 as been successfully installed for you by IT Department" to devices in collections after a package push.  We are new to software deployment with SCCM 2012 and my only idea was to run a package installation of a .vbs pop-up or something but that sounds a little silly, and how many of those will be in add remove programs after a couple of years??.

How would others or more experienced System Center Admins handle this request?

Thank You, Joe

Hi,

As title mentions, within an SCCM 2012-client, I have the message: App-v 5 installation "past due, will be retried", while it is installed.
Screenshot below to clarify, please advise:

Jan Hoedt

A customer asked me a question that hopefully someone here knows the answer to.  If a workstation has multiple IP addresses active, what is the logic in the agent that determines which to use to access a DP?  This doesn't happen very often but there are a few cases where there are valid situations where it can happen.  I can probably work it out experimentally, I'm just hoping that someone already knows the answer.

This would also apply to servers with multiple NICS, and most of the time we don't care which one gets used, but on occasion the communication will need to be over a management network, in which case being able to find the DP for the correct subnet is important.

I've never had an issue with it working, the customer asked what the logic was and I realized I don't know.

Bob

Hi guys,

Fairly new to SCCM so please bare with me. Have a single site server running SP1. All roles on this single VM.

Have a number of applications in the application catalogue, and all appears to be okay. Accidentially Office 2010 was deployed to All Users for a few hours two weeks ago. The deployment was soon removed, however a few machines already had 2010 by this point.

The following day a few more machine had it, although this appeared to be cached / delayed still so nothing to worry about. As week went on we heard of less and less machines being impacted. Around 90% of our estate was untouched, with them still using Office 2007.

However two weeks later - and I've had 8 machines so far install Office 2010. The application still has no deployment against it, and looking at the revision history it hasn't been touched since I last removed the deployment... So why on earth are these machines STILL installing Office 2010?!

From what I understand, SCCM will retry a failed install (unless it's a permanent fail code) within 10 minutes time, and keep doing this until it's successful or until the application in question is no longer deployed. (Ref: http://blogs.catapultsystems.com/jsandys/archive/2011/01/16/configmgr-and-failed-program-retry.aspx)

So ruling out retry issues... what else would be causing machines to be installing Office 2010 two weeks after I've removed the deployment? Mixture of desktops and laptops, all have 2007 installed prior to 2010, single site, fast LAN...

Where should I be looking to confirm the REASON for the installation? I've gone through the client logs but can't find any reaons - just the action itself.

Any help much appreciated!

Thanks,

Steve

I think all deployments would not be available until they have been evaluated.

But client do not evaluate a new application or software update deployment received from the mp immediately even the deployment deadline is set as "as soon as possible" .

I suspect whether the deployment is newly receiving or not, the application and software update evaluation triggers only when the re-evaluation interval is reached.

Is it ture?

I've read most of the threads I can find relating to this, but nothing which definitively answered my question.

I have an application for Dell's OMSA agent defined, which was created from the SysMgmt.msi installer. That worked just fine, but on a subset of machines a reboot was required to complete installation.

The machine which restarted has no maintenance windows defined, and in the deployment the available time and deadline time were both set to as soon as possible. I selected to allow installation outside of maintenance windows. It was my understanding that no maintenance windows was equivalent to never being able to do things at deadline without specifically excepting them.

This particular machine failed to install the app because a previous version of OMSA was installed which didn't support upgrade. I manually removed the old OMSA and hit retry in Software Center and it successfully installed - and noted a reboot required in the interface. "No problem" says I and put a request through to the stakeholder for a restart time.

24 hours later, it rebooted.

This is what I found in various logs. Firstly from System event log:

Moved on to RebootCoordinator:

Entered ScheduleRebootImpl - requested from 'DCMAgent'. Rebootby = 1367899016.	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
Scheduled reboot from agent DCMAgent. Deadline local time: 05/07/2013 01:56:56 PM	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
No CCM Identification blob	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
Not in Service Mode, check ServiceWindowsManager next	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
ServiceWindowsManager has allowed us to Reboot	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
MTC task does not exist. Creating new request.	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
MTC allowed us to reboot	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
Raising client SDK event for class NULL, instance NULL, actionType 4l, value 1367899016	900	600, user NULL, session 4294967295l, level 0l, verbosity 30l	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)
Notified UI grace period start with 900 grace seconds and 600 final seconds.	RebootCoordinator	7/05/2013 1:56:56 PM	8996 (0x2324)

Then on to DCMAgent:

DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::SetupJob - Add assignment Dell OpenManage Systems Management Software_Servers - Physcial_Install({E2EE3E72-070F-4512-B857-33F6E1676113})	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::PopulateCIsFromAssignment - CI policy Id:ScopeId_E76FFDBE-064E-4BC8-98E3-04BEA611B13E/RequiredApplication_d2e82aa2-22fd-47f0-9ee2-fe5039f055e5 version:2 with actions: Evaluation, Install, Uninstall, Update	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::SetUserParams	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::SetTimeout	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
CDCMAgentJobMgr::StartJob - Starting DCM Agent job {BFA65F91-7408-42B3-9819-8C30800701E1}	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::GetUserTokenParams	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore Transition	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=Transition, CurrentState=Idle)	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgent::InitiateCIAgentJob - Starting CI Agent Job {FDD72AFD-45D4-4C16-BDAF-3282D9E0A678} for target: machine. Refer to this CI agent job ID in ciagent.log for more details	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): TransitionState(From=Idle, To=Evaluating) for Event=Transition	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore Transition	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=Transition, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:51 PM	15208 (0x3B68)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:51 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:51 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:51 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:51 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:52 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:52 PM	16720 (0x4150)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore NotifyProgress	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Evaluating)	DCMAgent	7/05/2013 1:56:56 PM	31748 (0x7C04)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): NotifyComplete	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): TransitionState(From=Evaluating, To=Success) for Event=Transition	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore Transition	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)
DCMAgentJob({BFA65F91-7408-42B3-9819-8C30800701E1}): Registering for Immediate reboot	DCMAgent	7/05/2013 1:56:56 PM	8996 (0x2324)

So, I'm not sure why DCMAgent initiated the reboot. It seems a little rude to me. I have read about application definitions could cause application installers to reboot, but why was it 24 hours later?

The app enforcement looked like this: (no there was no /noreboot or ReallySuppress, but there will be in future)

+++ Starting Install enforcement for App DT "Dell OpenManage Systems Management Software - Windows Installer (*.msi file) x64" ApplicationDeliveryType - ScopeId_E76FFDBE-064E-4BC8-98E3-04BEA611B13E/DeploymentType_d59c9aa5-0b64-46b6-9b8e-7dd2e1adca41, Revision - 2, ContentPath - C:\Windows\ccmcache\4, Execution Context - System	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    A user is logged on to the system.	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    Performing detection of app deployment type Dell OpenManage Systems Management Software - Windows Installer (*.msi file) x64(ScopeId_E76FFDBE-064E-4BC8-98E3-04BEA611B13E/DeploymentType_d59c9aa5-0b64-46b6-9b8e-7dd2e1adca41, revision 2) for system.	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)+++ Application not discovered. [AppDT Id: ScopeId_E76FFDBE-064E-4BC8-98E3-04BEA611B13E/DeploymentType_d59c9aa5-0b64-46b6-9b8e-7dd2e1adca41, Revision: 2]	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    App enforcement environment: 
	Context: Machine
	Command line: msiexec /i "SysMgmtx64.msi" /qb
	Allow user interaction: No
	UI mode: 0
	User token: null
	Session Id: 3
	Content path: C:\Windows\ccmcache\4
	Working directory: 	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    Prepared working directory: C:\Windows\ccmcache\4	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    Prepared command line: "C:\Windows\system32\msiexec.exe" /i "SysMgmtx64.msi" /qb /qn	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
Valid MSI Package path = C:\Windows\ccmcache\4\SysMgmtx64.msi	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    Advertising MSI package [C:\Windows\ccmcache\4\SysMgmtx64.msi] to the system.	AppEnforce	6/05/2013 2:20:31 PM	19564 (0x4C6C)
    Executing Command line: "C:\Windows\system32\msiexec.exe" /i "SysMgmtx64.msi" /qb /qn with user context	AppEnforce	6/05/2013 2:20:32 PM	19564 (0x4C6C)
    Working directory C:\Windows\ccmcache\4	AppEnforce	6/05/2013 2:20:32 PM	19564 (0x4C6C)
    Post install behavior is BasedOnExitCode	AppEnforce	6/05/2013 2:20:32 PM	19564 (0x4C6C)
    Waiting for process 11568 to finish.  Timeout = 120 minutes.	AppEnforce	6/05/2013 2:20:32 PM	19564 (0x4C6C)
    Process 11568 terminated with exitcode: 3010	AppEnforce	6/05/2013 2:23:16 PM	19564 (0x4C6C)
    Looking for exit code 3010 in exit codes table...	AppEnforce	6/05/2013 2:23:16 PM	19564 (0x4C6C)
    Matched exit code 3010 to a PendingSoftReboot entry in exit codes table.	AppEnforce	6/05/2013 2:23:16 PM	19564 (0x4C6C)++++++ App enforcement completed (165 seconds) for App DT "Dell OpenManage Systems Management Software - Windows Installer (*.msi file) x64" [ScopeId_E76FFDBE-064E-4BC8-98E3-04BEA611B13E/DeploymentType_d59c9aa5-0b64-46b6-9b8e-7dd2e1adca41], Revision: 2, User SID: ] ++++++	AppEnforce	6/05/2013 2:23:16 PM	19564 (0x4C6C)

In anyone can point me in the right direction for an explanation, that'd be grand. This wasn't a one-off - at least 3 servers exhibited the same behaviour. So I'm assuming something in my configuration is leading to this reboot almost exactly 24 hours later.

Thanks.

hi guys

I'm breaking my head for days trying to understand why my clients choose to connect to whatever DP they want, randomly...

I have one site with three MP\DP's.

I have boundaries configured correctly, I'm sure.

boundaries are configured by subnets.

I checked the System management OU in AD for any leftovers from old SCCM2007

tried to remove the Management Point Role from all servers and Added the Rules again...

tried to remove subnets from boundaries and use a fallback status point - but still.... the client choose random management point.

here is the last part of the locationservices.log of one of the machines:

Default Management Points from MP: LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Name: 'BRANCH-MP.Domain.com' HTTPS: 'N' ForestTrust: 'Y' LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Name: 'MAIN-MP.Domain.com' HTTPS: 'N' ForestTrust: 'Y' LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Name: 'SECONDARY-MP.Domain.com' HTTPS: 'N' ForestTrust: 'Y' LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Persisted Default Management Point Locations locally LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 8:58:49 PM 1020 (0x03FC)
Calling back with the following distribution points LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Distribution Point='http://MAIN-MP.Domain.com/SMS_DP_SMSPKG$/NEW00182', Locality='LOCAL', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://MAIN-MP.Domain.com/SMS_DP_SMSSIG$/NEW00182', ForestTrust='TRUE', LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Distribution Point='\\MAIN-MP.Domain.com\SMSPKGD$\NEW00182\', Locality='LOCAL', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='', ForestTrust='TRUE', LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Distribution Point='http://SECONDARY-MP.Domain.com/SMS_DP_SMSPKG$/NEW00182', Locality='REMOTE', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://SECONDARY-MP.Domain.com/SMS_DP_SMSSIG$/NEW00182', ForestTrust='TRUE', LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Distribution Point='\\SECONDARY-MP.Domain.com\SMSPKGD$\NEW00182\', Locality='REMOTE', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='', ForestTrust='TRUE', LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Calling back with locations for location request {06634153-EAAA-4877-A749-1976DDE37599} LocationServices 5/12/2013 8:58:49 PM 1536 (0x0600)
Failed to send request to /SMS_MP/.sms_aut?MPCERT2 at host BRANCH-MP.Domain.com, error 0x2ee2 LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
[CCMHTTP] ERROR: URL=http://BRANCH-MP.Domain.com/SMS_MP/.sms_aut?MPCERT2, Port=80, Options=224, Code=12002, Text=ERROR_WINHTTP_TIMEOUT LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
Raising event:
instance of CCM_CcmHttp_Status
{
 ClientID = "GUID:04B87CCF-5575-4689-A8FA-14D25B733DCA";
 DateTime = "20130512175858.328000+000";
 HostName = "BRANCH-MP.Domain.com";
 HRESULT = "0x80072ee2";
 ProcessID = 3648;
 StatusCode = 600;
 ThreadID = 2256;
};
 LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
Successfully sent location services HTTP failure message. LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
Failed to refresh Encryption certificate information over HTTP(0x80072ee2) LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
Failed to refresh encryption cert info for BRANCH-MP.Domain.com. LocationServices 5/12/2013 8:58:58 PM 2256 (0x08D0)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 8:58:58 PM 1536 (0x0600)
1 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 5/12/2013 8:58:58 PM 1536 (0x0600)
Failed to send management point list Location Request Message to BRANCH-MP.Domain.com LocationServices 5/12/2013 8:59:10 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 8:59:10 PM 1536 (0x0600)
2 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 5/12/2013 8:59:10 PM 1536 (0x0600)
Attempting to retrieve local MPs from the assigned MP LocationServices 5/12/2013 8:59:10 PM 1020 (0x03FC)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 8:59:10 PM 1020 (0x03FC)
Failed to send management point list Location Request Message to BRANCH-MP.Domain.com LocationServices 5/12/2013 8:59:31 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 8:59:31 PM 2256 (0x08D0)
3 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 5/12/2013 8:59:31 PM 2256 (0x08D0)
Refreshing the Management Point List for site TLV LocationServices 5/12/2013 8:59:31 PM 1020 (0x03FC)
Retrieved management point encryption info from AD. LocationServices 5/12/2013 8:59:31 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 8:59:45 PM 1536 (0x0600)
Failed to send request to /SMS_MP/.sms_aut?MPLIST at host BRANCH-MP.Domain.com, error 0x2ee2 LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
[CCMHTTP] ERROR: URL=http://BRANCH-MP.Domain.com/SMS_MP/.sms_aut?MPLIST, Port=80, Options=224, Code=12002, Text=ERROR_WINHTTP_TIMEOUT LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Raising event:
instance of CCM_CcmHttp_Status
{
 ClientID = "GUID:04B87CCF-5575-4689-A8FA-14D25B733DCA";
 DateTime = "20130512175952.670000+000";
 HostName = "BRANCH-MP.Domain.com";
 HRESULT = "0x80072ee2";
 ProcessID = 3648;
 StatusCode = 600;
 ThreadID = 1020;
};
 LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Successfully sent location services HTTP failure message. LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Failed to retrieve MP certificate authentication information over http. LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 8:59:52 PM 544 (0x0220)
Refreshing trusted key information LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Refreshed Root Site Code from AD LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Attempting to refresh TRK from AD LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Refreshed TRK from AD LocationServices 5/12/2013 8:59:52 PM 1020 (0x03FC)
Failed to send request to /SMS_MP/.sms_aut?MPKEYINFORMATIONEX at host BRANCH-MP.Domain.com, error 0x2ee2 LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
[CCMHTTP] ERROR: URL=http://BRANCH-MP.Domain.com/SMS_MP/.sms_aut?MPKEYINFORMATIONEX, Port=80, Options=224, Code=12002, Text=ERROR_WINHTTP_TIMEOUT LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Raising event:
instance of CCM_CcmHttp_Status
{
 ClientID = "GUID:04B87CCF-5575-4689-A8FA-14D25B733DCA";
 DateTime = "20130512180013.779000+000";
 HostName = "BRANCH-MP.Domain.com";
 HRESULT = "0x80072ee2";
 ProcessID = 3648;
 StatusCode = 600;
 ThreadID = 1020;
};
 LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Successfully sent location services HTTP failure message. LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 9:00:13 PM 4072 (0x0FE8)
Failed to verify Certificate with error 0x80070057. LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Failed to refresh trusted key information while refreshing mp list. LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Persisting the management point authentication information in WMI LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Persisted Management Point Authentication Information locally LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
4 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 5/12/2013 9:00:13 PM 1536 (0x0600)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:00:13 PM 2712 (0x0A98)
Assigned MP error threshold reached, moving to next MP. LocationServices 5/12/2013 9:00:13 PM 544 (0x0220)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
MPLIST requests are throttled for 00:03:23 LocationServices 5/12/2013 9:00:13 PM 3964 (0x0F7C)
Ignoring MP error during post-rotation flush period of 20 seconds. LocationServices 5/12/2013 9:00:13 PM 4072 (0x0FE8)
0 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 5/12/2013 9:00:13 PM 4072 (0x0FE8)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Updated FSP 'MAIN-MP.Domain.com' from AD to local. LocationServices 5/12/2013 9:00:13 PM 1020 (0x03FC)
Failed to send Location Request Message LocationServices 5/12/2013 9:00:34 PM 2712 (0x0A98)
Failed to create Location Request Message body LocationServices 5/12/2013 9:00:34 PM 2712 (0x0A98)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 9:00:34 PM 1020 (0x03FC)
Executing Task LSSiteRoleCycleTask LocationServices 5/12/2013 9:00:34 PM 4072 (0x0FE8)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:01:35 PM 2712 (0x0A98)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:01:36 PM 2712 (0x0A98)
The number of discovered DPs(including Branch DP and Multicast) is 2 LocationServices 5/12/2013 9:01:36 PM 2712 (0x0A98)
Calling back with the following distribution points LocationServices 5/12/2013 9:01:36 PM 2712 (0x0A98)
Distribution Point='http://MAIN-MP.Domain.com/SMS_DP_SMSPKG$/TLV0002A', Locality='LOCAL' LocationServices 5/12/2013 9:01:36 PM 2712 (0x0A98)
Distribution Point='\\MAIN-MP.Domain.com\SMSPKGD$\TLV0002A\', Locality='LOCAL' LocationServices 5/12/2013 9:01:36 PM 2712 (0x0A98)
Received reply of type PortalCertificateReply LocationServices 5/12/2013 9:01:38 PM 544 (0x0220)
The reply from location manager contains 0 certificates LocationServices 5/12/2013 9:01:38 PM 544 (0x0220)
Updating portal certificates LocationServices 5/12/2013 9:01:38 PM 544 (0x0220)
There are no certificates available to install LocationServices 5/12/2013 9:01:38 PM 544 (0x0220)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:03:36 PM 1020 (0x03FC)
Current AD site of machine is MAIN-AD-SITE LocationServices 5/12/2013 9:03:36 PM 1020 (0x03FC)
Received reply of type PortalCertificateReply LocationServices 5/12/2013 9:03:36 PM 916 (0x0394)
The reply from location manager contains 0 certificates LocationServices 5/12/2013 9:03:36 PM 916 (0x0394)
Updating portal certificates LocationServices 5/12/2013 9:03:36 PM 916 (0x0394)
There are no certificates available to install LocationServices 5/12/2013 9:03:36 PM 916 (0x0394)

 thank you!

Hi,

I have a scenario at the moment where during application testing it has been commented that the uninstall (regression testing of all applications is a pre-requisite in our environment) of applications doesn't happen in a timely or predictable manner.

I've done some digging around and believe this is due to the "Schedule re-evaluation for deployments" client setting which is currently set to the default value of 7 days.  In my lab environment I have this set at 15 minutes and see the uninstalls happening pretty reliably within a few minutes of changing the collections.

I had planned to change the client settings in our Live Test and Production environments to reduce the re-evaluation cylce considerably (maybe even as low as 1 hour) but found an article on TechNet which states:

"We recommend that you do not change this value to a lower value than the default as this may negatively affect the performance of your network and client computers."

My questions are:

1) What exactly is the re-evaluation doing?  I assumed it was just re-running the detection method(s) and requirements to ensure all were still met (and hence for uninstalls executing them) but this seems to suggest that it's processing stuff against the Site systems too?

2) Is there any way of estimating the performance impact for both the client and the network?  I have an estate of ~80k users, so what sort of impact would it have if I was to re-evaluate every hour?

Cheers,

Stuart

I'm setting up an sccm 2012 remote distribution points using HTTPS.  the clients are failing to install from this DP and give the following access denied error message.

The CAS.log shows this:

Download failed for content 2cefe0ef-f4e1-4c3d-97f9-10a608c46c52.1 under context System, error 0x80070005

Previous line shows it found the download location:

Download location found 0 -  http://server.domain.com/NOCERT_SMS_DP_SMSPKG$/2cefe0ef-f4e1-4c3d-97f9-10a608c46c52

I am not using a network access account as all systems are in the same domain. I am relying on system or computer$ to access.

Previously, same client was able to access the central (fallback) DP on our primary site server prior to the installation of the new DP, but now is in the new DP's preferred content lookup boundary.

Thanks.

I've tried to piece together other posts on this topic but have yet to successfully do this.  Could someone please provide a step by step on how to run a vbscript with SCCM 2012 SP1?  Please be as detailed as possible, because I would like to understand the nuances of why a certain setting is being set and why certain selections are being selected.

I've tried many different settings but haven't found the correct combination or something.  If it matters, the vbscript copies a file from a network share available to everyone and also creates a shortcut to the company intranet site.  Everything tests out locally, but just cannot get this to work via SCCM 2012 SP1.  This is what I have to work. 

Please just post a how to with as much detail as possible.  THANKS!!!

Hello, we have the vulnerability MS10-079 on our computers.   It is a word vulnerability for each version.   When I do a serach for MS10-079 or the kb number, I cannot find them.   I have Office 2007 and Office 2010 checked in the catalog.  

Anyone else able to see MS10-079?   Any pointers?

Thanks

Greetings,

  We have started to implement a few maintenance windows on some collections.

  I thought that deployments would just happen within the maintenance windows without drama.

  We are getting errors in the deployment status saying "Program may never run due to Service Window Constraints". Is this normal maintenance window behaviour?

Thanks

David Z

Hello,

I've just started playing around with the new application model in SCCM 2012 and in the meanwhile I'm reviewing the installation procedures. In ConfigMgr 2012 I would like to use the application model and use Powershell scripting to do additional actions where possible.

I'm having an issue trying to install an application (Lotus Notes) where I have some additional actions to perform. I use a Powershell script to wrap the setup and the additional actions together.

When I run the script from Powershell_ise it completes successful (exitcode 0) but a folder and some icons are not created in %ProgramData%\Microsoft\Windows\Start Menu\Programs. When I run the script from an elevated Powershell_ise the installation is as it should be, including the folder and icons. I use Start-Process to run the msiexec... If I use the -Verb Runas parameter (without the -Wait parameter) the installation also completes successful. Problem here is that I also use the -Wait parameter which seems to cause issues in combination with the -Verb Runas parameter. So I need a way to elevate the script (I think)

In ConfigMgr 2007 you can run a program "as administrator" but in ConfigMgr 2012's applications there does not seem to be an option to do so. Note: In 2007 I sequenced 2 programs, one for the install and one (batch file) for the additional actions so I'm not sure if the script would work this way.

Does anyone know how to run the script using the application model with elevated rights?

Script looks like this:

Begin {
$ErrorActionPreference = "STOP"
$ScriptDirectory = split-path -parent $MyInvocation.MyCommand.Definition

$Application = "`"$ScriptDirectory\Lotus Notes 8.5.3\Lotus Notes 8.5.3.msi`""
$InstallDir = "`"C:\Program Files (x86)\Lotus\Notes`""
$DataDir= "`"C:\Program Files (x86)\Lotus\Notes\Data`""
$Logfile = "`"$env:LOGDIR\CCM\LotusNotes853.log`""
$Arguments = @("/i", $Application, "/q", "DATADIR=$DataDir", "PROGDIR=$InstallDir", "/l*", $Logfile)
}

Process {
    $Install = Start-Process -FilePath msiexec.exe -ArgumentList $Arguments -wait -PassThru
    $Exitcode = $Install.ExitCode

    Try {
        Copy-Item -Path "\\mydomain\Cfg\Lotus\icons\*.ico" -Destination "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Lotus Applications\" -Force
        Copy-Item -Path "\\mydomain\Cfg\Lotus\notes.ini" -Destination "C:\Program Files (x86)\Lotus\Notes\" -Force
        Copy-Item -Path "\\mydomain\Cfg\Lotus\setup.txt" -Destination "C:\Program Files (x86)\Lotus\Notes\data\" -Force
        Copy-Item -Path "\\mydomain\sys01\Cfg\Lotus\Dic\*.dic" -Destination "C:\Program Files (x86)\Lotus\Notes\data\" -Force
        }
    Catch {
        $Exitcode = "1604"
        Add-Content $logfile.Substring(1,$logfile.Length-2) $error[0]
        }
} #End Process

End {
return $Exitcode
}

Also I was wondering if SCCM actually picks up the Exitcode the script returns?

Thanks!

When trying to deploy office as part of an image or when tryign to install it from the software center in SCCM 2012 the deploment fails. I looked at the AppEnforce Log and noticed the error below. Need some help trying to resolve the timeout issue.

[LOG[    Prepared working directory: C:\Windows\ccmcache\2x]LOG]!><time="07:37:38.009+240" date="05-10-2013" component="AppEnforce" context="" type="1" thread="3000" file="appcontext.cpp:182">
<![LOG[    Prepared command line: "C:\Windows\ccmcache\2x\setup.exe"]LOG]!><time="07:37:38.011+240" date="05-10-2013" component="AppEnforce" context="" type="1" thread="3000" file="appcontext.cpp:331">
<![LOG[    Post install behavior is BasedOnExitCode]LOG]!><time="07:37:38.279+240" date="05-10-2013" component="AppEnforce" context="" type="1" thread="3000" file="appcommon.cpp:1091">
<![LOG[    Waiting for process 2636 to finish.  Timeout = 120 minutes.]LOG]!><time="07:37:38.282+240" date="05-10-2013" component="AppEnforce" context="" type="1" thread="3000" file="appexcnlib.cpp:1682">
<![LOG[Exceeded timeout of 120 minutes while waiting for process 2636 to finish.]LOG]!><time="09:37:37.785+240" date="05-10-2013" component="AppEnforce" context="" type="2" thread="3000" file="appexcnlib.cpp:1696">
<![LOG[WaitForRunningProcess failed.  Error 0x87d00213.]LOG]!><time="09:37:37.818+240" date="05-10-2013" component="AppEnforce" context="" type="3" thread="3000" file="appexcnlib.cpp:1712">
<![LOG[CMsiHandler::CompleteEnforcement failed with 0x87d00213]LOG]!><time="09:37:37.820+240" date="05-10-2013" component="AppEnforce" context="" type="3" thread="3000" file="msihandler.cpp:320">
<![LOG[CAppProvider::CompleteEnforcement failed with error 0x87d00213]LOG]!><time="09:37:37.821+240" date="05-10-2013" component="AppEnforce" context="" type="3" thread="3000" file="appprovider.cpp:2442">
<![LOG[++++++ Failed to enforce app. Error 0x87d00213. ++++++]LOG]!><time="09:37:37.830+240" date="05-10-2013" component="AppEnforce" context="" type="3" thread="3000" file="appprovider.cpp:2365">

I'm having some difficulty using custom scripts as the detection method for an application deployment type. I'm hoping someone can confirm what I'm running into.

Signed powershell scripts do not execute and powershell claims they are signed. After digging into this, I've discovered that any scripts uploaded in the detection method Script Editor window are converted so the newline character is no longer CRLF, but just LF. Powershell doesn't realize there is a signature block when the file is saved with just LF as the newline character.

The scripts don't live on the client for longer than it takes to execute them. To get around that, I've denied SYSTEM's ability to delete files from c:\windows\ccm\systemtemp. This way I can actually see the file that is being downloaded. It doesn't matter how I upload the file or paste the values into the Script Editor window, CRLF is converted to just LF when the file is downloaded.

I can always do VBScript or change powershell's execution policy, but is there a solution so I can use signed powershell code? My site is running on Server 2012, SQL 2012 SP1 and ConfigMgr 2012 SP1.

If I have a package that has a required reboot set, and it has a dependent install that also has the required reboot set, will SCCM install the dependency, then the main package and then process the reboot, or will it process a reboot for each package separately?

I would hope that SCCM waits until the last package is installed and only reboots once, but thats not what I'm seeing.  I'm not sure if I have something set incorrectly, or if SCCM doesnt manage reboots in this way.

Thanks in advance...