Hi All :
Here’s a hotfix for ConfigMgr 2007 that we recently published. This is an update that adds support for Windows 8-based client computers in System Center Configuration Manager 2007 SP2.
An update is available that adds support for Windows 8-based client computers in Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2).
Additionally, this update adds Windows 8 and Windows Server 2012 to the supported platform list in the following features:
This update also fixes the following issues:
For the latest version of this article as well as a link to the hotfix, please see the following:
2750782 - Update adds support for Windows 8-based client computers in System Center Configuration Manager 2007 SP2 (http://support.microsoft.com/kb/2750782)
Enjoy!
Justin Gao
Microsoft (China)
Microsoft Exchange Server 2013 brings a new rich set of technologies, features, and services to the Exchange Server product line. Its goal is to support people and organizations as their work habits evolve from a communication focus to a collaboration focus. At the same time, Exchange Server 2013 helps lower the total cost of ownership whether you deploy Exchange 2013 on-premises or provision your mailboxes in the cloud. New features and functionality in Exchange 2013 are designed to do the following:
This document will show you how to deploy Exchange Server 2013 RTM in your environment. This document not include any H/A solution.
Please use Adobe Reader X or above version to open .
Windows 8 and Windows Server 2012 released , I believe more and more company will begin to deployment. I think you will start to consider how to planning activation method. MAK ? KMS ? or ...
Windows Server 2012 have a new feature call Active Directory-Based Activation :
Active Directory-based Activation is a role service that allows you to use Active Directory Domain Services (AD DS) to store activation objects, which can further simplify the task of maintaining volume activation services for a network. With Active Directory-based Activation, no additional host server is needed, and activation requests are processed during computer startup. Any computers running Windows 8 or Windows Server 2012 with a Generic Volume License Key (GVLK) that are connected to the domain will activate automatically and transparently. They will stay activated as long as they remain members of the domain and maintain periodic contact with a domain controller. Activation takes place after the licensing service starts. When this service starts, the computer running Windows 8 or Windows Server 2012 contacts AD DS automatically, receives the activation object, and activates without user intervention.
This document is introduce how to installing and implementing ADBA.
Please use Adobe Reader X or above version to open.
Enjoy！
Hi all :
Windows 8 and Windows Server 2012 was RTM , many people may hope deploy Windows 8 in their company . Now System Center 2012 Configuration Manager SP1 beta can support Windows 8 .
In this post , I will to show how to use System Center 2012 Configuration Manager SP1 Beta to deployment Windows 8 .
Including these parts:
This post not contain MDT 2012 part.
Please use Adobe Reader X or above version to open !
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 .
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 )
New in System Center 2012 Configuration Manager, the Exchange Server connector allows you to find and manage devices that connect to Exchange Server (on-premise or hosted) by using the Exchange ActiveSync protocol. Use this mobile device management process when you cannot install the Configuration Manager client on the mobile device.
More details , you can reference this operations document.
最近SQL Server 2012正式发布，虽然目前无法正式销售，需要到7月1日以后才能有价格。但相信SQL Server 2012的不少新特性已经让大家跃跃欲试。像 Exchange Server 2010的高可用性(DAG)一样，SQL Server 2012也整合了以前所具有的几种高可用性功能，实现了新的高可用性技术，我们称为 AlwaysOn，一个类似于DAG的技术。
很多朋友在考虑SQL Server数据库高可用性的时候，一定会考虑群集方案，但实际部署会遇到很多难题，其中部署过程就非常让人头疼。
SQL Server 2012 的AlwaysOn同样需要利用到Windows Server Failover Cluster技术，但步骤较先前方式简单很多。
具体SQL Server 2012 AlwaysOn的实现，请各位参考附件的文档。
请使用Adobe Reader X或更高版本打开!
System Center 2012 SP1 CTP2 availability , you can download them from this link : http://www.microsoft.com/en-us/download/details.aspx?id=30133
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:
When you finished System Center 2012 cloud services process pack deployment , you need to create VMM , OM and Orchestrator connector , create and configure cost center and so on .
More details , please reference this document .
About one month ago , I posted a blog introduce how to deploy System Center 2012 Operations Manager RTM in a signle server environment , it's very easy and smoothly .
But based on different customers environment or requirments , you should to design and deploy SC2012 OM on a distributed environment .
This document will to show your how to deploy SC2012 Operations Manager RTM on a distributed environment .
Now , we are officially hit Windows Server 2012 Release Candidate , we've got one last round of scale updates for Windows Server 2012 with Hyper-V.
This is in addition to the huge scalability updates we already at announced at beta for Windows Server 2012 which are:
You can download Windows Server 2012 RC from : http://www.microsoft.com/en-us/server-cloud/windows-server/2012-server-virtualization.aspx
The System Center Cloud Services Process Pack provides a service solution for automating the deployment of private and public cloud infrastructures. With the System Center Cloud Services Process Pack, enterprises can realize the benefits of infrastructure as a service while simultaneously leveraging their existing investments in System Center 2012 – Service Manager, System Center 2012 - Orchestrator, System Center 2012 – Virtual Machine Manager, and System Center 2012 – Operations Manager.
The System Center Cloud Services Process Pack offers a self-service experience to facilitate private cloud capacity requests from your business unit IT application owners and end users, including the flexibility to request additional capacity as business demands increase.
You can download System Center Cloud Services Process Pack at the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkID=231143.
Build a CSPP environment need a patient and lengthy waiting process , the deployment phase , please reference this document .
When you install System Center 2012 Cloud Services Process Pack , you need to import lots of dependencies for the SC2012 VMM Discovery MP .
These packs contain the required management packs, namely:
The IIS 2008 management pack actually needs Microsoft.Windows.Server.2008.Discovery (which needs Microsoft.Windows.Server.Library.mp) which is part of Windows Server Operating System Management Pack for Operations Manager 2007.
To collect these MPs is so smarting .
Now , System Center 2012 Cloud Services Process Pack already collected relate MPs in the setup package .
And the last , you just need to import System Center 2012 Virtual Machine Manager Discovery monitoring pack :
System Center 2012 App Controller is a unified management public cloud and private cloud tool , and App Controller is simple and straightforward to install and use.
Now , i will to show you how to deploy SC2012 App Controller RTM , you can reference this document.
With Windows Server our goal is to provide the best platform for cloud and you can see that in spades in Windows Server 2012. We’ve quietly engaging on this strategy for years. For example, Linux support on Hyper-V. Microsoft has been contributing GPL to the Linux kernel for years now and we’ve long supported Red Hat, SUSE, CentOS and the latest release of Ubuntu 12.04 (released with the last couple of weeks) even includes the Hyper-V drivers built in by default. Now, we’re taking this to the next level:
FreeBSD support on Hyper-V.
We’ve listened to our valued customers who have told us that they’ve been successful virtualizing Windows and Linux and now want to take a look at their pockets of FreeBSD Unix and want to consolidate them on Hyper-V and better manage them via System Center. So, today, we’re announcing that we are working with our partners NetApp and Citrix to develop and extend support for FreeBSD on Hyper-V. This means that we’re developing FreeBSD drivers to enable FreeBSD to run as a first-class guest on Windows Server Hyper-V. The drivers will be fully released early this summer, including the source code for the drivers under the BSD license, and will initially work with FreeBSD 8.2 and 8.3 on Windows Server 2008 R2 and eventually on Windows Server 2012.
IT administrators perform many tasks and procedures to keep the health of their computing environment up-to-date and their business running. Tasks might include the following diverse activities, for example, new employees require that accounts and resources are configured, a business acquisition requires integrating a system from another vendor, and new hardware requires provisioning. Individual tasks and subtasks are automated, but typically, not the whole process. In addition, the administrators must maintain quality standards and system efficiency. System Center 2012 - Orchestrator can tie disparate tasks and procedures together by using the graphical user-interface Runbook Designer to create reliable, flexible, and efficient end-to-end solutions in the IT environment.
By using Orchestrator, you can carry out the following tasks:
Orchestrator provides tools to build, test, debug, deploy, and manage automation in your environment. These automated procedures, called runbooks, can function independently or start other runbooks. The standard activities defined in every installation of Orchestrator provide a variety of monitors, tasks, and runbook controls with which you can integrate a wide range of system processes. Each activity in a runbook publishes data that is available to any subsequent activity in that runbook. You use this Published Data to provide dynamic, decision-making capabilities, which can include creating emails, alerts, log files, accounts, and more.
Your IT organization can use Orchestrator to improve efficiency and reduce operational costs to support cross-departmental objectives. Orchestrator provides an environment with shared access to common data. By using Orchestrator, you can evolve and automate key processes between groups and consolidate repetitive manual tasks. You can automate cross-functional team processes and enforce best practices for incident, change, and service management by creating runbooks that are customized for your requirements. Through automation, regularly recurring tasks reduce the number of manual and error-prone activities in your environment. Orchestrator helps you improve the reliability and predictability of your IT procedures.
Orchestrator integrates with System Center, other Microsoft products, and non-Microsoft products to enable interoperability across the data center. Orchestrator improves efficiency across multiple tools, systems, and departments by eliminating or crossing technology and organizational process structures. You can extend the capabilities of Orchestrator with integration packs that include additional functionality for both Microsoft and non-Microsoft products and technologies. Orchestrator activities and integration packs reduce unanticipated errors and shorten service delivery time by automating the common tasks associated with enterprise tools and products.
Orchestration is the collective name for the automated arrangement, coordination, and management of systems, software, and practices. It enables the management of complex cross-domain processes. Orchestrator provides the tools for orchestration to combine software, hardware, and manual processes into a seamless system. These tools let you connect and automate workflows.
Just as manufacturing companies have automated common and repeatable tasks from their production processes, you can adopt this same efficiency in the IT environment by using Orchestrator to seamlessly perform and monitor your IT processes. Orchestrator can handle routine tasks, process enforcement, and reliably meet the demands of the largest enterprises. Orchestrator integrates seamlessly with other System Center products to integrate IT administrative tasks from start to finish.
If you have a custom in-house solution, Orchestrator provides extensible integration to any system through the Orchestrator Integration Toolkit. You can create custom integrations that allow Orchestrator to connect to any environment.
Orchestrator uses a Representational State Transfer (REST)-based web service that can perform processes like start and stop runbook jobs and get reporting information in Open Data protocol (OData) format. The web service lets you develop applications that can use live data from Orchestrator.
This post , i will to show you how to deployment System Center 2012 Orchestrator RTM.
System Center 2012 – Service Manager provides an integrated platform for automating and adapting your organization’s IT service management best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management.
This document i will to show you how to deployment System Center 2012 Service Manager at the distributed servers.
Please using Adobe Reader X or above version to open.
Because of the design changes that were introduced in Microsoft System Center 2012 Configuration Manager, you cannot upgrade an existing Microsoft System Center Configuration Manager 2007 infrastructure to System Center 2012 Configuration Manager. However, you can maintain your existing investment when you migrate to System Center 2012 Configuration Manager and use the built-in functionally within System Center 2012 Configuration Manager.
When you migrate from Configuration Manager 2007 to System Center 2012 Configuration Manager, you can access data from the site databases that you identify in the Configuration Manager 2007 infrastructure and then transfer this data to the System Center 2012 Configuration Manager hierarchy. Migration does not modify the data in the Configuration Manager 2007 hierarchy, but instead discovers the data and stores a copy of it in the System Center 2012 Configuration Manager database. You can migrate some or all of the supported data from a Configuration Manager 2007 site to a System Center 2012 Configuration Manager site. You can also migrate the data from a single Configuration Manager 2007 site to several different System Center 2012 Configuration Manager sites, or you can move data from multiple Configuration Manager 2007 sites to a single System Center 2012 Configuration Manager site.
Benefits of Migrating to System Center 2012 Configuration Manager :
When you migrate your Configuration Manager 2007 site infrastructure, you retain your existing management information and gain the following benefits from System Center 2012 Configuration Manager.
Native 64-bit code
System Center 2012 Configuration Manager is a native 64-bit application.
Site database improvements
The System Center 2012 Configuration Manager database supports full Unicode.
Database replication between sites
Replication in System Center 2012 Configuration Manager is based on Microsoft SQL Server, which improves the performance of site-to-site data transfer.
User-centric management
Users are the focus of management tasks in System Center 2012 Configuration Manager. For example, you can distribute software to a user even if you do not know the device name for that user. Additionally, System Center 2012 Configuration Manager gives users much more control over what software is installed on their devices and when it is installed.
Hierarchy simplification
The new central administration site type in System Center 2012 Configuration Manager, as well as changes to the behavior of primary and secondary sites let you build a simpler site hierarchy that uses less network bandwidth and requires fewer servers.
Role-based administration
This central security model in System Center 2012 Configuration Manager offers hierarchy-wide security and management that corresponds to your administrative and business requirements.
About how to migration from Configuration Manager 2007 to System Center 2012 Configuration Manager RTM , you can reference this document .