Rapid Desktop Replacement
-
@scottalanmiller said:
@Dashrender said:
@BRRABill said:
Is it really just a matter of ... hey if it is important to them they should know better?
Pretty much
.
.Or ... hey if it is really that important, it's more than just a personal machine and should be considered as such?
If it's a business machine, then the owner should care about these things. Needless to say, many don't think about it. They are spending most if not all of their time worrying about their core business, but they are failing their businesses because they are not also worrying about how their business will survive if that one machine that holds everything that matters to them suddenly dies.
One could argue that backups are about as core as business can get.
While I tend to agree with you, the countless thread at SW and in numerous other sites around the web show that business owners often overlook this.
-
@scottalanmiller said:
You don't do imaging for restores, or you don't have a standard deployment image?
I don't have a standard deployment image. And I don't do fresh installs, I'm happy with the HP image and uninstalling any bloatware (which isn't much, just a few HP utilities, there isn't generally any 3rd party crap anymore)
-
@BRRABill said:
@Dashrender said:
But a second drive for your computer. Then restore the image to that drive and run it in your computer for a while.. There you go, confirmed the image is good.. and you're always legal.
But that is hard. (LOL. Kidding.)
That's another lesson I have learned from this. A lot of this stuff works, and is for the convenience of IT. At a cost of licensing, of course.
While that is totally true (in some cases like MS Windows) I'm not seeing this as a convenience. I think that MS has licensing restrictions around this because this is not a good use case and they are licensing for other reasons.
-
@BRRABill said:
@Dashrender said:
But a second drive for your computer. Then restore the image to that drive and run it in your computer for a while.. There you go, confirmed the image is good.. and you're always legal.
But that is hard. (LOL. Kidding.)
That's another lesson I have learned from this. A lot of this stuff works, and is for the convenience of IT. At a cost of licensing, of course.
You had a problem, and I provided a simple solution. one that's pretty cheap to. Heck, using something like Clonezilla (which is 100% free) you could the drive into the computer, boot from the Clonezilla media, image from one drive to the other, then disconnect the first drive and boot.. test it, shut it down, disconnect the second drive, connect the first drive and go to work... every time you want to take an image.. just connect the second drive and do the above process again.
Is this for the normal home user - of course not!
The normal home user should be shoved into a Chromebook. Then 100% of their stuff is in the cloud and they just buy a new device and keep working.. problem solved.
But if you have special applications, settings, etc as you've mentioned - then you are no longer normal, and you need to act as such.
-
@Carnival-Boy said:
@scottalanmiller said:
You don't do imaging for restores, or you don't have a standard deployment image?
I don't have a standard deployment image. And I don't do fresh installs, I'm happy with the HP image and uninstalling any bloatware (which isn't much, just a few HP utilities, there isn't generally any 3rd party crap anymore)
Even at five minutes, seems like at that size it would justify a standard image. We use HP and to avoid the bloatware on ten machines we found the VL to be well worth it. Makes for a more stable system too, slightly.
-
@Dashrender is correct. Typical home users need Chromebooks.
-
@Carnival-Boy said:
@scottalanmiller said:
You don't do imaging for restores, or you don't have a standard deployment image?
I don't have a standard deployment image. And I don't do fresh installs, I'm happy with the HP image and uninstalling any bloatware (which isn't much, just a few HP utilities, there isn't generally any 3rd party crap anymore)
You never know for sure what could be hidden in a factory install.
-
@Jason said:
@Carnival-Boy said:
@scottalanmiller said:
You don't do imaging for restores, or you don't have a standard deployment image?
I don't have a standard deployment image. And I don't do fresh installs, I'm happy with the HP image and uninstalling any bloatware (which isn't much, just a few HP utilities, there isn't generally any 3rd party crap anymore)
You never know for sure what could be hidden in a factory install.
- cough * Lenovo * cough *
-
If I was doing 10 at a time I'd probably image, but I tend to do less than that to spread the workload a bit.
-
@Carnival-Boy said:
If I was doing 10 at a time I'd probably image, but I tend to do less than that to spread the workload a bit.
that's not really the point - unless your point is to waste your company's resources, namely your time.
-
How rude! I believe imaging would take me longer - obviously.
-
@BRRABill said:
@scottalanmiller said:
The answer here should be to move those critical data-storing apps elsewhere. To a server, to a hosted site... whatever. A high quality VPS starts at $5/mo. If the system isn't worth $5, it's not critical in the least.
Recommendation, for future storage ... in my brain?
I think this may have been missed in all the back and forth.
-
@Carnival-Boy said:
How rude! I believe imaging would take me longer - obviously.
Break even for imaging is around the 20-30 units deployed mark. It's not a big deal once you've got it up and running.
-
We have 15 here, and buy about .3 every year.
No imaging for me!
-
@Carnival-Boy said:
How rude! I believe imaging would take me longer - obviously.
What causing doing an image to take longer? I find an image faster for even one, let alone two. I'm confused where the extra time is coming from. What makes it so dramatically faster for me and slower for you? I can't think of any factor that is faster not imaging unless you are considering the time to download the initial clean image from Microsoft, but you do that with one click and it does it in the background. Done. Saves time on the first deployment.
-
@BRRABill said:
@BRRABill said:
@scottalanmiller said:
The answer here should be to move those critical data-storing apps elsewhere. To a server, to a hosted site... whatever. A high quality VPS starts at $5/mo. If the system isn't worth $5, it's not critical in the least.
Recommendation, for future storage ... in my brain?
I think this may have been missed in all the back and forth.
What's the question?
-
@BRRABill said:
We have 15 here, and buy about .3 every year.
No imaging for me!
You are 14 machines past the point where imaging would make things easier
-
-
@MattSpeller said:
@Carnival-Boy said:
How rude! I believe imaging would take me longer - obviously.
Break even for imaging is around the 20-30 units deployed mark. It's not a big deal once you've got it up and running.
Why so high? I find that it saves most of the deployment time of the very first one. Since there is zero overhead to basic image deployments, what causes there to be a need for a "break even" point.
It's like "how many cars do you need before Ferraris are faster than a Prius?" The answer is any... all Ferraris are faster than any Prius. Quantity isn't a factor.
-
@scottalanmiller said:
You are 14 machines past the point where imaging would make things easier
I'll put it on my todo list. (Seriously!)
