Today is my last day of using Win 7

[kingoranks]

We currently use win 7 in school, tomorrow I plan to install window 10 on my machine and start testing.

 

How did you deploy win 10 if you are using it?

 

We use MDT to deploy win 7, any advice, guide and info will be appreciated.

[DJ-1701]

MDT for Windows 10 (Basic Functionality) - Blogs - EduGeek.net

[FishCustard]

Just don't bother building 'fat' images, you'll be swapping out Win 10 builds too quickly for that. Thin image, apply software with GPO / scripting / black magic.

[free780]

It can depend on how quick you need to reimage PCs. If you can automate the image creation say via MDT you can still use a hybrid image. I deal with some large parts of pieces of software and imaging still has its place. You can apply a Culmative update when imaging to bring the image up to date.

[ThatBoringBloke]

Our build process is simple. When I say our, I mean my, since I'm on my own.

 

Light weight 'base' image - OS (without any customisation), Office 2016, and an old version of Photoshop that I couldn't get to deploy.

Sysprep and upload to WDS

Deploy image straight from WDS with an unattend file.

PDQ Deploy everything else including updates.

Job done.

[itmanager___]

PDQ deploy is new to me, can you please explain how you use it?

Also is the free version able to deploy updates?

 

Many thanks.

[Duke5A]

We currently use win 7 in school, tomorrow I plan to install window 10 on my machine and start testing.

 

How did you deploy win 10 if you are using it?

 

We use MDT to deploy win 7, any advice, guide and info will be appreciated.

 

What edition do you plan on deploying? It pretty much comes down to LTSB vs Education. If you're using Office 365 then it would make sense to go with Education or any other edition that has the full MS Store functionality and other bits. If you're not on Microsoft's cloud platform and you want something similar to the no hassle way of doing things that was 7, then LTSB is for you. Building an image around LTSB is really no different than how it was done on 7. I still pre-roll mine in a virtual machine, capture using DISM and deploy with WDS. Really only have to open it up for updates every five or six months.

[PotNoodleTech]

Savour the final day of everything working perfectly!

[mikkydoos]

Savour the final day of everything working perfectly!

 

Oh indeed. You voluntarily opted to end your life. Are you still breathing ?

[CHiLL]

I use SCCM & MDT to deploy out our Windows 10 image.

 

Once I have the ISO from VLSC and installed the latest ADK tools, I can extract the WIM from the ISO and use that when creating a new MDT Task Sequence in SCCM. Once the MDT TS has been created, I can take modifications/steps from my previous Task Sequences and use them in this new TS. Some of these steps include; installing drivers based on the detected make/model of the machine, setting the time zone to London (defaults at Pacific time), installing Windows Updates, installing essential software (such as Office, Adobe Reader, Chrome, 7-Zip, etc), setting default file associations (doesn't work properly, PITA) to name some.

 

That TS can then be PXE booted or deployed via USB if required.

 

Note: The TS image can be quite large if lot of machines/drivers are defined. For example, I have ~100 Ergo/surface style tablets that have no LAN and only one USB 3.0 port. As I cannot PXE boot them, I need to use a USB drive...but the complete image can be approximately 15GB. These tablets have a tendancy to corrupt USB drives on a regular basis and repeatedly waiting for a 15GB image to be created is a nightmare. So I copied the existing TS and disabled all drivers except the ones for these devices. Now the image to transfer is only about 8GB.

 

Note II: I have since been able to get a PXE solution working for these using a USB to Ethernet adapter (and a lot of investigation with WinPE!)

[Mujja]

I use SCCM & MDT to deploy out our Windows 10 image.

 

Once I have the ISO from VLSC and installed the latest ADK tools, I can extract the WIM from the ISO and use that when creating a new MDT Task Sequence in SCCM. Once the MDT TS has been created, I can take modifications/steps from my previous Task Sequences and use them in this new TS. Some of these steps include; installing drivers based on the detected make/model of the machine, setting the time zone to London (defaults at Pacific time), installing Windows Updates, installing essential software (such as Office, Adobe Reader, Chrome, 7-Zip, etc), setting default file associations (doesn't work properly, PITA) to name some.

 

That TS can then be PXE booted or deployed via USB if required.

 

Note: The TS image can be quite large if lot of machines/drivers are defined. For example, I have ~100 Ergo/surface style tablets that have no LAN and only one USB 3.0 port. As I cannot PXE boot them, I need to use a USB drive...but the complete image can be approximately 15GB. These tablets have a tendancy to corrupt USB drives on a regular basis and repeatedly waiting for a 15GB image to be created is a nightmare. So I copied the existing TS and disabled all drivers except the ones for these devices. Now the image to transfer is only about 8GB.

 

Note II: I have since been able to get a PXE solution working for these using a USB to Ethernet adapter (and a lot of investigation with WinPE!)

 

Almost exactly the way I deploy Windows 10.

 

What issues do you have with file associations? How to you apply them?

 

We found if applied using a script (e.g. task sequence) you need to apply every association, even if not changed, or you get the error notifications. If applying using GPO you only need a config file with the change associations. I'll post a link to the documents I followed when I find it.