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 :

         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 :

   Enjoy!

   Justin Gao

   Microsoft (China)

     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

     Please use Adobe Reader X or above version to open.

     Enjoy!

     Justin Gao

     Microsoft (China)

   Hi All :

   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.

     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 !

    Justin Gao

    Microsoft (China)