• Getting Azure Pack Up and Running In Your Lab…

    I finally got around to doing this in my lab last week.  Overall, pretty straightforward install, especially if you follow the blog post authored by Anders HERE.

    Another good link from TechNet here – including links to the Web Platform Installer to get WAP started.  http://technet.microsoft.com/en-us/library/dn296439.aspx

    Azure Pack setup success!!

    image

    A few things worth noting from my experience (and I’ll update this blog as I add more too my lab setup)

    • You can get WAP and SPF on the same server.  No issues there.
    • The SPF install comes off the Orchestrator Install media.  Mount the Orchestrator R2 ISO image and navigate to the SPF folder and click the setup.exe

    image

    • In my case, I ran VMM on a separate server (you’ll need to VMM console installed on the SPF/WAP server) and that VMM server manages a Hyper-V host that I’m using to deploy VM’s.
    • IMPORTANT:  Make sure you get everything updated to System Center 2012 R2 UR2.  INCLUDING SPF!!  There’s a separate update specifically for SPF.  I had an issue that was a pain to troubleshoot (thanks to the product team dev folks for the quick assist) because I had not installed the SPF UR2 update to the WAP/SPF server.  I had installed the UR2 for Orchestrator web service but that was not needed/required.  Also make sure that you don’t forget to apply the SQL script for UR2 to the VMM database.  You won’t be able to provision VM’s if you don’t do that.

    Otherwise, the install is pretty straightforward.  Just make sure you read through the setup guide first to prepare for any steps that you need to do in advance or can do in parallel to save you some time.

    One thing that’s worth doing is getting your VM setup with Server 2012 R2, latest updates, get Azure Pack installed but not configured as well as SPF with the appropriate updates and then create a checkpoint on the VM.  It was nice to have that checkpoint available to go back to when I messed up my configuration the first time and didn’t have to spend a half hour again on those installation steps.

    Next step is getting RD Gateway going (required for RDP connections), some add-ons, connecting with Service Manager and whatever else I can find. 

    Here’s the main System Center 2012 R2 UR2 link.  You can download all the packages there for install.  If your servers are set for automatic updates, they’ll get pulled down there too so check first to see if they are already installed.

    http://support.microsoft.com/kb/2932881

    Have fun!!

  • CentOS Linux - Monitoring Setup with SCOM 2012 R2

    I'm not a Linux guy...know very little but was able to pretty quickly get a CentOS 6.5 VM managed by both SCCM and SCOM 2012 R2. I did run into a few 'gotcha's' and thought I'd share here to hopefully save some of you the same experience...

    You can use Kevin Holman's Blog post here as a backdrop for the basic steps.

    http://blogs.technet.com/b/kevinholman/archive/2012/03/18/deploying-unix-linux-agents-using-opsmgr-2012.aspx

    You need to create the Linux Resource Pool, certificate stuff (in my lab I have only 1 management server so that part is easy - you just run the export command in the blog post...and that's it) and then run the discovery process.

    One important thing I missed up front is that the Linux VM needs to be able to resolve via DNS.  There is an IP lookup in the discovery wizard, but you need to have A and PTR records associated with the machine in DNS.  In my case, I created a static A record pointing the hostname I assigned during the CentOS setup to the OS with it’s IP address.  I clicked the checkbox to create the associated PTR record.  If you don’t create the PTR record you’ll get an error during the discovery (meaning, it won’t find anything).

    A couple things you’ll need to do to the VM:

    1) Make sure SSH is running.  That’s how you will connect to it via SCOM.

    2) You may run into a firewall issue – you’ll either want to disable it (lab) or poke holes.  SCOM needs ports 22 and 1270 open to communicate with the VM for discovery/management.

    3) OpenSSL needs to be installed/running as well.

    The one thing you will have to do is make sure you have the latest/greatest Linux/UNIX MP's installed.

    http://www.microsoft.com/en-us/download/details.aspx?id=29696

    Click the download link and make sure you scroll down a bit to pull the R2 bits down.

      image

    You will then import these MP’s into SCOM 2012 R2.  You should get to this version.  The key for CentOS is getting the Universal MP’s installed.  I went ahead and installed others as well…future proofing myself.   1021 is the version that you’ll get from the above download.

    image

    After a successful discovery you’ll click the “MANAGE” link and it will install the agent and put the OS under management.

    image

    image

    By the way, if you are interested in getting this working with SCCM (2012 R2 agent installed and managed by SCCM) – there is a great tutorial here. 

    http://www.windows-noob.com/forums/index.php?/topic/9357-how-can-you-manage-linux-based-clients-in-system-center-2012-r2-configuration-manager/