Q. What are the different ways in which Microsoft OEM System Builder Windows desktop operating system licenses can be distributed?
Q. Can I provide a computer system to my customer without an operating system (also referred to as a "naked PC")?
Q. Can I create my own recovery disks and sell these with the computer systems that I build? I have heard that direct OEMs can do this, so why can't I?
Q. Are system builders allowed to create a "ghost image" CD and ship it along with the system for OEM customers?
Q. What is the OPK and why do I have to use it?
Q. We would like to create a computer system using an OEM Windows operating system that has a dual-boot feature. The single system would use the same version of Windows on both boot images/partitions.
Does this require two different licenses, or can I use the same license and product key for both images/partitions, since they are both on a single system that can use only one operating system at a time?
Q. Can a PC with an OEM Windows operating system have its motherboard upgraded and keep the same license? What if it was replaced because it was defective?
Q. The new COA is shaped differently from the previous, rectangular COA. How do I apply it for the best coverage?
Q. How does a company qualify to become a direct Microsoft OEM? It seems that the larger companies currently have an unfair advantage compared with smaller OEMs.
Q. I am a reseller of PCs that come preloaded with OEM Windows operating systems. Am I allowed to load Microsoft Office 2010 onto these machines?
Q. Can two or more users access and fully utilize OEM Windows operating systems concurrently on the same machine?
Q. What can system builders offer their customers as a "legalization solution" for Windows desktop operating systems?
Return to top