Oops, I already deployed 200 PC’s and I forgot to include AutoDesk Inventor or Solidworks on the engineering computers.How can I remove this program and add this other one?. How can I add this driver when a new computer model is purchased?.Smaller environments? Forget it! You would have to go through a lot of work to get a working deployment system in place and the advantages of having a deployment solution typically didn’t outweigh the initial complexity and time spent.Īt the end-of-the-day, the monolithic-based deployment environment was hard to maintain and keep up to date. Granted, medium to large IT environments commonly tried to stick to 3-4 specific models of computers which may have worked fine for them initially, but as the environment and personnel changed over time, maintaining these images slowly became a nightmare. Not to mention, the amount of time spent maintaining separate images for one client, let alone, in my role as an IT consultant, maintaining dozens of client images – everyone unique for each location or customer. During this time, I witnessed first-hand how much time it would take getting that “golden” image perhaps even “universal” image (images that had hardware drivers for different make/models built-in that would work in nearly all deployment scenarios) setup with all the software they needed. It was tough to deploy Windows to different hardware platforms without maintaining separate reference images (a.k.a monolithic images) for each and every model of computers in your organization. Travel back with me for a moment to the pre-Windows 7 days. ISO build and then re-install that long list of applications, re-capture it, and hope didn’t miss any steps in the process, or you’ll have to do it all over again – ugh… Talk about a headache.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |