Today is Windows 8 RTM. You can download it from MSDN of Technet if you have a subscription. 
Category: Windows Servers
Windows Server 2012 Editions
Windows Server 2012 delivers a dramatically simplified licensing experience. Shaped by feedback from customers and partners, the new Windows Server licensing approach will help make choosing the right Windows Server easier while delivering the following benefits.
2 Simple
It’s easier than ever to determine the right Windows Server edition for you. Choose from just four editions of Windows Server 2012, based on the size of your organization and your requirements for virtualization and cloud computing.
3 Economical
All editions of Windows Server 2012 deliver excellent economics and ROI for your business. For example, Datacenter edition with unlimited virtualization rights provides the benefits of cloud-level scale with predictable, lower costs. Standard edition now offers all of the same enterprise-class features as Datacenter and is differentiated only by virtualization rights.
4 Cloud-optimized
Businesses today are rapidly adopting a hybrid approach across private and public cloud computing. Windows Server 2012 offers the right edition for you, no matter where you are on your path to the cloud; Datacenter edition for highly virtualized cloud environments, Standard edition for lightly virtualized environments progressing toward cloud, or Essentials edition for an ideal cloud-connected first server.
5 Editions Overview
|
Edition |
Ideal for… |
High Level Feature |
Licensing Model |
Pricing |
|
Datacenter |
Highly virtualized |
Full Windows |
Processor + CAL* |
$4,809** |
|
Standard |
Low density or non- |
Full Windows |
Processor + CAL* |
$882** |
|
Essentials |
Small business |
Simpler interface, |
Server (25 User |
$425** |
|
Foundation |
Economical general |
General purpose |
Server (15 User |
OEM Only |
*CALs are required for every user or device accessing a server directly or indirectly. See the Product Use Rights for details.
System Center 2012 Service Pack 1 CTP2 available
This Community Technology Preview (“CTP2”) enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012 Release Candidate. CTP2 includes updates and enhancements to the following System Center 2012 components:
- Virtual Machine Manager
- Improved Support for Network Virtualization
- Extend the VMM console with Add-ins
- Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
- Ability to convert VHD to VHDX, use VHDX as base Operating System image
- Configuration Manager
- Support for Windows 8
- Support for Mac OS clients
- Support for Linux and Unix servers
- Data Protection Manager
- Improved backup performance of Hyper-V over CSV 2.0
- Protection for Hyper-V over remote SMB share
- Protection for Windows Server 2012 de-duplicated volumes
- Uninterrupted protection for VM live migration
- App Controller
- Service Provider Foundation API to create and operate Virtual Machines
- Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
- Operations Manager
- Support for IIS 8
- Monitoring of WCF, MVC and .NET NT services
- Azure SDK support
- Orchestrator
- Additional support for Integration Packs, including 3rd party
- Manage VMM self-service User Roles
- Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
- Integration with App Controller to consume Hosted clouds
- Service Manager
- Apply price sheets to VMM clouds
- Create chargeback reports
- Pivot by cost center, VMM clouds, Pricesheets
- Server App-V
- Support for applications that create scheduled tasks during packaging
- Create virtual application packages from applications installed remotely on native server
You can get the System Center 2012 Service Pack 1 CTP2 Downloads here:
Windows Server 2012 Release Candidate Build 8400 in VMware Workstation Technology Preview 2012
This procedure describes how to install Windows Server 2012 in VMware Workstation. The following versions are used:
- VMware Workstation Technology Preview 2012 e.x.p Build-646643
- Windows Server 2012 Release Candidate Datacenter Build 8400
In VMware Workstation Technology Preview 2012 create a new VM with the following settings:
- New Virtual Machine
- Custom (advanced)
- Workstation Tech Preview
- Select “I will install the operating system later”
- Select “Microsoft Windows” and select as version “Windows 8 x64”
- Set the Name and Location
- Minimal 1 processor, 1 core
- 2048 MB memory
- Select “Use network address translation (NAT)”
- Select “LSI Logic SAS”
- Create a new virtual disk
- SCSI
- 60 GB disk size
- Leave default disk file
- Finish
- After the VM is created, edit virtual Machine settings and browse for the Windows Server 2012 ISO in the the CD/DVD option
Edit the VMX file and add the following line to the end to of the VMX file:
vmGenCounter.enable = FALSE
During the installation choose for the Windows Server 2012 Release Candidate (Server wit GUI)
Special thanks to my colleague Ivo Beerens
Free e-book: Introducing Windows Server 2012
Microsoft has released a free e-book entitled “Introducing Windows Server 2012”.
The Introduction:
“…Windows Server 2012 is probably the most significant release of the Windows Server platform ever. With an innovative new user interface, powerful new management tools, enhanced Windows PowerShell support, and hundreds of new features in the areas of networking, storage, and virtualization, Windows Server 2012 can help IT deliver more while reducing costs. Windows Server 2012 also was designed for the cloud from the ground up and provides a foundation for building both public and private cloud solutions to enable businesses to take advantage of the many benefits of cloud computing.
This book represents a “first look” based on the public beta release of Windows
Server 2012 and is intended to help IT professionals familiarize themselves with
the capabilities of the new platform. Although certain features may change
between now and RTM, much of the basic functionality likely will remain as
described here, meaning that most of what you learn from reading this book will
continue to benefit you as you begin to evaluate and deploy Windows Server
2012 in your own environment…”
Just click the picture to download the book
OS not starting after removing extra bitlocker boot partition
If you remove the 300mb hidden partition your system does not start anymore.
Solution 1:
Open command prompt
bcdboot c:\windows /s c:
Open diskmgmt.msc & Mark Partion as Active.
Reboot the VM.
Delete the BDEdrive partitie.
Extend the C-Disk with the empty space
Solution 2:
Boot with Windows 7 or WIndows 2008 R2 installation DVD, select repair and open a command prompt.
Type diskpart
Type select disk 0
Type list partition
then note the partition number where you installed windows 7.
Type select partition X (X is the partition number where Windows is installed)
type active
type exit
type bcdboot.exe c:\windows (if C is your windows partition)
Windows Server 8 Beta Active Directory install in Workstation 2012 Tech Preview
Some days ago I was installing Windows Server 8 aka 2012 in Workstation 2012 Tech Preview. I used the default settings where I choise for Windows 8 x64 as version. ![]()
I have used these VMs with the VMware Tools from the TechPreview.
As soon as I try to install and configure the Active Director Domain Services, the VM needs to reboot. Once it has rebooted, it goes in a blank screen, and there is nothing I can do. Workstation thinks the VM is running, but there is no response via the GUI in the VM, no response to ping traffic to the VM or RDP.
Solution:
Downgrade from Workstation TP2012 hardware to Workstation 8 hardware and to select Windows 2008 R2 as the guest OS
![]()
![]()
Setup KMS Server for Windows Server 2008 R2 or Windows 7
Open the command prompt and run the following command:
cscript c: \ Windows \ System32 \ slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Enter the product key xxxxx Windows Server 2008 R2. It is also able to activate Windows 7. The following text appears when the command is successful.
Microsoft ® Windows Script Host Version 5.7
Copyright © Microsoft Corporation. All rights reserved.
Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.
The installation of the KMS server is complete. The server installs itself on port 1688. This port must be opened to be put in the firewall. To change the port the following command can be used.
Slmgr.vbs / SPRT xxxx
Once the firewall is open and the key is installed, the KMS server service has to be restarted. Do this by using the following command:
slsvc & net stop & net start slsvc
To check whether the data will be registered correctly in the DNS, the following command:
nslookup-type = srv _vlmcs._tcp
Here, the following output should appear:
_vlmcs._tcp.test.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms.wardvissers.local
internet address = 192.168.150.7 kms.wardvissers.local
Clients / Servers
The clientele / servers need to connect to the KMS host will automatically find the host by dns. When the client / server using a MAK key is activated. Should this be put back to a KMS client key. These keys are released by Microsoft. When this key is set on the client / server will automatically look for a KMS host. When not present, the client / server activation.
KMS client keys:
Windows 7 Enterprise: 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows Server 2008 Standard: TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Enterprise: YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 R2 Standard – YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise – 489J6-VHDMP-X63PK-3K798-CPX3Y
The following commands can the key be changed from MAK to KMS here are the xxxxx is one of the above keys.
slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Note: To ensure that the client is forced to activate the command to be executed on the client.
slmgr-ato
It can happen that the RMS server returns the following message. This is because the KMS server is just beginning to work with 25 clients and 5 servers.
You can find here the list with error codes & solutions: http://support.microsoft.com/kb/938450
Special thanks to:Harm Hoekstra
Preventing Automatic Service Pack 1 Update to Windows 7 and Windows Server 2008 R2
Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.
Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.
Download
Download details: www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7
The tool can be used with:
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
Toolkit Components
The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.
The components are:
- A Microsoft-signed executable
- A script
- An ADM template
Registry key
The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.
Key value name: DoNotAllowSP
- When the key value name is not defined, distribution is not blocked.
- When the key value name is set to 0, distribution is not blocked.
- When the key value name is set to 1, distribution is blocked.
Blocker Script
The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.
When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.
When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.
Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.
Group Policy Administrative Template (.ADM file)
The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.
Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.
Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.
Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.
How to create a Windows 7 x86 or x64 WMI Filter
I want to deploy some applications to different OS versions. I created some WMI filters. I added the right Group Policy to the right WMI filter.
Target Win 7 32 bit machines:
select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"
Target Win 7 64Bit machines:
select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND OSArchitecture = "64-bit"
Target any 32 bit OS;
SELECT AddressWidth FROM Win32_Processor WHERE AddressWidth =’32’
Target any 64Bit OS:
SELECT AddressWidth FROM Win32_Processor WHERE AddressWidth =’64


