- #Windows testview on restart install
- #Windows testview on restart driver
- #Windows testview on restart windows 10
Identify varied workflows with department heads to make sure they are all tested. Test the environment first with VMs, Then test with whatever varied physical hardware you use. Then get control over your environment back from MS. Then get 10 ready for your business (takes a bit of wrestling with to rip the marketing out of it) and make it stop breaking itself with updates. Get AD ready for 10 if it isn't already, then get your head wrapped around what you need to do to exercise the same level of service and control. Does the version change of user profiles break anything? These kinds of things.Ĭontrol.
#Windows testview on restart install
Install all the things, in whatever varied combinations you use. 10 has quirks here especially with updates. You may have many different hardware combinations, they all need tested.
Pretty easy if you are like us and are 99% VDI. Everything it would run on, everything that will run on it, what is expected of it, and what is required to get it there.
#Windows testview on restart driver
It handles Windows 10, UEFI, and driver install better than anything else I've used. I have a couple spares that I give them and I image their regular computer using MDT. I use a similar process when I test new versions of software.ĮDIT: And for the rollout, I'm just doing a couple at a time - department by department. If they had any issues, I made sure they documented them so they could be fixed before I did a mass roll out. That gave them the chance to do an in-depth test of all of the applications they use, since they're more familiar with their software than I am. The third phase was me installing it on a select few power users' computers. If we used different versions (like Office 20), I made sure all of the versions worked as well. I made sure all of the software ran properly (able to launch and do basic tasks). The second phase was me installing it on a VM and installing every piece of software we use. This gave me a chance to poke around and find out all of the quirks - things I didn't like and things that users will need a little extra training on. The first phase was me installing it on a VM with nothing else installed.
#Windows testview on restart windows 10
How have you all handled windows 10 where you work? Would it be a good idea to ask users if they are interested in their own VM and perhaps ask them if they would test out the software for me and give me feedback, or do you think that wouldn't be appropriate for users to do? (I guess, how would you phrase it and what would you offer to users as far as testing?)
but I guess I would rather learn about quirks now vs when the OS is running on actual hardware. We use specialized software here and the vendors say it is totally compatible with Windows 10 but I usually don't use the software, just support users and open tickets on their behalf. I bounced the idea off of a couple of coworkers, generally they thought it sounded good but also said not sure how much interest I would get and figured everything is going to work fine. So I thought about setting up some Windows 10 test VMs for my users to test out. I am feeling the pressure to start rolling out windows 10 because other departments in my company managed by other IT folks are starting to do it too.