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)
Hi all :
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 :
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 :
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
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 !
Beginning with Configuration Manager SP1, you can configure a distribution point that is not on a site server to be a pull-distribution point. When you deploy content to a large number of distribution points at a site, pull-distribution points can help reduce the processing load on the site server and can help to speed the transfer of the content to each distribution point. This efficiency is achieved by offloading the process of transferring the content to each distribution point from the distribution manager process on the site server. Instead, each pull-distribution point individually manages the transfer of content by downloading content from another distribution point that already has a copy of the content. A pull-distribution point can only obtain content from a distribution point that is specified as a source distribution point.
Pull-distribution points support the same configurations and functionality as typical Configuration Manager distribution points. For example, a distribution point that is configured as a pull-distribution point supports the use of multicast and PXE configurations, content validation, and on-demand content distribution. A pull-distribution point supports HTTP or HTTPS communications from clients, supports the same certificates options as other distribution points, and can be managed individually or as a member of a distribution point group. However, the following configurations are exceptions to support for the pull-distribution point:
The attached document will to show you how to installing and configure a DP being a Pull-DP.
Please use Adobe Reader X or above version to open!
Hi Everyone:
Long time no see :) . I had just internal transfer to Microsoft Enterprise Services, as an Solution Architect to dedicated to the smart city project in China, MSFT called CityNext.
Recently, many of customers very interested in Windows Azure, many people planning to use Windows Azure Pack build a internal IaaS Public Cloud.
This blog will introduce how to express deployment Windows Azure Pack.
More information please reference : http://technet.microsoft.com/en-us/library/dn296435.aspx
When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.
Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.
1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created. Right click, select New –> Computer :
2. In the Computer name box, type the name that was assigned to the database availability group :
3. Click OK , the computer account created . Right-click this account and click Properties :
4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :
6. When presented with the disable dialog, select Yes :
7. After the object has been successfully disabled, press the OK button on the success confirmation :
8. And now , you can start to creating DAG successfully !
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
Lync Server 2013 CU (KB 2809243) has been released at Jan.8 2014. You can download this CU from this link : http://www.microsoft.com/en-us/download/details.aspx?id=36820
The update process is very simple. For the best practice, you can refer this flowchart :
Now I will to show this process.
Logon to the Lync Server Frontend server for enterprise edition or standard edition. Open the Powershell cmdlet , run Get-CsPoolUpgradeReadinessState , If the State value of the pool is Busy, wait for 10 minutes, and then try to run the Get-CsPoolUpgradeReadinessState cmdlet again. If you see Busy for at least three consecutive times after you wait 10 minutes in between each attempt, or if you see any result of InsufficientActiveFrontEnds for the State value of the pool, there is an issue with the pool.
Stop new connections to the frontend server by using the Stop-CsWindowsServers cmdlet and run Get-CsPoolUpgradeReadinessState again
Make sure the State is Ready, go to the update phase. Open the Lync Server 2013 Cumulative Update Installer, you will to see the updates list :
Click Install Updates will start automatic installing process
Wait some minutes, the updates install completed
Then use Start CsWindowsServices cmdlet to starting all services. Logon to the Lync Server 2013 Control Panel, you can see the version is 5.0.8308.556:
Now the update is completed. For more information, please check the KB 2809243 : http://support.microsoft.com/kb/2809243/en-us
This post will to introduce how to deploy Lync Server 2013 Standard Edition, the whole processes is easy.
More information, you can refer TechNet website:http://technet.microsoft.com/en-us/library/gg398616.aspx
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.
Today, Cumulative Update 2 for System Center 2012 R2 Configuration Manager released. There is also an updated version of the UNIX/Linux client to provide support for Ubuntu 14.04; It is referenced in the CU2 KB and has a standalone KB too.
Regarding how to install CU2, please refer : http://blogs.technet.com/b/justin_gao/archive/2014/06/21/you-need-to-know-how-to-apply-cumulative-update-1-for-system-center-2012-r2-configuration-manager-kb2938441.aspx
When updated, the Administrator Console version is 5.0.7958.1303:
The Client version that is displayed on the General tab of the Configuration Manager Control Panel item or the Client Version field of device properties in the Administrator Console is 5.00.7958.1303:
In the System Center 2012 R2 Configuration Manager console, you can see the Client Version in the collection:
The System Center Configuration Manager Company Portal app allows users of Windows 8 and Windows 8.1 machines to view and install applications made available to the user by their administrators. The machine must be managed by Microsoft System Center 2012 R2 Configuration Manager, or later, with the agent installed. The app communicates directly with the Configuration Manager on-premise server infrastructure. Note that this contrasts with the Windows Intune Company Portal app (available through the Windows Store and the Download Center) which communicates directly with the Windows Intune service.
You can download System Center Configuration Manager Company Portal app from : http://www.microsoft.com/en-us/download/details.aspx?id=40795
The enclosed document will to show how to install Company Portal app and how to deploy applications throw Company Portal.
More information, please refer the TechNet library : http://technet.microsoft.com/en-us/library/jj822984.aspx
System Center 2012 R2 Configuration Manager released cumulative update 1 at Mar. 28. This update contains fixes for various issues including Windows PowerShell, and an updated version of the Endpoint Protection client.
You can download CU1 for System Center 2012 R2 Configuration Manager from : http://support.microsoft.com/kb/2938441
For more information about the Windows PowerShell changes, refer to the following knowledge base article:
KB 2932274: Description of PowerShell changes available in Cumulative Update 1 for System Center 2012 R2 Configuration Manager
For more information about the Endpoint Protection client, refer to the following TechNet blogs:
http://blogs.technet.com/b/configmgrteam/archive/2014/03/27/anti-malware-platform-updates-for-endpoint-protection-will-be-released-to-mu.aspx
http://blogs.technet.com/b/configmgrteam/archive/2014/03/27/fep-and-scep-anti-malware-protection-support-after-oses-reach-end-of-life.aspx
Today, I will use this blog post to instruct you how to apply CU1 for System Center 2012 R2 Configuration Manager.
My testing environment have six VMs:
1-3 OS based on Windows Server 2012 R2 DataCenter RTM ; 4-6 OS based on Windows 8.1 Enterprise RTM ; Database is SQL Server 2012 with SP1. The System Center 2012 R2 Configuration Manager RTM version is 5.0.7958.1000 :
This update totally have three main step:
1) Let's starting step one now. Download CU1 for SC2012 R2 CM on the Site Server and click it to run, the install wizard dialog box appears:
2) Click Next, make sure the prerequisite check all passed:
3) On the Console Update Option page, make sure your selected Install the update for the Configuration Manager console:
4) On the Database Update page, keep the default settings, Yes, update the site database:
5) On the Deployment Assistance Options page, make sure your selected all options:
6) On the next three page, you can confirm this three packages information:
Server update package:
Console update package:
Client update package:
7) Then start installing phase, waiting some minutes, the installation completed:
8) Review the SC2012 R2 Configuration Manager site server's version is 5.0.7958.1203 :
9) The update packages has been created:
10) Now will into the Client updating phase. Deploy the R2 CU1 - x64 (or x86) client update - MCM software package :
11) On the Monitoring workspace, Deployments node, you can see this package deploy status:
12) On the Client computer, you will see the installing notification:
13) Wait some minutes, the install completed, you can see the Configuration Manager Client version is 5.00.7958.1203 :
14) Throw the management console, you can see all client agent has been updated to the CU1:
15) The last step is updating Remote Console. Use the same method, deploy R2 CU1 - console update - MCM software package:
16) On the Console computer, you can see the installing phase on the Software Center :
17) The installing phase is very fast, then you can see the complete notification :
18) Then open the management console, you can see the CU1 version is 5.0.7958.1203:
19) Now CU1 has been updated.
Regarding more update System Center 2012 (R1 or R2) Configuration Manger information, please refer : http://technet.microsoft.com/en-us/library/jj553405.aspx
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.
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 )
CU3 for System Center 2012 Configuration Manager SP1 released, you can download it from MSFT Support website. http://support.microsoft.com/kb/2882125/en-us
This update adds support for Windows 8.1-based client computers in Microsoft System Center 2012 Configuration Manager Service Pack 1. Windows 8.1 is added to the supported platform list for the following features:
Issues that are fixed
This cumulative update includes the following updates:
Additionally, this cumulative update fixes the following issues:
This cumulative update fixes the following issue:
This cumulative update fixes the following issues:
This cumulative update includes the following update:
Additionally, this cumulative update fixes the following issue:
This post will introduce how to deploy Lync Server 2013 Enterprise edition , the whole process is very similar to the standard edition. About more details information , please refer TechNet library : http://technet.microsoft.com/en-us/library/gg398616.aspx
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 !
With Work Folders users can store and access work files on personal computers and devices, often referred to as bring-your-own device (BYOD), in addition to corporate PCs. Users gain a convenient location to store work files, and they can access them from anywhere. Organizations maintain control over corporate data by storing the files on centrally managed file servers, and optionally specifying user device policies such as encryption and lock-screen passwords.
Work Folders can be deployed with existing deployments of Folder Redirection, Offline Files, and home folders. Work Folders stores user files in a folder on the server called a sync share. You can specify a folder that already contains user data, which enables you to adopt Work Folders without migrating servers and data or immediately phasing out your existing solution.
This Document will to show how to enable Work Folders feature in your enterprise.
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.
System Center 2012 Configuration Manager Support Center helps you to gather information about System Center 2012 Configuration Manager clients, so that you can more easily address issues with those clients when working with product support specialists. Configuration Manager Support Center includes a tool that gathers a bundle of log files, and also a tool that is used by product support specialists to examine log files and other client data for in-depth analysis of issues with Configuration Manager clients.
You can from this link to download Configuration Manager Support Center : http://www.microsoft.com/en-us/download/details.aspx?id=42645&751be11f-ede8-5a0c-058c-2ee190a24fa6=True
When you installed Support Center, you can see two tools, are Support Center and Support Center Viewer:
You can use Support Center remote connecting computer and collect all data:
Collect result like this:
Client Details:
Client Policy:
Content:
Logs:
Regarding Configuration Manager Support Center , please refer TechNet Library : http://technet.microsoft.com/en-us/library/dn688621.aspx
Lync Server 2013, Persistent Chat Server enables you to participate in multiparty, topic-based conversations that persist over time. Persistent Chat Server can help your organization do the following:
In Lync 2013, Persistent Chat functionality is integrated into the Lync 2013 client. As a result, users have access to Instant Messaging/Presence, Audio/Video, Conferencing, and Persistent Chat all in the Lync 2013 client.
This document will to show how to deploy Lync Server 2013 Persistent Chat server.
IP Address Management (IPAM) in Windows Server® 2012 and Windows Server® 2012 R2 is an integrated suite of tools to enable end-to-end planning, deploying, managing and monitoring of your IP address infrastructure, with a rich user experience. IPAM automatically discovers IP address infrastructure servers on your network and enables you to manage them from a central interface.
This post I will to show IPAM part 2 : How to using IPAM on the Windows Server 2012 R2 environment.
More information you can refer : http://technet.microsoft.com/en-us/library/hh831353.aspx