IE10 setup detection method

Installing IE10 in Task sequence. Not using IEAK, so command line is
IE10-Windows6.1-x86-en-us.exe" /quiet /update-no /norestart
Installs fine and reboot suppressed. Problem is the detection method detects as failed because prior to reboot nothing appears to change. Neither iexplore.exe or the registry entries have been updated to V10. Therefore SCCM registers as a failed install
After reboot all fine, but the reports say that step of the TS failed
Is there a way round this ?
Ian Burnell, London (UK)

Ian,
I would recommend that you use packages for OSD rather than applications. You don't need detection with OSD, it's completely irrelevant and if used within the TS those rules need to be valid. Create an application for non OSD endpoints that are already out
there that need the update.
Packages give you the option also to run direct from the DP - which might be handy for larger applications that fill up the cache locally.
Ultimately keep it simple. Why over complicate your OSD with unnecessary 'frigging' around?
Just because the model exists doesn't mean you are reducing to using that method only.
Cheers
Paul | sccmentor.wordpress.com

Similar Messages

SCCM 2012 - IE10 - Detection Method - Compliance?

Hi, I am successfully deploying IE10 to the domain. I have amended the detection method to the below:
i have updated the content. How do I update the compliance to reflect to the deployment as it is still @ 0% for each Collection? Do i need to redeploy the application?. I need to get the results asap if possible!
Thanks

Hello, there is still no change in the Compliance. I have changed the Detection Rule to
Operator: Greater than or Equal to rather than Equals:
Hoping this will make a difference or any more solutions? Cheers

MSO 2010 Application deployment hangs if detection method for presence of deployment is specified

SCCM 2012 R2 is configured to deploy MSO 2010 to our systems, even the ones that already have it deployed. Regular deployment does not re-install MSO 2010 because it detects it already installed on a system, so I added "Detection Method" and configured
it to look for a file "mso_installed.txt" in C:\WINDOWS. A custom MS Office package was created to place this file into C:\WINDOWS during the setup as part of App deployment.
The logic is: if the app deployment does NOT find this file in C:\windows, it will force MSO reinstall. Introducing this method appears to hang the setup. I can see that deployment shows up in Software Center, content is downloaded, status changes to "installing"
and then nothing happens. Setup32.exe process appears to sit doing nothing - no change in CPU or MEM utilization. Eventually, the status changes to "Past due - will be installed".
We currently have a deployment that works, but doesn't have the detection method logic above. What could be causing this deployment not to work and if my method above is not ideal, what are my options for forcing re-install of the app, even if already present
on the system?

Log contents are pasted below:
<![LOG[ Prepared working directory: C:\Windows\ccmcache\9]LOG]!><time="07:25:05.581+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="444" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\Windows\ccmcache\9\setup.exe" /config \\scdp01\staging$\MSO2010PRO_SP2\ProPlus.WW\config.xml]LOG]!><time="07:25:05.592+300" date="02-25-2015" component="AppEnforce"
context="" type="1" thread="444" file="appcontext.cpp:338">
<![LOG[ Executing Command line: "C:\Windows\ccmcache\9\setup.exe" /config \\scdp01\staging$\MSO2010PRO_SP2\ProPlus.WW\config.xml with system context]LOG]!><time="07:25:05.593+300" date="02-25-2015" component="AppEnforce"
context="" type="1" thread="444" file="appexcnlib.cpp:201">
<![LOG[ Working directory C:\Windows\ccmcache\9]LOG]!><time="07:25:05.595+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="444" file="appexcnlib.cpp:215">
<![LOG[ Post install behavior is ProgramReboot]LOG]!><time="07:25:05.774+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="444" file="appcommon.cpp:1094">
<![LOG[ Program will restart the computer after the enforcement...]LOG]!><time="07:25:05.776+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="444"
file="appcommon.cpp:1099">
<![LOG[ The program rebooting flag has already been created before.]LOG]!><time="07:25:05.777+300" date="02-25-2015" component="AppEnforce" context="" type="2" thread="444"
file="appcommon.cpp:1363">
<![LOG[ Waiting for process 3524 to finish. Timeout = 120 minutes.]LOG]!><time="07:25:05.781+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="444"
file="appexcnlib.cpp:1958">
<![LOG[Exceeded timeout of 120 minutes while waiting for process 3524 to finish.]LOG]!><time="09:25:05.903+300" date="02-25-2015" component="AppEnforce" context="" type="2" thread="444"
file="appexcnlib.cpp:1972">
<![LOG[WaitForRunningProcess failed. Error 0x87d00213.]LOG]!><time="09:25:05.920+300" date="02-25-2015" component="AppEnforce" context="" type="3" thread="444" file="appexcnlib.cpp:1988">
<![LOG[CMsiHandler::CompleteEnforcement failed with 0x87d00213]LOG]!><time="09:25:05.938+300" date="02-25-2015" component="AppEnforce" context="" type="3" thread="444" file="msihandler.cpp:320">
<![LOG[CAppProvider::CompleteEnforcement failed with error 0x87d00213]LOG]!><time="09:25:05.943+300" date="02-25-2015" component="AppEnforce" context="" type="3" thread="444" file="appprovider.cpp:2544">
<![LOG[++++++ Failed to enforce app. Error 0x87d00213. ++++++]LOG]!><time="09:25:05.963+300" date="02-25-2015" component="AppEnforce" context="" type="3"
thread="444" file="appprovider.cpp:2467">
<![LOG[+++ Starting Install enforcement for App DT "Microsoft Office Professional Plus 2010 - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_D8679AD5-B893-419B-8D14-FCB316DEB10C/DeploymentType_6ef2b4c3-b40f-4697-bf16-b673c5d3669d,
Revision - 2, ContentPath - C:\Windows\ccmcache\9, Execution Context - System]LOG]!><time="09:48:04.703+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appprovider.cpp:1702">
<![LOG[ A user is logged on to the system.]LOG]!><time="09:48:04.709+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appprovider.cpp:2083">
<![LOG[ Performing detection of app deployment type Microsoft Office Professional Plus 2010 - Windows Installer (*.msi file)(ScopeId_D8679AD5-B893-419B-8D14-FCB316DEB10C/DeploymentType_6ef2b4c3-b40f-4697-bf16-b673c5d3669d, revision 2) for system.]LOG]!><time="09:48:04.718+300"
date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_D8679AD5-B893-419B-8D14-FCB316DEB10C/DeploymentType_6ef2b4c3-b40f-4697-bf16-b673c5d3669d, Revision: 2]]LOG]!><time="09:48:04.773+300" date="02-25-2015" component="AppEnforce"
context="" type="1" thread="1404" file="localapphandler.cpp:291">
<![LOG[ App enforcement environment:
Context: Machine
Command line: setup.exe /config \\scdp01\staging$\MSO2010PRO_SP2\ProPlus.WW\config.xml
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\9
Working directory: ]LOG]!><time="09:48:04.775+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appcontext.cpp:85">
<![LOG[ Prepared working directory: C:\Windows\ccmcache\9]LOG]!><time="09:48:04.779+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\Windows\ccmcache\9\setup.exe" /config \\scdp01\staging$\MSO2010PRO_SP2\ProPlus.WW\config.xml]LOG]!><time="09:48:04.785+300" date="02-25-2015" component="AppEnforce"
context="" type="1" thread="1404" file="appcontext.cpp:338">
<![LOG[ Executing Command line: "C:\Windows\ccmcache\9\setup.exe" /config \\scdp01\staging$\MSO2010PRO_SP2\ProPlus.WW\config.xml with system context]LOG]!><time="09:48:04.786+300" date="02-25-2015" component="AppEnforce"
context="" type="1" thread="1404" file="appexcnlib.cpp:201">
<![LOG[ Working directory C:\Windows\ccmcache\9]LOG]!><time="09:48:04.788+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appexcnlib.cpp:215">
<![LOG[ Post install behavior is ProgramReboot]LOG]!><time="09:48:04.906+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404" file="appcommon.cpp:1094">
<![LOG[ Program will restart the computer after the enforcement...]LOG]!><time="09:48:04.907+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404"
file="appcommon.cpp:1099">
<![LOG[ The program rebooting flag has already been created before.]LOG]!><time="09:48:04.908+300" date="02-25-2015" component="AppEnforce" context="" type="2" thread="1404"
file="appcommon.cpp:1363">
<![LOG[ Waiting for process 3932 to finish. Timeout = 120 minutes.]LOG]!><time="09:48:04.913+300" date="02-25-2015" component="AppEnforce" context="" type="1" thread="1404"
file="appexcnlib.cpp:1958">

Detection Methods for Microsoft Office

Hi Guys
It seems the most common detection method for deploying Microsoft Office (in particular for me Office 365 pro plus) is the existence of 'Office15' in %program files%\Microsoft Office 15\
However my concern is that what if some other Office 2013 product has created this folder?
Has anyone used a differnet detection method other than the existence of the folders?
thanks for your help!

That is the best way...
If the condition of Office 2013 components already being installed is met (Folder location exists) just use a custom .msp (instead of the setup.exe with custom.msp) adminfile to alter their installation and enable the components they are required
to have.
Office 365 Pro Plus does not use MSPs the way Office 2013 does so this isn't really applicable -- in fact, it installs Office in a completely different way than Office 2013 does so can't be detected the same way. The registry value noted is the best path
IMO.
Jason | http://blog.configmgrftw.com | @jasonsandys

Detection method - file NOT exist?

I have a need to remove the Outlook feature from Office 2013 if it is present on certain machines. I create my MSP to remove Outlook and run msiexec /p removeoutlook.msp and it works great.
My problem is that the detection method for applications is the opposite of what I need. If the Outlook.exe file is NOT present, then it is installed.
I'm sure there must be a way to do this via the custom detection script but I am a scripting noob.

You can create a 'dummy' application "Outlook 2013", configure it as follows:
Leave install command blank
Configure uninstall command to use your detection method (outlook.exe exists)
Deploy the Uninstall to the collection where you want to remove the outlook
Or you could use simple package/program to just remove the outlook by running your uninstallation command. Or you could configure your Office 2013 with OCT (Office Customization Tool by running setup.exe /admin) to remove Outlook from your Office 2013 installation
for future deployments.

How to use property Upgrade Code in detection method "Windows Installer"?

Hi
I am a packaging specialists helping our deployment guys to add our software (100rds of installers) as application entries in SCCM 2012. The methods supplied by SCCM seem however quite generic and limited.
The detection method "Windows Installer" is hardcoded to use the Product Code, why?
Normal detection of Windows Installer packages are done using the Upgrade Code and the Product Version. Is it possible for us our self to add/reconfigure to use that method or are we forced to use the custom detection method?(both those methods should be provided
by SCCM to better match Windows Installer architecture)
Ps. It says in http://technet.microsoft.com/en-us/library/bb632336.aspx for Version that "This
must be in the standard Windows Installer four-part version number format.", but the version number is 255.255.65535 (which is real stupid) as described by http://msdn.microsoft.com/en-us/library/aa370859(v=vs.85).aspx. Ds.
Regards
Pär

Under LV 7.1 with DSC installed I get the same error code (-2147418113) but "explain error" gives me this.
"LabVIEW DSC: (Hex 0x8000FFFF) Catastrophic failure."
This prompts the question is it possible to set an activeX object running in a container for Full Screen.
This is probably a Q for MS.
If it look like it is possible, try to get a VB example and that will tell us what we have to do to make this work.
Ben
Message Edited by Ben on 10-31-2005 04:45 PM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

HT5552 I am unable to setup payment method using American Express.

I am unable to setup payment method using American Express.

Contact iTunes Customer Service and request assistance
Use this Link > Apple Support iTunes Store Contact

Application Detection Method not being honored.

We have a deployment of a patch for Lync 2010. In the Detection Method we are using the path for communicator.exe and the version number. We have a few systems testing Lync 2013. The paths are completely different so we don't understand
why these clients are getting prompted for installation of the update.
The Detection Rule is a as follows:
David Jenkins

The path is there but no communicator.exe. In 2013 it's part of MS Office so it's in the Office directories.
I'd expect if communicator.exe doesn't exist in the directory it would mean the check fails and the patch would not advertise.
I think you're getting tangled up with the logic at play here...
If this detection rule is on your patch deployment, the logic is this:
"if this path/file/version is not detected, then I must deploy this patch to this machine"
So, on your machines that do have Lync2013, they will also *not* have the unpatched Lync2010 binary, therefore, it will attempt to deploy the patch.
You could consider applying another detection rule (maybe *AND* Lync2013 is not present), or, flip your detection logic around, and instead, detect for the unpatched Lync2010 binary (i.e. if version is less than 4.0.7577.4409) ?
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Detection method - date modified-greater than issue

Hi,
My detection method for a file doesn't seem to be working properly. I have an application advertised to run a .cmd file and replace files in an already existing folder. So I am using the date modified of the files I am replacing. When I check the status
of the deployment it states that the machines are already compliant even though the date modified on the file is less than the new file I am trying to deploy.
Example:
C:\ProgramData\Microsoft\Network\Connections\Cm\Test\test.cms (date modified 9/14/2014)
My detection rule:
C:\ProgramData\Microsoft\Network\Connections\Cm\Test\test.cms (Date Modified must be greater than 01.01.2015 00:00:00)
And it is stating that it is compliant even though the detection rule should be returning false?

Date format is seems to be correct, basically it depend on your local date format.
Are you sure that file is exist on the client at expected location. (If file does not exist and existential rule is not added in CI then CI will return to Compliant) If not then make sure that:
you have added existential rule in addition with value rule.
otherwise make sure that you have selected this checkbox "Report noncompliance if this setting instance is not found."
This posting is provided "AS IS", provides no warranties, and confers no rights. -Praveen S.

Creating enhanced detection method via powershell

Hi folks,
im trying to automate the application creation process and so far I got a lot of usefull hints and tipps from technet forum etc.pp.
I would like to set an registry detection method via powershell.
Since I am not used to C# I found a nice approach translating a C# script into PS script.
http://social.technet.microsoft.com/Forums/de-DE/93bddee4-6aee-4641-b104-170968ad1549/automating-application-creation?prof=required
Unfortunately I can't get it to work... (same error as descriped in the link above "generic Error from the Put()-Function.") When I am using e.g. an MSI productcode as detection method in my script, I am able to create an application with
deploymenttype and detectionmethod.
Has anyone a solution for this problem ? Or was anyone able to set a registry detection via powershell ? Is it possible ?
Any help will be appreciated.

Any time I've seen a Put() error, the problem has been I've been missing a needed property.
If you are using Config Manager 2012 R2 (Not sure about previous versions), you can use the built in cmdlet Add-CMDeploymentType. This is the command I use. For a PS detection type, change ScriptType to Powershell and $Script will be your detection
script.
$param = @{ApplicationName=$Name
               DeploymentTypeName=$ScriptName
               InstallationProgram=$Install
               ScriptType="VBScript"
               ScriptContent=$Script
               InstallationBehaviorType="InstallForSystem"
               ContentLocation=$SourceLocation
               UninstallProgram = $Uninstall
               LogonRequirementType="WhetherOrNotUserLoggedOn"
               InstallationProgramVisibility="Hidden"
       Add-CMDeploymentType @param -ScriptInstaller -ManualSpecifyDeploymentType -DetectDeploymentTypeByCustomScript

Deploying Lync 2013 client and SCCM Detection method

So I am deploying the stand alone Lync 2013 client via SCCM 2012 R2, I have used OCT to create a .MSP, and I am trying to import it into SCCM. However, I am curious as to what others are using for the Detection method? Normally I would just
use the MSI code, but since there is no single MSI, that is not possible with this particular version? I'm not sure what the best method would be, Option 1 is to find a registry key that is installed by Lync, or Option 2, use a file, maybe Lync.exe under
the Program Files?

From the testing I've done Lync creates this reg location...
HKLM>Software>Microsoft>Office>15.0>Lync
Try using one of the keys in there, or you could use the file version but not sure if this would change with updates.

Detection Method Process during install

My question is in Reference to how it appears the detection method works in SCCM 2012. <o:p></o:p>
I am running the
AcrobatCleaner Tool which uninstalls Acrobat. In my case I am looking to uninstall version
11.x. This is set in the command line for the tool.<o:p></o:p>
In SCCM I have an application deployment type. I set a detection of the MSI for Acrobat
10. (If I set for 11.x It would not run and ver 10 it will not run if Acrobat 10 is installed which 11 would not be.) <o:p></o:p>
During the Application Discovery the MSI GUID is found.
The application is installed (Uninstalling version 11, producing a return code of 0)<o:p></o:p>
I am getting a return code 0 in the AppEnforce log. However it is showing failed in the Software Center and an error code of 0x87D00324<o:p></o:p>
Is there another process which the checks for the component which was set for the detection? <o:p></o:p>
It seems the install is running correctly.
Since Acrobat 10 is still not installed (Which is expected) after the uninstall it appears, The detection is being re-run and not finding it.<o:p></o:p>
If this is the case, any thoughts on what I should use for detection instead of Acrobat 10.x. Guess on option would be to put the exe in a MSI.<o:p></o:p>
Thanks for any input and helping me to know I am not crazy.

Hi,
Are you deploying the Application with the option to "Uninstall" and not install so you have your command in the uninstall string? That is what you should do, the error translates to "The application was not detected after installation
completed." which is correct if you have the Uninstall command for Acrobat in the Install option in the deployment type and not Uninstall.
So switching it to uninstall should do the trick.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

ABAP Unit: Can one call a method in the setup/teardown methods?

Hi all,
I'm using ABAP Unit test ClasseS (what's with the odd capitalization BTW?) in the class builder on NW7.0.
In my SETUP method I do not want to do a CREATE OBJECT, but want to use a GET_INSTANCE method of my main class to instantiate my object.
When I execute my unit test however the instance methods all fail with CX_REF_NOT_ASSIGNED - meaning there is no instance m_ref.
OK, fair enough methinks, let me debug and see what's going on.
Surprise: When I set a breakpoint in the SETUP method it all runs fine. Instances are instantiated and instance method tests execute successfully.
So now I'm a bit stuck trying to investigate a problem that disappears everytime you look at it, a bit like trying to see if the light is off when the fridge is closed... Any ideas?
Cheers,
Mike
Edit: Just to clarify, here's some code:
method setup.
    m_ref = zcl_myclass=>get_instance( im_key = 'ABC' ).
    " when debugging m_ref is always instantiated and test runs successfully!
endmethod.       "Setup
method get_some_data.
    result = m_ref->get_some_data( ).
    " without breakpoint in the setup method, this fails because m_ref is not assigned
endmethod.
Edited by: Mike Pokraka on Jun 23, 2008 11:57 PM

Never mind, found problem, schoolboy error:
My class_setup method created test data but the update hadn't completed so my GET_INSTANCE failed in normal execution but worked in debug because of the associated delay. 'commit work' needed an 'and wait' and now it's happy.

Windigo Botnet - Is this detection method correct?

After reading today about the Windigo Botnet (http://www.eset.com/int/about/press/articles/article/operation-windigo-largest-s erver-botnet-uncovered/) I used the suggested method for checking for infection, which was detailed in the article.
The code to be run is
$ ssh -G 2>&1 | grep -e illegal -e unknown > /dev/null && echo "System clean" || echo "System infected"
After running the command in Terminal, the response was "System infected".
Can someone confirm if the code given is correct for checking my OS X Mavericks.
I would hate to re-install my OS if it was just echoing back "System infected" rather than actually detecting the malware.
Can someone from Apple let us know if this is indeed the correct method of detection?

GITHUB (https://github.com/eset/malware-ioc/tree/master/windigo)
One can use the following command to determine if the server he is on is compromised:
ssh -G 2>&1 | grep -e illegal -e unknown > /dev/null && echo "System clean" || echo "System infected"
This code is missing the "$" and has the output of "System clean"

Access to Setup- Notification Methods without any Pack?

Hello,
I try to configure E-Mail notification in EM GC 10.2.0.4, but it is unaccessible after deactivating all purchasable packs.
("Notification Methods" under Tab "Setup" is deactivated).
Do I need to buy a Management Pack for configure and use an E-Mail notification?
Thanks!

ok, I need management pack...
But one is strange - why I get E-Mail for metric "Audited User" == SYS from metric category "User Audit",
but dont get any E-Mail for metrics from "Dump Area" category?
I would have expected that in both cases no email is sent ...

IE10 setup detection method

Similar Messages

Maybe you are looking for