Microsoft is broadening support for cross-platform in System Center 2012. If you’re amongst the Linux-challenged now faced with monitoring or managing *NIX systems with System Center 2012, read on. I have some GREAT resources for you here. To get comfortable with any technology, you need to start by getting your hands dirty in the lab. A cheat sheet to show you what to do (and in what order) can be a big help. Below is a kind of homegrown resource kit of tools and tips from the web that will make the journey less daunting.
This is going to serve as the start of a collection of a cross-platform configuration notepad, so I’ll update from time to time. Feel free to share your tools and tips via comment or e-mail.
Step 1: Get a Linux Distribution
I love CentOS for two reasons: 1) it’s free and 2) it’s basically Red Hat Enterprise Linux (RHEL) with the licensing stripped out. What works on RHEL generally works on CentOS, with a few exceptions. Download at http://centos.org/
Step 2: Linux Integration Components (for Hyper-V)
In order to get a mouse to work in a Linux VM running on Hyper-V, you’re going to need the integration components. Download the integration components, mount the ISO to your Linux VM. You could walk through the process of extracting, installing, which is torture akin to waterboarding. See step-by-step at http://www.hyper-v-mart.com/Howto/Install_CentOS_5_VM_Step_by_Step.aspx. I recommend you DO NOT attempt to install the integration components before you check out what’s in Step 3.
Step 3: Say hello to your new best friend – the Set-LinuxVM PowerShell Module
This may be the best kept secret amongst PowerShell modules anywhere. The first time I used this module, the results were so amazing I nearly cried tears of joy. In a (long) PowerShell one-liner, this module will 1) install the Hyper-V integration components 2) Name your host 3) configure your IP stack (IP, default gate, DNS, etc.) 4) and installs / configures synthetic NIC. Other parameters include changing root password, setting time zone and extending logical volumes. It supports a wide variety of Linux distributions including Debian, Ubuntu, Centos, Fedora, Redhat, Suse and CloudLinux. Yusuf Ozturk deserves a medal for this!
EXAMPLE (Sets hostname and IP configuration to VM called “Linux01” which is CentOS)
Set-LinuxVM -VMName "Linux01" -Distro "CentOS" -Username "root" -Password "123456" -Hostname "server.yusufozturk.info" -IPAddress "192.168.2.2" -SubnetMask "255.255.255.0" `
-GatewayAddress "192.168.2.1" -PrimaryDNSAddress "22.214.171.124" -SecondaryDNSAddress "126.96.36.199"
Step 4: Load a GUI
US If you are a Windows person, you may want a graphical user interface (GUI). I like Gnome or KDE.
Install the GNOME Desktop (if you want a UI)
yum groupinstall "X Window System" "GNOME Desktop Environment"
Install the K Desktop Environment (another UI)
yum groupinstall "X Window System" "KDE (K Desktop Environment)"
To start the UI, type startx. You can configure the UI to load automatically, but I tend not to do this to conserve resources. If you would like to set the GUI to start automatically, you need to set the runlevel to 5 in the /etc./inittab. People tend to run CentOS (or RHEL) at runlevel 3 or runlevel 5 — both full multi-user modes. The default runlevel for the system is listed in /etc./inittab. To find out the default runlevel for a system, look for the line similar to the following near the top of /etc./inittab:
id:3:initdefault:To configure the GUI to load in the VM automatically, change the 3 to 5. Source: http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-boot-init-shutdown-sysv.html
MISC OS and VM Configuration
Here is the file you can update to manual configure your network settings. Be sure to connect the VM to the right virtual switch as well!
Configure the primary network adaptor (from the CLI)
Edit this file – /etc/sysconfig/network-scripts/ifcfg-eth0
Restart network services (so changes take effect)
service network restart
Here are a couple of must-have utilities to help remotely control the VM and do basic file transfers (like System Center agents) to and from the VM.
TIghtVNC – Free remote control utility (for full screen capability) – http://www.tightvnc.com/
WinSCP (secure copy) – http://winscp.net/eng/index.php
WinSCP is really handy when fixing up certificates on *NIX systems (comes up a lot when configuring OpsMgr X-Plat agent).
With cross-platform support already present or coming soon in System Center 2012 Virtual Machine Manager, Operations Manager, Configuration Manager and beyond, it’s not a bad idea to start getting comfortable if you’re org uses *NIX.
Here are a few additional private cloud-related posts featuring current and vNext System Center technologies that may be of interest