I'm new to SCCM and have successfuly installed it in a lab enviorment.

I've been researching the possibility of deploy application/packages to a specific computer.

This possibility does not exist!!! Or am I wrong?

Hi All,

After I solve the cause of a failure for a failed deployment, is there a better way to retry the deployment?

Currently, I am doing the steps below to speed up the retrying:

1. update content of the package so that the revision changes

2. run Application Deployment Evaluation Cycle action on client

Any suggestion would be appreciated

Hi,

We are trying to deploy KB3020369-x64 and KB3125574-x64 via SCCM.

I tried creating the package 3 X different ways but both comes up with this error 0x80070001 (-2147024895)

1st Way - Created application as with script installer(Technology)->Content Location as FQDN location->wusa.exe "Windows6.1-KB3020369-x64.msu" /quiet /norestart 

2nd Way - Created application as with script installer(Technology)->Content Location as FQDN location->c:\windows\system32\wusa.exe "Windows6.1-KB3020369-x64.msu" /quiet /norestart

3rd Way - Created application as with MSI installer(Technology)->Content Location as FQDN location->wusa.exe "Windows6.1-KB3020369-x64.msu" /quiet /norestart

All 3 ways received the same error.

I can't deploy this package via Software Update feature of SCCM(Long story so please don't ask) so I need to deploy it as an application or package. Please assist

Hi,

Is it posable to detect the installation of MSU files(KB3125574 and KB3020369) via File System or Registry in SCCM 2012?

I tried the following VB Script which didn't work and cannot use Powershell (Not allowed to change PowerShell execution policy to anything other than "All Signed" )

If you look at the results for a specific DTCI in the results of the function fn_AppDeploymentAssetDetails(1033), you'll notice the 'Start Time' is always the same for the collection in question. If you've created more than one deployment off that deployment type, you can have more than one Start Time, but it will be the same for every deployment event on record that happened due to membership in that collection.

Despite that, a MachineName is returned and details are provided about the status of the deployment per-device. In fact, if more than one deployment occurred against that device, it will show up twice (or however many deployments of that DTCI occurred).

Based on this, can I use any of the data from the query to link to a 'time of deployment' against a specific device - that is, when that client received a notification about the available package, downloaded it, installed it, and returned a status code that indicated the result of the installation? I've already got the result code, but a 'begin time' would be nice. 'Begin time' (client acknowledges package available) + 'finish time' (time installation of package complete), to take into account maintenance windows, would be ideal.

I'm aware I need to go off and query other tables, views or functions for this, but given the number of columns with GUID's and ID's returned by this function, I'm sure some of them could be used to link to whatever table holds the time data.

I might perhaps have to wade into the message tables (link to an example of where tables of status messages are used to find data) for this?

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

My organization primarily uses Application Catalog for users to self service themselves... (service desk installed a licensed program last year to 3500 computers by accident by adding one collection to another, so we are now self service and use the Application catalog for 99% of installs,  we have basically moved away from computer based collections and utilize the Application Catalog for all software) 

 I have users in my environment that have SO many different versions of Java for legacy software and installing the new one does not uninstall some of the other versions of Java thus  there is a conflict on the system.  I have the all the installs published for all different versions that are out in the field in the Application Catalog AND I have a script that uninstalls all versions of Java so that they can uninstall the wrong ones and then go back and install the ones that they know they need after.

I use a script to run the uninstalls, then have it echo out a file and the detection method sees the file and congratulates the program and declares it a success. BUT users want the ability to uninstall and reinstall without contact service desk to be able to re-run it - the file already exists and can not be ran again... thinks it is already completed.

how do I get the system to be able to re-run an application so that the APPLICATION can run several times when launched from Application Catalog to suit the users needs.  I don't want to keep adding computer to collection or having user contact the service desk to delete the detection file so that it can be ran again...

i.e. user uninstalls Java, installs correct verstion for what they need today - run the uninstall application again, then run the other version of Java they want tomorrow.

is there a way SCCM  to detect that program is uninstalled and pass the success back to the console to say that the program is a success? or any other method so that the application can be ran - sometimes MULTIPLE times just like this Java application?

Hi,

I have an issue deploying SQL through SCCM.  My detection method is to check the registry for version number.

Current I check : SOFTWARE\Microsoft\Microsoft SQL Server\110\SQLServer2012\CurrentVersion

Version

11.0.2100.60

I have a separate package for SP3 and I check for version 11.3.6020.0

The problem I have is when SP3 installs it thinks the original package is not present.  I package different service packs separately as the user choose what service pack they need to replicate the environment they are building.

I have the same problem with SQL14

Whats a better method of detection for SQL?

Hi,

This is the scenario. 

Through Application Deployment, I want to deploy a script/command that will uninstall Adobe Reader prior to installation of Adobe Acrobat.  I am stumped on the "Detection Method" part.  It says, "Specify how Config Manager determines whether this deployment type is already present on a device..." - But I am trying to do the opposite.  I want to issue this uninstall command if Adobe Reader is present. So the Detection Method is not applicable on my scenario.

The detection method basically says, "If your computer has Adobe Reader then it won't install this program because it is already satisfied..." but what I am trying to do is, "Uninstall Adobe Reader if Adobe Reader is detected." Instead of "Don't Run This is program if Adobe Reader is already detected" - which what the Detection Method is for.

Does it mean that it would be best to just use "Package Deployment" instead of Application Deployment in this case?

Thanks!

I'm running an application that is getting an immediate error of 0x87DD0213(-2016411117) Timeout occurred. The application is set to uninstall the x64 version of Office 2010 or 2013 and then install Office 2010.

-Installation program command is: setup.exe /qn /norestart

-Also tried running with the msp as command line: Setup.exe /adminfile Officex86.msp (Once again, this install has had no issues in the past.)

-Detection Method is checking for Microsoft Office folder in Program Files.

-Requirements is looking for Windows 7.

-Dependencies is scrubbing off Office 2013 or 2010 x64(Scrubs we've used with no issue before).

I have it set to a maximum allowed run time of 120 by standards and it immediate returns a timeout.. and when I say immediately, I mean in the time it takes me to change from the deployment being sent to the monitoring screen.

-My Collection is populating fine from an AD group.

Any ideas?

I know how to setup AppX Apps for offline deployment via SCCM, setting up Dependencies folders for frameworks etc.

However I have an App that also requires metadata files in ProgramData before installation. In a batch file for manual install (or MDT deployment) I just have a copy line which targets C:\ProgramData\Microsoft\Windows\DeviceMetadataStore\en-US.

However this doesn't seem like the solution for SCCM Application Deployments. Is there some extra tweak required in the Application or do I need to setup some clunky file copy somewhere?

Hi,

I’d need to have a csv of all computers and all software on them in my SCCM 2012. Please advise howto approach.

J.

Jan Hoedt

I've a batch script that uninstall an application perfectly fine when i run it locally on the system. the script contains few msi switches only nothing else.

When i try to deploy this .bat as a package or application using SCCM it does not get deployed. I want this scrip to be deployed on the clients and execute silently so that the required application can be uninstalled silently.

Silent parameters are already passed in batch script. Can any one please help me here?

Hi,

Just wanted to recap why clients become inactive. It's a combination of

• Heartbeats
• System Discovery
• Network Discovery

We have

Hearbeat: 1 week
Network: we don't enable this
System Discovery: we don't have this enabled

So how to make the math again: when a system will be inactive, after 1 week (or are there other factors involved)?
Note: we have no deletion rule in site maintenance activated (yet).

J.

Jan Hoedt

Good Morning Guys,

I'm currently looking into deploying Intel SCS with my SCCM 2012 R2 environment.  I've gone through all the steps mentioned in this guide (Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU ) and have got to the stage where I'm running the various Task Sequences.  I can run the first one which is Intel SCS Platform Discovery, which runs fine, but when I get to the second stage, which is Intel AMT Discovery, it errors out.  There's nothing wrong with the task sequence through SCCM, as it's running the discover.bat file without problem, but when it's running that file, it fails.

Below are the SystemDiscovery logs from the workstation. 

I have not been able to find anything online about this error and haven't been able to see anyone who is having the same problem as I am.  Any help would be greatly appreciated.

2016-07-13 16:31:06: Thread:3388(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:31:06

2016-07-13 16:31:06: Thread:3388(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:31:06: Thread:3388(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:31:06: Thread:3388(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:31:06: Thread:3388(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:31:06: Thread:3388(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:31:31: Thread:3128(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:31:31

2016-07-13 16:31:31: Thread:3128(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:31:31: Thread:3128(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:31:31: Thread:3128(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:31:31: Thread:3128(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:31:31: Thread:3128(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:32:10: Thread:2320(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:32:10

2016-07-13 16:32:10: Thread:2320(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:32:10: Thread:2320(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:32:10: Thread:2320(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:32:10: Thread:2320(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:32:10: Thread:2320(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:41:58: Thread:3796(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:41:58

2016-07-13 16:41:58: Thread:3796(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:41:58: Thread:3796(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:41:58: Thread:3796(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:41:59: Thread:3796(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:41:59: Thread:3796(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:52:14: Thread:3748(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:52:14

2016-07-13 16:52:14: Thread:3748(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:52:14: Thread:3748(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:52:14: Thread:3748(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:52:14: Thread:3748(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:52:14: Thread:3748(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:54:17: Thread:3332(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:54:17

2016-07-13 16:54:17: Thread:3332(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:54:17: Thread:3332(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:54:17: Thread:3332(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:54:17: Thread:3332(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:54:17: Thread:3332(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-14 08:23:07: Thread:2448(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-14 08:23:07

2016-07-14 08:23:07: Thread:2448(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-14 08:23:07: Thread:2448(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-14 08:23:07: Thread:2448(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-14 08:23:07: Thread:2448(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-14 08:23:07: Thread:2448(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

Hello Folks,

Few software getting too delay to arrive in Software center post OS build, the same laptops when we had install windows 7 , the same applications arriving very quick. What would be the case.

KMI

Please click answer If it works Thanks KMI

Hi,

I have a HTA file that i need to run in sccm. I created a package and set the option "Allow users to intecact with this program" I need that option as the HTA file need user input. It works perfectly on Windows 7, but on Windows 8.1 and Windows 10 i do not get the HTA window. It just runs for a second and then just show as installed.

No log files show any indication of the problem.

Your assistance would be greatly assisted.

computer hangs during install of software/uninstall also

using windows 10

Install it hangs at 0% or 1%, has to be killed in task mnager

also, trying to uninstall software hangs same way.

WHY does this happen and can someone help me fix this??

Hi All,

I am migrating a SCCM2007 implementation to a SCCM 012 implementation.

A few things are OK, thanks! but i get an issue with package deployment when a User Group is the target. And I migrated a lot of deployments based on User Groups...

So, to troubleshoot, this is what I did:

If I use a collection, based on a direct rule targetting a user, this user is found and can use the application catalog web page to run the installation.

BUT, if i use a collection, based on direct or query rule targetting a User Group, nothing is found, and the application catalog stays empty.

Anyone to help me?

Dear SCCM folks,

I have been pulling my hair our for 3 hours trying to get SCCM2012 RTM to detect whether or not VB6 SP6 is installed on a machine.

For that, I have decided to check the file version of VB6.exe for a certain value.

However, the installation always fails with the application not being detected after the setup.

Here is what the dialog is set to:

I have tried unchecking the 32/64 checkbox, and hardcoding the path to C:\Program Files (x86)\... and neither helped.

I have then tried a custom powershell script which failed because it wasn't signed.

Also, I couldn't locate any documentation about the detection methods in general, such as what values would be expected (i.,e. date format for file modified date, or what "between" means in terms of version number - Is 6.0.7 between 6 and 6.1 for example?).

The AppEnforce.log shows nothing useful either (such as actual path checked, version determined, etc):

<![LOG[    Performing detection of app deployment type Scripted(ScopeId_11524E4C-BC98-4E7A-8289-0AECA6C31D3A/DeploymentType_c92589fa-9f69-463c-804a-f1fc993be36e, revision 9) for system.]LOG]!><time="16:33:17.010+00" date="06-15-2012" component="AppEnforce" context="" type="1" thread="2680" file="appprovider.cpp:2064"><![LOG[+++ Application not discovered. [AppDT Id: ScopeId_11524E4C-BC98-4E7A-8289-0AECA6C31D3A/DeploymentType_c92589fa-9f69-463c-804a-f1fc993be36e, Revision: 9]]LOG]!><time="16:33:17.069+00" date="06-15-2012" component="AppEnforce" context="" type="1" thread="2680" file="localapphandler.cpp:291"><![LOG[++++++ App enforcement completed (4 seconds) for App DT "Scripted" [ScopeId_11524E4C-BC98-4E7A-8289-0AECA6C31D3A/DeploymentType_c92589fa-9f69-463c-804a-f1fc993be36e], Revision: 9, User SID: ] ++++++]LOG]!><time="16:33:17.071+00" date="06-15-2012" component="AppEnforce" context="" type="1" thread="2680" file="appprovider.cpp:2345">

Is it possible to increase the AppEnforce logging to maximum to see what values are being compared and which files checked?

Please, could anybody tell me what I'm doing wrong here? I can't for the life of me figure out what else I should try, or what log file would yield useful information.