Imaging Rights - Windows - Looking for clarification
-
I do not do imaging, because i have so few same hardware machines at each site. there is just not enough to gain from setting up imaging and then updating images and all that.
If I had more similar machines per site, or more failures of the ones that are similar, that would be different.
-
@JaredBusch said:
I do not do imaging, because i have so few same hardware machines at each site. there is just not enough to gain from setting up imaging and then updating images and all that.
If I had more similar machines per site, or more failures of the ones that are similar, that would be different.
For imagine yes, I agree, it's pretty rare that I take the time and effort to image. Reimaging rights, though, I use often just so that we don't have to maintain media for different machines, track which go to which or worry about any bloatware at all.
-
You can just setup your image to have all of the drivers you have in a local folder on the image. Make a registry change to include this folder.
At system startup on the hardware windows will search this folder for additional drivers and install them as required.
Imaging just makes so much more sense when you take full advantage of it.
This way, if we went and bought a completely different computer, all I have to do is update the image to include drives for that hardware type, and deploy it.
Done.
In a working state in a little as 30 minutes.
-
Yes, definitely, for a shop of any size imaging AND reimaging together make total sense. Pretty much unbeatable.
