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 :

   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

   Please use Adobe Reader X or above version to open.

   Enjoy!

   Justin Gao

   Microsoft (China)

   Hi All :

   CU2 for System Center 2012 Configuration Manager SP1 released, you can download it from MSFT Support website. http://support.microsoft.com/kb/2854009/en-us     

   Issues that are fixed

Administrator Console

• The Add Site Server Roles Wizard incorrectly blocks adding a site server when the first word of the server's fully qualified domain name is longer than 15 characters.
• Multiple nodes and property sheets in the Administrator Console can now be announced correctly by screen reader software.

Application Virtualization

• Virtual Application packages that are saved on a Distributed File System (DFS) share may not migrate from Configuration Manager 2007 to Configuration Manager 2012. Errors that resemble the following are logged in the MIGMCTRL.log file:

  Failed to connect to share \\production\dfs\Virtual Applications\App Source : Error 0x80070520 
  Impersonation is reverted. 
  Set the status of the entity Virtual Application 1 to Failed. 
  Set the status of the job entity Virtual Application 1  to Failed. 
  Microsoft.ConfigurationManagement.Migration.MigrationException: Failed to connect to share \\production\dfs\Virtual Applications\App Source : Error 0x80070520

• Nonalphanumeric characters in the CertificateIssuers string cause site assignments not to work
        (http://support.microsoft.com/kb/2841764/            )    
  in a System Center 2012 Configuration Manager Site environment.

Operating system deployment

• Task Sequences may ignore the Multicast Only flag when downloads are performed within the full operating system instead of Windows PE.
• A task sequence that has multiple "Install Application" steps may fail. Additionally, the following error message is logged in the SMSTS.log file:

  Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

• Clients may not download a new operating system image when custom ports are defined for the site server. The SMSTS.log file will contain error messages that resemble the following:

  WinHttpQueryHeaders() returns status code 404 (Not Found)
  SendWinHttpRequest failed. 80190194.
  DownloadFile failed. 80190194.
  Error downloading file from http://siteserver.contonso.com:80/SMS_DP_SMSPKG$/CAS0000A/sccm?/install_ipremote.cmd to C:\_SMSTaskSequence\Packages\CAS0000A\install_ipremote.cmd
  DownloadFiles failed. 80190194.

• Cumulative Update 2 offers limited support for deployment of Windows PE 3.1-based images. These images must be completed before they are added to the site server. If later changes are needed, they can be made by using the Deployment Image Servicing and Management (DISM) tool. Any Distribution Points that have the old image must be updated.
  
  The following optional components have to be installed beforehand:
  • WinPE-Scripting.cab
  • WinPE-WMI.cab
  • WinPE-WDS-TOOLS.cab
  The following operations are not supported:
  • Installing additional optional component through Configuration Manager
  • Adding drivers
  • Setting scratch space
  • Configuring prestart command
  • Configuring background image file
  • Enabling and disabling command prompt support (debug mode)

Asset Intelligence

• "Software 09B - Computers with infrequently used software installed" reports do not contain accurate data for Windows Installer-based applications that are updated.

Mobile device management

• Windows Mobile 6.5 devices no longer receive application policies after the site server is upgraded from the release version of Configuration Manager 2012 to Configuration Manager 2012 Service Pack 1.

Software distribution

• The content status of a package is stuck in the "In progress - Waiting for Content" status
        (http://support.microsoft.com/kb/2828900/            )    
  in System Center 2012 Configuration Manager SP1.
• Content status may show a state of "Unknown" when a distribution point on a Configuration Manager 2007 Secondary Site is upgraded to Configuration Manager 2012.
• Status messages from pull-distribution points are now routed through management points instead of directly to site servers. This decreases the site server performance effect of having multiple pull-distribution points.

Updated list of supported Linux and UNIX clients

• The list of supported UNIX and Linux platforms is updated to include x86 and x64 versions of the following:
  • Ubuntu 12.04
  • Ubuntu 10.04
  • Oracle Linux 5
  • Oracle Linux 6
  • CentOS 5
  • CentOS 6
  • Debian 5
  • Debian 6

Site systems

• Status Manager may not process changes to built-in Status Filter Rules on localized Configuration Manager installations. Entries similar to the following may be logged in the STATMGR.log file:

  ERROR: The component item for SMS_STATUS_MANAGER in the master site control file does not contain property list items for a status filter named "SMS_STATUS_MANAGER", or those property lists are corrupt or badly formatted.

• Installation of the Client Notification component (bgbisapi.msi) will fail on sites that have custom websites (SMSWEB) or custom ports that are defined. The BGBSetup.log will contain the following errors messages:
  bgbisapi.msi exited with return code: 1603
  Backing up X:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log to X:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log.LastError
  Fatal MSI Error - bgbisapi.msi could not be installed
  The bgbisapiMSI.log will also contain errors that resemble the following:

  ERROR: Failed to configure sms ports '0x80020009'.
  ERROR: Failed to process port information.
  @@ERR:25011
  Product: BGB http proxy -- Internal Error 25011. 80020009
  Internal Error 25011. 80020009
  CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603

• Active Directory User and Group Discovery methods may not update group relationship data when the "Enable delta discovery" option is selected.

Configuration Manager SDK

• The CPApplet.CPAppletMgr Automation object returns error 0x80040154 when you use the object on a 64-bit operating system that has Configuration Manager Compatibility Shims (32BitCompat.msi) installed.

Client

• Automatic client updates are unsuccessful for Configuration Manager 2007 clients
        (http://support.microsoft.com/kb/2832622/            )    
  in System Center 2012 Configuration Manager Service Pack 1

Cumulative Update Setup Wrapper (Installer)

• The installer can now be run again on the same site server to create or to re-create deployment assistance items (packages and programs).
• The installer can update the Administrator Console directly when the installer is run on a site server or on a workstation where the console is installed. Earlier versions of the installer only copied the Administrator Console update (.msp) to the file system, and the console update had to be installed separately. The previous installation method of installing the update manually is still supported.
• The logging format is improved to increase detail for tracking progress or for troubleshooting installation failures.

      Enjoy!

      Justin Gao

      Microsoft (China)

    Hi All :

    With the announcement on TechEd Europe 2013 ,  new version's Microsoft Cloud OS preview are available.

    This including Windows Server 2012 R2 preview , System Center 2012 R2 preview and SQL Server 2014 CTP1.

    You can download these version from TechNet Evaluation Center, link is below :

•     Windows Server 2012 R2 Preview : http://technet.microsoft.com/en-us/evalcenter/dn205286.aspx
•     Windows Server 2012 R2 Essentials Preview : http://technet.microsoft.com/en-us/evalcenter/dn205288.aspx
•     System Center 2012 R2 Configuration Manager and Endpoint Protection Preview : http://technet.microsoft.com/en-us/evalcenter/dn205297.aspx
•     System Center 2012 R2 Preview : http://technet.microsoft.com/en-us/evalcenter/dn205295.aspx
•     SQL Server 2014 Community Technology Preview 1 :  http://technet.microsoft.com/en-us/evalcenter/dn205290.aspx

     Enjoy !

     Justin Gao

     Microsoft (China)