Hi all,

I may be being a complete muppet, so please bear with me :)

I'm tryng to use a powershell script to install an msi as part of a deployment type. I'm doing this because after the installtion a file needs to be copied.

I have dveloped and tested the script and it works perfectly fine when run manually, however SCCM just doesn't seem to be able to find or launch the script.

In the Installation Program field i have tried various combinations of (always including the script files ofc)...

powershell -noprofile -excecutionpolicy bypass -command scriptname.ps1 > file.log -noexit

But nothing works, the deployments always fail with a software change error code of 0x1(0). I have simplified the script to just popup a message box or copy a file, but it's clear the scripts aren't runnign at all. I've entered powershell only as the command, and it launches correctly as system. I have also set the powershell excecution policy to bypass on the test machine.

I suspect that the working directory of the powershell process is not the path of the CCM cache folder, so when the ps1 file is referenced, it can't find it. Of course I can't refer to the exact path of the ps1 file as the folder name it resides in in the SCCM cache folder won't be the same accross all clients.

Therefore I suspect that in need to enter somethign either in the Installation Start In field or I need to do something to ensure the powershell process knows where to find the script. What should I do? :)

Cheers,

Matt

Eric O'Dell

Hello,

I have written a simple bat file that copies 2 shortcuts to the desktop and I created an application for it so it can be run from the Application Catalog.  Everything works like it should and the shortcuts get copied to the users desktop but I can't get the detection method to work so even though the shortcuts are there the user is told the installation failed.

I assumed I could use %UserProfile%\Desktop and then the name of the shortcut as the file name in the Detection Method but that never detects the shortcut.

If I use the full path of C:\User\username\Desktop and the same file name it does detect it and says the installation completed successfully.

Is it possible to use system variables such as %UserProfile% as part of the path in the detection Methods?

Thanks,

Dustin

I have a question:

I'm creating a new build & capture (task sequence) of windows 7 with Office 2013 included. When doing this the task sequence is not completed because of 3 errors (see below). When i disable this step and run the command"setup.exe /config "\\server name\Source\Office2013\proplus.ww\config.xml" manually it works. Any idea what this could be?

Error 1

The task sequence execution engine failed executing the action (Install Office 2013) in the group (Install Software) with the error code 2147942659
Action output: tion...
Waiting for job status notification...
Waiting for job status notification...
CompleteExecution received
Received job completion notification from Execution Manager
Installation completed with exit code 0x80070103
CompleteExecution processedSetting TSEnv variable 'SMSTSInstallSoftwareJobID_HZU00081_HZU20022_Install'=''
GetExecRequestMgrInterface successful
Releasing job request, jobID='{1ADDA1E1-F32F-4456-891B-BB19256A5E86}'
Releasing of Job Request successful
CompleteJob successful
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\HZU00081
reference count 1 for the source C:\_SMSTaskSequence\Packages\HZU00081 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\HZU00081
Released the resolved source C:\_SMSTaskSequence\Packages\HZU00081
pInstall->Install(sPackageID, sProgramName), HRESULT=80070103 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Installation failed with error (0x80070103)
Install Software failed, hr=0x80070103. The operating system reported error 2147942659: No more data is available.

Error 2

The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147942659: No more data is available.

Error 3

The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned.

Hi

Im deploying SCEP 2012 to a Customers evironment, they are Currently running Symantec Endpoint Protection Version 11.X and i have a bit of trouble.

Background:

With the built in AV Replacement in SCCM i get a failiure when Liveupdate 3.3 is being uninstalled so i Created one Application for SEP 11 with MSI uninstall string and i Also created a Application for SCEP 12 with a supersedence rule to uninstall SEP 11 before applying SCEP 2012. (This has been tested successfully in another environment with same versions)

The Simulated Deployment gives a green light but the live deployment fails. (Failed to uninstall superseded deployment type)

Running the uninstall string for SEP 11 msiexec /x {26624215-248C-4F88-A415-35301812FB75} /q only works in a elevated cmd wich requires local admin user and password.

So my question is : Is there a way to uninstall SEP 11 on clients fromwithin SCCM with Admin Privilegeies since the User isn't part of the Local Admin Group?

My goal is to migrate from SEP 11 to SCEP 2012 in a sequence so  i can confirm that SCEP is being installed after SEP 11 is removed.

Any infromation that could point me to the right direction is higly appreciated, ive been searching the web with no luck yet.

I have been doing some searching for an answer a bit, but can't seem to find one.  Maybe I am doing this the only that is possible at the moment...maybe not but I am hoping that someone can confirm or suggest something differently.

Here is the situation.  Our users currently are running CRM 4.0 Outlook client and I need to move them to CRM 2011 RU11 Outlook client.  So right now, I have three Applications created.  I have CRM 4.0, CRM 2011 and CRM 2011 RU11 installer.  Currently, the CRM 2011 client supersedes the CRM 4.0 client and the CRM 2011 client is a dependent of CRM 2011 RU11.  So basically the system should go through and uninstall CRM 4, install 2011 and then RU11.

I have been attempting to figure out if there is a better way of doing this.  Is there a way to slipstream RU11 into CRM 2011 so that I only have one Application?  Or is there just another way of doing this that I may not be thinking of?

Thank you in advance.

Hi All,

we have Planning to introduce SCCM 2012 to our Environment and we have 17K+ systems and distributed to 70+ sites worldwide.

we have more than 40+ sites with 50 - 400 Users and my management doesn't want to have any servers outside our main office (i.e. DataCenter)

i have recommended to have Windows 7 based DPs in the 40+ sites where Network is Slow and we are planning to enable BITS throttling for Client Communication.

My Management is recommending to have Branch Distribution Point in all Sites and they dont want dedicated Distribution Points.

Kindly suggest me the best practices and Advantages and Disadvantages in Branch Cache in Remote site with Slow Link.

Thanks in Advance

SithaYuvaraj.

I have three applications deployments, and contents of applications are available in 2 DPs within same boundary group;

I take one DP offline,after that, I find my client get the first application content from one DPs which is online and installation is success.

The client then try to get remain contents of other application from the offline DP and it failed. Status in Software Center display 0% downloading and keep this status almost 1 hour.

I find one document for SCCM 2007:

How Clients Choose Distribution Points from the List

Clients receive the list of distribution points, perform their own selection criteria, and then attempt to connect with the first distribution point. In most scenarios, if that connection fails (for example, the distribution point computer is down or the name fails to resolve), clients retry that distribution point for 8 hours before trying the next distribution point  on the list. Clients retry with exponentially increasing delays, starting with 30 seconds, then 1 minute, then 2 minutes, and so on, until they try once an hour.

Is that behavior same with SCCM 2012 do ?

I think 8 hours is too long,how could I change duration for clients retry ?

And why do MP not validate the DPs availability before it return the DP List to the client?

if win zip package was deployed into collection a if we use application package supersede then difference of content will copy onto dp server or call content package will available to CM 2012 clients

Hey,

I have an application that needs to be installed in SYSTEM context and in addition a script that generates a user spesific file (for automation) that needs to run in USER context. Therefore I need two seperate Deployment Types under the same defined 'Application'.

How do I sequence these together? Can I use Requirements and tell SCCM to install BOTH, always? Or do I have to link them together using a dependency from the Prioirty #1 Deployment Type?

Hi, I was successful in syncing my SCCM 2012 machine with WSUS server and got all the updates. For 2 days it checked the list of collections which has the client configmgr and the updates each client has. My question is if for example client 1 has already the update for example KB2574819 and client 2 hasnt installed this update but both systems are in 1 collection, If I deploy the update again on that collection, basically it will install in client 2 right? but what will happened in client 1? Will it overwrite? or just ignore this update?

I can actually do this technically but since this is a live server, I really don't want to mess it up, thats why I ask this question first, maybe some of you has already experience with this.

regards,

 I have the error : - GetDPLocations failed with error 0x87d00215
- Failed to get DP locations as the expected version from MP "SCCM Server". Error 0x87d00215. Can you help me?

thanks

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.