Hi, here’s Martin again.
With the cumulative Update 2 for Microsoft System Center 2012 configuration Manager there was added Support for some more Linux Distribution, and for me, I waited for the Support of Debian, Debian is my fav. Unfortunately only Debian 5 and Debian 6 is currently supported, Debian 7 “Wheezy” is not supported.
So, what do you Need?
You will have installed CU2 on your SCCM 2012 SP1 Infrastructure:
Next you will Need a installed Linux, I used the Mini Boot CD from Debian 6 to get a Standard Desktop System x64. This takes about 30 Minutes.
After this, you have to download the additional SCCM 2012 SP1 Clients, thus a Push Installation is not supported for Non-Windows Clients:
The following Linux/Unix and Mac Versions are supported:
Mac OS X 10.6 (Snow Leopard)
Mac OS X 10.7 (Lion)
Mac OS X 10.8 (Mountain Lion)
AIX Version 7.1, 6.1, 5.3
Solaris Version 11 (SPARC and x86) , 10 (SPARC and x86), 9 (SPARC)
HP-UX Version 11iv2 (PA-RISC and IA64) , 11iv3 (PA-RISC and IA64)
RHEL Version 6 (x64 and x86) , 5 (x64 and x86), 4 (x64 and x86)
SLES Version 11 (x64 and x86), 10 (x64 and x86), 9 (x86)
CentOS Version 6 (x64 and x86), 5 (x64 and x86)
Debian Version 6 (x64 and x86), 5 (x64 and x86)
Ubuntu Version 12.4 LTS (x64 and x86), 10.4 LTS (x64 and x86)
Oracle Linux 6 (x64 and x86), 5 (x64 and x86)
Now you got all the prerequisites, extract the downloaded additional Clients, and bring the data on your Linux Client. If this is done, start a console and elevate it to get root Access. If this is done, navigate to the Folder of the Client Installation files and type:
chmod +x install
When this is done, start the Installation by:
./install –mp $FQDN-SCCM -sitecode $Sitecode ccm-Universal-x64.$Downloaded-Version.tarFor more Installation properties of the Linux Client, look at this TechNet article: http://technet.microsoft.com/en-us/library/jj573939.aspx#BKMK_CmdLineInstallLnUClient
If you would like to control the Installation procedure, refer to: /var/opt/microsoft/scxcm.log
So with a HTTP hierarchy, the Client will now create a self signed certificate and uses this to identify to SCCM. The Client will now Show up in the SCCM console, and the most important part now is to “Approve” (right click on the Client and choose “Approve”) the Client, because the Client is handled as a Workgroup Client (with Standard Settings, only members of the trusted forests are automatically approved).
If you would like to force a policy download just type the following command in the console:
/opt/microsoft/configmgr/bin/ccmexec -rs policy
Or to start a Hardware Inventory:
/opt/microsoft/configmgr/bin/ccmexec -rs hinv
If you want to increase the Level of Information written to the log file, modify the following file: /opt/microsoft/configmgr/etc/scxcm.conf
Refer to this link for more Information: http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_LogFilesforLnU
And now what? I want to go chatting with IRC, and for this, I want to deploy IRCII on my Debian via SCCM 2012, so, I have to create a legacy Package, because the new Application Model does not work for Linux Clients. So I don’t need a package Location, because in Linux, usually the data for an application is downloaded through the repository. This is the command used for the Installation of IRCII:
apt-get install ircii -y
So from now on, you can manage and Report Linux Clients aswell 🙂