That’s a simple question, but as with practically everything in the world of computer management, “it depends” is the right answer. As the product manager for Nomad I would love to guarantee they always are, but there are the occasional exceptions so I’d rather advise you to do a bit of due diligence. To aid that process I’m pleased to announce the availability of a comprehensive new technical whitepaper, our “Nomad Upgrades Guide”, available here: Nomad Upgrades Guide – 1E Resource Center
I’ve worked with my fellow product manager, Paul Thomsen, and a broad team of 1E experts to ensure that we properly answer that question for you.
We not only help you with Nomad upgrades themselves, but also related scenarios including:
- Microsoft System Center Configuration Manager (ConfigMgr, or SCCM) upgrades or migrations
- Consolidation of ConfigMgr hierarchies (such as from the result of a merger or acquisition)
- And combinations of these scenarios.
Nomad upgrades are generally simple, straightforward, and low-impact. However, as with any change, specific conditions and circumstances might require unique consideration and handling that must be accounted for during planning and testing. With prudent analysis and planning you can ensure a successful and efficient upgrade project. The guide is based on 1E’s experience working with many organizations of all sizes to upgrade Nomad.
In particular, you’ll find:
- Key considerations that might complicate your upgrade or migration
- Complete upgrade processes, including example scripts and troubleshooting guidance
- Best practices
- Additional resources for further background
While much of the document concentrates on Nomad upgrades themselves, you might encounter similar considerations when doing ConfigMgr migrations, even if you’re not upgrading Nomad itself during the migration. A ConfigMgr 2007 to ConfigMgr 2012 migration requires co-existing ConfigMgr hierarchies and under some circumstances that can impact Nomad behavior. By understanding the possibilities you can incorporate appropriate steps in your project plan if need be.
As an example of an issue you should consider, ConfigMgr 2007 uses file hashes that are different from ConfigMgr 2012. Nomad easily works with both but if you have not configured Nomad appropriately, and if you will have a mix of clients on your subnets for some time, additional steps can be needed to manage the hashes.
The best practices detailed in the document not only ensure that your project is successful but also that you maximize the software deployment benefits of Nomad for years to come.
Enjoy reading this document! We look forward to seeing your comments.