Well, didn't today make me smile with pride.
Busy working away when this e-mail landed in my inbox...
This is my first year that I've been awarded this and I hope all the blogging, tweeting and book writing has been useful and helped at least a few people.
No time to rest on my laurels now... more content and books to come!
Regards,
Steve Beaumont / MVP
Technical Director / PowerONPlatforms
Twitter: @StevybSC
Blog: http://systemscentre.blogspot.com/
Community: http://cloudoscommunity.com/
Showing posts with label Cloud. Show all posts
Showing posts with label Cloud. Show all posts
Tuesday, 1 October 2013
Tuesday, 17 January 2012
Microsoft Private Cloud, System Center 2012 and License Changes
http://www.microsoft.com/business/events/en-us/PrivateCloudExec
Today Microsoft announced a change in the licensing for System Center.
The multiple SKUs and versions have been greatly simplified down to just 2 (yes that's just TWO!!) offerings.
That's a big change from currently the four different licensing schemes, Datacenter, Enterprise, Single Enterprise, and Single Standard.
The new license types are:
System Center Standard - Manage a physical server, or very lightly virtualised (2 VM's)
System Center Datacenter - Manage unlimited VM's on a physical host
Both the System Center license types contains the following products:
Another couple of major changes....
Licences are now only needed for endpoints being managed, no management servers or SQL licensing. (Yep, you heard it right, SQL licenses for the SC Management Servers is now included in the new licenses)
Both types (Std & DataCenter) are both processor based Licenses, but covers up to two processors per license.
There is also a transition model from the old licensing model to the new.
If you have Software Assurance coverage on your current System Center licenses at the time of System Center 2012 General Availability, you will receive the following System Center 2012 Server ML grants at the ratios listed below:
That covers off licensing Server Operating Systems, however for the Configuration Manager and Service Manager parts of System Center for example, you still require Client Management Licenses for non-server OSE's
Microsoft also have a useful interactive site online that can provide some common scenario questions about System Center 2012 licensing:
http://www.microsoft.com/licensing/about-licensing/SystemCenter2012.aspx
Further information:
System Center 2012 Licensing Datasheet
System Center 2012 Licensing FAQ
Today Microsoft announced a change in the licensing for System Center.
The multiple SKUs and versions have been greatly simplified down to just 2 (yes that's just TWO!!) offerings.
That's a big change from currently the four different licensing schemes, Datacenter, Enterprise, Single Enterprise, and Single Standard.
The new license types are:
System Center Standard - Manage a physical server, or very lightly virtualised (2 VM's)
System Center Datacenter - Manage unlimited VM's on a physical host
Both the System Center license types contains the following products:
- Configuration Manager
- Service Manager
- Virtual Machine Manager
- Operations Manager
- Data Protection Manager
- Orchestrator
- App Controller
- Endpoint Protection
Another couple of major changes....
Licences are now only needed for endpoints being managed, no management servers or SQL licensing. (Yep, you heard it right, SQL licenses for the SC Management Servers is now included in the new licenses)
Both types (Std & DataCenter) are both processor based Licenses, but covers up to two processors per license.
There is also a transition model from the old licensing model to the new.
If you have Software Assurance coverage on your current System Center licenses at the time of System Center 2012 General Availability, you will receive the following System Center 2012 Server ML grants at the ratios listed below:
That covers off licensing Server Operating Systems, however for the Configuration Manager and Service Manager parts of System Center for example, you still require Client Management Licenses for non-server OSE's
Microsoft also have a useful interactive site online that can provide some common scenario questions about System Center 2012 licensing:
http://www.microsoft.com/licensing/about-licensing/SystemCenter2012.aspx
Just to pre-empt the most likely couple of questions likely to get asked around this:
Q) Are there separate offerings without SQL Server Technology?
A) No. All System Center 2012 products include the right to run a runtime version of SQL Server Technology to support System Center so there are no longer separate offerings.
A) No. All System Center 2012 products include the right to run a runtime version of SQL Server Technology to support System Center so there are no longer separate offerings.
Q) Do I need to purchase separate Management Server Licenses to run Management Server software?
A) No. With System Center 2012, the right to run Management Server software is included with the Server MLs and Client MLs.
A) No. With System Center 2012, the right to run Management Server software is included with the Server MLs and Client MLs.
System Center 2012 Licensing Datasheet
System Center 2012 Licensing FAQ
Labels:
2012,
Cloud,
ConfigMgr,
Configuration Manager,
DPM,
License,
Licensing,
Operations Manager,
OpsMgr,
SCCM,
SCO,
SCOM,
SCORCH,
SCVMM,
Service Manager,
System Center
Friday, 9 September 2011
Private Cloud, make sure you choose right!
This is brilliant Microsoft advertising.
It's good to see that Microsoft have got a sense of humour, but the points it mentions are valid.
One thing in particular did catch my attention when the IT guy asks Tad if his solution would allow him to see deep inside his apps (1:30 min though).
Rather than Tads blank expression reply...
This is where System Center comes into its own and the upcoming 2012 wave will just blow the competition out of the water.
Imagine having your data centre built as a private cloud infrastructure using System Center as the pivotal part of the solution. When the IT guy then asks if the solution would allow him to find out performance problems, bottle necks and root causes the reply would be a resounding YES!
Virtual Machine Manager handles the virtualisation management piece of the solution, providing management of the "cloud" and dynamically assigning resources where and when required to ensure optimum performance. However, with Operations Manager sat within the environment gathering events and metrics constantly it would alert IT staff to potential problems, automatically raising Incidents directly within Service Manager. The necessary and relevant information is immediately at hand for the engineer to work on resolving the incident, coupled with Operation Managers ability to deeply dive into .Net applications to such a level as to even show which line of code is at fault
Once the root cause is identified using the information surfaced through Operation Manager (Events & Performance) and Service Manager (Configuration & Changes), then, if for example an update was required, the necessary Change Control would be raised in Service Manager to apply the update and once approved Orchestrator could pick up the change. Orchestrator could proceed to automate the remediation by talking across the infrastructure management products to take a backup of the system using Data Protection Manager, put the system into maintenance mode to suppress alerts in Operation Manager then create the necessary tasks with Configuration Manager to deploy the update to the system and finally check the success and report this information back into Service Manager for later review and analysis.
Once service is restored and operating normally, it may be deemed that either during a known busy period or to support an advertising campaign for example, that the corporate web site will need extra resources to cope with demand. A Change Request is raised within Service Manager and once approved Orchestrator can take on the responsibility of setting the wheels in motion for adding those resources for example by instructing Virtual Machine Manager to provision a new Virtual Server, Configuration Manager to deploy a new Operating System and any required software along with updates, settings and configuration. Orchestrator would enable the bringing online of a new web server and adding it into a web farm as extra resources with little to no interaction of highly skilled technical resources.
This is all so easily possible due to the tight integration that is now present within the System Center product suite and is only going to continue to grow stronger with this next 2012 wave and beyond.
The tight integration allows for data about the infrastructure to flow across products, negating the need for duplication of effort or manual input.
The end net result is a very dynamic, private cloud infrastructure and much more efficient service delivery model.
This has several other benefits such as:
One key thing to note, while I’ve mentioned various Microsoft products such as Data Protection Manager as the backup tool and Hyper-V as the virtual hypervisor, this doesn’t have to be the case
Microsoft have done a real good job of “growing up” these last couple of years and have finally embraced the fact that data centres are heterogeneous environments. So while I’ve mentioned the best products (sorry, couldn’t resist) you can still use the System Center tools like Virtual Machine manager to manage your VMWare or Citrix hypervisors and Operations Manager to monitor your Solaris and Unix servers while Orchestrator can use integration packs to work with other vendor systems such as BMC Remedey and HP Openview etc
Why is this worth mentioning? Because it means that to implement a private cloud and reap the benefits doesn’t require a complete rip and replace of your current infrastructure and the costs associated. You can introduce the tools, methodologies and principals behind the cloud now as you plan towards full implementation (Based on Hyper-V et al of course!)
Finally, as we start to move towards the release of the System Center 2012 wave of products, the dedication Microsoft has towards enabling businesses to implement private clouds and also link them with public clouds is very evident with new product features such as Virtual Machine Manager 2012's ability to provision storage and networking elements, Operation Manager 2012's increased Networking & Application Monitoring along with more Azure integration, Configuration Manager 2012's more user centric approach and it's support of "IT Consumerisation" and Service Manager 2012's expansion of ITIL/MOF process support with Service Requests and the further integration with Orchestrator to help with automation of processes all show Microsoft is serious about making this all a reality, and achievable for all, not just the biggest companies around with the most cash as these solutions scale both up and down.
http://www.microsoft.com/en-us/server-cloud/private-cloud/default.aspx
http://www.microsoft.com/en-us/server-cloud/system-center/default.aspx
Footnote:
This is only scratching the surface of what the System Center products can do, areas like reporting, SLA management, patching, baselines, tuning etc etc would make this post just too long to read.
It's good to see that Microsoft have got a sense of humour, but the points it mentions are valid.
One thing in particular did catch my attention when the IT guy asks Tad if his solution would allow him to see deep inside his apps (1:30 min though).
Rather than Tads blank expression reply...
This is where System Center comes into its own and the upcoming 2012 wave will just blow the competition out of the water.
Imagine having your data centre built as a private cloud infrastructure using System Center as the pivotal part of the solution. When the IT guy then asks if the solution would allow him to find out performance problems, bottle necks and root causes the reply would be a resounding YES!
Virtual Machine Manager handles the virtualisation management piece of the solution, providing management of the "cloud" and dynamically assigning resources where and when required to ensure optimum performance. However, with Operations Manager sat within the environment gathering events and metrics constantly it would alert IT staff to potential problems, automatically raising Incidents directly within Service Manager. The necessary and relevant information is immediately at hand for the engineer to work on resolving the incident, coupled with Operation Managers ability to deeply dive into .Net applications to such a level as to even show which line of code is at fault
Once the root cause is identified using the information surfaced through Operation Manager (Events & Performance) and Service Manager (Configuration & Changes), then, if for example an update was required, the necessary Change Control would be raised in Service Manager to apply the update and once approved Orchestrator could pick up the change. Orchestrator could proceed to automate the remediation by talking across the infrastructure management products to take a backup of the system using Data Protection Manager, put the system into maintenance mode to suppress alerts in Operation Manager then create the necessary tasks with Configuration Manager to deploy the update to the system and finally check the success and report this information back into Service Manager for later review and analysis.
Once service is restored and operating normally, it may be deemed that either during a known busy period or to support an advertising campaign for example, that the corporate web site will need extra resources to cope with demand. A Change Request is raised within Service Manager and once approved Orchestrator can take on the responsibility of setting the wheels in motion for adding those resources for example by instructing Virtual Machine Manager to provision a new Virtual Server, Configuration Manager to deploy a new Operating System and any required software along with updates, settings and configuration. Orchestrator would enable the bringing online of a new web server and adding it into a web farm as extra resources with little to no interaction of highly skilled technical resources.
This is all so easily possible due to the tight integration that is now present within the System Center product suite and is only going to continue to grow stronger with this next 2012 wave and beyond.
The tight integration allows for data about the infrastructure to flow across products, negating the need for duplication of effort or manual input.
The end net result is a very dynamic, private cloud infrastructure and much more efficient service delivery model.
This has several other benefits such as:
- End users of the service gain improvements around time taken to respond to requests
- Total Cost of Ownership is lower to support and maintain the environment
- IT staff have more time to be proactive rather than constantly being reactive
- High control of the environment can be achieved, helping with compliance (PCI, CoCo, Sarbanes Oxley)
- Conversion of processes to automation helps with both workload reduction and better auditing of changes to the environment
- Paves the way for Platform as a Service (PaaS)
One key thing to note, while I’ve mentioned various Microsoft products such as Data Protection Manager as the backup tool and Hyper-V as the virtual hypervisor, this doesn’t have to be the case
Microsoft have done a real good job of “growing up” these last couple of years and have finally embraced the fact that data centres are heterogeneous environments. So while I’ve mentioned the best products (sorry, couldn’t resist) you can still use the System Center tools like Virtual Machine manager to manage your VMWare or Citrix hypervisors and Operations Manager to monitor your Solaris and Unix servers while Orchestrator can use integration packs to work with other vendor systems such as BMC Remedey and HP Openview etc
Why is this worth mentioning? Because it means that to implement a private cloud and reap the benefits doesn’t require a complete rip and replace of your current infrastructure and the costs associated. You can introduce the tools, methodologies and principals behind the cloud now as you plan towards full implementation (Based on Hyper-V et al of course!)
Finally, as we start to move towards the release of the System Center 2012 wave of products, the dedication Microsoft has towards enabling businesses to implement private clouds and also link them with public clouds is very evident with new product features such as Virtual Machine Manager 2012's ability to provision storage and networking elements, Operation Manager 2012's increased Networking & Application Monitoring along with more Azure integration, Configuration Manager 2012's more user centric approach and it's support of "IT Consumerisation" and Service Manager 2012's expansion of ITIL/MOF process support with Service Requests and the further integration with Orchestrator to help with automation of processes all show Microsoft is serious about making this all a reality, and achievable for all, not just the biggest companies around with the most cash as these solutions scale both up and down.
http://www.microsoft.com/en-us/server-cloud/private-cloud/default.aspx
http://www.microsoft.com/en-us/server-cloud/system-center/default.aspx
Footnote:
This is only scratching the surface of what the System Center products can do, areas like reporting, SLA management, patching, baselines, tuning etc etc would make this post just too long to read.
Thursday, 9 December 2010
6 Steps to Get Ready for Private Cloud
I was reading Mohamed Fawzi's blog today and noticed this link he had to a useful MS Blog post:
http://blogs.technet.com/b/windowsserver/archive/2010/11/11/6-steps-to-get-ready-for-private-cloud.aspx
Replicated here for my own reference and laziness.
Improve data quality in your identity infrastructure - audit existing users and groups to ensure your ad store is running only accurate data
Enable Federated identity - self-explanatory, but it's a big part of bridging the gap between public and private clouds
Enable all the building blocks of a private cloud - that includes Windows Server 2008 R2 with Hyper-V, an optimized Active Directory store and System Center (notably Configuration Manager and Virtual Machine Manager).
Standardize and automate your processes and workflows - to take the best advantage of a private cloud infrastructure, you'll need to build standardized server, platform and application packages and templates. That's only possible if you've done your homework and standardized the processes and workflows that those software packages will support.
Think about how the IT Pro role needs to change - the cloud enables huge efficiencies in the data center. Be a hero today as you enable the cloud, but work to become a Director tomorrow. Combine a deep knowledge of your business' needs, future directions and work processes with your expertise in technology. Use this combination and the power of the cloud to not just enable IT for your business, but to actually turn IT into a competitive edge the business can directly convert into new business and revenue. That's the big win for tomorrow's cloud IT pro.
Last, take advantage of Microsoft guidance - We'll be releasing lots of guidance, both technical and higher-level, regarding the journey to cloud computing in the coming months. Check the Microsoft cloud pages, TechNet's cloud resources and especially the Hyper-V Cloud Fast Track pages for in-depth technical guidance. There's much more to come, so check back often.
http://blogs.technet.com/b/windowsserver/archive/2010/11/11/6-steps-to-get-ready-for-private-cloud.aspx
Replicated here for my own reference and laziness.
Thursday, 11 November 2010
IT as a Service and "The Cloud"
We were discussing in the office this morning Marnix Wolf's post about TechEd day 3 and "The Cloud" as well as some of the videos of the sessions at TechEd that Marnix was blogging about.
That got us talking about just how far off "The Cloud" are we in our infrastructure.
So I finally got home from the office and thought I'd blog our discussion, but as I routinely do, I thought I'd check the other various blogs first and what do I see?
Only a post on the System Center Nexus blog that is almost a list of everything we discussed this morning!
http://blogs.technet.com/b/systemcenter/archive/2010/11/11/what-is-your-journey-towards-it-as-a-service-allow-microsoft-to-accelerate-your-journey.aspx
Basically we discussed this morning that we're not that far away from being considered to be running a cloud environment.
So what are we missing?
Well really we're just missing the Self Service components. There's some self serve features in Service Manager and some in ConfigMgr 2012, but these are around software deployment rather than the data center.
So we'll be taking a look at System Center Virtual Machine Manager Self-Service Portal 2.0
Now to enable this we really need to look again at Virtual Machine Manager 2008 R2.
We've looked at it before, and even though we're a VMWare estate, we was impressed by it. However we were really looking forward to the integration with Operations Manager, but hit a major fault/bug and had to shelf it as there was no way to fix it.
With those two additions we should have an estate that allows for quick provisioning of services in a streamlined process with monitoring and automation to provide for capacity increases on demand/response, erm, isn't that a cloud?
Moving forward from there, the 2012 roadmap of System Center products are only going to help make this even easier to achieve with even more integration and focus on "The Cloud". Add to that Azure and Server Application Virtualization that allow you to re-host or repackage your existing applications so they can run in Windows Azure and I can see exciting times ahead!
That got us talking about just how far off "The Cloud" are we in our infrastructure.
So I finally got home from the office and thought I'd blog our discussion, but as I routinely do, I thought I'd check the other various blogs first and what do I see?
Only a post on the System Center Nexus blog that is almost a list of everything we discussed this morning!
http://blogs.technet.com/b/systemcenter/archive/2010/11/11/what-is-your-journey-towards-it-as-a-service-allow-microsoft-to-accelerate-your-journey.aspx
Basically we discussed this morning that we're not that far away from being considered to be running a cloud environment.
- Our infrastructure is already virtualised, apart from some key Tier 1 apps like Exchange and our SQL Clusters meaning we can rapidly commission servers as users request them.
- We deploy applications via Configuration Manager 2007 R3 meaning we can rapidly deploy applications to large volumes of users/devices as Service Requests come in and are looking forward to ConfigMgr 2012 and user targeting.
- We monitor our estate using Operations Manager 2007 R2 giving us that insight into the estate and how it's performing, along with using distributed application monitoring as we move our mind set towards monitoring applications and their performance as a service that we deliver so we can talk about Application Service SLA's rather than "This server had 99.9% uptime" which means nothing to the user.
- We've got Opalis that we're using to help us automate our common tasks, as well as the more complex and time consuming processes. This also helps strengthen our ITIL implementation by ensuring things are in ITIL terms, Standardised, Repeatable & Auditable.
- We've started moving from 2003 Terminal Server with XenApp 4.5 to 2008 R2 Terminal Services with XenApp 6 and utilising App-V to isolate our applications on those servers. This allows us to rapidly deploy corporate applications (Using ConfigMgr, App-V and the Citrix connector) to large numbers of users, both within our Intranet and remote users with no downtime.
- I was also asked the other day about user virtualisation. Well we already re-direct the users documents, pictures etc to a central network store, enabling easier backup and security. We don't really need to use roaming user profiles as the desktops are that locked down and most apps are published via Citrix that there isn't that many user settings left that we get asked why they don't follow the user, except Outlook signatures that I really need to get following users.
- I'm in the process of implementing Service Manager 2010 with pre-production working with our customisations etc and waiting to move into live production. This will help by dragging all that data from AD, SCCM & SCOM and giving us not only a better insight into the CI's in our environment, but be able to finally relate them all together and see what changes affect what and automate/streamline our processes (We're also going LEAN at the moment).
So what are we missing?
Well really we're just missing the Self Service components. There's some self serve features in Service Manager and some in ConfigMgr 2012, but these are around software deployment rather than the data center.
So we'll be taking a look at System Center Virtual Machine Manager Self-Service Portal 2.0
Now to enable this we really need to look again at Virtual Machine Manager 2008 R2.
We've looked at it before, and even though we're a VMWare estate, we was impressed by it. However we were really looking forward to the integration with Operations Manager, but hit a major fault/bug and had to shelf it as there was no way to fix it.
With those two additions we should have an estate that allows for quick provisioning of services in a streamlined process with monitoring and automation to provide for capacity increases on demand/response, erm, isn't that a cloud?
Moving forward from there, the 2012 roadmap of System Center products are only going to help make this even easier to achieve with even more integration and focus on "The Cloud". Add to that Azure and Server Application Virtualization that allow you to re-host or repackage your existing applications so they can run in Windows Azure and I can see exciting times ahead!
Subscribe to:
Posts (Atom)
