I’ve checked the AppEnforce log and the install exits with exit code 0, but then fails detection. The package is picked up in the software center, I begin the install, run through the wizard (on a 64bit client), the package asks if you would like to install within “Program file(x86)” and on clicking next (at this point the installation would start on a 32bit client) the wizard closes and the software center shows the package as failed. I’ve not passed in any command line switches to the exe and can confirm the exe runs fine on a 64bit client when called with a bat file. I’ve ensured the option to “run installation an uninstall program as 32bit process on 64bit clients” is selected. The executable I’m using will not run as a silent install, so have set the logon requirement to “only when a user is logged on”, the installation visibility to maximum and ticked the option to allow users to interact with the program so the users run through the GUI themselves. I’m having trouble deploying an exe to 64bit machines, I’ve created the deployment as detailed above which works perfectly on 32bit machines. You can now distribute the content to the DP ready for deployment to a collection or via a Task Sequence. Click Next.Ĭhoose your deployment criteria accordingly and click Next.Ĭlick Next all the way to the end of the wizard. Click Next.Īdd in a detection clause for the application. Click Next.Įnter a name for the deployment type and click Next.Įnter the share location for the application source files and enter the command to execute the installation, in this instance wusa.exe Windows6.1-KB2533623-圆4.msu /quiet /norestart. Click Next.Ĭhoose ‘Manually specify the application information’ again. exe for the installation.Ĭhoose ‘Manually specify the application information’. However the command to deploy the hoftfix is wusa.exe Windows6.1-KB2533623-圆4.msu /quiet /norestart so I am referencing an. In the following example I will actually be deploying a Microsoft Hotfix (KB2533623) which is really an. There’s a way around this to get an exe file deployed. The choices for application type in SCCM 2012’s Application drop down does not include an option to install.
0 Comments
Leave a Reply. |