TechEd 2014, Day 1…

TechEd Keynote Panel

I remember a couple significant moments in my career when new technologies were born that might not have been immediately recognized as the innovative technologies that they really would become.  Things that seemed cool at the time perhaps, but became something much larger.  Today, the announcement (and explanation) of Microsoft RemoteApp might have been one of those moments. 

But even though I’m blown away by RemoteApp, there were a bunch of announcements!  Here are my top few of the day:


The new RemoteApp (now in preview), built on RDS technology, offers two options with which you can deliver apps to users — straight out of Azure!  I guess now we know why the RDS clients were recently released for Mac/IOS and Android, eh? 😉  Anyway, RemoteApp comes in 2 options: the first is the simpler “Cloud” option, with canned Microsoft productivity apps.  The second “Hybrid” option is more complex, but in a nutshell permits you to deliver apps right from your own templated RDS server; built how you want, with the apps you want.  That’s right, *your* corporate apps, available after authentication via a browser, served over RDS technology.  Servers that provide the service for your users automatically scale up and down based on load.  Wow.

Azure Site Recovery

Expanded (and rebranded) from the well-known Hyper-V Recovery Manager, Azure Site Recovery (coming preview soon) utilizes VMM to permit you to replicate Private Clouds of Virtual Machines right into Azure.  The previous version, of course, only permitted this functionality between two of your own sites.  But what if you did not have a second site?  Solved. 


ExpressRoute (in general availability today) utilized various connectivity vendors, providing high-speed connectivity directly into Azure.  The best part of this is that if you already have Internet or Branch connectivity from one of the vendors that have partnered with Microsoft for ExpressRoute, you can have linkage into Azure with very little change.  And the list of vendors is growing…

Azure Files

Think of Azure Files (in preview now) as a “file share service” that servers can consume inside of Azure.  This way, you can save yourself having to deal with servers to serve servers inside the Azure space.  More to come on this…

Still other announcements include intra-Azure, cross-region, routed inter-connectivity capbility, and multi-site/premises connection to Azure (meaning more than one of your locations can connect into your cloud), and so on.

It’s been a whirlwind day.  Oh, and by the way… If you go to the Channel 9 page for TechEd Day 1, you’ll get the chance to hear *me* ask a question of the presenters. I’m not telling you where…  😉

2017-07-27T00:01:02+00:00 May 12th, 2014|Uncategorized|

About the Author:

Jeremy is just a regular guy that likes to occasionally tell the world about stuff.

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113