Latest posts by Joseph Moody (see all)
- SCCM and Group Policy update rings make updates easier - Wed, Sep 27 2017
- Softerra Adaxes 2017 - AD self-service with an offline twist - Wed, Jul 12 2017
- Windows 10 S – A Chromebook alternative? - Fri, May 5 2017
Having to test, deploy, and manage dozens of applications is difficult enough. Managing applications across multiple architecture types can be downright tricky. There are many ways to deploy multi-architecture applications, including using WMI filters and architecture security groups. I prefer to keep things simple, though. Simple means fewer parts and more automation.
Group Policy and SCCM support multi-architecture deployments that require just a one-time setup. Let’s start by covering these deployments with a Group Policy software installation and then look at SCCM.
Installing X86 and X64 applications with a Group Policy ^
In both parts of this article, we will be using 7-Zip as our test application. It comes in both architecture flavors. Download both versions in a share accessible by domain computers. Create a folder named 7-Zip, a sub-folder for the version, and an additional folder for each architecture. Your software share structure should now look like this:
Splitting up the application into architecture folders will reduce network traffic if you move to SCCM.
Create a new GPO and a security group named APP_7-Zip. Scope the GPO so that it is linked to an OU containing X86 and X64 test computers and only applies to your APP_7-Zip security group. Edit your GPO and navigate to Computer Configuration/Policies/Software Settings/Software installation.
Add a new package and browse to your X86 application. For the deployment method, select Advanced. On the Properties page, select Advanced (again) and uncheck Make this 32-bit X86 application available to Win64 machines.
This will prevent X64 machines from installing the X86 application.
Set any additional options (such as adding MSTs under Modifications), and then add a second new package. Add your X64 application. You do not need to make any advanced deployment changes with this package. You should now have two applications listed in your GPO.
This GPO will now install applications based on architecture.
If you reboot an 32-bit and an 64-bit client, they will each install their respective applications. With Group Policy software installation mastered, let’s cover architecture installs with SCCM.
Deploying 32-bit and 64-bit applications with SCCM ^
First, ensure that your applications are organized with the folder structure under the Group Policy software installation section. When the System Client evaluates the applications that need to be installed, content divided by architecture will ensure a faster caching time.
Terminology can be a bit confusing with SCCM. For simplicity’s sake, an application will contain multiple deployments (MSIs). These deployment types allow our computers to choose based on their architecture.
Start by creating a new application in SCCM. Instead of automatically detecting the MSI information, select Manually specify the application information. Fill out the general application information. Be sure to list a publisher and a software version.
Under Deployment types, select Add and then list your X86 application in the Location field. Under Name, be sure that the application name contains something like (x86 edition). This will make reporting easier after the install. Continue through the wizard until you reach the Requirements pane. Create a new Device requirement and change the condition to Operating system. Leave the Operator value as One of. This will allow you to specify OR statements.
Expand each operating system that you support and check the 32-bit version. Under Windows 7, you would check All Windows 7 (32-bit). Finish the wizard and then add a second deployment type. This time, import your X64 application. Be sure that the name contains X64 and set the OS requirements accordingly. Your requirements should look something like the screenshot below.
Configuring X64 OS requirements in SCCM
Under Deployment types, you should now have two items listed. When the SCCM client evaluates the application, it will check the requirements. This allows you to manage one application and one collection deployment.
Our completed application with two architecture-dependent installs
Whether you use Group Policy or SCCM, you can deploy applications without worrying about the OS architecture. This makes your deployments and management easier. If you face other application issues, let me know in the comments below.