PowerShell Script to Upgrade to W10
- Thread starter Mainstay
- Start date
Your PCMD
Well-Known Member
- Reaction score
- 3,387
- Location
- Gainesville, TX
I agree with @nerd2u so +1 for his posting.
The last thing you want - going through an RMM - is a mass silent, but forced upgrade to Windows 10. There are many reasons to not do this, compatibility for one. Are all machines on Windows 7 all running 64 bit or are there 32 bit ones as well? You really don't want 32 bit. What about peripherals? Is everything supported with Windows 10? How about software? Not all software is supported, even if the manufacturer says it is. I found this out the hard way with Quickbooks and Quicken for a real estate company and it cost them $$$ because they had no choice but to pay for the latest versions. To say they were pis*ed is an understatement.
The last thing you want - going through an RMM - is a mass silent, but forced upgrade to Windows 10. There are many reasons to not do this, compatibility for one. Are all machines on Windows 7 all running 64 bit or are there 32 bit ones as well? You really don't want 32 bit. What about peripherals? Is everything supported with Windows 10? How about software? Not all software is supported, even if the manufacturer says it is. I found this out the hard way with Quickbooks and Quicken for a real estate company and it cost them $$$ because they had no choice but to pay for the latest versions. To say they were pis*ed is an understatement.
Mainstay
Well-Known Member
- Reaction score
- 747
Options for companies with disparate hardware running Windows 7:
1. Have each system, 1-by-1, come into our shop and get a fresh ssd, and a fresh setup (massive amounts of time and energy and highly disruptive to the operations)
2. Remotely access each machine and upgrade it manually... could still yield an unhappy upgrade to W10
3. Blanket fleet upgrade (great new machines, but high cost that most companies don't *really* budget for, plus I get to be the messenger that tells them they have to upgrade or die).
4. RMM deploy on batches of systems using a script to minimize our initial time spent on each system, and then put out whatever fires are started during the upgrade. We can select systems for the upgrade and others that are simply too old to languish in W7 purgatory or mark them for replacement.
Guys, I get it, a fresh re-do is best, but I don't see how it is practical on a larger scale.
So how are you handling your fleets? Especially for those operations that aren't used to the idea of equipment replacement plans or having *real* IT budgets (as is the case for 100% of every customer I have ever encountered, including the big boys that talk a good talk but then somehow will have to put that deployment on next years budget).
1. Have each system, 1-by-1, come into our shop and get a fresh ssd, and a fresh setup (massive amounts of time and energy and highly disruptive to the operations)
2. Remotely access each machine and upgrade it manually... could still yield an unhappy upgrade to W10
3. Blanket fleet upgrade (great new machines, but high cost that most companies don't *really* budget for, plus I get to be the messenger that tells them they have to upgrade or die).
4. RMM deploy on batches of systems using a script to minimize our initial time spent on each system, and then put out whatever fires are started during the upgrade. We can select systems for the upgrade and others that are simply too old to languish in W7 purgatory or mark them for replacement.
Guys, I get it, a fresh re-do is best, but I don't see how it is practical on a larger scale.
So how are you handling your fleets? Especially for those operations that aren't used to the idea of equipment replacement plans or having *real* IT budgets (as is the case for 100% of every customer I have ever encountered, including the big boys that talk a good talk but then somehow will have to put that deployment on next years budget).
Sky-Knight
Well-Known Member
- Reaction score
- 5,627
- Location
- Arizona
No SSD means no Win10. I've already "handled" my fleet, in planned staged upgrades over years. Now is not the time to be doing this, the game is already over. Systems with Win7 on them are all without exception, well past EOL. Upgrade in mass is only going to knock entire networks offline as the platter drives give up the ghost.
If a new client came to me, I'd sell them a batch of refurbs, migrate people to them, take what was replaced, and refurb what I can, sell more fresh refurbs to fill the gap... repeat. This process continues until the entire network is refreshed. I can sell an Optiplex refurb with Win10 pro on it for less than an iPad, if they can't afford that, they can't afford to be in business.
If a new client came to me, I'd sell them a batch of refurbs, migrate people to them, take what was replaced, and refurb what I can, sell more fresh refurbs to fill the gap... repeat. This process continues until the entire network is refreshed. I can sell an Optiplex refurb with Win10 pro on it for less than an iPad, if they can't afford that, they can't afford to be in business.
This idea works well in large environments where the have 2-3 basic models or machines with similar setups.
This allows them to make a corporate base image and deploy in mass.
This doesn't work well when you have 20 random off the shelf best buy machines all with different specs.
Sent from my SM-G870W using Tapatalk
This allows them to make a corporate base image and deploy in mass.
This doesn't work well when you have 20 random off the shelf best buy machines all with different specs.
Sent from my SM-G870W using Tapatalk
Similar threads
