Hi All :
Recently many of my friends are in consultation on Domain rename issus , so i finished a new version document that Windows Server 2008 R2 ADDS domain renaming.
Operation is not complicated, for your reference. Hope useful for you.
Enjoy!
Justin Gao
Microsoft (China)
This document will to show you how to implementing Application Virtualization 5.0 deployment, and how to sequence application and so on .
More information you can reference TechNet library : http://technet.microsoft.com/en-us/library/jj713487.aspx
Please use 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 .
Please use Adobe Reader X or above version to open .
Enjoy !
Hi all :
This post will to show how to migration from Exchange 2007 and Exchange 2010 coexistence environment to Exchange 2013. This document just have core migrate phase, Mailbox role.
About Upgrade from Exchange 2010 to Exchange 2013 , please reference TechNet document : http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
About Upgrade from Exchange 2007 to Exchange 2013 , please reference TechNet document : http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
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 :
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 .
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 !
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 )
This doucment teach you how to deploy AGPM v3 on AD enviroment , including setup , config and recovery GPO .
System Center 2012 Configuration Manager RC is coming , you can through this link to download RC image : http://www.microsoft.com/download/en/details.aspx?id=27841
About official document please access this link : http://technet.microsoft.com/en-us/library/gg682129.aspx
I found more changed and improve in RC , like fully support SQL Server 2008 R2 , and integration System Center 2012 Endpoint Protection (Formerly known as Forefront Endpoint Protection).
Some snapshot provide to your reference .
Integration Server and Client mutil-language :
Need open or setting FW 4022 port for SQL Server Service Broker to replicate data between sites
RC Version :
Adjusted console workspace :
Advanced security mode ! need to config certificates.
System Center 2012 Configuration Manager deployment document will publish when RTM.
The next version of Opalis is named System Center Orchestrator 2012 , this document introduct how to deployment System Center Orchestrator 2012 Beta.
Data protection is essential to a business or organization, and System Center 2012 Data Protection Manager (DPM) is an effective solution for providing that protection.
DPM includes the following features:
You can back up the DPM database to tape, or you can use a second DPM server in a geographically separated location to protect the primary DPM server.
If you use a second DPM server, you can restore data to protected computers directly from the secondary DPM server. The secondary DPM server can also protect computers until the primary DPM server is brought back online.
Now , you can download System Center 2012 DPM RC to testing , about deployment DPM 2012 RC , you can reference this document .
Upgrading Exchange Server 2010 RTM to SP1 is a relatively straightforward process. However, DAG member 's upgrade is not easy , this document intro how to upgrading RTM to SP1 in DAG environment step by step process . For you reference. ;)
Jusitn Gao
Now , you can download Microsoft Deployment Toolkit 2010 Beta1 from Connect website . http://connect.microsoft.com/
What's new in MDT 2010 Beta1:
The new features in MDT 2010 Beta 1 are supported only for Lite Touch Installation (LTI)–based deployments and are not supported for Zero Touch Installation (ZTI)–based deployments using Microsoft System Center Configuration Manager 2007.
The MDT 2010 Beta 1 release includes the following new features:
· Support for Windows 7 Beta. Deploy Windows 7 Beta by using MDT 2010 Beta 1.
· Support for Windows Server 2008 R2 Beta. Deploy Windows Server 2008 R2 Beta by using MDT 2010 Beta 1.
· Support for Windows Automated Installation Kit (Windows AIK) version 2.0. Deployment of Windows 7 Beta and Windows Server 2008 R2 Beta by using MDT 2010 Beta 1 requires the use of Windows AIK version 2.0.
· Support for Windows User State Migration Toolkit (USMT) version 4.0. USMT 4.0 is required to support Windows 7 Beta deployments. Specifically, the following new features of USMT 4.0 are supported in LTI-based deployments:
· Support for USMT 4.0 hardlink migration. USMT 4.0 includes a new method of saving user state called hardlink migration. Hardlink migration creates a snapshot of current user data files before reinstallation, which keeps data in the same location on the disk while upgrading the system and rebuilds the links after Windows 7 Beta is installed. Hardlink migration dramatically reduces the time required to migrate user state, because the data is never moved, which is faster than copying the user data to another disk.
· Support for USMT 4.0 shadow copy. USMT 4.0 supports the ability to archive files that are in use by using the shadow copy feature in Windows 7 Beta and Windows Server 2008 R2 Beta.
· Support for the Deployment Image Servicing and Management (DISM) tool. The new DISM tool (Dism.exe) allows for servicing offline images, mounting and unmounting Windows Imaging format (WIM) files, and customizing Windows Preinstallation Environment (Windows PE) boot images. The DISM tool replaces many of the tools in previous versions of the Windows AIK, including Package Manager (Pkgmgr.exe), the International Settings Configuration Tool (Intlcfg.exe), and the Windows PE command-line tool (PEimg.exe).
· Support for Windows PE version 3.0. Windows PE 3.0 is included as a part of the Windows AIK version 2.0 and is required to deploy Windows 7 Beta and Windows Server 2008 R2 Beta by using MDT 2010 Beta 1.
· Support for the Boot Configuration Data (BCD) management tool. MDT 2010 Beta 1 uses the new BCDEdit command-line tool to manage BCD files. MDT 2008 Update 1 used the BitLocker™ Drive Preparation Tool (BdeHdCfg.exe) to manage boot configuration.
· Support for Windows 7 Beta default disk partition configuration. In MDT 2010 Beta 1, the disk partition configuration for Windows 7 Beta will be similar to the Windows BitLocker Drive Encryption disk configuration, where the operating system is installed on Disk 0, Partition 2, and the system partition is on Disk 0, Partition 1.
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.
System protection aims to protect you against two scenarios – one where your computer starts, but you have lost system files and registry; and the other where the computer does not start and you have to recover everything. System Center 2012 – Data Protection Manager (DPM) enables you to protect your computer against both these scenarios.
In the past, disaster recovery entailed rebuilding a computer from scratch. This meant installing the operating system, applying updates, installing applications, and then finally recovering data. This was a laborious and error-prone method. DPM saves you the time and trouble of rebuilding your system.
In DPM, System State protection consists of protecting the operating system files, and bare metal recovery (BMR) protection consists of protecting the operating system files and all data except user data on critical volumes.
DPM uses Windows Server Backup (WSB) to perform System State backup and BMR backup. For recovery, DPM will retrieve the backups and you will use the backup data to perform recovery by using WSB.
The following scenarios are not supported for BMR:
Now , i will to show how to protection system status and implementing bare metal recovery .
Create a protection group for a server that protected target , and select Bare Metal Recovery under System Protection node , the System State will be selected at the same time :
on the Select Data Protection Method step , enter a protection group name , and select your protection method , Disk or Tape :
and finish this wizard , the recovery point will start creating :
Waiting some minutes , backup finished :
Now , i will recovering BMR (Bare Metal Recovery) , on the Recovery workspace , select any System Protection recovery point , and then click Recover on the Ribbon :
The Recovery Wizard Review Recovery Selection dialog box appears :
On the Specify Destination dialog box , assign a path that store recovered files :
And finish recovery :
Now , i will to recovery this BMR to bare metal server . start up a bare metal server throw the Windows Server OS image :
On the install windows step , click Repair your computer , and will into Re-image your computer step , assign BMR files path (this path should be a network path):
and will start to recover this Windows Server OS :
Waiting about 15-40 minutes , recovery finished . Restart and logon this OS , you can see recovery successfully :
More detail steps , you can reference the attachment document !
System Center 2012 Operations Manager released , Operations Manager 2012 enables you to monitor services, devices, and operations for many computers in a single console. Operators can gain rapid insight into the state of the IT environment and the IT services running across different systems and workloads by using numerous views that show state, health, and performance information, as well as alerts generated for availability, performance, configuration and security situations.
This post i will to show you how to rapid deploy SC2012 OpsMgr RTM , including MS, Reporting , ACS and so on . You can reference enclosd 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 was GA ! I will continue to post SP1 related documents for your reference.
Now I will first to show you how to deploy System Center 2012 Configuration Manager SP1 on Windows Server 2012 and Windows 8 environment . And how to manage Unix/Linux and Mac client will post in the future.
Microsoft(China)
Office Web Apps Server can communicate with SharePoint 2013, Lync Server 2013, and Exchange Server 2013 by using the HTTPS protocol. In production environments, we strongly recommend that you use HTTPS. In test environments that contain no user data, you can use HTTP for SharePoint 2013 and Exchange Server 2013 and skip the certificate requirement. Lync Server 2013 supports only HTTPS.
Certificates that are used by Office Web Apps Server must meet the following requirements:
The certificate must come from a trusted Certificate Authority and include the fully qualified domain name (FQDN) of your Office Web Apps Server farm in the SAN (Subject Alternative Name) field. (If the FQDN is not in the SAN when you try to use the certificate, the browser will either show security warnings or won’t process the response.)
The certificate must have an exportable private key. On single-server farms, this option is selected by default when you use the Internet Information Services (IIS) Manager snap-in to import the certificate.
The Friendly name field must be unique within the Trusted Root Certificate Authorities store. If you have multiple certificates that share a Friendly Name field, farm creation will fail because the New-OfficeWebAppsFarm cmdlet will not know which of those certificates to use.
The FQDN in the SAN field must not begin with an asterisk (*).
The certificate properties and extensions do not matter. For example, customers have asked us whether Client Enhanced Key Usage (EKU) extensions or Server EKU extensions are required. Office Web Apps Server requires no particular certificate property or extension.
When you installed Office Web Apps Server, you need to request a valid certificate. Now I will to show how to request a OWA certificate.
1. Logon to ADCS server, open the Certificate Template Console, right-click Web Server and click Duplicate Template :
2. Enter a Template name , and select Allow private key to be exported :
3. Click OK to create it, then issue this template:
4. Logon to Office Web Apps Server, open the Certsrv website :
5. Click Request a certificate --- advanced certificate request --- Create and submit a request to this CA --- Advanced Certificate Request page , select just created template and enter a certificate name and a Friendly Name :
6.Click Submit>, then click Install this certificate on the Certificate Issued page:
7. Then use New-OfficeWebAppsFarm cmdlet to create the Office Web Apps Server farm by HTTPS:
Note : The URL that you specify for -InternalURL is the FQDN name of the server that runs Office Web Apps Server. The URL that you specify for –ExternalURLis the FQDN name that can be accessed on the Internet. You must specify the friendly name of the certificate by using the –CertificateName parameter. The –EditingEnabled parameter is optional and enables editing in Office Web Apps when it is used together with SharePoint 2013. The –EditingEnabled parameter is not used by Lync Server 2013 or Exchange Server 2013 because those hosts do not support editing.
8. Last , access https://server.contoso.com/hosting/discovery to verify that the OWA server farm was created successfully, if Office Web Apps Server works as expected, you should see a Web app Open Platform Interface (WOPI)-discovery XML file in your web browser :
System Center 2012 Configuration Manager supports the management of virtual applications that are created with Microsoft Application Virtualization (App-V). When you use Configuration Manager to manage App-V applications, Configuration Manager takes over the management and streaming components of a typical App-V infrastructure.
When you use Configuration Manager to manage virtual applications, you gain the benefits of using a single management infrastructure. You will also gain the benefits of scalability, deployment, and content distribution features, such as collections and user device affinity, and additional advanced application management features that Configuration Manager provides. App-V also integrates with Configuration Manager features, such as operating system deployment, software and hardware inventory, software metering, and Asset Intelligence to support virtual applications.
To deploy virtual applications to computers, you must have the Configuration Manager client and App-V Client installed on your computers. Client devices can include desktop and portable computers, and Virtual Desktop Infrastructure (VDI) clients. The Configuration Manager and App-V Client software work together to deliver, locate, and launch virtual application packages. The Configuration Manager client manages the delivery of virtual application packages to the App-V Client. The App-V Client runs the virtual application on the client.
Now, System Center 2012 SP1 Configuration Manager fully support Application Virtualization 5.0, this document will to show you how to integrate Configuration Manager 2012 SP1 with App-V 5.0.
If you deployment SCCM 2007 based on SQL Server 2008 R2 , and enabling Reporting Service Point , you may occur this error information : SMS_SRS_Reporting_Point Error 7403 - SRS Web Service is not running on SRS Reporting point server "SiteServer Name".
But everything seems normal except for these obnoxious error messages.
So you need to install Cumulative Update package 4 for SQL Server 2008 R2 and resolve this error . KB2345451: http://support.microsoft.com/kb/2345451
Setup this CU4 package and restart , the error is gone , the Green is back !