Share This Post

ConfigMgr 2012 SP1 Beta & Linux Client

Hi All,

over the past few days i was playing with SCCM 2012 SP1 Beta and Linux…and i have to say that there are few bugs (i'll see bellow), but it works quite well…

anyway…before you start, you need a Linux box…I'm using Suse Enterprise Server 11. I downloaded it from https://www.suse.com/ and installed it….i used the default settings and after the installation, checked the network was working fine (i had a couple of problems with vmware 9 network not being able to ping the dns properly…) i added the machine to the domain. as far as i know it is not required, but i wanted to see how easy it was…and it was easy…

2nd..you need to download the linux client, and you can get the .exe from http://www.microsoft.com/en-us/download/details.aspx?id=34609

next step is to extract the file you just download

after this, copy all files to the linux server. I copied them to CM12Client (note: wihtout spaces. this is because i tried before with spaces and it did not work) and as root (i used sudo) use the command ./install (all switches you can find here http://technet.microsoft.com/en-us/library/jj573939.aspx). as you can see, i used -mp for the Management Point, -sitecode for the Sitecode, -fsp for the fallback status point and the name of the taf file

after the installation, if you open the "windows explorer" equivalent, navigage to /opt/microsoft/configmgr

because of a but at this moment, all new linux client will be always not approved…to see this, add a column approved and approve them

after this, stop the client (a list of the switches and location you can find http://technet.microsoft.com/en-us/library/jj573937.aspx. note that for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -s)

delete the cookie file using rm /opt/microsoft/configmgr/root/ccm/policy/servercookies.xml

start the client (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -d)

perform the policy refresh (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -rs policy)

and as soon as it finishes, request the hardware inventory (for Suse 11, you'll be using /opt/microsoft/configmgr/bin/ccmexec -rs hinv)

but keep in mind,Always monitor log file. as we don't have cmtrace you can use tail -f /var/opt/Microsoft/scxcm.log (**Thanks to Rob Marshall for this tip)

the logs are created in 2 different places (unfortunatelly the documentation has the wrong place at this moment)

on suse 11, the scxcm.log is located on /var/opt/microsoft

and the scxcmprovider.log is located on /varopt/microsoft/nanowbem instead /var/opt/microsoft/nanowbem

 

Couple of extra links:

http://technet.microsoft.com/en-us/library/jj573940.aspx

http://technet.microsoft.com/en-us/library/jj573941.aspx

http://technet.microsoft.com/en-us/library/jj573945.aspx

 

Share This Post

Leave a Reply