MOM v3 - sorry "System Center Operations Manager 2007"
Beta 2 is due in Q2 2006 (next month or two) and we'll ship in Q4 2006 (November/December). We have a R2 release scheduled for 12 to 18 months after we ship (early 2008).
This session was nearly all demos. Three big themes: Easy to Use, Knowledge Driven and Service Oriented. Demos of each theme - the two I can recall were:
Easy to use demonstrated how we've integrated with Active Directory to find devices to manage and for devices to find Operations Manager. Management Packs are self tuning for thresholds (i.e. we'll work out that your systems "normally" run at, say 30% - so this will be the threshold). Reports will be better and easier to author. Management Packs will be XML and will include versioning. We'll have one console with role based security (i.e. you'll only get the functionality in your console that you need/have been given) that gives very granular control. Console also has search to enable you to find what you're looking for.
Knowledge Driven demonstrated more, deeper knowledge in views, dashboards and inline tasks. The ability to define your own personalised workspace. We include the ability to monitor Vista & XP clients for utilisation, reliability and errors. Audit Collection Services has finally found a home - it will be in this release of Operations Manager. We include the ability for you to design your own diagram views of a distributed application - to model the relationships between all the components and to filter for specific components (i.e. I just want to see the components of my distributed, line of business application that are in error).
Operations Manager 2007 R2 will have deep integration with System Center 'Service Desk', will be able to manage Service Levels and Capacity.
More later. Dave.
WOW - that was pretty good.
Kirill Tatarinov (Corporate VP, Windows Enterprise Management Division) covered off System Center - current & future.
He positioned System Centre as the vehicle to deliver the "Manage Complexity, Achieve Agility" part of our People Ready message.
We'll be doing well if we help you to Ensure Your Business is Always Running, Eliminate Unneccessary Complexity and Establish a Responsive Infrastructure.
He covered off Infrastructure Optimisation (http://www.microsoft.com/io) - which is all about getting from where you are now to an eventual destination of Dynamic Systems (it's all about implementing Best Practices).
So System Center is Microsoft's branding for our 'knowledge driven management solutions family', which are Enterprise Ready, Flexible & Extensible.
He covered off what we have delivered so far (Data Protection Manager, Capacity Planner, Reporting Manager, SMS, MOM, etc and betas of some new stuff).
"SMS is dead - long live System Center Configuration Manager 2007" (previously known as SMS v4).
"MOM is dead - long live System Center Operations Manager 2007" (previously known as MOM v3) - public beta due in May/June.
The roadmad of future products is pretty exciting. The big investments are around Deeper Knowledge, a Self Service Portal, a CMDB and Workflow. Also products that cover Operations Management, Incident & Problem Management, Asset Lifecycle Management, Change Management and Configuration Management. Products are: SMS R2 (soon), System Center Operations Manager 2007 (this year), System Center Essentials 2007 (MOM & SMS & Reporting Manager in one box for small organisations - early 2007), System Center Configuration Manager 2007 (early 2007), System Center "Carmine" (Management of a Virtualised environment - late 2007), System Center "Service Desk" (late 2007) and System Center Operations Manager 2007 R2 (early 2008).
Some fantastic demos of all this, including one of SMS and AssetMetrix (a recent Microsoft aquisition) that enables "real" business level asset management - it showed how to report on what's installed side by side with what you own (licenses) - excellent..
Too much information in too short a time - there was definately more (but I can't remember it all). Must dash, I'm late for the next session.
More later, Dave.
Management in Windows Vista.
Three big goals: Maintain PC Configuration, Simplify Configuration Management & Desktop Troubleshooting and Task Automation.
This was a very good session with loads of demos.
The big thing to help maintain the PC's configuration is User Account Control - users can be dumb users and not admins. This restricts what users can do to a system (which will mean less downtime and higher productivity) and it will mean less requirement to re-image PCs, as the worst a user will be able to do is screw their own profile (it's quicker to put a new user profile onto a machine than it is to re-image it). Windows Resource Protection also plays a big part here - only the OS Trusted Installer Service can change system files or system registry settings. Of course all this is managed via Group Policy (something like another 500 new settings - including what removable devices are allowed and what can be done with them - i.e. only Read or read/Write). We've improved update management (less reboots, the ability to update an image and the ability to use auto-update to fix everything - not just critical Windows fixes). We also introduce Windows Remote management (WinRM) - a WS-Management, Firewall friendly remote access protocol.
I really like the new Event Viewer and Task Scheduler. All events are actionable - I can assign a tast to an event. The Reliability Analysis Console is very good - the ability to monitor reliability over time and map changes in reliability to application installations and windows configuration changes.
Virtual Server update
You can run over 1000 operating systems in Virtual Server (i.e. they are compatible). Microsoft Supports lots more than you'd think (we now support various versions of red Hat & SuSE Linux as well as Microsoft OS's - have a look at knowledge base article Q917437).
We released a new MOM management pack for Virtual Server R2 last week. It includes the ability to provide a diagram view of a Host machine with all it's guests. The really cool thing it offers is a 'Virtualisation Candidate Report' - so if you've got MOM, download the Virtual Server management pack and you'll be able to report on which of your existing servers are good candidates for virtualisation.
SMS SP1 understands Virtual Server as well - if you look in the resource explorer there's now a node that tells you if you're running in a VS.
When we released R2 of Virtual Server, we introduced 64-bit host support (not guest - yet) - this basically means more memory and more performance (twice as many guest machines on the same hardware). We also introduced Host Cluster Support - which gives you planned downtime support (move resource to another node on the cluster - move a guest machine in seconds) and unplanned downtime support (in the event of a cluster node failing, the guest machines will fail over to another node in the cluster (High Availability for ANY operating system / application).
We're working on the next release of Virtual Server (SP1 for R2) which is soon to be in beta (and will ship in early 2007). It will introduce support for Intel's VT and AMD's Pacifica technologies. It will also be Active Directory aware (virtual servers will register themselves in AD) and we'll have support for Volume Shadow Copy (VSS) - the ability to do snapshot backups of guest machines.
All pretty cool..
Windows Hypervisor won't ship until Longhorn Server.
Microsoft Management Summit 2006 - breakout sessions.
Been to a couple of pretty good sessions his morning (and flitted in and out of a few "not-so-good" ones). Pretty lame session on Data Protection Manager (DPM) - I lasted about 5 minutes before I realised I knew it all & could probably present the content better myself.
Sat in a good session on Antigen, MOM & ISA server. Covering off how by using the three products together to find out what's going on you can very simply change the settings to stop 'bad stuff' happening. There's a MOM management pack for Antigen now that looks for pretty much anything you'd ever need to know.
ISA server 2006 is due out this summer and includes some very useful features: the use of AD/AM for configuration & policy settings (taking it out of AD and not requiring a schema modification), logging direct to SQL, built in IDS and built in reporting (per user, per application and per site).
Off to eat lunch - more later..
I'm spending the week in San Diego attending the Microsoft Management Summit 2006.
I've just come out of the first keynote presentation delivered by Bob Muglia (VP for Server & Tools). Basically his presentation was an overview of what's on for the week. He covered off how Microsoft's "People Ready Business" messages touch IT.
His quick messages around how Windows Vista will work within businesses was pretty clear: Security & Compliance, Empowered Professional, Enabling the Mobile Workforce and Optimising the Desktop Infrastructure. He was explaining how Vista, MOM & SMS will work together and let slip that the next version of MOM will monitor Vista - Desktop monitoring. We got a little demo of using Group Policy to manage USB device installation restrictions (what devices are allowed or not) - better that filling the USB connector with epoxy.
We learned that what used to be codenamed "Monad" (our new command line scripting shell) is now called the "Windows PowerShell" - it looks pretty cool. It's got things like auto-complete, the ability to do whatif's and validate before executing the command. Exchange 2007 (used to be known as Exchange 12) will be the first product that uses it (it's GUI system manager, will just execute PowerShell commands). The next version of MOM will also use it.
We got a bit on Longhorn Server - more later..
And got a demo of the next version of SMS - how Windows Vista, Longhorn Server and SMS will handle Network Access Protection (NAP) - pretty neat. SMS finally has drag & drop and looks way easier to use (the update wiward has gone from 18 steps to 5).
A long piece on the Dynamic Systems Initiative and some product name anouncements: MOM becomes "System Centre Operations Manager 2007", SMS becomes "System Centre Configuration Manager 2007" and he anounced "System Centre Service Desk" (our ITIL/MOF based, SDM-based CMDB that is fully integrated into our other management products and includes all our product knowledge). We saw a demo of using Service Desk to deploy an update; issuing a change request, initiating a workflow and finally calling SMS to deploy the update. He also showed the self service portal.
Looks like I've got a pretty exciting week ahead of me, so watch this space. More after the sessions...
I've been asked a few times now about how to get Windows Vista running inside Virtual PC and/or Virtual Server. Finally here's the answer:
First up, to get it working you are going to need the latest Virtual Machine Additions that come with the current version of Virtual Server. Download it (for free) from http://www.microsoft.com/virtualserver. If you're a Virtual PC user, you're still going to need the Virtual Server Additions (VMAdditions.iso).
Create a new Virtual Machine. Give it at least 512Mb of memory. Put the Windows Vista DVD into the drive (either physically of mount the ISO). Boot the virtual machine. Setup starts. Enter your Product Key. Select the Custom Installation option (Upgrade is greyed out). Click Advanced. Create a new partition and format it. I've seen a "feature" whereby even though you now have a formatted partition on which to install, setup ignores it - reset the virtual machine and re-run setup - it always works second time around. Once you have selected a partition on which to install, setup will continue (go and do something else for a couple of hours - this part takes a long time). Setup will end and ask you for a username a computername and your timezone, then it automatically logs you on.
Next you have to install the Virtual Machine Additions - until you have done this, the machine is VERY SLOW.
For Virtual Server select: Edit Configuration, then scroll down and select Virtual Machine Additions, check Install Virtual Machine Additions and click OK.
For Virtual PC: Right Click the CD icon in the lower left hand corner of the Virtual PC window, Select Capture ISO Image, then Browse for VMAdditions.iso that you’ve taken from a Virtual Server install.
Click through the setup screens, reboot and you're done.
The local administrator's password is blank - so set it please.
Windows Vista speeds up with time, especially after the initial install - so leave it running for a long while (overnight) before you start "playing".
Enjoy - Dave.
I was presenting at a couple of TechNet events the other week in Cork & Galway. Part of my session was demonstrating how to extend MOM to do "other things". I'd read the Irish TechNet Newsletter the other week, where Darren Dillon (http://blogs.technet.com/ddillon) wrote about "Extending MOM into non-Microsoft environments". Basically me demo was how I'd taken Darren's article and learnt how do extend MOM.
One of the little demos I did was to using MOM to ping a non-Microsoft device on the network and report back on success or failure. This raised a very "interesting" licensing question: How do I license the non-Microsoft device that I am monitoring (I'm not using any Management Packs)?
In Cork, my answer was "I don't know - but I'll find out". I couldn't imagine Microsoft charging the same amount to ping a device on the network as we do to manage an Exchange server, for example. After the event, I found out that we do (or at least "did").
In Galway, when the same question came up, I was able to give the correct answer "You need a MOM Operations Management License (OML) for every device being managed". The feedback was that this didn't seem too fair. I took the action of giving that feedback to the product groups and to report back my findings.
So, I've done that and the response was that this is a "very grey area". I won't take responsibility for this (because it was probably happening anyway), but we have changed the way we license devices (see http://www.microsoft.com/mom/howtobuy/default.mspx). What we have now is two versions of the OML: an Enterprise version and a Standard version.
The Enterprise OML is for "Full Application and Server Management" and the Standard OML is for "Operating System and Basic Workload Management Only".
I still think it's a bit "grey", but at least we have responded to customer feedback.
The lesson learned is that you should always give feedback - we can't promise to change anything, but it happens sometimes (and if we don't get the feedback, we don't know there is an issue).