Vmware Windows Activation Oem Remote' title='Vmware Windows Activation Oem Remote' />I own a small computer shop, and when we reinstall windows for a customer whose Hard Drive has crashed, we reuse the customers OEM key. Most PCs are Home Premium. Creating Samsung recovery disc on a Windows 8 laptop Last Modified 20130807 1854 UTC Created 20130805 1650 UTC. How to Build a VMware v. Sphere VM Template for Windows Server 2. R2 Jason. Samuel. Get that Windows XP Mode to work on the locked versions of Windows 7 quick As editorinchief of 99U, Adobes publication for creative professionals, Matt McCue oversees stories about topics like client work, storytelling, and productivity. This post describes how to license virtual machines that are running Windows Server 2012 or Windows Server 2012 R2. A co worker and myself were asked to create a VMware v. Sphere ESX template for Server 2. R2 and its not as easy as you might think. Over the course of a day and half and through much research and trial and error, we have come up with the perfect template for our organization. Its a perfect base template for us but depending on where you intend to deploy it and your own organizations requirements, you may have to edit it a bit. How To Prevent or Grant access to Registry Editor in Your Windows 7810. Microsoft has been busy getting rid of all the Windows activation cracks that started to pour out even before the final release of Microsoft Windows 7. VMware ESX How to Build a VMware vSphere VM Template for Windows Server 2008 R2. This piece originally appeared in Lauren ONeals email newsletter Activism for NonActivists. It is reprinted here with permission. Firefox 32 Bit Windows 7 Ultimate firefox 32 bit windows 7 ultimate Windows 7 ultimate 32 bit activation key free download Solved Solved Product key free download. We intend to tweak the template even further and possibly even create separate images depending on if the VM will be deployed internally or externally. Please do comment if you have any suggestions or think we may have missed something. Building a VMware template for Server 2. Server 2. 00. 8 R2 has some differences. This blog post will cover everything we did to successfully get it working and a detailed explanation of why we chose certain settings. Big thanks to to Jeremy Waldrop and his blog post that described setting up a template for 2. R2. OS Used Windows Server 2. R2 Standard x. 64 Volume License Edition. VM Hardware config Single v. CPU 4 GB RAM 4. 0 GB Primary Hard Drive for Operating System 1. GB Secondary Hard Drive for Page File. LSI Logic SAS SCSI Controller. VMXNet 3 Network Adapter. I know most organizations using Server 2. GB C partition. With 2. I suggest going to 4. GB OS drives as a standard. Server 2. 00. 8 especially x. Out of the box 2. R2 x. 64 takes up 1. GB. Also Server 2. This is because 2. Remember, Server 2. MS product is all about componentizationWhen you install a component from this store, my understanding is that it is projected to the OS. So basically Windows 2. As the system receives updates over time, expect this directory to grow even larger since it never deletes old stuff. Think of the different versions of kind of stacking on each other. I believe with each service pack there is a tool to uninstall components that are no longer necessary or superseded. So stick with a 4. GB OS partition and you should be fine for a long time. You will also notice we have a 1. GB secondary drive for a page file. Well get to that later in the article. Now on to the actual build First create a new VMSelect Custom Configuration. Enter VM Name and Inventory Location Select Datastore. Select Virtual Machine Version 7. Select Microsoft Windows Server 2. R2 6. 4 bit as OS Version of Virtual Processors 1. Amount of RAM 4. GBNetwork of NICs 1. Adapter Type VMXNET 3. Select Connect at Power On. SCSI Controller LSI Logic SASCreate New Virtual Disk 4. GBAdvanced Options No Change. Now prepare the virtual hardware Edit VM Settings Options General Section Uncheck Enable loggingBoot Options Check box to force going into the BIOS on next boot. Power on the VM will go directly to BIOS Advanced IO Device Configuration Disable Serial port ADisable Serial port BDisable Parallel port. Exit and Save OS Installation and Configuration. Install Windows 2. R2 Standard Full Install After OS install and reboot, change Administrator Password will promptDisconnect Windows 2. R2 ISO and set device type to Client Device. Set Time Zone. VMware Tools Install. Install VMtools, choose Custom Install Type. Disable the Shared Folders drive and install Tools Note we are disable Shared Folder due to profile loading issues which was documented even back in ESX 3. VMware Tools here on the VMare Communities forum. I have not personally had an issue leaving it enabled but just to be cautious and the fact we dont use this feature in our organization, we have left it disabled. Set time synching between the VM and ESX host. Reboot after Tools Install. Network Configuration. From Server Manager, select View Network Connections. Right click on Local Area Connection and select properties. Uninstall Qo. S Packet Scheduler and both Link Layer Topologies Mapper Responder We dont do QOS at the server level, our switches do that. Link Layer is not used by us. Uncheck IPv. 6 and close network connection screens We dont use IPv. Server Name. From Server Manger select Change System Properties. On System Properties screen click Change on Computer Name Tab. Set Server Name and restart. Windows Updates. From Server Manager under Security Information, select Configure Updates. Select Let me choose. Under Important Updates, select Never check for updates, click ok. Start All Programs Windows Update Check for updates and install all Recommended Updates. Enable Remote Desktop, choose Allow connections from computers running any version of Remote Desktop 2nd optionDisable Windows Firewall Not best practice to disable, but my environment requires it. From Server Manager, select Do not show me this console at logon and close Server Manager. Taskbar Changes. Right click 3rd icon from Start Button Windows Explorer and select Unpin this program from taskbarRight click 2nd icon from Start Button Windows Power. Shell and select Unpin this program from taskbarRight click Taskbar and choose Properties and choose Customize under Notification Area. Select Turn system icons on or off, and turn Volume Off, click Ok. System Performance. From Server Manager select Change System Properties. Select Advanced Tab Settings and choose Adjust for best performanceFolder and Search Options. Open Computer Select Organize Choose Folder and search options. Under View Tab. Select Show hidden files, folders and drivesUncheck Hide extensions for known file typesIE ESCFrom Security Information Section, select Configure IE ESCChange Administrators to Off and leave Users On My reasoning for this is the only Users should be service accounts on a server so leaving it On should not matter. Change IE Home Page to blank so you dont get that pesky Internet Exploer Enhanced Security Configuration warning page. Under Computer, right click c and select properties, uncheck Allow files on this drive to have contents indexed in addition to file propertiesApply changes to c and all subfolderfiles. ContinueIgnore on Access Denied errors. Power Options from Control PanelChange option to High Performance. Disable Hibernation. Command Prompt, enter powercfg. Delete the Page file and reboot so c can be fully defragmentedRun defrag. Page File. Edit VM Properties. Add a 2nd hard drive 1. GB and change to SCSI 1 0Run Disk Manager and format as Z drive We use Z as the drive letter so it does not interfere with adding additional drives later on. From Server Manager, select System Properties Advanced Performance Settings Advanced Virtual Memory Change. Assign 1. 02. MB Page file to c Assign 5. MB Page file to z SNMPServer Manager Add Features SNMPServer Manager Configuration Services SNMP Security. Accepted community names Add your community as READ ONLYAccept SNMP Packets from these hosts Add your hosts remember to leave localhost in thereTurn VM into a Template This procedure will copy the Administrator account profile into the default user profile so that all users that login or that will be created in the future will get the same profile with all the customizations you have done above. When you sysrep a server template and create a new VM from it, a new SID is generated which means a new local Administratior account is created during the sysrep procedure. This means all the customizations you have done will be wiped out above unless you copy all your settings above when you create a new VM. In the past with Server 2. Server 2. 00. 8, you had the Copy To feature to copy a user profile to another. With Server 2. 00. R2, Microsoft has disabled this feature. Virtualisation Licensing for WS2. WS2. 01. 2 R2. I am not answering any more questions on this post  to be honest, there have been too many for me to have the time to deal with them. Dont bother asking Ill ignoredelete it. My recommendations are Re read this post if you do not understand it after the first or second reads. To be honest, most of the questions have been from people who are just trying to make things complicated. Just license the hosts for the maximum number of Windows Server VMs that can ever run on that host, even for 1 second. It is that simple Ask your LARdistributorreseller thats their job and thats why you pay them. This post follows my dissertation on Windows Server 2. Edit The below is unchanged with WS2. R2. The only difference is that WS2. R2 Datacenter edition only includes Automatic Virtual Machine Activation. Im putting Hyper V aside for just a few minutes to talk about how you will license virtualisation of Windows Server 2. Sphere, Hyper V, Xen. Server, or whatever tickles your fancy. BTW, the counting here also applies to System Center 2. Core Infrastructure Suite CISEnrolment for Core Infrastructure ECI minimum of 2. Please read this post s l o w l y and let it sink in. Then read it again. If you have been eating bowls full of VMware FUD then read it a third time slowly. FAQVOSE or virtual operating system environment is a licensing term for virtual machine VM. It is used when talking about licensing a VM for Windows Server. When you buy a license for virtualisation you legally buy and assign it to hardware, not to VMs. The virtualisation rights of Windows Server licenses the VMs on the licensed host for Windows Server. There is no mobility with OEM. You can move a volume license and its virtualisation rights once every 9. If you want to use HA clustering, Live Migrationv. Motion, DRSDynamic OptimizationPRO, then you need sufficient virtualisation rights on each host to support the maximum number of VMs that is possible on that host, even for 1 second. You cannot split a license or its virtualisation rights across hosts. Virtualisation rights are 2 VOSEs for a host licensed by Windows Server 2. Standard and unlimited VOSEs for a host licensed for Windows Server 2. Datacenter. Virtualisation rights covers the host for the assigned edition of Windows Server 2. Windows Server.   It does not include Windows 87Vista. You can assign more than 1 license to a host. In other words, you license a host for the maximum number of Windows Server VMs that it could host. Host, 1 CPU, 2 VMs. Here you want to run a single host that has 1 CPU. The host will run 2 Windows Server virtual machines. You will assign a single Windows Server 2. The license covers 2 CPUs there is only 1 and provides virtualisation rights for 2 virtual operating system environments VOSEs. In other words, you get rights to install Windows Server 2. Standard or previous versions in 2 VMs on this host. Host, 2 CPUs, 4 VMs. The Standard edition covers 2 VOSEs, but the customer wants 4 VMs running Windows Server Standard 2. R2.   A single copy of WS2. Standard will not suffice. VOSEs VMs with licensing. Host, 2 CPUs, 1. 0 VMs. There are two options do you go with the Standard or Datacenter editions of Windows Server 2. The Standard edition covers 2 VOSEs, but the customer wants 1. VMs running Windows Server Standard 2. R2. A single copy of WS2. Standard will not suffice. VOSEs VMs with licensing. Based on USA Open NL pricing the licensing of these VMs will cost 8. The Datacenter edition of WS2. VOSEs and covers 2 CPUs in the host. This solution will require a single Windows Server 2. Datacenter license which will cost 4,8. Atlantic Shopify Theme Designers. Decision If you will not go over 1. VMs on this host then Windows Server 2. Standard edition is the way to go. If you estimate that there is a good chance of the VM numbers growing then spend an extra 3. Windows Server 2. Datacenter with its unlimited VOSE rights. USA Open NL pricing. Once you reach 1. VOSEs on a 1 or 2 CPU host, you need to consider the Datacenter edition because it is cheaper once you hit 1. VOSEs. 1 Host, 4 CPUs, 4 VMs. Its an unusual configuration but a valid one for the demonstration. The WS2. StandardDatacenter SKUs cover 2 CPUs each. In this case there are 4 CPUs. This will require 2 copies of Windows Server 2. Standard, which also covers the 4 VMs. Lets pretend that 3. VMs will run on this host with 4 physical CPUs. Then we would assign 2 copies of Windows Server Datacenter on it. CPUs each 4 CPUs and unlimited VOSEs. That Host with 3. Logical Processors 1. CPUs with 1. 6 Cores with Hyperthreading. The maximum specification for Windows Server 2. Hyper V is 3. 20 logical processors in the host. That could be 1. Intel CPUs, each with 1. Hyperthreading enabled. We dont count cores or logical processors when we license. We count CPUs, sockets, or plain old processors pick the term you prefer. There are 1. CPUssocketsprocessors in this server. That requires 5 copies of either Windows Server 2. Standard or Datacenter, depending on the required number of VOSEs. Clusters. Lets move on to the clusters, where people usually get things wrong because they dont understand or dont want to understand the mobility rights. VOSEs licensed by OEM cannot move. VOSEs licensed by VL can move once every 9. The correct solution is to license each host for the maximum number of VOSEs that it can have for even one second. And when I say correct I mean legal. Software Asset Management professionals auditors are not stupid and the tricks I hear people proposing are neither original or unknown to these auditors. Reminder This applies even to you non Hyper V folks. Hosts, 1 CPU each, 4 VMs. Dont get fooled  This is not one host with 3 VMs and 1 host with 1 VM. This is 2 hosts, each of which can have up to 4 VMs. In the past we would have used Enterprise edition on each host. That has been replaced by Windows Server 2. Standard edition, that now has all the features and scalability of the Datacenter edition. Take each host and size it for 4 VOSEs. That means we need to assign 2 copies of Windows Server 2. Standard edition to each host. Thats 4 copies of WS2. Standard. 2 Hosts, 2 CPUs each, 1. VMs. 10 VMs with 2 hosts means that it is possible to have all 1. VMs on a single host. You have two options to license each host for up to 1. VOSEs. Firstly you could license each of the hosts with 5 copies of Windows Server 2. Standard.   That will give you 1. VOSEs.   This requires 1. Standard at a cost of 8,8. USA Open NL. Alternatively you could license each host with 1 copy of Windows Server 2. Datacenter, at a cost of 9,6. The extra 7. 98 will allow you to burst beyond 1. VOSEs to unlimited VOSEs. Switching to licensing hosts using the Datacenter edition means we dont have to count VOSEs and we have unrestricted mobility between hosts. Hosts, 2 CPUs each, 2. VMs. We have exceed the magic number of 1. Datacenter edition with its unlimited VOSEs per host. Each host has 2 CPUs, so each host requires 1 copy of Datacenter. There are 2 hosts so we require 2 copies of Windows Server 2. Datacenter. You could add more hosts to this cluster and each could have unlimited VMs. As long as the hosts have 1 or 2 CPUs each, each additional host requires only 1 copy of Windows Server 2. Datacenter to license it for unlimited installs of Windows Server for the VMs on that host. Lots of Hosts, Lots of VMs, 4 CPUs per Host. The magic number of 1. VOSEs is a dot in the rear view mirror. We now have lots of hosts with lots of VMs flying all over the place. Each host has 4 CPUs. To license the VOSEs on each host, we will require licensing for 4 CPUs. This will require 2 copies of Windows Server 2. Datacenter per host, each covering 2 CPUs. Live Migration Outside the Cluster. And new for WS2. 01.