SCCM agent installation fails in Linux Servers

If you come across with an issue related to SCCM agent installation on top of Linux Servers, below might be a one reason for it. Specially if you are not familiar with Linux.

The error is as follows;

The OS /Version /Architecture of this archive file does not match this system, exiting.

The given error little confuse when it comes to the trouble shooting. The reason is, its says that the OS Version Architecture is not match  or something. So quickly what comes to or mind is that, does this agent version not compatible with this Linux version!!!!! 😦

Check the below screen


However, the issue is not because of the OS version or Agent version. When you copy the Agent in to Linux Server and if you are copying the entire folder and if the folder name contains spaces, it will lead to prompt the error which i have highlighted above.


So in my case I have copied the Agents Contained folder name call Linux Client. in this case the folder name contains the spaces in between Linux and Client.

The solution,

simply remove the spaces in the folder name and keep it as simple. So in my case I am going to rename it as Client and see the results after I ran the same command.







Hi Everyone,

Today I am going to configure the Parallels integration in to SCCM 2012 R2 server. In my Part 1 which is about the step-by-step-how-to-integrate-parallels-mac-management-with-sccm-2012-r2-part-1, I have explain and given the guidance how to prepare the general requirements before do the Parallels integration in to SCCM 2012 R2. So in this step which is Part 2, I will show you how you need to do the integration.

1- Get the Parallels installation files and make it available on the site server (In my case I have only one Primary Server). Run the Setup file with Administrative Privileges. ( I am using the Parallels 3.5 Version in this Lab). Figure 1.0


Figure 1.0

2- On the Welcome page Click Next to continue. Figure 1.1


Figure 1.1

3- On the License Agreement Page Accept the Terms and Conditions and Click Next to Continue. Figure 1.2


Figure 1.2

4- On the Select Component Page Select the Below Two Option if you plan only to Manage the MAC devices using SCCM.

I. Configuration Manager Proxy

II. Configuration Manager Console Extension

In case if you plan to do a MAC OS deployment from the SCCM Server, then you must Enable the Net Boot Server Option. It is purely based on your requirement. But it is optional.

However in my case I have select the all three option, since my future Posts I am planning to showcase the MAC OS deployment via SCCM. J

Check Figure 1.3


Figure 1.3

5- On the Ready to Install Page, Click Install tab to start the installation based on your selection you have done on previous steps.

Check Figure 1.4


Figure 1.4

6- On the Setup Completed Page, You have the Option to select the configuration Part of the Parallels Add-in you have installed in SCCM site Server. This is the Place you configure how the Parallels need to communicate and work with SCCM server. However, If you Un-tick this option, still you have the rights to configure it is in later stage.

Although, in my case I am going to configure the Parallels Add-in now. Click Finish tab to open the configuration page.

Check Figure 1.5.


Figure 1.5

7- On the SMS Provider Location Page, Select the Local server (In my case it is Local server, because I have only one site server). However, if you have multiple site servers and if you install the Parallels Add-in in a different server, then you have to give the remote server IP or FQDN which runs the SMS service and select Next. Check the Figure 1.6.


Figure 1.6

8- On the Configuration Manager Proxy Service Account page, provide the User Credential who has the access (Read/Write) to SMS provider and click Next to continue.

Note- Configuration Manager Proxy enable the MAC clients to communicate with SCCM server. In my case I used the Service Account which I am using in my SCCM server. Look in to Figure 1.7.


Figure 1.7

9- On the Next page it will check whether all the Prerequisites are met or not. Once it confirmed all the needs are there, then just Click Next as shown in the Figure 1.8.


Figure 1.8

10- On the Client certificate management settings page, check HTTP and click Next to continue. If you using Certificate Authority, then you must select the HTTPS option. In my lab I don’t use the Certificate Authority. Check the Figure 1.9


Figure 1.9

11- On the Role-Based Security page configure the user permissions as you prefer and Click Next to Continue as shown in Figure 1.10.


Figure 1.10

12- Next is about the Configuration Manager Proxy Communication Ports setup page where you have to mentioned the TCP ports which use for the communication in between SCCM server and the MAC clients. So in my case I left the Default Ports and Click Next to Continue. Check Figure 1.11


Figure 1.11

13- On the Customer Experience page select the both option you prefer and Click Next to continue. Refer to Figure 1.12


Figure 1.12

14- Once you configure the all above steps accordingly, Click Finish Tab to Start the Configuration Manager Proxy settings updates. Figure 1.13


Figure 1.13

15- Once all successfully updated, you will get a final message as shown in below Figure 1.14.


Figure 1.14

16- Once the Configuration Manager Proxy and Configuration Manager Console Extension configuration completes, it will automatically prompt for the NetBoot Sever Configuration wizard. This is the place where you need to configure for MAC OS deployment configurations to work with SCCM server.

17- On the SMS Provider Location page, Select the Server which the SMS Provider service is running and Click Next to continue the setup wizard as shown in Figure 1.15


Figure 1.15

18- Under Parallels NetBoot Server service account, assign the user who has Read/Write Permission for the SMS provider and Click Next to Continue as shown in Figure 1.16.


Figure 1.16

19- Next step is about to assign the folder path where you want to store the disk image files (.dmg). Once you assign the storing path just Click Next to continue. Refer to Figure 1.17


Figure 1.17

20- On the Enable Unknown Mac support page, Enable the option if you want to allow MAC OS deployment to unknown MACs. In my case I have enable the Unknown Mac Support and Click Next. Refer to Figure 1.18


Figure 1.18

21- On the Summary page, verify the configurations you going to do and Click Next to start the installation. Refer to Figure 1.19


Figure 1.19

22- Finally verify the configuration successfully completed and Click Finish as shown in Figure 1.19.


Figure 1.19

So if you have followed the above configuration accordingly as I stated in each and every steps, you will be end up with successful story at now. However, the next blog post which is Part 3, I will show you how to Enable the Network Discovery to find the MAC devices in your infrastructure. Keep in Touch for Part 3 J


Related Links;