Ath3na

you can always set to continue on error.

should the command be something like ? biosconfigutility.exe /CurSetupPasswordFile:"passwordfile.bin" /setconfig:Elitebook820.REPSET Ours are like this. The password is set at an earlier stage, both occur during winpe

Hi, Exit code 11 means: Config file not valid, BCU was unable to locate the configuration file or unable to read the file at the specified path. http://whp-hou4.cold.extweb.hp.com/pub/caps-softpaq/cmit/whitepapers/HP_BCU_FAQ.pdf

Nice

Here is the .reg if it makes it easier. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{f4d8fb9e-3bce-4152-add4-2f4e5f647610}] "Product"="Name of Application" "StubPath"="C:\\Program Files (x86)\\Internet Explorer\\iexplore.exe" "Version"="1"

Hi, If you want the application to be configured for each new user that logs onto the machine and you only want it to occur once per user than Microsoft have something built for this already. It's called activesetup. You just add a few registry keys to HKLM. User logs on and it runs whatever is in the stubpath info Example If you run the below code in the ISE as administrator, then log off and back on again IE will load just one time per new user For each new activesetup make sure you make it unique with a new GUID #requires -Version 1 <# Author: Richard Knight Version:1.0 Purpose: Creates Active Setup keys random GUID created at https://www.guidgenerator.com/ #> $Appname = 'Name of Application' $stubpath = 'C:\Program Files (x86)\Internet Explorer\iexplore.exe' $Reglocation = 'HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{f4d8fb9e-3bce-4152-add4-2f4e5f647610}' New-Item -Path $Reglocation -Force New-ItemProperty $Reglocation -Name 'Product' -Value "$Appname" New-ItemProperty $Reglocation -Name 'StubPath' -Value "$stubpath" New-ItemProperty $Reglocation -Name 'Version' -Value '1'

Thank you !!

Hi, The appenforce.log is the correct log to monitor application installation when monitoring application model deployments. When the installation starts that's the log that shows the process running and exit code etc Try adding in a second application and push it to the same device. From a glance at your logs it hasn't received the software via policy yet, the second link is the one you want. Does the client look healthy? if you open control panel there is a Configuration Manager applet. In the actions tab are there more than 2 listed? You are correct about the catalogue, you need the role installed to be able to use it. But you do not need it for software deployments. Software center will be fine. https://blogs.technet.microsoft.com/manageabilityguys/2013/10/01/configmgr-2012-tracking-application-model-installations-on-clients/ https://web.archive.org/web/20160422151315/http://www.moyerteam.com/2013/10/troubleshooting-configmgr-application-deployments-detailed-log-file-analysis/

Hi, You would generally have the old adobe product added as an application, then when you want to remove it and install a newer product you would set supercedence, this would then automatically remove the old product and install the new. When you are doing an 'install' deployment then the detection rule will be looking for the presence for something added. The reverse is true for a removal. There are many ways to sort this, one option would be to create your new application as a script installer, this isn't tested and thrown together but maybe a pointer. :Remove Old Product AdobeCleaner.exe -S reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL && set OS=32BIT || set OS=64BIT if %OS%==32BIT SET APP_PATH=C:\Program Files\Adobe\Acrobat 11.0\Acrobat if %OS%==64BIT SET APP_PATH=C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat ECHO %APP_PATH% if exist "%APP_PATH%\Acrobat.exe" ( ECHO Failed to remove old product, exiting with 1603 EXIT /B 1603 ) else ( ECHO Old product removed, moving on to install new product Msiexec /i "InstallNEWAPP.msi" Transforms="NEWMST.mst" /qn SET returncode=%errorlevel% Echo Any other actions can go here EXIT /b %returncode% )

Nothing fancy is required. Create the application the standard way by pointing to the MSI. Configuration Manager will do all of the heavy lifting. All you then need to do is update the command line to be msiexec /i "CrashPlanPROe-x64_Win.msi" /qn CP_SILENT=true http://prajwaldesai.com/deploying-applications-using-sccm-2012/

Use reporting to get accurate information. The console updates periodically and depends on how old the deployment is. What happens if you run the status summeriser, does it update the information? What does execmgr.log say on one of the clients that doesn't report it has the software installed via the monitoring node?

Hi, Is there any reason you don't want to allow the content to cache down to each machine? It's been years since I looked at 2007 but I would always set 'this package contains source files' and browse to the directory that contains the setup files, then distribute the content to DPs. This will then cache the package down to each machine and run it locally when you target a device.. No server access headache issues, and it's the way Configuration Manager is designed to run. It's all via bits so should be fine. 99.99999999999 % of the time I go with a standard program. Run = hidden weather or not a user is logged on. runs with a UNC name for office though I would set to run only when no user is logged on. If the user is running office it will fail or a user might try and look for office while it's in the process of installing \ removing. I would create 2 or 3 separate programs for this. 1 cscript.exe OffScrub10.vbs ProPlus /bypass 1 /q /s /NoCancel 2 setup.exe /configure \\server\share\office365\proplus.xml I rolled out this change sometime last year and found 20 % of the devices failed to run the scrub properly. So I had the full content for office 2010 cache down locally set to fully remove the product, then it ran the office scrub, then it ran a 3rd program to install the new office, each was set to reboot the machine after. Each was chained via the program advanced tab, run other program first without the 'Always run this program first' checked (as you only want it to run once and not every time that program runs)

Try removing appdata\local from the sequencer exclusions and resequence. I think Chrome might be saving the data in this location and it's being excluded from your package.

Cool, no need for a mapped drive in the package. Just stick your bat or .cmd in a folder. Make that folder the source for the package and it will cache down to each machine. Your command to run the bat is just the name of the .bat or .cmd Hope you got it sorted.

Hi Doug, You only need to use %~DP0 when you need to know your current working directory or reference another directory, say a sub directory. an example are some of the adobe applications. Sometimes they have a setup.exe file and you have to reference the full path to a customisation xml. In that case an example would be (both files in package root folder) SETLOCAL SET WORKING=%~dp0 %WORKING%Setup.exe %WORKING%custom.xml This is specifying the full path to the setup.exe and the xml file. If you just had a setup.exe and no custom xml to reference then just setup.exe on it's own as the command line would be fine. another example for a response file: Where the setup.exe is in a sub folder of your package called FOLDER and the response file is in a subfolder called FOLDER2 "%~dp0FOLDER\setup.exe" -s -f1"%~dp0FOLDER2\Setup.iss" In your script I wouldn't bother with CD, there is no need, just put the full path to the file you want to run. There is no need to use ~dp0 in your example. I would tackle your task with something like this:(not tested but might set you on the right path) ECHO off reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL && set OS=32BIT || set OS=64BIT if %OS%==32BIT SET APP_PATH1=C:\Program Files\Ultravnc\unins000.exe if %OS%==32BIT SET APP_PATH2=C:\Program Files\Uvnc bvba\Ultravnc\unins000.exe if %OS%==64BIT SET APP_PATH1=C:\Program Files (x86)\Ultravnc\unins000.exe if %OS%==64BIT SET APP_PATH2=C:\Program Files (x86)\Uvnc bvba\Ultravnc\unins000.exe if exist "%APP_PATH1%" ( "%APP_PATH1%" /VERYSILENT /NORESTART EXIT /B %errorlevel% ) else ( ECHO EXE not found ) if exist "%APP_PATH2%" ( taskkill /F /IM winvnc.exe "%APP_PATH2%" /VERYSILENT /NORESTART EXIT /B %errorlevel% ) else ( ECHO EXE not found ) Have a look at execmgr.log on the client to see why your package fails to install. Another troubleshooting step might be to download psexec and run your script with psexec -i -s cmd.exe this will open a command window under the system account, the system account is the account ConfigMgr uses to do the install so great for testing.