Hi All :
Today , I am installed a System Center 2012 Operations Manager SP1 Beta on new platform , Windows Server 2012 , SQL Server 2012 and so on .
Installation phase the same on Windows Server 2008 R2 platform .
For your reference .
Please use Adobe Reader X or above version to open.
Enjoy!
Justin Gao
Microsoft (China)
Hi all :
At any time after installing Windows Server 2012, you can run Setup to repair the installation (sometimes called “repair in place”) or, in certain cases, you can convert to a different edition.
You can run Setup to perform a “repair in place” on any edition of Windows Server 2012; the result will be the same edition you started with.
For Windows Server 2012 Standard, you can the system to Windows Server 2012 Datacenter as follows:
From an elevated command prompt, determine the current edition name with the command DISM /online /Get-CurrentEdition.
Make note of the edition ID, an abbreviated form of the edition name. Then run DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, providing the edition ID and a retail product key.
And press Enter :
Note : About KMS Client setup key , you can find it from : http://technet.microsoft.com/en-us/library/jj612867.aspx
Press Y and the server will restart twice. When you logon again , the version is converted to Datacenter :
System Center 2012 SP1 Beta announced , you can download them from this link : http://www.microsoft.com/en-us/download/details.aspx?id=34607
The Beta of System Center 2012 Service Pack 1 (“SP1”) enables System Center customers to jointly evaluate System Center 2012 with Windows Server 2012 and Windows 8.
For Configuration Manager SP1 Beta , the new features including :
This post , you can follow me to build a System Center 2012 Configuration Manager SP1 Beta on Windows Server 2012 and Windows 8 OS platform , including SQL Server 2012 being a database.
You can reference this document .
Windows Server 2012 already RTM , you may want to install more applications to the Windows Server 2012 . SQL Server 2012 is one of the most important applications!
SQL Server 2012 need .Net Framework 3.5 and .Net Framework 4.0 ; .Net Framework 4.0 is already installed on Windows Server 2012 , so you need to installing .Net Framework 3.5 , even under the Windows Server 2012 OS.
When you installing SQL Server 2012 on Windows Server 2012 , on Feature Selection dialog box , you can see the .Net Framework 3.5 to be turned on :
If you Ignore this step , you may encounter Error Code : -2146498298 , like this :
And the finally , installing failed :
Now I use DISM command tool to check windows server features status :
Dism / online /get-features | more
Run this command , you can see NetFx3ServerFeatures & NetFx3 features not enable :
Use two commands to enable these two features :
Dism /online /enable-feature /featurename:NetFx3ServerFeatures /source:X:\sources\sxs
Dism /online /enable-feature /featurename:NetFx3 /source:X:\sources\sxs
Enable finished , you can check them again :
You can reinstall SQL Server 2012 ,on the Feature Selection dialog box , you can saw .Net Framework 3.5 already installed :
Continue to complete the installation.
Enjoy !
Hi All:
Exchange Server 2013 preview published , all server components can install on the newest server OS (Windows Server 2012) . If you hope to try it ,you can download it from : http://technet.microsoft.com/en-US/evalcenter/hh973395.aspx?wt.mc_id=TEC_116_1_6
Today , I will to introduction how to installing Exchange Server 2013 preview .
My test lab environment OS is all Windows Server 2012 datacenter RTM , forest and domain level are Windows Server 2012.
The first phase is prepare AD , this phase need to running three commands :
1.PrepareSchema :
2.PrepareAD :
3.PrepareDomain :
When you finished AD preparation , now you will start to install Exchange Server 2013 preview . Because Exchange Server 2013 just have Mailbox and CAS roles , and Microsoft recommand first install Mailbox role .
Now insert Exchange Server 2013 Preview image to starting install.
"STOP!!!!!!!" I think you may to ask "You need to install Exchange requirements firstly".
The answer is NO , Exchange Server 2013 more simplifying the installation process. When you start to install , you will into Check for Update ? dialog box :
Check finished , will copy install file to local :
Copy finished , will into Introduction dialog box :
Click Next , will into License Agreement dialog box :
Accept and click Next , will into Error Reporting dialog box :
Select your option and click Next , will into Server Role Select dialog box , now you can select your need to installing Exchange role , Mailbox or CAS or both . By default , setup will automatically install Windows Server roles and features :
Click Next , will into Installation Space and Location dialog box :
Choose a location and click Next , will into Malware Protection Settings dialog box :
Select your option and click Next , will into CEIP dialog box :
Select your option and click Next will into Readiness Checks phase :
Check if OK you can click install to start installing process , waiting some 10 minutes, install finished :
Click complete , you can find Exchange Server 2013 preview shortcut in Start :
The last , Exchange 2013 have not EMC (Exchange Management Console) mmc snap-in console , in 2013 they called EAC (Exchange Admin Center) , you can throw web browse to access , the address is : http(s)://CAS(FQDN)/ecp .
Now you can build a test lab to testing more new features .
Throughout the development of Windows Server 2012, we have regularly pushed the scale boundaries as test resources and engineering schedule allowed. For example, in pushing Hyper-V scale to support up to 64 virtual processors per VM, it isn’t just replacing some static variables and retesting. There is serious engineering prowess that is brought to bear to ensure uniform and consistent scaling across the board such as:
Scalability means systematically breaking through one scalability barrier only to find the next one, addressing that to ultimately achieve system balance. To that end, Windows Server 2012 is redefining performance and scale and the reason for its success has been the tremendous work cross-team to identify and mitigate these issues across the platform. To that end, I’d like to extend a huge thanks to all of the teams helped us achieve these goals including:
>> Windows Core Kernel, Storage, Networking, Hyper-V, Clustering <<
Because the Windows Server 2012 scale limits have continuously grown throughout development, I want to make sure that everyone is using the same FINAL scalability numbers and present one more update courtesy of the Failover Clustering Team. With Windows Server 2012 RTM, we now support up to…
>> 8,000 Virtual Machines in a Cluster <<
Read that last sentence one more time.
Yes , that’s right, 8,000 VMs in a cluster. To put that in perspective in terms of numbers for VMs per server in a cluster that translates to:
Nodes in Cluster
Number of VMs per Server
8
1000
16
500
32
250
64
125
As you can see, you could do an 8 node cluster with 1,000 VMs per server, but failing over 1,000 VMs per server will logically take some time and be dependent on a multitude of factors most of them storage related.Thus, the ability to support up to 64 nodes (twice as many as VMware) to disperse the load is significant.
Awesome.
So, let’s take a look at the final scalability numbers for Windows Server 2012 Standard AND Datacenter Editions with Hyper-V enabled.
===========================================================================
Windows Server 2012 Standard/Datacenter Editions with Hyper-V Enabled
Windows Server 2008 R2
Windows Server 2012
Improvement Factor
Logical Processors Per Host
320*
5x
Physical Memory per Host
1 Terabyte
4 Terabytes*
4x
Virtual Processors per Host
512
2048*
Virtual Machines per Host
384
1024*
2.7x
Virtual Processors per VM
4
16x
Memory per VM
64 Gigabytes
Maximum Virtual Disk
~2 TB
64 TB*
32x
Nodes in a Cluster
64*
Virtual Machine in a Cluster
1,000
8,000*
8x
*= Industry Leading
I am so exciting to tell you , Windows Server 2012 & Hyper-V Server 2012 RTM !
Windows Server 2012 RTM Evaluation and VHD download from : http://technet.microsoft.com/en-us/evalcenter/hh670538.aspx?wt.mc_id=TEC_108_1_33
Other related resources you can find them from : http://www.microsoft.com/en-us/server-cloud/windows-server/trial.aspx?WT.mc_id=MSCOM_EN_US_DLC_FEATURE_131C1ENUS26852
Windows Server online launch website : http://www.windows-server-launch.com/
Microsoft Deployment Toolkit is the recommended process and toolset for automating desktop and server deployment.
MDT provides you with the following benefits:
Now , the MDT newest version is MDT 2012 Update 1 , you can order it from : http://www.microsoft.com/en-us/download/details.aspx?id=25175
Some of the key changes in MDT 2012 Update 1 are:
MDT 2012 Update 1 Deployment Workbench :
This document will to show you how to using Microsoft Deployment Toolkit 2012 Update 1 to deploy Windows 8 RTM . (Not contain integration with System Center 2012 Configuration Manager )
Please use Adobe Reader X or above version to open .