Troy is a Technical Architect at 1E, which entails providing technical direction for 1E technologies, assuring their qualities in efficiently managing hardware, systems, users and other end points. Troy is well known in the Configuration Manager community as a speaker and subject matter expert. Working with some of the largest companies in the world as a consultant with 1E for 5 years, he has been involved with dozens of SCCM and Windows migrations and upgrades. Troy has been instrumental in collaborating with others at 1E to creating some of the core foundations of Software Lifecycle Automation (SLA) such as automated application rationalization and OSD mapping solution to name a couple. Many Fortune 500 companies have since benefited from SLA for their Windows migrations and are sure to take advantage of it during their ongoing migration to Windows 10.
The second part of this webinar series with Jim Bezdan and Troy Martin looked into the Windows 10 update process in detail. There were lots of questions and we have the answers for you. If there’s something we missed, please let us know and we will help you solve the problem. Question: Does this stuff tie
Yesterday we provided you with some free tools to help you get started on your Windows 10 planning and execution. Today we are answering some of the questions from last week’s webinar. If there’s something we missed, please let us know and we will happily guide you through it. As always, you can always head
Last week during our webinar, Windows 10: A Roadmap for Rapid Success, I mentioned several tools and files that were key to understanding the fundamentals of Windows 10. Do you feel confident about your current plan? Hopefully, now you have an understanding of your environment and how that will affect the remainder of your planning.
Last week was (unofficially) Device Guard week here at 1E. Not only did we have our Device Guard webinar, ‘Beating Malware with Device Guard and AppLocker’ (the second in our Windows 10 Security Webinar Series), but we also unveiled an exclusive white paper, ‘Understanding and Deploying Device Guard’. The former was very well attended, meaning
Cyber-attacks commonly occur through applications, browsers, un-patched vulnerabilities, or social-engineering. Deploying Device Guard (a central feature in the suite of Microsoft’s Windows 10 security features) does not eliminate the possibility of being targeted for attacks, but it does significantly reduce the attack surfaces favored by bad actors and malware writers. What Device Guard does is
Introduction Welcome to the third and final blog in the series on Device Guard!! In part two of the blog series Device Guard: The Theory, the key points were: Device Guard hardens various attack surfaces on an endpoint creating a “chain of trust” from the hardware through to the Windows OS kernel and to software
Welcome to the second of a three-part series on Device Guard!! In part one, Device Guard: The Holy Grail of Endpoint Security?, the key points were: Endpoint security in Windows has evolved, but a true enterprise solution has been lacking Solely relying on 3rd party vendor solutions and community-centric intelligence for endpoint security puts organizations
Welcome to the first of a three-part series on Device Guard!! Judging by the number of tweets in the last couple of months which include the hashtag #DeviceGuard, you may conclude that this important and game-changing feature in Windows 10 security might be…well, not be that important. Don’t be fooled. In this three part series
Today 1E is proud to announce the general availability release of Nomad 6.0!! 8.5 months and over 6K hours were spent adding new features and enhancements that will help turbocharge your Windows 10 migration. You can learn exactly how it does this by joining our Nomad 6.0 Launch webinar on September 3, 2015. Sincere thanks
On May 14, Microsoft released ConfigMgr 2012 SP2/R2 SP1 with support for Windows 10 included. On June 1, Microsoft announced the July 29 release date for Windows 10. We had an important decision to make: Test ConfigMgr 2012 SP2/R2 SP1 by itself and release a support statement for it. Test Windows 10 by itself and