Hi,

I have problem. When I set shedule time except from 0:10 am to 1:20 am, scom not send emails to subscriber whole day.

SCOM has all updates.

Thank You

Hi,

Users reported they could not install Windows updates. Some hundred should get their updates mandatory end of this week. We found out the Windows update package did not get on the distribution points.

We tried to:

*update the distribution points, but that did not work
*deleted the package from the distribution point and tried to redistribute it but that did not work either

The logfile mentions that it cannot access the package or it doesn't exist: "\\ourdomain\SCCM\WindowsUpdates\d8b72e39-6103-49fb-b1f6-14e096dd3cd6" (doesn't exist and it does not indeed) or the SMS service cannot access it.
STC00187 is our package with Windows updates.

Note: the package is > 24 GB in size. We did use https://gallery.technet.microsoft.com/scriptcenter/Remove-Expired-Superseded-f35495e1 

 to cleanup expired updates.

Please advise howto troubleshoot. J.

Distmgr.log:

Skipping content d06c958a-2d7a-4b19-a140-e84cc9ac4c9c, 9865 KB, since snapshot for this content already exists...               SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12       2680 (0x0A78)

STATMSG: ID=2376 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=oursccmserver.ourdomain SITE=STC PID=3596 TID=2680 GMTDATE=Tue Apr 21 12:38:12.094 2015 ISTR0="d06c958a-2d7a-4b19-a140-e84cc9ac4c9c" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="STC00187"              SMS_DISTRIBUTION_MANAGER               21/04/2015 14:38:12       2680 (0x0A78)

Snapshot processing content with ID 16810274 ...          SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12               2680 (0x0A78)

The source directory \\ourdomain\SCCM\WindowsUpdates\d8b72e39-6103-49fb-b1f6-14e096dd3cd6 doesn't exist or the SMS service cannot access it, Win32 last error = 2             SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12              2680 (0x0A78)

STATMSG: ID=2306 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=oursccmserver.ourdomain SITE=STC PID=3596 TID=2680 GMTDATE=Tue Apr 21 12:38:12.100 2015 ISTR0="\\ourdomain\SCCM\WindowsUpdates\d8b72e39-6103-49fb-b1f6-14e096dd3cd6" ISTR1="STC00187" ISTR2="30" ISTR3="94" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="STC00187"       SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12       2680 (0x0A78)

Failed to take snapshot of one or more contents in package STC00187SMS_DISTRIBUTION_MANAGER               21/04/2015 14:38:12       2680 (0x0A78)

CDistributionSrcSQL::UpdateAvailableVersion PackageID=STC00187, Version=66, Status=2302               SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12       2680 (0x0A78)

STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=oursccmserver.ourdomain SITE=STC PID=3596 TID=2680 GMTDATE=Tue Apr 21 12:38:12.131 2015 ISTR0="DPA - Windows Updates" ISTR1="STC00187" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="STC00187"    SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12       2680 (0x0A78)

Failed to process package STC00187 after 6 retries, will retry 94 more times     SMS_DISTRIBUTION_MANAGER               21/04/2015 14:38:12       2680 (0x0A78)

Exiting package processing thread for package STC00187.          SMS_DISTRIBUTION_MANAGER            21/04/2015 14:38:12              2680 (0x0A78)

Currently using 0 out of 3 allowed package processing threads.              SMS_DISTRIBUTION_MANAGER               21/04/2015 14:38:15       2304 (0x0900)

Jan Hoedt

Hello,

I'm trying to use device collection query to get a list of computers that have a specific software (Application A) not installed on Apr 16. So i would create a criteria with:

Installed application (x64) history > Display Name. Set string to "Application A"
Installed application (x64) history > Installed Date. Set Installed Date to "is no equal to" 20150416.   

When i query the collection it should list all systems with all version of application A not installed on Apr 16. However, it ends up showing only Application A installed on Apr 16.

 Hi,

I would appreciate your input on a design question on App-V 5 on SCCM 2012 R2.

Where we are:

• We have Terminal Servers running with App-V 4.6 Clients for some years. The users on these Terminal Servers could only receive the App-v 4.6 packages (since the terminal server only had the App-V client)
• Some time ago we started the rollout of App-V 5.0 packages to Terminal servers via SCCM 2012 R2.
• In parallel we rolled out some App-V 5.0 clients to Windows 7 machines.

What’s happening:

• Users get App-V package meant for TS (licensed applications which should not end on clients) and they should not

 What we want:

• deploy App-V packages (via SCCM) to W7 computers only, later we will deploy to users but for now our administration system doesn’t cover that
• select which App-V packages to deploy to Windows 10 (when it’s there)
• select which App-V packages to deploy to terminal servers (WKX)
• uninstall of users/computers not in collections anymore
  

ð TTo achieve this we would create different deployment types of an App-v package with each a prereq “W7, Windows 10, Windows terminal services”. Then also we would create an uninstall mechanism (like this http://blogs.technet.com/b/configmgrdogs/archive/2014/11/03/managing-app-v-deployments-in-configmgr-2012.aspx)

Guess that would work, but wonder if you would see any flaws/issuesin/with this setup?

Thanks for your input.

J.

Jan Hoedt

Update: then also I wonder the supersedence within the application (with different deployment types), f.e. 7-Zip on terminal servers should be replaced but not for Windows 7. Would that work?

Hi,

Is there any way you can see which source an App-v package is using? In applications and packages you can easily, in App-v pacakges I just don't see that option. I'd need to know if the pacakge is effectively is using the correct source files.

J.

Jan Hoedt

I am installing an MSI using a task sequence command line.

The program should create an icon in the C:\Users\Public\Desktop folder.

Whenever I run the program without specifying an account (Run this step as the following account) it installs correctly but it does not create the icon.

Whenever I specify the sccm domain account which has full domain administrator rights and access to this folder it fails to install the program at all UNLESS I have logged into the workstation with the sccm account, if I have already logged into the box it runs perfectly and create the icon fine...

Here is the log file of the failing install-

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:33:41.911-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1348" file="instruction.cxx:751">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="16:33:41.911-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="executionenv.cxx:782">
<![LOG[Executing command line: smsswd.exe /run:NDC0002B msiexec /i "Sectra RIS Client 16.1.15 Basic Install.msi" STRSERVERNAME="BCDVTRNRIS01.NIPACS.NET" INSTALLDIR="D:\Program Files (x86)\Sectra\" SPEECH_INSTALL_AS_WINDOWS_SERVICE=1 SPEECH_INI_REMOTE_SERVICE_HOST_NAME="BCDVTRNRIS01.NIPACS.NET" SPEECH_INI_DOWNLOAD_FREQUENCY=180 SPEECH_INI_REMOTE_FILE_TRANSFER_PORT_NUMBER=6005 SPEECH_INI_REMOTE_SERVICE_PORT_NUMBER=6000 SPEECH_INI_UPLOAD_FREQUENCY=30 /qn]LOG]!><time="16:33:41.911-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1348" file="commandline.cpp:827">
<![LOG[[ smsswd.exe ]]LOG]!><time="16:33:41.925-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="main.cpp:289">
<![LOG[PackageID = 'NDC0002B']LOG]!><time="16:33:41.930-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="main.cpp:318">
<![LOG[BaseVar = '', ContinueOnError='']LOG]!><time="16:33:41.930-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="main.cpp:319">
<![LOG[ProgramName = 'msiexec /i "Sectra RIS Client 16.1.15 Basic Install.msi" STRSERVERNAME="BCDVTRNRIS01.NIPACS.NET" INSTALLDIR="D:\Program Files (x86)\Sectra\" SPEECH_INSTALL_AS_WINDOWS_SERVICE=1 SPEECH_INI_REMOTE_SERVICE_HOST_NAME="BCDVTRNRIS01.NIPACS.NET" SPEECH_INI_DOWNLOAD_FREQUENCY=180 SPEECH_INI_REMOTE_FILE_TRANSFER_PORT_NUMBER=6005 SPEECH_INI_REMOTE_SERVICE_PORT_NUMBER=6000 SPEECH_INI_UPLOAD_FREQUENCY=30 /qn']LOG]!><time="16:33:41.930-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="main.cpp:320">
<![LOG[SwdAction = '0001']LOG]!><time="16:33:41.930-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="main.cpp:321">
<![LOG[Getting linked token]LOG]!><time="16:33:41.979-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="runcommandline.cpp:334">
<![LOG[failed to get the linked token information. It may not be available. Error 1312]LOG]!><time="16:33:41.979-60" date="04-13-2015" component="InstallSoftware" context="" type="2" thread="652" file="runcommandline.cpp:341">
<![LOG[ResolveSource flags: 0x00000000]LOG]!><time="16:33:42.113-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="resolvesource.cpp:3201">
<![LOG[SMSTSPersistContent: . The content for package NDC0002B will be persisted]LOG]!><time="16:33:42.113-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="resolvesource.cpp:3212">
<![LOG[Resolved source to 'F:\_SMSTaskSequence\Packages\NDC0002B']LOG]!><time="16:33:42.113-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="runcommandline.cpp:453">
<![LOG[Working dir 'F:\_SMSTaskSequence\Packages\NDC0002B']LOG]!><time="16:33:42.113-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="runcommandline.cpp:546">
<![LOG[Executing command line: Run command line]LOG]!><time="16:33:42.113-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="commandline.cpp:827">
<![LOG[Process completed with exit code 1603]LOG]!><time="16:33:42.647-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="commandline.cpp:1123">
<![LOG[Command line returned 1603]LOG]!><time="16:33:42.647-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="652" file="runcommandline.cpp:569">
<![LOG[Process completed with exit code 1603]LOG]!><time="16:33:42.663-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1348" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:33:42.664-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1348" file="instruction.cxx:804">
<![LOG[Failed to run the action: Install RIS Basic Install.
Fatal error during installation. (Error: 00000643; Source: Windows)]LOG]!><time="16:33:42.664-60" date="04-13-2015" component="TSManager" context="" type="3" thread="1348" file="instruction.cxx:895">
<![LOG[Set authenticator in transport]LOG]!><time="16:33:42.665-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=1603]LOG]!><time="16:33:42.831-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="16:33:42.832-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="16:33:42.832-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="executionenv.cxx:807">
<![LOG[Let the parent group (RIS 16.1.15 Install) decides whether to continue execution]LOG]!><time="16:33:42.837-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1348" file="instruction.cxx:1004">
<![LOG[The execution of the group (RIS 16.1.15 Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="16:33:42.839-60" date="04-13-2015" component="TSManager" context="" type="3" thread="1348" file="instruction.cxx:217">
<![LOG[Failed to run the last action: Install RIS Basic Install. Execution of task sequence failed.
Fatal error during installation. (Error: 00000643; Source: Windows)]LOG]!><time="16:33:42.839-60" date="04-13-2015" component="TSManager" context="" type="3" thread="1348" file="engine.cxx:213">

And this is the log of a successful install-

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:43:46.776-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1440" file="instruction.cxx:751">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="16:43:46.776-60" date="04-13-2015" component="TSManager" context="" type="0" thread="1440" file="executionenv.cxx:782">
<![LOG[Executing command line: smsswd.exe /run:NDC0002B msiexec /i "Sectra RIS Client 16.1.15 Full Configuration UK.msi" /qn]LOG]!><time="16:43:46.776-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1440" file="commandline.cpp:827">
<![LOG[[ smsswd.exe ]]LOG]!><time="16:43:46.787-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="main.cpp:289">
<![LOG[PackageID = 'NDC0002B']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="main.cpp:318">
<![LOG[BaseVar = '', ContinueOnError='']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="main.cpp:319">
<![LOG[ProgramName = 'msiexec /i "Sectra RIS Client 16.1.15 Full Configuration UK.msi" /qn']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="main.cpp:320">
<![LOG[SwdAction = '0001']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="main.cpp:321">
<![LOG[ResolveSource flags: 0x00000000]LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="resolvesource.cpp:3201">
<![LOG[SMSTSPersistContent: . The content for package NDC0002B will be persisted]LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="resolvesource.cpp:3212">
<![LOG[Resolved source to 'F:\_SMSTaskSequence\Packages\NDC0002B']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="runcommandline.cpp:453">
<![LOG[Working dir 'F:\_SMSTaskSequence\Packages\NDC0002B']LOG]!><time="16:43:46.792-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="runcommandline.cpp:546">
<![LOG[Executing command line: Run command line]LOG]!><time="16:43:46.793-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="commandline.cpp:827">
<![LOG[Process completed with exit code 0]LOG]!><time="16:43:47.112-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="commandline.cpp:1123">
<![LOG[Command line returned 0]LOG]!><time="16:43:47.112-60" date="04-13-2015" component="InstallSoftware" context="" type="1" thread="1968" file="runcommandline.cpp:569">
<![LOG[Process completed with exit code 0]LOG]!><time="16:43:47.113-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1440" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:43:47.113-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1440" file="instruction.cxx:804">
<![LOG[Successfully completed the action (Install RIS Full Configuration) with the exit win32 code 0]LOG]!><time="16:43:47.113-60" date="04-13-2015" component="TSManager" context="" type="1" thread="1440" file="instruction.cxx:830">
<![LOG[Set authenticator in transport]LOG]!>

Any ideas?

Hi,

We are working with packages a long time now on SCCM 2012 R2. We started deploying App-V packages + uninstall of App-v packages with SCCM since no automatic uninstall occurs.
Does the same mechanism apply for regular applications? So iow: you need to deploy an uninstall for an application in order to make it uninstall when a user isn't member of a group we deploy it to?

J.

What are design would be, f.e. 7-Zip:

Application 7 Zip - INSTALL:
*Deployment Type App-V 7-Zip Install (prereq Windows 7)
*Deployment Type APp-V 7-Zip Install (prereq Windows Server) => in order to control wether or not to deploy to server
*Deployment Type MSI 7-Zip Install (prereq Windows 7) => since we only want to deploy App-v packages to servers

Application 7-Zip UNINSTALL:
*Deployment Type App-V 7-Zip Uninstall (prereq Windows 7)
*Deployment Type APp-V 7-Zip Uninstall (prereq Windows Server) => in order to control wether or not to uninstall to server
*Deployment Type MSI 7-Zip Uninstall (prereq Windows 7) => since we only want to deploy App-v packages to servers

Jan Hoedt

Hi,

trying to deploy a ModernUI LOB App with Config Manager 2012. After downloading the content to ccmcache, installation starts and ends up with error message 0x80073CF9.

------------------------------------------------------------------------------------------------------------------------------------------------------

AppDiscovery.log:

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5" AND Revision = 1)"AppDiscovery23.04.2015 14:01:116148 (0x1804)
    Performing detection of app deployment type SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5, revision 1) for user.AppDiscovery23.04.2015 14:01:116148 (0x1804)
Working with Package: 0bbc1bc5-a8eb-4bc0-9fbe-2a6141b7c835_2015.416.1305.4090_neutral_~_vv150cwvqh76cAppDiscovery23.04.2015 14:01:116148 (0x1804)
+++ Application NOT Discovered [AppDT Id: ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5, Revision: 1]AppDiscovery23.04.2015 14:01:126148 (0x1804)
+++ Did not detect app deployment type SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5, revision 1) for S-1-5-21-2924055433-2284826678-407803137-85917.AppDiscovery23.04.2015 14:01:126148 (0x1804)
   ActionType - Install will use Content Id: Content_c458dc52-e321-40be-ab2f-a4599c387c7b + Content Version: 1 for AppDT "SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)" [ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5], Revision - 1AppDiscovery23.04.2015 14:01:136148 (0x1804)
   ActionType - Install will use Content Id: Content_c458dc52-e321-40be-ab2f-a4599c387c7b + Content Version: 1 for AppDT "SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)" [ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5], Revision - 1AppDiscovery23.04.2015 14:01:136148 (0x1804)
Method EnforceApp failed with error 80073CF9 AppDiscovery23.04.2015 14:01:156148 (0x1804)
CAppProvider::ExecMethodAsync failed. Error 80073cf9AppDiscovery23.04.2015 14:01:156148 (0x1804)

---------------------------------------------------------------------------------------------------------------------------------------------------

CITaskMgr.log

Initiating task ContentDownload for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1 (SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)) for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer: {9C03F93F-11ED-4E9A-B3C0-C2CB8F056002} CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Initiating content download : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.ContentDownload)CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Contents already available.CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Contents download already in Success state : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.ContentDownload)CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
State transition to (Success), Param(0) : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.ContentDownload)CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
State transition to (Success), Param(0) : CTaskConsumer(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.{3C50E03E-1849-4371-820E-695BD2986F91})CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Already completed state (Success) : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.ContentDownload)CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Release task ContentDownload for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {9C03F93F-11ED-4E9A-B3C0-C2CB8F056002}CITaskMgr23.04.2015 14:01:136616 (0x19D8)
Release task ContentDownload for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/Application_0e314ec1-b991-4c77-a980-58183b18d83f.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {A542B598-30EC-4690-A462-4EA1958EA7C6}CITaskMgr23.04.2015 14:01:136616 (0x19D8)
Release task ContentDownload for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/RequiredApplication_0e314ec1-b991-4c77-a980-58183b18d83f.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {F0354997-44B3-428F-9F46-2D7FF9EE5933}CITaskMgr23.04.2015 14:01:136616 (0x19D8)
Initiating task Enforce for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1 (SicherUndWeg.Windows - Windows app package (*.appx, *.appxbundle)) for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer: {0FC6DA00-8B41-458A-BDF2-130128CAFF57} CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Submitted new MTC request 0a4ea4a5-a0b6-4c41-95a4-0f89861f545fCITaskMgr23.04.2015 14:01:136940 (0x1B1C)
State transition to (WaitSerialize), Param(0) : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
State transition to (WaitSerialize), Param(0) : CTaskConsumer(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.{3C50E03E-1849-4371-820E-695BD2986F91})CITaskMgr23.04.2015 14:01:136940 (0x1B1C)
Sending ack to MTC for task 0a4ea4a5-a0b6-4c41-95a4-0f89861f545fCITaskMgr23.04.2015 14:01:136604 (0x19CC)
Starting Enforcement : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:136604 (0x19CC)
Initiated application enforcement. : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:136604 (0x19CC)
State transition to (InProgress), Param(0) : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:136604 (0x19CC)
State transition to (InProgress), Param(0) : CTaskConsumer(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.{3C50E03E-1849-4371-820E-695BD2986F91})CITaskMgr23.04.2015 14:01:136604 (0x19CC)
Application enforcement completed : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:159060 (0x2364)
Enforcement completion state Failure : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:159060 (0x2364)
State transition to (Failure), Error(0x80073cf9) : CITask(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.S-1-5-21-2924055433-2284826678-407803137-85917.Install.Enforce)CITaskMgr23.04.2015 14:01:159060 (0x2364)
State transition to (Failure), Param(-2147009287) : CTaskConsumer(ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1.{3C50E03E-1849-4371-820E-695BD2986F91})CITaskMgr23.04.2015 14:01:159060 (0x2364)
Active enforcement task with MTC Id 0a4ea4a5-a0b6-4c41-95a4-0f89861f545f not foundCITaskMgr23.04.2015 14:01:155632 (0x1600)
Release task Enforce for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/DeploymentType_3838926b-1593-41aa-bec7-f57b8df37ee5.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {0FC6DA00-8B41-458A-BDF2-130128CAFF57}CITaskMgr23.04.2015 14:01:152972 (0x0B9C)
Release task Enforce for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/Application_0e314ec1-b991-4c77-a980-58183b18d83f.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {550FED48-B73A-4CDA-9CCD-895F4A39BE60}CITaskMgr23.04.2015 14:01:152972 (0x0B9C)
Release task Enforce for CI ScopeId_11FA4582-378A-44FF-ADF8-174A38635DF5/RequiredApplication_0e314ec1-b991-4c77-a980-58183b18d83f.1 for target: S-1-5-21-2924055433-2284826678-407803137-85917, consumer {C47690C7-AD25-496D-9880-96439013C199}CITaskMgr23.04.2015 14:01:152972 (0x0B9C)

-------------------

Any Ideas?

Hi all,

I feel like I'm missing something obvious here, but I've been trying to find out where this information is stored.  Say I have package "PE123456" - is there an easy way to locate where this is stored within the ccmcache directory? 

I've come across some logs that occasionally, but not always, store this information (I believe cas.log lists it, but not consistently - I'm not sure of when it does/doesn't). I've been playing with the Roger Zander's smsclictr.automation.dll within Powershell to try to retrieve this information, but have had no luck so far (although I have managed to query and retrieve all the machine's advertisements, it does not return the path to the package themselves).

Assume I do not have access to the configmgr console for this task.

Thanks

Monitoring of an application tells me that the installation was successful, but after a while, the same monitoring tells me that the installation that was successful now got a lot of errors.

This is the monitoring windows telling me that Elements have a compliance % of 57,1, and it was about 98-99%...

As you can see, I’ve got 92 clients that are successful and 69 errors, which is wrong…

And the correct amount of errors are 2 computers that failed.

I’ve checked some of the computers that get this deployment, and who is not located in the successful status, and they all got Elemets installed.

Why do I get all these errors when the installation is successful?
I find it very strange that its random which computers that report successful, and after a while then reports error(but nothing is logged in the error log…)

Hi everyone. I am using SCCM 2012 R2 CU2 on a Windows Server 2008 R2 Standard. I am having an issue with a Task sequence seeming not beeing able to complete a "Restart Computer" Task. Some Clients get stuck at the shutdown - after a built-in reboot was initialized - at the message "stop Services".

After days of log-watching and googling I finally decided to ask that question. I can't find an accordance between the Clients except a message out of the statusmessagedetails telling me that a component triggered an exception which couldn't be processed, SOURCE advanced Client ("Agent got terminated immediately")

Componentname: UnknownModule

Client-Version: different, some older, some latest.

The next entry is that the TSMGR could not execute a tasksequence successfully - unknown Interface. I think that happens when relevant wmi-services already got stopped and the Agent could not finalize the reboot command. I could not read out any Information out of the Event logs.

Scenario: Maintenance Window is configured from 12 to 5 am. Mostly around 12:15 am starting the maintenance TS running a script forcing a check for latest Windows Updates via WSUS, rebooting the Client, checking Client configuration and so on. No Problem on Clients with no other deployments. Mostly These machines have a second or a third deployment in the Queue.

Here is a cut from the SMSTS.log of an affected machine:

Start executing the command line: smsboot.exe /target:HD TSManager 29.01.2015 00:18:50 884 (0x0374)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2015 00:18:50 884 (0x0374)
Expand a string: WinPEandFullOS TSManager 29.01.2015 00:18:50 884 (0x0374)
Executing command line: smsboot.exe /target:HD TSManager 29.01.2015 00:18:50 884 (0x0374)
Creation event received for process 4548 mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
========================= [ smsboot.exe ] ========================= Reboot 29.01.2015 00:18:50 3984 (0x0F90)
SMSTSRebootDelay=1 Reboot 29.01.2015 00:18:50 3984 (0x0F90)
SMSTSRebootMessage=Initiating system reboot Reboot 29.01.2015 00:18:50 3984 (0x0F90)
SMSTSRebootRequested=HD Reboot 29.01.2015 00:18:50 3984 (0x0F90)
Process completed with exit code 0 TSManager 29.01.2015 00:18:50 884 (0x0374)
Unable to collect process information as process has terminated mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
No usage will be tracked for process 4548, as failed to get owner info or executable file name 80004005 mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
Termination event received for process 4548 mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
No active process found with ID 4548 mtrmgr 29.01.2015 00:18:50 4552 (0x11C8)
!--------------------------------------------------------------------------------------------! TSManager 29.01.2015 00:18:50 884 (0x0374)
Successfully completed the action (Reboot Client before Update) with the exit win32 code 0 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set authenticator in transport TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 29.01.2015 00:18:50 884 (0x0374)
Clear local default environment TSManager 29.01.2015 00:18:50 884 (0x0374)
Updated security on object C:\_SMSTaskSequence. TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a TS execution environment variable _SMSTSNextInstructionPointer=8 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSInstructionStackString=0 6 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a TS execution environment variable _SMSTSInstructionStackString=0 6 TSManager 29.01.2015 00:18:50 884 (0x0374)
Save the current environment block TSManager 29.01.2015 00:18:50 884 (0x0374)
Executing command line: "bcdedit.exe" TSManager 29.01.2015 00:18:50 884 (0x0374)
Creation event received for process 4124 mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
Unable to collect process information as process has terminated mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
Process completed with exit code 0 TSManager 29.01.2015 00:18:50 884 (0x0374)
No usage will be tracked for process 4124, as failed to get owner info or executable file name 80004005 mtrmgr 29.01.201500:18:50 1816 (0x0718)
Termination event received for process 4124 mtrmgr 29.01.2015 00:18:50 1816 (0x0718)
No active process found with ID 4124 mtrmgr 29.01.2015 00:18:50 4552 (0x11C8)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 29.01.2015 00:18:50 884 (0x0374)
Updated security on object C:\_SMSTaskSequence. TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a TS execution environment variable _SMSTSNextInstructionPointer=8 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a global environment variable _SMSTSInstructionStackString=0 6 TSManager 29.01.2015 00:18:50 884 (0x0374)
Set a TS execution environment variable _SMSTSInstructionStackString=0 6 TSManager 29.01.2015 00:18:50 884 (0x0374)
Save the current environment block TSManager 29.01.2015 00:18:50 884 (0x0374)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 29.01.2015 00:18:50 884 (0x0374)
Error executing InitiateSystemShutdownEx(). Code 0x800706b5 TSManager 29.01.2015 00:18:50 884 (0x0374)
Failed to initiate a system reboot. Error code 0x800706b5 TSManager 29.01.2015 00:18:50 884 (0x0374)
Failed to reboot the system. Error 0x(800706b5) TSManager 29.01.2015 00:18:50 884 (0x0374)
Failed to initialize a system reboot.
The interface is unknown. (Error: 800706B5; Source: Windows) TSManager 29.01.2015 00:18:50 884 (0x0374)
Fatal error is returned in check for reboot request of the action (Reboot Client before Update).
The interface is unknown. (Error: 800706B5; Source: Windows) TSManager 29.01.2015 00:18:50 884 (0x0374)
An error (0x800706b5) is encountered in execution of the task sequence TSManager 29.01.2015 00:18:50 884 (0x0374)
Set authenticator in transport TSManager 29.01.2015 00:18:50 884 (0x0374)
Task Sequence Engine failed! Code: 800706B5 TSManager 29.01.2015 00:18:51 884 (0x0374)
**************************************************************************** TSManager 29.01.2015 00:18:51 884 (0x0374)
Task sequence execution failed with error code 800706B5 TSManager 29.01.2015 00:18:51 884 (0x0374)
Cleaning Up. TSManager 29.01.2015 00:18:51 884 (0x0374)
Removing Authenticator TSManager 29.01.2015 00:18:51 884 (0x0374)
Cleaning up task sequence folder TSManager 29.01.2015 00:18:51 884 (0x0374)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 29.01.2015 00:18:51 884 (0x0374)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 29.01.2015 00:18:51 884 (0x0374)
SetNamedSecurityInfo() failed. TSManager 29.01.2015 00:18:51 884 (0x0374)
SetObjectOwner() failed. 0x80070005. TSManager 29.01.2015 00:18:51 884 (0x0374)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 29.01.2015 00:18:51 884 (0x0374)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 29.01.2015 00:18:51 884 (0x0374)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 29.01.2015 00:18:51 884 (0x0374)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 29.01.2015 00:18:51 884 (0x0374)
Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister TSManager 29.01.2015 00:18:51 884 (0x0374)

Does anyone have expirience with that issue? Thanks in advance!

I tried to search the solution , But I couldn't but I saw lot of posts the same issue in different blogs /forums . 

If any one / MVP's can give the solution for this issue. 

For your reference below two links for problem which i am taking 

https://social.technet.microsoft.com/Forums/en-US/5ad3d7d4-2a87-473d-8c9d-41ad100e134a/random-client-failures-ccmexecexe-exception-code-0xeeeefffe?forum=configmanagergeneral#30791e92-6dc3-4466-9e07-bc2552e6aa3b

http://www.networksteve.com/enterprise/topic.php/Configuration_Manager_2012_Agent_Crashing_-_Faulting_Application/?TopicId=67828&Posts=0

Really appreciate for your help in Advance.............!

Best Regard's Krishna

Good Afternoon!

In need of some assistance from you more experienced SCCM admins. Let me quickly run down the steps of what I've done:

1) Created a network share for CRM 2015 that everyone can see
2) Ran the EXE from Microsoft and followed the instructions from them to create the CrmClient_32.msi 
3) In SCCM, created a new application, and linked the shared folder. SCCM auto-populated the install command, publisher data, etc. The only thing I added was "/s" for the MSI package to install

4) Created a Device Collection with one test PC that already has CRM 2013 installed

5) Deployed the application to the device collection with the following options:

Under Content Tab:

Content Location: \\networkshare\Installs\CRM2015
Persist content in the client cache is NOT checked
Allow clients to share content with other clients on the same subnet IS checked
Deployment options: Do not download content

Under the Programs Tab:

Installation program: msiexec /i /s "CrmClient_32.msi"
Installation start in: blank
Uninstall program: msiexec /x 

Run installation and uninstall program as 32-bit process on 64-bit clients IS checked

Under User Experience Tab:

Installation Behavior: Install for system
Logon requirement: Whether or not a user is logged on
Installation program "margin-bottom:9px;padding-right:0px;padding-font-family:Arial, Helvetica, sans-serif;font-size:14px;line-height:21px;word-wrap:break-word;color:#333333;">Maximum allowed run time ( 120 minutes)
Estimated installation time (0 minutes)

6) I schedule the install (for most applications I've seen this works best)

Now when I go to Monitoring, all I see is the deployment is "In Progress" and the category is "Waiting for content" 

I'm frustrated because I don't understand why this won't work. It seems so painless and the method I've described above works for almost any other application I've pushed out.

I'm all ears - is there anything you see that isn't correct? Any ideas or suggestions? If you've successfully pushed out CRM 2015 some how (even if it's not through SCCM), could you please share your solution?

Thank you so much! -Nick

Hi all,

I'm struggling to deploy virtual application via ‘Application Catalog’ in lab environment, it fails with error ‘Application installation not started, There was a problem starting the application installation on your computer’ ,  not sure for reason of failure but I can see some errors inConfigMgrSoftwareCatalog.log... logs as below..

--------

[1][01/28/2013 18:09:23] :RTMWindowsClient.EvaluateScriptAndLog:Script function 'PollCDRSDKMethod' returned '1,16'
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.PollCDRSDKMethod:Polling method returned 1,16
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.InstallAppProgression-Error:The call to poll CDR SDK method failed with status of 16
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.UpdatePageView:PageViewMode changed to:FastInstallError
[1][01/28/2013 18:09:24] :FastInstallPageView:Create Page View FastInstallError
[1][01/28/2013 18:14:44] :PortalContext.NotifyShortcutReceived:Keyboard shortcut Shift
[1][01/28/2013 18:14:44] :PortalContext.HandleEventOnDemand:begin handling ShortcutReceived

---------

Please advise

Hello!

Whenever i delete a Deployment from a collection, it doesn't get deleted out of the clients Softwarecenter. The Application is still visible on the client and if I click the button to install it, I get an error telling me that the Softwarecenter can't update the needed Information.

i've already tried to reinstall the Client. This removes all old (deleted) deployments from the softwarecenter, but as soon as i deploy an aplication and then delete the deployment I get the same Error again.

Has anyone experienced something like this before?

Thanks in advance!

Hello,

We've created Server Driver Package (Dell Power Edge) using SCCM2012 from a console available at Unique server location (Not the usual one)

Now after creating this, we replicated it to all our DP's, It got replicated as well, but looking at the size column under the content status, it showing size as Zero MB.

But checking at source location, this driver package has size = 42.9MB

Now why it behaves like this i am not sure. This is something i am doing first time, and all our Server installation has stopped right now. Is this because of any permission I am not having on a console available at Unique server location or something else? 

What share and NTFS permissions must I give users to deploy software through SCCM? I have one folder with all of the applications and would like to know.

Thanks

James A+, Network+, MCP

James A+, Network+, MCP

I need to run multiple steps to deploy an desktop emergency alert system. The software requires an install via MSI with specific switches. Then I need to stop start/start a service. Then I need to add a batch file to everybody's start folder.

I'm real weak at scripting.

Is there a simple way to do multiple steps for an app deployment?