Power, Productivity and the Internet: Part 1 – The core of the problem

A recent NYTimes article touches upon a number of topics in the ongoing conversation about data center energy efficiency. Some reading that article may react as if some secret revelation has been exposed, incriminating our beloved social media networks and data center as spendthrifts or environmentally ignorant.

The fact of the matter is that we live in an information driven world. Information systems are the foundation of our economies, governments, entertainment and many aspects of our daily lives. Maintaining this information and conducting the data processing around it is an industry. It is as much a part of our industrial fabric as steel and manufacturing were in the 20th century.

The data processing that serves our 21st century lives takes place in facilities called “data centers.”  Data centers are essentially industrial factories. From an energy profile perspective, they look exactly like any other factory in that they consume large amounts of resources (electricity and water in their case).

1E has a pedigree of addressing data center energy efficiency and we’ll share that with you presently but first we’d like to give you a little more background.

The core of the problem

There are some out there that will claim the heart of the problem is our dependency or desire for more and more data processing. That is, we are a data processing driven society, hurtling toward the planet’s demise. We’ll leave that to another discussion and instead assume that the increase of data processing demand in our society is a reflection of progress, commerce, and democracy. If you grant me that assertion, the core of our energy demand problem here is that silicon semiconductor-based data processing systems require energy to operate and produce a good bit of heat as a byproduct of their activity. This is compounded exponentially by a matter of scale. 

Semiconductor devices have become increasingly dense (in terms of number of transistor gates per unit of area), with higher and higher clock speeds. As these increase, so does energy demand. As individual devices become increasingly dense, we correspondingly demand more and more of them. The result is computer rooms with massive quantities of data processing servers, each of which have massively dense semiconductor chips.

We mentioned a moment ago that a byproduct of the power going to the server is heat. These very dense silicon chips operate at temperatures so high that one could not possibly touch them bare handed. Interestingly, this large amount of heat produced by the semiconductor chips is also a threat to their very health.  Consequently, computer servers have lots of fans that pull cool air into the front of the server and blow hot exhaust air out of the back of the server. Yes, fans consume loads of energy too, but the bigger problem still is all this hot exhaust air from all the servers sharing the same space in the data center. For this reason, a large amount of mechanical equipment and resources are a part of data centers as well. These mechanical systems are in the form of air handlers, chillers, cooling towers, and plumbing that is in place simply to remove all this hot air from the data center for the purpose of maintaining a healthy ambient operating temperature for the servers.

In an average run-of-the-mill data center today, approximately half of the electricity supplied by the utility to the data center makes it to the power cord of the IT (server) equipment.  Why only half?  Well, the mechanical equipment that cools the data center requires a large amount of it, and there are other losses along the way due to common inefficiencies in power distribution and mechanical and electrical technology (one never gets 100% of what one puts in). To make matters worse still, of the electricity which actually makes it to the IT power cord, much less than that actually goes toward actual data processing due to fan energy consumption, conversion losses, and other subsystems within the server itself.

In summary, we need lots of data processing, and data processing technology consumes large amounts of energy.

All hands on deck

These issues have been thoroughly understood and very publically visible steps taken to address them for many years already. In the United States, the US Department of Energy (DoE) created the “Save Energy Now” program. This program partners the DoE with industry to drive energy efficiency improvements year over year in data centers, with specific goals of saving over 20 billion kWh annually (as compared to historic trends). In the EU, the “EU Code of Conduct” was created to establish a framework of best practices covering energy efficiency, power consumption, and carbon emissions.

Within the data center community, numerous industry groups, trade organizations, and ad hoc committees have been at work on these issues for years. The work of the Green Grid, in particular, has been instrumental in creating the common language used in the community addressing this problem, resulting in a number of energy efficiency management metrics and data center design conventions that we now consider de rigueur.

With governments and the industry itself working the problem, the equipment manufacturers have a role to play as well. Mechanical and Electrical plant (MEP) equipment manufacturers have responded with higher efficiency transformers and UPS, and innovations in pump, fan, and cooling technologies. When it comes to the IT equipment which is truly the engine of this factory we call a data center, the work of participating equipment manufacturers in the ASHRAE TC9.9 body of work is truly remarkable. This is remarkable in that major server manufacturers mutually revealed engineering details of their products to one another to the extent allowing specification of wider ranges of operating temperature and humidity envelopes. This is crucial to energy efficiency in that it is fundamental to allowing reduced energy consumption of MEP, and greatly expands the opportunities for use of free cooling.

Once can go on about this, but suffice to say the evidence is clear that energy consumption by data processing facilities is a widely recognized problem, and much is being done in a coordinated and public way, to provide relief. It’s improper to draw conclusions about a specific data center facility, based upon news of a high profile business with completely different data centers.  Some energy efficiency techniques are available to everyone everywhere, and many are not.  This is a complex subject with significant nuance, and generalizations can come with risk.

In the end, the Business has invested quite a lot of money in its data center, and to acquire the servers and software within it.  Over the years, the Business spends quite a lot of money maintaining and supporting these systems, and is also spending quite a lot of money on energy for power and cooling.

In part two, I’ll look at how to identify server waste and what you can do to eliminate it. 

What can IT learn from the US Open & Wimbledon Ball boys & girls?

You would think that IT and tennis have nothing in common. One is a sport that rewards cunning guile, a strategic mind, and peak physical prowess whilst the other involves hitting a ball over a small net. In all seriousness, there are some good lessons you could garner from watching tennis that are also applicable in the IT world. Specifically from the way the ball boys and girls conduct themselves in such an exemplary, disciplined manner. Ambareesh Kulkarni, Vice President of Professional Services at 1E, has published his insight into an article over on TechRepublic entitled: “What can IT learn from the US Open & Wimbledon Ball boys & girls?

Here’s a snippet of the article Ambareesh has published:

“Have you ever noticed the US Open or Wimbledon ball boys or girls during a tennis match? No?

That is because one isn't meant to. These boys & girls work, train and practice extremely hard to stay unnoticed. If one doesn't notice these boys & girls, then they have done a fantastic job. These boys & girls have one aim, which is to keep the game going…”

He concludes with a few tips and tricks that can help you improve your IT and apply a little bit more tennis to your IT world. Read the full article here.

1E Contributes to Authoritative Text on Microsoft System Center 2012 Operations Manager

The first comprehensive reference and technical guide to Microsoft System Center Operations Manager 2012, "System Center Operations Manager 2012 Unleashed" contains contribution by 1E's Data Center Practice Professional Services Consultant, Scott Moss.

This soon to be released book, is the authoritative text for integrating OpsMgr 2012 to manage cloud and datacenter applications and services, and provides comprehensive coverage of all aspects of data center IT infrastructure management.

Scott Moss is the author of Chapter 23, covering PowerShell, and joins an expert team of Operations Manager MVP authors contributing to this text.  The book will be used globally by administrators, consultants and other IT professionals seeking guidance with this new data center infrastructure product.

Expertise of this type is in very short supply, and this demonstrates the continued value we offer our Customers engaged in data center transformation and implementation of System Center Operations Manager 2012.

Scott also has his own System Center Operations Manager 2012 blog and was the first person to start blogging on SystemCenterCentral.com, a site that was started and maintained by OpsMgr MVPs.

Other notable authors and contributors in the 1E camp include Andy Dominey who co-authored "Microsoft Operations Manager 2005 Field Guide", "System Center Operation Manager 2007 Unleashed" and "System Center Operation Manager 2007 R2 Unleashed" and Paul Thomsen who co-authored and contributed to multiple technical books such as "Microsoft SMS 1.2 Administrator's Survival Guide".

1E Introduces “Useful Work”-based Data Center Governance, at Data Center Dynamics Converged, 2012 Washington DC

Data center performance metrics have struggled to accurately represent business value of IT assets invested in the enterprise data center.  Data center metrics are either constrained to raw power usage data, or make vague approximations about business-relevant performance through assumptive percentages or abstract proxies.

At Data Center Dynamics in Washington, DC this week, 1E introduced an improved method of data center performance measurement and governance based on empirically derived measures of data processing “usefulness.”

Continue reading

Supercharging private cloud efficiencies

I’ve recently written a piece that has become a featured article over at TechNet UK. It talks about the issues organizations face when it comes to the data center space and touches on controlling virtual sprawl and our concept of “Useful Work”. Microsoft and 1E continually share roadmaps, planning strategies and technical insights so that 1E’s solutions can continue to add value and bring greater efficiencies for the enterprise: better together.

I hope you find it useful when you start thinking about how to improve your private cloud efficiencies :)

Andy Hawkins, Product Manager at 1E

What’s happening in September 2012? 1E Events and Webinars

Here at 1E we love giving back to the community that gives us so much. We love helping our organizations make the most out of our products to maximize their savings and increase the efficiency of their IT. Technology keeps evolving with newer features constantly being released and manipulating these features becomes more complex. So in order to help you, the amazing IT community out there, we’re hosting a few webinars and sponsoring some events. Here’s a short list of what we have planned in September for you:

Upcoming Webinars for September 2012

1E’s Windows 7 Deployments: Achieve record-breaking Windows 7 deployments
When?
Thursday, September 13, 2012 – 14:00 BST/15:00 CET
Thursday, September 13, 2012 – 11am PST/2pm EST

Join our webinar on September 13, to discover how you can:

  • Mitigate the impact of transferring massive OS images across your network
  • Reduce desk-side visits by automating the OS process
  • Allow users to upgrade at a time convenient to them
  • Save on software licenses by analyzing application usage and only re-installing the ones that are used.

1E’s AppClarity 3.1: Visibility of all software installations, physical or virtual (App-V)
When?
Thursday, September 20, 2012 – 14:00 BST/15:00 CET
Thursday, September 20, 2012 – 11am PST/2pm EST

  • Join our webinar on September 20, to discover how AppClarity:
  • Detects unused software: Every physical and virtual (App-V) software installation is instantly analyzed to determine if it is used, occasionally used or unused
  • Financially quantifies waste: Obtain a global picture of the financial impact of any unused software and shelfware Reduce desk-side visits by automating the OS process
  • Automatically reclaims and recycles licenses: Unused licenses can be harvested from machines using a policy-based approach. Savings achieved are tracked and reported
  • Improves audit readiness: Replace the time consuming process of producing reports for vendor audits with just a few clicks.

Upcoming Events [US]

The Greater Midwest System Center Rally 2012
When?
Thursday, September 27, 2012 – 8am to 5pm CDT
Where?
3700 Broadway, Kansas City, Missouri 64111

You'll hear from speakers on a variety of real-world topics that range from desktop to data center and into the cloud.  We are very excited to have Wally Mead of Microsoft joining us, and he will be presenting three sessions at The Rally!

Twenty-plus sessions, delivered by some of the industry's sharpest talents, discussing and demonstrating how to leverage Microsoft System Center and Windows Server 2012 to address challenges such as:

  • Enabling Self Service End Users
  • Automating IT Process
  • Datacenter Management Zero to Sixty
  • Windows Server 2012 – The New Hyper-V
  • Windows 7 / Windows 8 Desktop Deployment
  • Windows Server 2012 Remote Desktop
  • App Management with System Center 2012
  • Local Admins, Jail, and You
  • IT Rationalization
  • Role-based Administration in SC 2012
  • Infrastructure as a Service / Meet Azure
  • Windows Server 2012 Storage & Availability
  • IT Analytics – Leveraging SC Data for Business Decisions
  • BYOD Strategies
  • Adapting Your IT Group to the 2012 Platforms

September 27th at The Uptown Theater in Kansas City, Missouri.

Click here for a direct link to the registration page.

ConfigMgr 2012 SP1 Overview Featuring Wally Mead
When?
Friday, September 28, 2012 – 9:30am to 3:30pm CDT
Where?
National Instruments, 11500 N Mopac Expy, Austin, TX 78759

Join us Friday, September 28th for an action packed day of demos and deep dives featuring one of CTSMUG's finest – Wally Mead. The full agenda will be published the week of the event, but you can expect several topics specific to ConfigMgr SP1, such as managing Windows 8, enhancements to OS deployment, software distribution and more.

Agenda:

9:00 – Welcome and Coffee
9:30 – ConfigMgr 2012 SP1 Overview
10:30 – ConfigMgr 2012 SP1 Deep Dive
12:00 – Lunch (provided by 1E www.1e.com)
1:00 – 1E Presentation
2:00 – ConfigMgr 2012 SP1 Deep Dive – II
3:30 – Open forum and discussion

1E Blogs

Hey! Can I have a jacket?

It seems I started something with my post about the Ambassador Program jackets (which was kind of the point)… A couple of our sales team sent me emails saying that their customers had read the blog and were saying :

“Hi [Sales Guy]

I spent lots of money with you last year – I deserve a jacket surely?”
 
Cheers
 
[Your Favourite Customer]”

Let me explain what ‘the jacket’ really means… It’s recognition of being welcomed into an a club of people who have not simply bought our products, but have used them to make their organization more efficient and are telling people about how much they’ve saved.

ambassador for 1e jacket
 
So to make it a tiny bit more transparent – here’s the rules for getting in:
 
1.       You have to have bought one of our “IT efficiency solutions" to help your organization’s IT become more efficient

2.       It has to be implemented in your organization – We don’t want our stuff to be shelfware¹

3.       Be seen showing benefit to your organization that you can explain ideally as cash savings, but less tangible benefits such as speed of OS deployment or lower admin overhead is fine too.  We want our stuff to be used and to achieve the ROI we promised.

4.       Be publicly telling people about what was achieved (forums, case study, tweets, blog, video, etc…)
For example…Maybe you’re a hardcore techie, then blog about how you integrated it with something on a personal blog or maybe a post on a technical community forum, such as myITforum.com, on how you used it to make some bit of administration more simple… or maybe, if you’re more of a management type, you want to post about how it helped you from a process of business perspective.
 
So in short – if you want some miscellaneous vendor marketing swag – keep pestering your sales guy². If you want into our IT Efficiency Ambassador club, get in touch and let’s get you there :)
 
Regards
 
Geoff Collins

Director of Product Management, 1E

1E Blogs


¹ – which ironically would be indentified in one of our AppClarity reports
² – which ironically our sales guys loved being pestered


Extreme OSD – Upgrading the OS of the Curiosity Rover on Mars

NASA is now preparing to upgrade the OS on the Curiosity Rover. No big deal, except it landed on Mars yesterday so a DVD or USB key are probably not viable deployment options. DHL to mars might be a little bit on the expensive side.

I couldn’t help but imagine the conversations in the NASA camp that might have led to this…
 
"OK, we launch in 3 months. How's that OS going?"
 
"Yeah yeah, good, maybe a bit behind, but we'll be OK"
 
"A bit behind?"
 
"Yeah, yeah, having some trouble with the drivers"
 
"Which ones?"
 
"Just a couple.. wheels.. laser.. The camera is working fine though.. well, black and white at the moment, but that's OK."
 
"Riiight.. And you'll have this fixed for launch?"
 
"Yeah yeah, well, actually we were thinking about that. Maybe we could patch it post launch"
 
"Patch?"
 
"Yeah yeah, like we do with our PCs"
 
"And that'll work?"
 
"Yeah. Easy. We do it all the time here"
 
"But this thing will be on Mars, you know that right..?"
 
"Yeah yeah Mars. It's fine. We've got some ideas on that"
 
"I'm listening"
 
"How long did you say it take to get to Mars?"
 
"253 days"
 
"Ah! That's OK then. We'll have our long distance upgrade module by then. Yeah. Worst case, you'll land and won't be able to move for a few days"
 
NASA Curiosity Operating System Deployment
 
I watched the live stream from NASA during the landing and was struck by the blend of technology and emotion on display. The amount of effort and planning that was involved captivated me. The smallest of mistakes would have rendered this mammoth project a failure and the high stakes made it even more spectacular. NASA even created a video dubbed “Seven minutes of Terror” that went viral highlighting the feat of this event. So when the Mars Curiosity landed I was relieved and excited.

When “stuff just works”

Isn’t it great when “stuff just works”? All of the planning had paid off. All of the technology put in place to get the Curiosity Rover to Mars had yielded a successful landing. Then NASA announced their website had gone down due to heavy load.

This left me conflicted. I’d just witnessed an awesome showcase of innovation, engineering and technology yet was not surprised that a website suffered a temporary outage. We have a habit of associating a sense of inevitable problems when major events take place. When it isn’t business-as-usual we fear something unusual is bound to happen. NASA has spent $2.5 billion on this project and the official website went down.

The link from Mars Curiosity to Earth started out at just five megabits. That’s now up to forty megabits when conditions are right and that’s before the Curiosity deploys its main antennae. Forty Megabits before the main antennae – that’s a better link than some sites can muster on Earth so surely the OS deployment will be a lot easier for the Mars Curiosity Rover?

How will the OS upgrade go for the Curiosity Rover? Will it be a success and go as smoothly as planned or will there be unexpected issues? Migrating Operating systems on Earth from Windows XP to Windows 7 feels like a major event and not business as usual. Is that true? Does it have to be like this? Is OS deployment on Earth more difficult than on Mars?


Is OS deployment on Earth harder than on Mars?

The Mars Curiosity doesn’t require business as usual for its OS deployment. The OS deployment is a critical stage in the project and will not disrupt their “business”. They can afford the upgrade to be an “event”. Deployment on Earth on the other hand does not share this same luxury. The cost of making an OS deployment a project can spiral out of control. The cost of personnel, time and expertise will all factor in. The planning required moving large amounts of data from one site to another without causing user disruption and not forgetting the migration of applications and user data. This isn’t business as usual. But why isn’t it?

OS Deployment on Earth should be easier than Mars

Unlike the NASA scenario, we have done OS upgrades before. In fact we’ve done them several times and we’ll do it again. We understand the challenges of OS deployments and our infrastructures so we created software such as Nomad 2012 that integrates with Microsoft System Center Configuration Manager to achieve highly optimized and rapid migrations with 100% automation across the majority of PCs. We’ve proven this in our ability to perform a complete Windows 7 migration on 39,000 machines in just one month.

This is business as usual.

This is how OS deployment should be done.

No disruption to users. Applications and user data all appear where it is supposed to be and all within a newly upgraded OS.

OS Deployment should be easier than on Mars. With Nomad and SCCM it is.

Written by Andy Hawkins

NASA Curiosity OSD




Why run Nomad 2012 vs nothing at all?

How does Nomad 2012 control your SCCM bandwidth management?
Nomad 2012 is a pure software solution which dynamically manages the bandwidth of IT content distribution in order to prioritize business traffic over IT traffic instead of traffic competition where it’s business traffic vs IT traffic. Nomad 2012 does this by Reverse QoS™.

By using Nomad in your SCCM (ConfigMgr) designs for branch offices and SCCM bandwidth management you no longer have to deliberate whether onesite should be your central location site vs another site. Instead when it comes to Microsoft SCCM WAN bandwidth management at branch offices you can target Applications and Packages without any additional SCCM branch office constraints due to the complete Nomad integration. There is no risk with using Nomad 2012 in your SCCM branch office design as it will augment the System Center infrastructure rather than compete with it.

Many organizations have a list of key criteria they need to meet within thier environments when evaluating Nomad 2012 vs other methods for managing client systems at SCCM branch offices.

How many servers will they reduce to before creating a single point of failure? Nomad reduces the server infrastructure at Microsoft ConfigMgr branch offices more than any other product on the market. It does this without having to ask the question of "should I deploy this?" versus "will this create a single point of failure?" because Nomad 2012 accounts for all scenarios.


Reducing your network infrastructure compared to creating a single point of failure

Nomad also has Byte-level differencing,  client cache management and  Peer to peer based redundancy, and the distribution mechanisms of Nomad 2012 allow an organization to dramatically reduce infrastructure servers by 95% or more without creating any risk such as a single point of failure, unnecessary client overhead or kernel drivers.
The requirements for many organizations require multiple sites in comparison to one site for many reasons, political, geographical or even high availability and disaster recovery, and Nomad 2012 can cater for all these scenario whereas others cannot.

Additionally, the OSD facilities of Nomad 2012 allow organizations to supercharge migration projects without any additional staff and achieve the highest possible amount of automation on most client systems. The PXE Everywhere functionality that is native to the Nomad 2012 solution allows for PXE in branch offices to happen without any server infrastructure while still effectively managing the ConfigMgr bandwidth to the branch. Try Nomad 2012 for yourself, whittle your list of ten questions down to none and manage the Microsoft SCCM bandwidth for your branch office at one site like you would your central site – in other words manage them all the same.
Continue reading

Notes from the field – How 1E has supercharged OSD with Nomad 2012

There has been a lot of news recently – for instance in TechWeek Europe and ComputerWorld UK – about how 1E helped a large US telecommunications provider complete a Win7 migration of 30,000+ systems in just one month which we believe to be a world record. The main infrastructure tool used to do this was Nomad 2012. A lot of the buzz around this real and proven deployment has raised some questions about how we achieved this:
 
·         What were the requirements we needed to achieve this amazing feat? We didn’t offer a solution which required network hardware requirements, configuration, pings, system level drivers or anything like that. Nomad 2012 used the revolutionary Reverse QoSTM algorithm, an autonomic throttling system which dynamically backs off when business applications need network resources.

·         How much of the deployment process required administration? The solution was also fully integrated into SCCM so that zero administration was needed. No separate consoles were necessary and the data was sent out in a safe and secure manner. Since Nomad 2012 only sends IT content where it is targeted, i.e. Nomad doesn’t “scatter” data around to several systems, it mitigates any security concern or possibly licensing issues.

·         How did we handle user data? Nomad 2012 offers OSD flexibility not available anywhere else. For instance at onesite where we assisted with their migration, a customer had more than 200gb of data which needed to be transferred to a new Operating System during the deployment. Without the Peer Backup functionality that Nomad 2012 offers this would have meant either a massive impact to the network or it would have been simply impossible without an onsite visit by IT support staff.

·         Why 1E and Nomad? The customer we set this record with (and many others) recognizes that with 1E and the above points, risks are low and success is high because they could perform their Win7 migrations:
 

  • Business as usual and during business hours
  • With existing IT staff, no separate project teams

 
These are exciting times with results that have never been seen before. There are many other advantages that the Nomad 2012 solution that are brought to the table such as integrated Task Sequence actions and the fantastic PXE Everywhere functionality that we’ll talk about in another blog post soon. We’ve also got some exciting integration features with other 1E products such as AppClarity and Shopping which allows for intelligent content pre-staging that you cannot do without. Stay tuned.

Windows 7 OS deployment Fast vs slow




Why run Nomad 2012 vs nothing at all?

How does Nomad 2012 control your SCCM bandwidth management?
Nomad 2012 is a pure software solution which dynamically manages the bandwidth of IT content distribution in order to prioritize business traffic over IT traffic instead of traffic competition where it’s business traffic vs IT traffic. Nomad 2012 does this by Reverse QoS™.

By using Nomad in your SCCM (ConfigMgr) designs for branch offices and SCCM bandwidth management you no longer have to deliberate whether onesite should be your central location site vs another site. Instead when it comes to Microsoft SCCM WAN bandwidth management at branch offices you can target Applications and Packages without any additional SCCM branch office constraints due to the complete Nomad integration. There is no risk with using Nomad 2012 in your SCCM branch office design as it augments the System Center infrastructure rather than compete with it.

Many organizations have a list of key criteria which they want to ask about their environment when evaluating Nomad 2012 vs other methods for managing client systems at SCCM branch offices.

How many servers will they reduce to before creating a single point of failure? Nomad reduces the server infrastructure at Microsoft ConfigMgr branch offices more than any other product on the market. It does this without having to ask the question should I deploy this vs will this create a single point of failure because Nomad 2012 accounts for all scenarios.

 

Reducing your network infrastructure VS creating a single point of failure

Nomad also has Byte-level differencing,  client cache management and  Peer to peer based redundancy and distribution mechanisms of Nomad 2012 allow an organization to dramatically reduce infrastructure servers by 95% or more without creating any risk such as a single point of failure or unnecessary client overhead or kernel drivers.
The requirements for many organizations require multiple sites vs one site for many reasons, political, geographical or even high availability and disaster recovery reasons and Nomad 2012 can cater for all these scenario where-as others cannot.

Additionally the OSD facilities of Nomad 2012 allow organizations to supercharge migration projects without any additional staff and achieve the highest possible amount of automation on most client systems. The PXE Everywhere functionality that is native to the Nomad 2012 solution allows for PXE in branch offices to happen without any server infrastructure and still effectively managing the ConfigMgr bandwidth to the branch. Try Nomad 2012 for yourself and whittle your list of ten questions down to none and manage the Microsoft SCCM bandwidth for your branch office at one site like you would your central site – in other words manage them all the same.

How does Nomad Enterprise determine network bandwidth and protect your network? Ping? Nope. Try Reverse QoS TM instead

How does Nomad Enterprise determine network bandwidth and protect your network? Ping? Nope. Try Reverse QoS TM instead


Network Ping, DiffServ, QoS or something special?

There are lots of ways to calculate network bandwidth. A network ping can determine WAN speed but this is not ideal as many organizations disable IGMP for many security reasons. Windows firewall alone blocks a lot of ping traffic by default due to the inherent security issues that can be associated by it.
DiffServ can give good QoS but requires hardware investment that can utilize this technology not to mention some solutions leveraging this technology only calculates QoS on edge routers. This may be okay for route paths with a short amount of hops (number of routers in-between each edge router) but once we hit the big wide area network we become unable to determine how many hops we take. There’s also the issue of issue of requiring clients to use this technology down at the network level.
This means we need drivers to create these special types of network packets that can utilize DiffServ effectively on each of our clients and Microsoft themselves once attributed that the reason why nearly all windows machines get the dreaded “blue screen of death” was because of drivers.

So how does Nomad do it? Reverse QoS TM.

Nomad doesn’t want to use QoS. Why? QoS is literally Quality of Service. It ensures that certain packets are prioritised over other packets. What does this mean in laymen terms? It means that your packets compete over bandwidth over a link. This means that the link still can get saturated and that the prioritised packets get “right of way” over these saturated links.
What does Nomad do? Nomad uses a special system called Reverse QoSTM.

What is Reverse QoS TM?

Reverse QoSTM is a method that looks at the complete round trip time that it takes blocks of data to traverse a WAN link. It is able to back off or speed up accordingly in a safe manner. This is special because it can actually take everything into account. This includes high CPU utilization of a client down to even disk read latency from the OS. This is hugely beneficial to business due to the fact that network hardware such as router queues do not need to be accounted for as the solution is purely hardware based. It also means that Nomad is able to avoid using any system level drivers that risk a blue screen of death as previously mentioned which could cause havoc to your organization and possibly require the need to visit every system if there is a problem.

So what’s the problem with other methods?

Other methods for network bandwidth throttling soon start to break down when you have multiple network hops and routes through different switches on the way to an endpoint because the only look at edge routers and not the whole end-to-end WAN like Nomad does with Reverse QoSTM. You can see how some of the largest organizations in the world like HSBC, Verizon Wireless and AT&T are actually using Nomad in the video and documented case studies at http://www.1e.com/it-efficiency/software/nomad-enterprise-software-deployment/#casestudies





Why run Nomad 2012 vs nothing at all?

How does Nomad 2012 control your SCCM bandwidth management?
Nomad 2012 is a pure software solution which dynamically manages the bandwidth of IT content distribution in order to prioritize business traffic over IT traffic instead of traffic competition where it’s business traffic vs IT traffic. Nomad 2012 does this by Reverse QoS™.

By using Nomad in your SCCM (ConfigMgr) designs for branch offices and SCCM bandwidth management you no longer have to deliberate whether onesite should be your central location site vs another site. Instead when it comes to Microsoft SCCM WAN bandwidth management at branch offices you can target Applications and Packages without any additional SCCM branch office constraints due to the complete Nomad integration. There is no risk with using Nomad 2012 in your SCCM branch office design as it augments the System Center infrastructure rather than compete with it.

Many organizations have a list of key criteria which they want to ask about their environment when evaluating Nomad 2012 vs other methods for managing client systems at SCCM branch offices.

How many servers will they reduce to before creating a single point of failure? Nomad reduces the server infrastructure at Microsoft ConfigMgr branch offices more than any other product on the market. It does this without having to ask the question should I deploy this vs will this create a single point of failure because Nomad 2012 accounts for all scenarios.


Reducing your network infrastructure VS creating a single point of failure

Nomad also has Byte-level differencing,  client cache management and  Peer to peer based redundancy and distribution mechanisms of Nomad 2012 allow an organization to dramatically reduce infrastructure servers by 95% or more without creating any risk such as a single point of failure or unnecessary client overhead or kernel drivers.
The requirements for many organizations require multiple sites vs one site for many reasons, political, geographical or even high availability and disaster recovery reasons and Nomad 2012 can cater for all these scenario where-as others cannot.

Additionally the OSD facilities of Nomad 2012 allow organizations to supercharge migration projects without any additional staff and achieve the highest possible amount of automation on most client systems. The PXE Everywhere functionality that is native to the Nomad 2012 solution allows for PXE in branch offices to happen without any server infrastructure and still effectively managing the ConfigMgr bandwidth to the branch. Try Nomad 2012 for yourself and whittle your list of ten questions down to none and manage the Microsoft SCCM bandwidth for your branch office at one site like you would your central site – in other words manage them all the same.