Share This Post

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.

Share This Post

Leave a Reply