|
|
|
Zero Touch Desktop Deployment |
|
Achieve end to end zero touch operating system deployment without enterprise level overheads |
|
Maximize your return on investment, modernize your environment and jump start your zero touch solution today It’s a well known perception within the I.T consulting and systems design industry that in order to achieve full end to end zero touch operating system deployment and provisioning, at the enterprise or small to medium levels, tools or systems such as SMS or SCCM need to be implemented. Sure, zero touch can be achieved by adopting this approach, however, it is not widely understood that zero touch can still be achieved without introducing SMS or SCCM.
It’s a bit of give and take really, if you want the logging, scheduling, reporting, database inventory and all the other advanced features that SCCM can provide, including the design time, effort, implementation, skills transfer and sustainment, the go for it. The corporate desktop increases to become more complex, costly and challenging to manage, from maintaining driver libraries to a seamless standard operating environment rebuild process to a desktop environment that could be dispersed across multiple sites or offices. Sometimes, the investment of third party tools or enterprise products to manage the desktop may not pay dividends in the long run and sometimes, making the environment even more complex. Subsequently, the evaluation and introduction of enterprise level products such as Microsoft SMS or SCCM for desktop rebuilds and deployment may introduce a too complicated and costly overhead to manage, depending on the size of the organization. However, there is an alternative, and I believe alternatives should always be investigated. The procedures that I have developed will guide you in achieving this. Think of this guide as a filtered rapid uptake, telling you only the key points you need to achieve impressive results in quick time. Basically, the hard yards and research have already been done. Working with the new deployment toolkits can prove very useful, but the big question that I hear in a lot of circles is “Then what’s next”.
I have been designing, deploying and managing operating system deployments based on Microsoft technologies for the past 15 years, focusing mainly on the desktop, starting with Windows 95 through to today’s newest Vista builds under Windows 2003 server. This guide is the direct result of the experience that I have gained over those years, totally focusing on this exact discipline, extracting the bits only relevant to this solution and applied in a manner that will change the way you design, construct and even cost an I.T. standardization project. The primary purpose of this technical guide is to provide fast guidance in order to enable a standard rapid desktop build / rebuild framework, based on leading industry Microsoft technologies with minimal complexity and with a simple user metaphor. The key goal with this very solution that you are about to learn is the simple user metaphor. Let get this straight right up front. This solution is to compliment an existing Microsoft based environment that does not achieve zero touch for operating system deployments, but you want to do so. Think of it as an enabler, a set of procedures that, when implemented, compliments an existing environment. I need to repeat that sentence “compliments an existing environment “. Changing or “tweaking” it into doing more that it did before without the enterprise level overheads of SMS or SCCM. It will get your environment up to speck quickly and rapidly, the results will be seen almost instantly when implemented. This guide is intended for a target audience of I.T professionals with at least a minimum of 5 years working in the field of desktop standardization and image development. A sound knowledge of Microsoft technologies is required in order to fully understand and implement the procedures in this guide. Yours for the taking... Enjoy!
|
