Remote server administration tools is a windows server component which is used by system administrators and IT Staff to remotely manage features, roles and services. RSAT includes tools such as Group Policy Management, Active Directory Users and Computers, DNS Management and many more.
IT Staff use these tools daily. Usually these tools are installed manually. To make things easier you can install these tools via SCCM instead so that they are available to staff the will use them.
This post will guide you through how to create the application through System Center Configuration Manger.
Create RSAT Application
Download the latest RSAT tools from Microsoft. We will need the installation files as these will be used as the source of the application. Ensure these files are saved in your application source folder or locally on the SCCM Server.
From the SCCM Console navigate to Software Library > Applications
- Right click on Applications and select Create Application
- In the Create Application Wizard select manually specify the application information and then click Next.
- On the General Information tab enter the name of the application.
- Enter the version as Windows 10 and populate the other fields as required and then click Next.
- On the Application Catalog tab fill in the required information as you would like shown in Software Center and then click Next.
- In my example below I have only filled in the “localized application name” and chosen an icon for the application.
- On the Deployment Types tab click on Add to create a new deployment type for the application.
- On the General tab of the Create Deployment Type Wizard select manually specify the deployment type information and then click
- On the General Information tab populate the name field. i.e RSAT (64-bit) and then click
- On the Content tab enter the Content Location by clicking Browse and searching for the location of the source file.
- Enter the following in the Installation Program field:
Wusa.exe WindowsTH-KB2693643-x64.msu /quiet /norestart
- Enter the following in the Uninstall Program field and then click Next.
Wusa.exe /uninstall WindowsTH-KB2693643-x64.msu /quiet /norestart
- On the Detection Method tab, click Add Clause.
- On the Detection Rule tab, select File System as the setting type and select File in the Type
- In the Path field enter:
- In the File or folder name field enter:
- If you are using the 32 bit installation file, ensure you select the tick box that says This file or folder is associated with a 32-bit application on 64-bit systems.
- Ensure the option This file setting must satisfy the following rule to indicate the presence of the application.
- Select Version in the Property field, Greater than or equal to in the Operator field and 0.10514.0 in the Value field and click OK.
The Detection Rule is used to evaluate if the application has already been installed or not. If the application has already been installed then the application will only show up in the “Installed Software” tab of Software Center.
- In the User Experience tab, change installation behaviour to Install for system if resource is device; otherwise install for user.
- Change the Logon requirement field to be Whether or not a user is logged on, click Next.
- In the Requirements tab, click on the Add
- Select the condition as Operating System and choose All Windows 10 Professional/Enterprise and higher (64-bit). If you are installing 32-bit be sure to choose the 32 bit option instead. Once finished, click next.
- Click Summary to proceed to the confirmation page of the Create Deployment Type Wizard. Click Next to apply the settings and then Close to exit the wizard.
You should now see one deployment type in the Deployment Types tab. If you wish to also deploy the 32 bit version of the RSAT tools you can create another deployment type with the 32bit installation file.
Complete the wizard by clicking Next and following along until the wizard is complete.
You will now need to deploy the application to your respective collections. If you wish to manage the deployment of the application a bit more securely you can deploy the application to a user collection and choose to require administrator approval if the user requests the application in the Deploy Software Wizard.