Hi All :
When you install Office Web Apps Server 2013 SP1 on Windows Server 2012 R2, and standalone to use OWA without Exchange, Lync and SharePoint.
You may encounter this error when you open the file:
When you look at the Event Log, you can see the Error Event ID 8115, from Office Web Apps, the general information is Could not contact WOPI End Point. Error details - 'NotImplemented url - https://XXXXX . ....'
To resolve this error, you may install Microsoft .NET Framework 4.5.2.
You can download it from this link : http://www.microsoft.com/en-us/download/details.aspx?id=42643
More information, please refer KB2901954 : http://support.microsoft.com/kb/2901954
Enjoy!
Justin Gao
Microsoft (China)
Online Viewers enable users to use a web browser to view Excel, PowerPoint and Word files that are stored on web servers or shared folders in an organization. Users can conveniently view Office files in a web browser without having to open a separate application. In addition, Online Viewers do not require Office 2013 to be installed on users’ computers. Online Viewers also generate the code that is required to link or embed the URL inside a webpage. You can use Online Viewers within your Intranet, or on the Internet.
Office Web Apps Server provides a page at the address http://OfficeWebAppsServername/op/generate.aspx that you can use to generate links to publicly available documents that have UNC or URL addresses. When a user selects a generated URL, Online Viewers enable Office Web Apps Server to get the file from its location and then render it by using Office Web Apps. The user can view the Word, Excel, or PowerPoint file in a browser with Office features intact. Formatting and layout in Word documents are preserved, data in Excel workbooks can be filtered and sorted, and animations play in PowerPoint presentations. However, be aware that Online Viewers allow users to view but not edit files, and Online Viewers can't open any files that require authentication.
This blog post neither introduce how to install a Office Web Apps Server 2013 environment nor how to configure a certificate. These part you can refer my previous blogs. I am assume you have completed these phase.
Now open the Windows PowerShell cmdlets, using Set-OfficeWebAppsFarm - OpenFromUrlEnabled to enable URL opening files. When Online Viewers are turned on (set to True by using OpenFromUrlEnabled), this parameter turns on or off the ability for Online Viewers to display files in UNC paths. By default, this parameter is set to True, but make sure OpenFromUrlEnabled is also set to True before you enable opening files from UNC paths. We recommend you set this parameter to False if you have set up Office Web Apps Server to connect to the Internet.
Then open online viewers generate website : https://<OWA's FQDN>/op/generate.aspx , enter the file UNC address and click Create Link:
Then click Test this link, will online viewing the file:
Also you can open the PDF file:
Powerpoint Web App:
Slide Show:
Web Application Proxy is a role service of the Remote Access server role in Windows Server® 2012 R2. Web Application Proxy provides reverse proxy functionality for web applications inside your corporate network to allow users on any device to access your web applications from outside the corporate network. Web Application Proxy pre-authenticates access to web applications by using Active Directory Federation Services (AD FS), and also functions as an AD FS proxy.
This blog post will to teach you how to install WAP server to support external user through ADFS access internal website.
Please use Adobe Reader X or above version to open!
AD FS provides simplified, secured identity federation and Web single sign-on (SSO) capabilities for end users who want to access applications within an AD FS-secured enterprise, in federation partner organizations, or in the cloud.
In Windows Server® 2012 R2, AD FS includes a federation service role service that acts as an identity provider (authenticates users to provide security tokens to applications that trust AD FS) or as a federation provider (consumes tokens from other identity providers and then provides security tokens to applications that trust AD FS).
Today's post I will to show how to use Active Directory Federation Services 3.0 to build a simply federation architecture for internal user. Regarding the external user supporting, please refer the Part 2.
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
Please use Adobe Reader X or above version to open.
Today, Cumulative Update 3 for System Center 2012 R2 Configuration Manager released.
Regarding how to install CU3, 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.1401:
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.1401:
This post I will to show IPAM part 1 : How to deploy IPAM on the Windows Server 2012 R2 environment.
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:
Enjoy !
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
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
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 blog post I will show you how to implementing external user remote access Lync, at Lync Server 2013 environment, I will simulate external user through Lync Edge Server role to access Lync Server.
Certificates configure is very important.
More information you can access TechNet library : http://technet.microsoft.com/en-us/library/gg398918.aspx
Although Forefront TMG 2010 retired, Forefront UAG 2010 still handle edge access security protection. In fact, TMG was bundled with UAG, so you can still use TMG through UAG server.
This blog post will to show how to deploy Forefront UAG 2010.
More information, please refer TechNet library: http://technet.microsoft.com/en-us/library/ff358694.aspx
Continue last blog post for Windows Azure Pack express deployment, this post will to show you how to reconfigure WAP website FQDN , Ports and Certificates.
The core phase including:
More information , please refer : http://technet.microsoft.com/en-us/library/dn528551.aspx
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
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.
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
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.
System Center 2012 R2 Configuration Manager released, this document will to show how to deploy System Center 2012 R2 Configuration Manager in the Windows Server 2012 R2 and Windows 8.1 environment. This post will including how to request and configure certificates part.
More detail information, please refer TechNet library : http://technet.microsoft.com/en-us/library/gg682041.aspx
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:
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.
Archiving in Lync Server 2013 can archive the following types of content:
Additionally, Archiving in Lync Server 2013 provides new features that improve deployment and operations efficiency. These new features consist of:
The following types of content are not archived:
This document I will to show how to add and enable archiving feature in existing environment.
Hi all :
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
Service Provider Foundation is provided with System Center 2012 - Orchestrator, a component of System Center 2012 Service Pack 1 (SP1).
Service Provider Foundation exposes an extensible OData web service that interacts with Virtual Machine Manager (VMM). This enables service providers and hosters to design and implement multi-tenant self-service portals that integrate IaaS capabilities available System Center 2012 SP1.
This document will to show how to deploy Service Provider Foundation. More information , you can refer TechNet website: http://technet.microsoft.com/en-us/library/jj642895.aspx
Please use Adobe Reader X or above version to open !
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 :