Computer imaging for depolyment
-
What is the "official" say from Microsoft on the Windows 10 free upgrade in a domain environment. I understood it that all machine would qualify for the upgrade? Or is it just for "Home" users?
I don't mind buying a Volume License for both Win10 and Win7 to get the imaging rights. But I don't want to but 100's of Windows 10 licenses :), but I also don't want issues when it comes audit time or reimage a machine after the FREE offer expires. -
@hobbit666 said:
@scottalanmiller said:
You can build a lot of drivers and such into a base image. Although standardizing on a model is a good first step. You want to reduce "Model Sprawl" whenever possible.
Yeah we have started trying to buy the same model over the last 6 months, but doesn't help when these suppliers/manufactures keep changing things all the time lol.
How much are they changing? We can go years buying from a single vendor and the changes are really minimal.
-
Have you looked into bulk refurbed desktops? You can generally get them at 50-70% off retail. Bump up the RAM and you can generally get 4-5 years out of them if not longer. This would go a long way to standardizing your systems and save some money.
-
@coliver said:
Have you looked into bulk refurbed desktops? You can generally get them at 50-70% off retail. Bump up the RAM and you can generally get 4-5 years out of them if not longer. This would go a long way to standardizing your systems and save some money.
We do this, works great.
-
@scottalanmiller said:
You can build a lot of drivers and such into a base image. Although standardizing on a model is a good first step. You want to reduce "Model Sprawl" whenever possible.
I haven't made model specific images since the early 2000's when Win98 and Ghost ruled the land. Since about 2005 or so I've stuck with creating a universal image in Vmware and deploying it to machines.
And since the consolidation of all the hardware with AMD and Intel it's been much easier to keep OOBE in line on boot. Used to be lots of different drivers would need to be deployed, but now I can just lay down basic Windows drivers, put the updated ones on a directory, then deploy it out.
-
To get your Windows 10 upgrade (home or Pro) you have to do the upgrade manually first. That process will attach the Windows 10 license to your machine via MS servers.
Then once you have upgraded it, you can blow it away and push your image onto the machine.
-
@Dashrender said:
To get your Windows 10 upgrade (home or Pro) you have to do the upgrade manually first. That process will attach the Windows 10 license to your machine via MS servers.
Then once you have upgraded it, you can blow it away and push your image onto the machine.
But is the FREE upgrade allowed on machines that will be joined to the domain??
-
But I will still need to buy a VL version of Win10Pro and Win7Pro so I can use the generic key to create and deploy the image onto machines?
-
@hobbit666 said:
@Dashrender said:
To get your Windows 10 upgrade (home or Pro) you have to do the upgrade manually first. That process will attach the Windows 10 license to your machine via MS servers.
Then once you have upgraded it, you can blow it away and push your image onto the machine.
But is the FREE upgrade allowed on machines that will be joined to the domain??
Yes as long as they are Professional not Enterprise. If you are using volume media you need to install OEM then do the inplace upgrade. You can then blow it away with a clean install of windows 10 Professional using Retail or Volume media if imaging.
-
@hobbit666 said:
But I will still need to buy a VL version of Win10Pro and Win7Pro so I can use the generic key to create and deploy the image onto machines?
Just one copy.
-
@Jason said:
@hobbit666 said:
But I will still need to buy a VL version of Win10Pro and Win7Pro so I can use the generic key to create and deploy the image onto machines?
Just one copy.
Agreed, you don't need both, only VL for Win10, you get downgrade rights if you really need Win7
-
Can you image home machines, even with a VL?
-
Couple of the most key points I've learned about deployment(s)
-
Have one replacement laptop & desktop at minimum ready to roll 24/7, 365. You will need it most when you least expect it.
-
Have a base image, update it a week after patch Tuesday every month
-
Buy all the same model of laptop / desktop. There is no good reason to have more than 1 model of desktop and AT MOST two models of laptop purchased in a year.
-
Make a checklist for deployment and stick it on each computer. Tick all the boxes as you complete them and sign it, date it, and leave it on the computer until it gets deployed.
-
Have a standardized method of data xfer/backup and stick to it.
-
Label/serialize laptops/desktops and keep a list of it all. More details the better.
.... more as I think of them.
-
-
@Dashrender said:
@Jason said:
@hobbit666 said:
But I will still need to buy a VL version of Win10Pro and Win7Pro so I can use the generic key to create and deploy the image onto machines?
Just one copy.
Agreed, you don't need both, only VL for Win10, you get downgrade rights if you really need Win7
Probably not. You probably have to start with Windows Pro on that machine. Physical location doesn't matter.. just are you running Win 10 Home or Win 10 Pro.. I'm sure you can only apply VL to Pro because the imaging rights only apply to the same version that exists within VL.
-
@Dashrender that was my feeling too. But sometimes "Home" is considered a lower version of "pro".
-
@scottalanmiller @Dashrender are you not allowed to sysprep and change the key on a home license? I swear you could, but yeah no VL for sure.
-
@MattSpeller said:
@scottalanmiller @Dashrender are you not allowed to sysprep and change the key on a home license? I swear you could, but yeah no VL for sure.
As only VL offers that right, if VL doesn't apply then it can't be done for Home.
-
@MattSpeller said:
Couple of the most key points I've learned about deployment(s)
-
Have one replacement laptop & desktop at minimum ready to roll 24/7, 365. You will need it most when you least expect it.
-
Have a base image, update it a week after patch Tuesday every month
-
Buy all the same model of laptop / desktop. There is no good reason to have more than 1 model of desktop and AT MOST two models of laptop purchased in a year.
-
Make a checklist for deployment and stick it on each computer. Tick all the boxes as you complete them and sign it, date it, and leave it on the computer until it gets deployed.
-
Have a standardized method of data xfer/backup and stick to it.
-
Label/serialize laptops/desktops and keep a list of it all. More details the better.
.... more as I think of them.
Thanks for all the tips there, all along my way of thinking.
So how do I start making a deployment image now
-
-
I was in the same boat as you not so long ago...until I did a trial of SmartDeploy. Much like PSX mentions above, we have one VM that is our master image, and we are able to use the platform packs SmartDeploy makes to push our image along with the drivers we need onto different model PCs without much trouble (PXE boot SmartDeploy with a thumb drive that has the right drivers and pull down the image over the network). We are primarily a Dell shop, even when we buy refurbished machines. I love the product, and it has saved us many a man hour. The licensing for 250-300 PCs is probably about $30 per station plus about 20% per year for software maintenance. Talk with CDW, SHI, or your favorite reseller to get a quote. But even before that, I recommend doing an evaluation of SmartDeploy. You won't be sorry, and then hardware standardization will no longer be a roadblock for you.
-
I will also say SmartDeploy has released / will release a product called PointFlip that creates layers on your end user PCs, allowing you to install an application on a reference computer and then push that application install to another computer running PointFlip. I believe you can also use it to upgrade the OS of a machine from 7 to 8.1 or probably to 10 at some point. I did some beta testing for this product earlier in the year but ran out of time to test it as much as I wanted. But it looks like it will be something very useful. It might be worth a look also down the road.
