|
Terminal
Services (Remote Desktop Services) in Windows Server 2008
|
|
|
Remote
Desktop Services (Terminal Services) on Windows Server 2008 R2 SP1
|
|
|
Remote
Desktop Services in Windows Server 2012
|
|
|
Remote
Desktop Services in Windows Server 2012 R2
|
Thursday, October 22, 2015
TechTip: Microsoft TS/RDS Updates for Windows Server 2008 and 2012
My colleague Aaron Silber sent over a handy-dandy table with hyperlinks to the Microsoft pages of patches and updates available for Windows Server 2008 and Windows Server 2012.
Friday, October 16, 2015
StoreFront 2.6 and Windows 10 Edge Browser
If you've been following Feng Huang's blog on customizing Receiver, you've probably seen StoreFront 3.0 and Windows 10 Edge Browser. In it, Feng explains how StoreFront 3.0 has been given the smarts to allow you to use the native Receiver with Edge.
What if you are still running StoreFront 2.6 (or 2.5)? Since Edge cannot run the ActiveX controls necessary for client detection, only the HTML5 Receiver would be used (see: Receiver Feature Matrix for HTML5 Receiver limitations).
This post will use a slightly modified version of another one of Feng's posts - Preparing for NPAPI Being Disabled by Google Chrome - to give you the ability to use the native Receiver with Edge.
In that post, Feng discusses how to:
However, the modifications discussed in the post are specific to Chrome. With just a bit of tweaking, we can add the above features for any browser.
We begin by adding the following strings to custom.wrstrings.en.js and a localized version for every language you need to support to custom.wrstrings.[language].js.
Next, we need to add the code below to custom.script.js (in the contrib folder of the StoreWeb site).
What if you are still running StoreFront 2.6 (or 2.5)? Since Edge cannot run the ActiveX controls necessary for client detection, only the HTML5 Receiver would be used (see: Receiver Feature Matrix for HTML5 Receiver limitations).
This post will use a slightly modified version of another one of Feng's posts - Preparing for NPAPI Being Disabled by Google Chrome - to give you the ability to use the native Receiver with Edge.
In that post, Feng discusses how to:
- Disable the prompt to install the Receiver
- Provide a permanent link for downloading the Receiver
- Provide a link to switch between the native (full) Receiver and the HTML5 Receiver (referred to as the 'Lite' version of the Receiver).
However, the modifications discussed in the post are specific to Chrome. With just a bit of tweaking, we can add the above features for any browser.
We begin by adding the following strings to custom.wrstrings.en.js and a localized version for every language you need to support to custom.wrstrings.[language]
Next, we need to add the code below to custom.script.js (in the contrib folder of the StoreWeb site).
The code above adds the following links to the dropdown next to the user's name:
Subscribe to:
Posts (Atom)