Additional options

  • Last update on September 27th, 2024

During the packaging process, after selecting your file option, you have additional choices to optimize how Configuration Manager handles the installation process.

Consider enabling these options based on your needs:

Use Configuration Manager Standard Install.bat:

When checked, Configuration Manager’s Install.bat adds a standard batch file to assist in the app installation process. The install file orchestrates the installation of any file named Setup.exe/msi or Setup-x64.exe/msi located in the same directory as the install.bat.

rem generic setup script for installing microsoft.graph.win32LobApp (intunewin) packaged applications that have both x86 and x64 installers
SETLOCAL EnableDelayedExpansion
reg query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86"  nul && set setup=setup|| set setup=Setup-x64
@echo Status of PendingFileRenameOperations before install
%SystemRoot%\System32\reg.exe query "HKLM\System\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations
if exist "%~dp0%setup%.exe" (
	start "" /b /wait "%~dp0%setup%.exe" %*
	set returncode=!errorlevel!
) else if exist "%~dp0%setup%.msi" (
    set "SystemPath=%SystemRoot%\System32"
    if exist "%SystemRoot%\Sysnative\cmd.exe" set "SystemPath=%SystemRoot%\Sysnative"    
	start "" /b /wait !SystemPath!\msiexec.exe /i "%~dp0%setup%.msi" %* /quiet /l*v install.log
	set returncode=!errorlevel!
	type install.log
)
@echo Status of PendingFileRenameOperations after install
%SystemRoot%\System32\reg.exe query "HKLM\System\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations
@echo Exiting %0 with ERRORLEVEL=%returncode%
exit /b %returncode%

 

Automatically version application:

When checked, Configuration Manager will automatically include a detection rule so that the app is reinstalled any time you make changes to the package.

For instance, when a new version of an application like 7-Zip is released, you can simply update the download URL in Configuration Manager. The system then detects this change, automatically repackages the application with the new version, and prepares it for deployment.

It's important to note that while Configuration Manager automates the repackaging process, it doesn't automatically deploy the new version. This gives you control over when and where to roll out updates. The system maintains versions of your applications, allowing for easy rollbacks or selective deployments of specific versions if needed. 

 

 

Enable Application Install Logging:

An important aspect of application install/uninstall troubleshooting is valid and consistent logs on the end-user’s device. When “Enable Application Install Logging” is checked, Configuration Manager includes the property enableInstallLogging in the application configuration .json file to assist with the logging process. 

All logs captured during application installation will be written to the %temp% directory in a file named: MobileApp.{name of application}.{version}.install.log. This setting allows the installCommandLine in the application configuration .json file to be:

"enableInstallLogging": true,
...
"installCommandLine": "Install.bat /S",

When uploaded to Intune, Configuration Manager changes the install command line to:

cmd /s /v /c "(Install.bat /S)  "!temp!\MobileApp.7-Zip.012.install.log" 2&1"

If the application is running as System, the logs will be found in C:\windows\temp. Or if the application is running in the user’s context, the logs will be in the user’s temp directory.