Search the Community

I'm trying to use a PowerShell script to verify the installation of an application deployment, but so far it hasn't worked well. I've never had any issues with the detection rules, but I'm quite new to SCCM, and this is the first time I'm using PowerShell to do it. The application is deployed to computers, it is installed for system, and whether the user is logged in or not (although I've been logged in for the most part I've attempted to solve this). The detection script works fine when run manually; it does some checks and then if it succeeds it runs Write-Host 'Installed', and as far as I've understood it, that's all it should take. I've tried a couple other things, like using return, just in case I misunderstood, but this doesn't seem to be the issue. I have tried to change the execution policy on the client computers. The value is stored in the HKLM so I assume it's not context related with regards to user, unless there's some special execution policy for SCCM. I have, just in case, tried to sign the detection method script as well, with no luck (I used open when fetching the script instead of pasting it in the text field, to be clear). The following error (currently) shows up even if I set execution policy to unrestricted, and regardless of whether the script is signed or not. It should be noted that I haven't had any issues with the installation script for the very same application, which is also a PowerShell script. AppIntent.log: <![LOG[ScopeId_54761859-29CE-43B8-9BEE-B88049CB81CB/DeploymentType_d02b19f5-fc3c-4474-a737-f60fc632dfb7/24 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = MySoftware]LOG]!><time="10:01:30.360-120" date="09-24-2015" component="AppIntentEval" context="" type="1" thread="4068" file="appconstructs.cpp:2357"> <![LOG[ScopeId_54761859-29CE-43B8-9BEE-B88049CB81CB/Application_8aa515e3-1cb7-401d-8b54-8d80ea8253d9/37 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = MySoftware]LOG]!><time="10:01:30.360-120" date="09-24-2015" component="AppIntentEval" context="" type="1" thread="4068" file="appconstructs.cpp:3057"> AppDiscovery.log: <![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_54761859-29CE-43B8-9BEE-B88049CB81CB/DeploymentType_d02b19f5-fc3c-4474-a737-f60fc632dfb7" AND Revision = 25)"]LOG]!><time="10:04:09.403-120" date="09-24-2015" component="AppDiscovery" context="" type="1" thread="5060" file="appprovider.cpp:406"> <![LOG[ Performing detection of app deployment type MySoftware(ScopeId_54761859-29CE-43B8-9BEE-B88049CB81CB/DeploymentType_d02b19f5-fc3c-4474-a737-f60fc632dfb7, revision 25) for system.]LOG]!><time="10:04:09.406-120" date="09-24-2015" component="AppDiscovery" context="" type="1" thread="5060" file="appprovider.cpp:2148"> <![LOG[ In-line script returned error output: & : File C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1 can not be loaded. The file C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3 c51ada3.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy , see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170 . At line:1 char:3 + & 'C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1' + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : SecurityError: ( [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess ]LOG]!><time="10:04:09.819-120" date="09-24-2015" component="AppDiscovery" context="" type="2" thread="5060" file="appexcnlib.cpp:1022"> <![LOG[Script Execution returned error message: & : File C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1 can not be loaded. The file C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3 c51ada3.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy , see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170 . At line:1 char:3 + & 'C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1' + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : SecurityError: ( [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess , ExitCode: 1]LOG]!><time="10:04:09.819-120" date="09-24-2015" component="AppDiscovery" context="" type="2" thread="5060" file="scripthandler.cpp:473"> <![LOG[ Script Execution Returned :1, Error Message: & : File C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1 can not be loaded. The file C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3 c51ada3.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy , see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170 . At line:1 char:3 + & 'C:\Windows\CCM\SystemTemp\803c4b19-c156-4d0d-b65d-6d3e3c51ada3.ps1' + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : SecurityError: ( [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess . [AppDT Id: ScopeId_54761859-29CE-43B8-9BEE-B88049CB81CB/DeploymentType_d02b19f5-fc3c-4474-a737-f60fc632dfb7, Revision: 25]]LOG]!><time="10:04:09.820-120" date="09-24-2015" component="AppDiscovery" context="" type="3" thread="5060" file="scripthandler.cpp:506"> <![LOG[CScriptHandler::DiscoverApp failed (0x87d00327).]LOG]!><time="10:04:09.822-120" date="09-24-2015" component="AppDiscovery" context="" type="3" thread="5060" file="scripthandler.cpp:546"> <![LOG[Deployment type detection failed with error 0x87d00327.]LOG]!><time="10:04:09.822-120" date="09-24-2015" component="AppDiscovery" context="" type="3" thread="5060" file="appprovider.cpp:2203"> <![LOG[Failed to perform detection of app deployment type MySoftware(MySoftware, revision 25) for system. Error 0x87d00327]LOG]!><time="10:04:09.822-120" date="09-24-2015" component="AppDiscovery" context="" type="3" thread="5060" file="appprovider.cpp:545"> AppEnforce.log is currently void of any references to "MySoftware".

Hi, I work with SCCM 2012 SP1 and I would like to create an application that deploy files in the user profile. However, I'm stuck on the detection method because I can not use the variable %USERPROFILE% or %USERNAME%. (view picture 1 and 2) However, SCCM knows other variables such as "%windir%" or "%ProgramFiles%" (view picture 3) Someone has an idea

I recently discovered that an outlook plugin I push out as an application through SCCM wasn't getting installed on some computers. Upon further investigation, I found that the deployment listed these computers as not meeting requirements. The requirement missing is listed as "Microsoft Office". That's the name of a dependency group I created, which contains Office 2010 and Office 2013. According to the text in the "Edit Dependency" window, this should mean that one or the other of those applications has to exist on the machine. Office 2010 is part of our standard image, and is on every workstation we put out. I confirmed that it is still installed on the workstation I'm using to troubleshoot this issue. Checking the properties of the deployment type used by the Office 2010 application, the detection method is set to check for the existence of MSI Product code {90140000-0011-0000-0000-0000000FF1CE}. On the affected computer, I searched the registry for that product code, and found it contained in the multi string value "ProductCodes" under key: HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS The ProductCodes value contained multiple entries, as listed below: {90140000-0011-0000-0000-0000000FF1CE} {90140000-002C-0409-0000-0000000FF1CE} {90140000-00BA-0409-0000-0000000FF1CE} {90140000-002A-0000-1000-0000000FF1CE} {90140000-0044-0409-0000-0000000FF1CE} {90140000-001F-0C0A-0000-0000000FF1CE} {90140000-001B-0409-0000-0000000FF1CE} {90140000-0019-0409-0000-0000000FF1CE} {90140000-0117-0409-0000-0000000FF1CE} {90140000-0015-0409-0000-0000000FF1CE} {90140000-00A1-0409-0000-0000000FF1CE} {90140000-001F-0409-0000-0000000FF1CE} {90140000-001F-040C-0000-0000000FF1CE} {90140000-001A-0409-0000-0000000FF1CE} {90140000-0016-0409-0000-0000000FF1CE} {90140000-0018-0409-0000-0000000FF1CE} {90140000-0115-0409-0000-0000000FF1CE} {90140000-006E-0409-0000-0000000FF1CE} {90140000-002A-0409-1000-0000000FF1CE} {90140000-0116-0409-1000-0000000FF1CE} I also checked the appdiscover.log on the affected computer. There I find that it accurately detected Office 2010 as installed, and the plugin as not installed. What am I missing here? I've got about 60 workstations that don't have this plugin installed because SCCM thinks they don't meet requirements, but everything I can find says they do meet the requirements.