Installing Configmgr R2 2012 Client For Mac

• Configmgr 2012 R2 Sp1

November 19, 2018 You can use Microsoft System Center Configuration Manager (SCCM) to deploy Citrix Receiver for Windows. Note Only Citrix Receiver for Windows Version 4.5 and later supports SCCM deployment. There are four parts to completing the deployment of Citrix Receiver for Windows using SCCM:. Adding Citrix Receiver for Windows to the SCCM deployment.

Copy the downloaded Citrix Receiver to a folder on the Configuration Manager server and launch the Configuration Manager console. Select Software Library Application Management. Right-click Application and click Create Application.

The Create Application wizard appears. In the General pane, select Manually specify the application information and click Next. In the General Information pane, specify information about the application such as Name, Manufacturer, Software version, and so on. In the Application Catalog wizard, specify additional information such as Language, Application name, User category and so on and click Next. Note: Users can see the information you specify here. In the Deployment Type pane, click Add to configure the deployment type for Citrix Receiver setup.

Microsoft, SCCM 2012 R2, System Center Configuration Manager Microsoft, SCCM, SCCM 2012R2 Before you can start managing a device with Configuration Manager, you must install the client software on it. The next step is to download and install the Mac client files. Click on the below link to download the Mac client for SCCM 2012 R2. Download Mac Client for SCCM 2012 R2. Download the Mac OS X client file package on your windows computer, file name is ConfigmgrMacClient.msi, and save it to a computer.

Configmgr 2012 R2 Sp1

The Create Deployment Type wizard appears. In the General pane: Set the deployment type to Windows Installer (.msi file), select Manually specify the deployment type information and click Next.

In the General Information pane: Specify deployment type details (For example: Receiver Deployment) and click Next. In the Content pane:. Provide the path where the Citrix Receiver setup file is present. For example: Tools on SCCM server.

Specify Installation program as one of the following:. CitrixReceiver.exe /silent for default silent installation.

CitrixReceiver.exe /silent /includeSSON to enable domain pass-through. CitrixReceiver.exe /silent SELFSERVICEMODE=false to install receiver in Non-Self Service Mode. Specify Uninstall program as CitrixReceiver.exe /uninstall (to enable uninstallation through SCCM). In the Detection Method pane: Select Configure rules to detect the presence of this deployment type and click Add Clause. The Detection Rule dialog appears.

Set Setting Type to File System. Under Specify the file or folder to detect the application, set the following:. Type – From the drop-down menu, select File.

Path –%ProgramFiles (x86)% Citrix ICA Client Receiver. File or folder name – Receiver.exe. Property – From the drop-down menu, select Version. Operator – From the drop-down menu, select Greater than or equal to.

Value – Type 4.3.0.65534 Note: This rule combination applies to Citrix Receiver for Windows upgrades as well. In the User Experience pane, set:. Installation behavior - Install for system. Logon requirement - Whether or not a user is logged on. Installation program visibility - Normal. Note: Do not specify any requirements and dependencies for this deployment type. In the Summary pane, verify the settings for this deployment type.

A success message appears. In the Completion pane, a new deployment type (Receiver Deployment) is listed under the Deployment types.

Click Next and click Close. Add distribution points. Right-click Receiver for Windows in the Configuration Manager console and select Distribute Content.

The Distribute Content wizard appears. In the Content Distribution pane, click Add Distribution Points.

The Add Distribution Points dialog appears. Browse to the SCCM server where the content is available and click OK. In the Completion pane, a success message appears.

Click Close Deploy the Receiver software to the software center. Right-click Receiver for Windows in the Configuration Manager console select Deploy. The Deploy Software wizard appears.

Select Browse against Collection (can be Device Collection or User Collection) where the application is to be deployed and click Next. In the Deployment Settings pane, set Action to Install and Purpose to Required (enables unattended installation). In the Scheduling pane, specify the schedule to deploy the software on target devices. In the User Experience pane, set the User notifications behavior; select Commit changes at deadline or during a maintenance window (requires restart) and click Next to complete the Deploy Software wizard. In the Completion pane, a success message appears. Reboot the target endpoint devices (required only to start installation immediately). On endpoint devices, Citrix Receiver for Windows is visible in the Software Center under Available Software.

Installation is triggered automatically based on the schedule you configure. Alternatively, you can also schedule or install on demand.

The installation status is displayed in the Software Center after the installation starts. Creating device collections. Launch the Configuration Manager console, click Assets and Compliance Overview Devices. Right-click Device Collections and select Create Device Collection. The Create Device Collection wizard appears. In the General pane, type the name for the device and click Browse for Limiting collection. This determines the scope of devices, which can be one the default Device Collections created by SCCM.

In the Membership Rules pane, click Add Rule for filtering the devices. The Create Direct Membership Rule wizard appears. In the Search for Resources pane, select the Attribute name based on the devices you want to filter and provide the Value for Attribute name to select the devices. Click Next.

In the Select Resources pane, select the devices that are required to be part of device collection. In the Completion pane a success message appears. Click Close.

In the Membership rules pane, a new rule is listed. In the Completion pane, a success message appears. Click Close to complete the Create Device Collection wizard. The new device collection is listed in Device Collections. The new device collection is a part of Device Collections while browsing in Deploy Software wizard.

Note When you set the MSIRESTARTMANAGERCONTROL attribute to False, deploying Citrix Receiver for Windows using SCCM might not be successful. As per our analysis, Citrix Receiver for Windows is NOT the cause of this failure. Also, retrying might yield successful deployment. The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language.

No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Citrix product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Disney fonts for mac. Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content.

Today I presented a session about Mastering Apple OS X with Configuration Manager 2012 R2 at the Swiss Configuration Manager User Group in Bern. Mac OS X support by Configuration Manager 2012 R2 has two ways of supporting Settings Management namely, managing settings through preferences directly or managing it through Shell Scripts.

One of the things I showed was the ability to change user preferences in Mac OS X. In an I described how you could use the $USER variable if you want to change a user setting, but for some reason how the Configuration Manager clients interacts with Mac OS X is changed. The context in which the Configuration Manager client runs and now changes preferences or running scripts is not the current user but the ROOT user.

System preferences can still be changed via the native Mac OS X preferences. So for this reason you see that nothing is changed when pointing to a preference file in a Configuration Item in Configuration Manager like this /Library/Preferences/com.apple.safari. The Tilde means current user so when checking and changing “ /Library/Preferences/com.apple.safari” you will actually check and change the file located in /users/root/Library/Preferences/. This took me a while to figure that out but, but it is logical that the Configuration Manager client runs in a different context since the client needs unlimited access to the system. So to be able to change user preferences, like the default homepage of Safari, we need to create a script that is able to gather and use the user that is currently logged on the Mac OS X device, check the setting and remediate it if necessary. Creating the discovery and remediation scripts Discovery Script The discovery script is used to find and return the value of a setting that you want to assess, so for us the first step is checking the current user, thanks to the great community I was able to figure this out quickly. With the command stat -f%Su /dev/console you are able to report the current user that is logged on.

Placing the current user to a variable which can be used in the script is done as follows myuser=$(stat -f%Su /dev/console). The second step is gathering the current setting of the default homepage of Safari. With the command defaults read you are able to read certain settings. If we combine the variable with the defaults read command you should be able to retrieve the current setting of the default homepage of Safari. The command defaults read /users/$myuser/library/preferences/com.apple.Safari HomePage will report the current value. Because we want to check the current value, it is wise to also place the value to a variable like shown above.

Setting rule to define the compliance for this setting Remediation Script If the default homepage needs to be remediated we need to create a remediation script. The first step is again retrieving the username of the user that is logged on to the system before we are going to actually remediate the preference setting. With the command default write you are able to change settings of a specific value in a preference file. To be able to change the default homepage of Safari you need to execute the following command; defaults write /users/$myuser/library/preferences/com.apple.safari HomePage -string “. After the setting is changed also the permissions to the com.apple.safari.plist file are changed so that users cannot access the file anymore. So you need to revert the permissions with the following command; chmod ugo=rwx /users/$myuser/library/preferences/com.apple.safari.plist. Meaning that all users will be having Read, Write and Access permissions to the file.

Peter is a Principal Consultant, Trainer and Enterprise Mobility (Configuration Manager/Microsoft Intune/Enterprise Mobility Suite) MVP with Daalmans Consulting with a primary focus on the Enterprise Client Management and Enterprise Mobility. Writing blogs and sharing his knowlegde since 2010 on ConfigMgrBlog.com / PeterDaalmans.com. Also one of the founders and leads of the Windows Management User Group Netherlands. Peter tries to speak every year on several events like TechDays Netherlands, ExpertsLive, IT/Dev Connections, BriForum, Midwest Management Summit, TechEd Australia, TechEd New Zealand and in 2017 Peter had the honor to speak at Microsoft Ignite. Author of four books about Configurtion Manager and Microsoft Enterprise Mobility +Security.