Oem application profile windows 10
- #OEM APPLICATION PROFILE WINDOWS 10 FOR WINDOWS 10#
- #OEM APPLICATION PROFILE WINDOWS 10 PC#
- #OEM APPLICATION PROFILE WINDOWS 10 WINDOWS 8#
Another thing to also consider, that is sometimes overlooked, is bus speed.
I wouldn’t bother with anything under a quad-core i7.
If you can get a CPU with more cores, 6, 8, great! Xeon CPUs are really nice. You could use a dual-core CPU, but recall the part from above about under powered PCs and virtualization.
#OEM APPLICATION PROFILE WINDOWS 10 PC#
Quad-core CPUs should be a pre-requisite for a host PC that will do virtualization. Intel CPUs have extensions specifically for virtualization. Modern CPUs are plenty powerful for many tasks, virtualization too. 32GB, 64GB of RAM is not unreasonable for this type of work. RAM is also very important because, when using VMs, RAM is being used by both the host and guest operating systems, at the same time.
A combination of something like a 256GB SSD for the host operating system and applications with a 4TB spinning HDD for storage would work well. SSDs are king, but still not equal to spinning disks in price per gigabyte. It’ll work on something smaller, but in that case, you are limiting the whole process. I would not bother using a drive smaller than 1TB. Creating images, multiple images with snapshots, and testing uses up a great deal of space on the disk drive(s). Not all of us have Dell Precision workstations, or even access to a server with Hyper-V or vSphere installed, but using an under powered PC will make building images, and just using virtualization a slow and miserable experience. Given that, you’re going to want to do this work on a moderately beefy PC. I’m sure everything would be fine if Windows was not the host operating system. I think it is best to just stick with that for the whole process. I am aware that there are virtualization products for macOS, and Linux, but we’re working with Windows.
#OEM APPLICATION PROFILE WINDOWS 10 WINDOWS 8#
Microsoft Hyper-V – Comes with 圆4 server versions of Windows (2008 and later), and 圆4 desktop versions of Windows 8 and later.VMware Workstation/ Player – Not free, but feature-rich and integrates into vSphere.Choose whatever virtualization tool out there, they all work very well, some are even free. The actual hardware approach worked for Ghost, but it is not necessary anymore with MDT.
Using actual hardware could work, but there still may be remnants of that hardware that sysprep does not generalize, and could potentially make it into production. This approach allows me to create an image that is truly hardware-neutral. I like to build my images in a virtual machine.
#OEM APPLICATION PROFILE WINDOWS 10 FOR WINDOWS 10#
Largely, the process of making an image for Windows 10 is the same that is was for Windows 7 with a few twists. This summer, Windows 10 is upon us, and we have already begun slowly transitioning some areas to Microsoft’s ultimate operating system. On that note as well, the folks over at Deployment Research have a great post on creating an updated Windows 7 master image with MDT, very helpful. This post is a follow-up or compliment to creating an image of Windows for mass-distribution (Windows 7).