Windows PowerShell 3.0 and Server Manager Quick Reference Guides

Quickly learn tips, shortcuts, and common operations in the new Windows Powershell 3.0, Windows PowerShell Workflow, Windows PowerShell ISE, Windows PowerShell Web Access, Server Manager for Windows Server 2012 Release Candidate, WinRM, and WS-Man.

http://www.microsoft.com/en-us/download/details.aspx?id=30002

 

PowerShell on Linux, Solaris, Mac, PHONES!!! etc

Igor Moochnick announced the first release of PASH, an open source implementation of PowerShell.  (I tripled check the date on his blog to make sure it really said April 6th and not April 1st. 🙂 ).  This is really exciting stuff.  This is one of the most requested items from IT shops that run heterogeneous environments.  They love PowerShell and want ALL their IT Pros to adopt it.  I haven’t tried it yet so I don’t know what it does/does not implement but I’m pretty excited about it.  I can’t wait to give it a try.

I’ll have to talk with the .NET guys about how they work with the MONO team to ensure compatibility.  If it gets/stays compatible, that is a super good thing for customers.  It it becomes a variation or separate dialect and confuses our customers, then that would be problem.

BTW – just to make one point REALLY clear – PowerShell running across heterogeneous platforms was a project goal from the very beginning of the project.  We architected and designed PowerShell so that our only “true” dependency was on .NET.  There are only 1 or 2 cases where I know that we call a Windows API (code signing).  In other words – what Igor is doing IS PERFECTLY FEASIBLE.  Sure, he won’t have WMI cmdlets on those other environments – you’ll have incidental variations – that is not a problem.  The engine and the language should work perfectly.

One last point.  I’m really looking forward to getting the Open Source communities input on PowerShell and suggestions on ways to improve it.  Their usage scenarios will be different and will highlight any flaws or shortcomings we have in other areas (e.g. text parsing/manipulation).  I look forward to hearing their complaints/recommendations.  Adding their perspective and insight will make PowerShell a better technology for everyone.

 

Check this out:

Windows (duh !..)

Pash on Mono + SuSE Linux

Pash on Compact .NET Framework

and (drum roll …) Pash on Mac

 

What a nice day!

Microsoft Launches Company’s First-Ever Direct Startup Accelerator

Microsoft Azure
Today, Microsoft is launching the first startup accelerator* in the company’s history in an effort to encourage more entrepreneurs to build their cloud-based applications using Windows Azure. The program will take place at the Microsoft Israel Research and Development Center, and is a part of the Israel R&D Center’s outreach program Think Next as well as the Microsoft BizSpark program for startups.

Like most accelerators, Microsoft will provide the typical accouterments, including free office space, coaching, mentorship, legal assistance and more, but in this case, it’s specifically after companies building cloud-based startups. The companies will be provided with free access to Windows Azure, but will not receive seed funding.

According to Zack Weisfeld, Sr. Director of Strategy and Business Development at Microsoft’s Israel Development Center, the decision to launch the company’s first accelerator in Israel had to do with the center’s strategic location for Microsoft, and is part of its ongoing efforts to bring startup culture back to the company.

Israel has a very active startup community, Weisfeld explains. “We have 4,900 startups in Israel today, and the third largest V.C. spending in the world after Silicon Valley and New England,” he says. He also notes that out of the startups participating in Microsoft’s BizSpark One, a sort of “best of breed” selection from the larger BizSpark program, 25% of the companies are located in Israel.

“Because we have such an innovation-driven and startup-driven R&D center, we basically came with a proposal to basically change the way Microsoft deals with entrepreneurs,” Weisfeld says of the program’s beginnings. “Part of that proposal was to start, for the first time in the world for Microsoft, our own startup accelerator.”

The new accelerator aims to tap into the region’s activity, by encouraging startups to launch using Microsoft software.

The Windows Azure Accelerator, as it’s called, will be the first of many themed accelerators Microsoft plans to launch in the same space. The program will also serve as a blueprint for future accelerators Microsoft plans to launch globally, Weisfeld says. And those global programs will arrive sooner than later, it seems.

“I don’t think we’ll wait a year,” Weisfeld says, “we’re going to learn a lot through the first class…we’ll be ready to move as soon as possible to other places.”

During the four-month, biannual program, entrepreneurs will have access to 850 square meters of newly renovated, shared workspace in the center, which also includes meeting rooms, a usability lab, and a place to record their demo videos. Over 30 mentors from the industry (names TBA) have been lined up to provide leadership, coaching and support. These include startup CEOs, investors, marketing experts and more.

The startups will also receive all the software currently available through Microsoft BizSpark, including, of course, access to Windows Azure. Companies will receive two years (up to $60,000) of Windows Azure, Weisfeld tells us. This is the same offering available through the BizSpark Plus program, which is now offered to TechStars and all members of its Global Accelerator Network. This new program, too, will function as a member of that network, we’re told.

Startups in the program may choose to use open source software, Weisfeld says, but Microsoft “would like” them to use Azure. (Read: should use Azure).

Although the new program is being positioned as an accelerator, unlike many of today’s incubators, there isn’t seed funding involved, nor will Microsoft take an equity stake in the participating companies. However, there will be something else of value offered: access to Microsoft’s partners who may serve as potential customers.

“We know it’s so critical, even in early stages, for startups to have access to people who may use whatever they produce or can start working as beta customers.” Weisfeld says. “We’re going to work both locally and internationally [on that],” he adds.

Microsoft will reach out both to its own customers with whom it already has relationships with, he says, but will also be doing grassroots-level work when necessary.

The program will culminate with two demo days, one in Israel and a second in the U.S. The first class, which will include 10 companies, will be announced April 22nd at Think Next 2012, which is sort of like a TechCrunch Disrupt-style event for Israel.

As for what’s in it for Microsoft? Besides the obvious (Azure adoption), it’s about an attempt to reinvigorate Microsoft culture.

“We believe that for the Israel R&D center, it’s going to make the center much better. We’re going to have fast-moving, agile startups that want to change the world working closely with our engineers,” explains Weisfeld. “It’s going to make us much better by working with them.”

Interested startup founders can apply to the program here: accelerato.rs/azure/apply

* UPDATE: To be clear, it is Microsoft itself, and those involved with The Windows Azure accelerator, who are positioning the program as the “first-ever” accelerator run by the company. Microsoft, however, has involvement with TechStars, including with its Kinect Accelerator, it should be noted. In that case, though, TechStars takes its usual 6% equity stake, which may be the reason for the distinction. Also, the Azure accelerator will be run by two Microsoft employees, who are in the process of being hired now from the outside startup community.

Here’s further explanation, per Weisfeld:

“Windows Azure Accelerator is the first Microsoft accelerator. The one in Seattle is a TechStars accelerator. Startups get funded and equity by TechStars. The Kinect accelerator is operated by TechStars. It is not a Microsoft accelerator.

WAA is the only by Microsoft, at Microsoft, run by our employees. This is certainly our first direct accelerator. The other one is a TechStars driven accelerator.”

(source : http://techcrunch.com/2012/03/13/to-boost-windows-azure-microsoft-launches-companys-first-ever-startup-accelerator/ )

Download Windows Server 2012 Release Candidate Datacenter

The next release of Windows Server, Windows Server 2012, will offer businesses and hosting providers a scalable, dynamic, and multitenant-aware, cloud-optimized infrastructure. It securely connects across premises and helps IT Professionals to respond to business needs faster and more efficiently.
Windows Server 2012 Release Candidate (RC):

  • Takes you beyond virtualization
  • Delivers the power of many servers with the simplicity of one
  • Opens the door to every app on any cloud
  • Enables the modern work style

http://technet.microsoft.com/en-us/evalcenter/hh670538

 

How to: Using Windows Azure to create Micro Finance App

Microsoft Azure

We recently embarked on a proof of concept project to create a line of business web application using some of the latest technologies such as Windows Azure and HTML5 and see if we could combine these technologies with great design to produce an awesome experience for the end user. You can see the application itself, MicroFinance, at our web site at http://labs.mandogroup.com.

 

On the road to creating our MicroFinance application, there were some key technical requirements that we were aiming to achieve;

  • The core data behind the application should be consumable on several platforms including Windows Phone.
  • The application should be scalable to be able to cope with hypothetical growth in demands.
  • The application should be reliable and should be available whenever required.

We wanted to see if Windows Azure could help us achieve the above objectives and how easy it would be to work with the Azure platform.

With this in mind we then set about splitting the planned application into several discreet components;

  • The raw data behind the application (i.e. customer details, task lists)
  • The HTML5 web application itself
  • A service to allow the data to be consumed where needed

Now that we had the above separation we needed to decide how each of them could be implemented using the Azure platform.

The Data

For the data behind the application and how it is stored / accessed, we had a couple of options.

  • The first was SQL Azure, a cloud based implementation of the familiar SQL Server database we all know and love. Using SQL Azure would allow us to use large data sets and perform heavy data-processing on the data held, as well as being able to define strong relationships between our data entities using out of the box functionality such as SQL joins etc.
  • Our second option was to use Azure Table Storage, which provides a persistent and durable storage medium, but without many of the features (and complexities) of SQL Azure.

We decided to use Azure Table Storage as in the initial version of the application we are not storing hugely complex or massive amounts of data, meaning we could easily implement Table Storage for our data, perform joins on our data using LINQ once we have retrieved it from storage. We felt that SQL Azure was overkill for our requirements, but that’s not to say that it isn’t a good solution for many scenarios.

MSDN Magazine featured an article by Joseph Fultz which provides a detailed comparison of SQL Azure and Table Storage and I would highly recommend you read it if you are facing a similar decision.

The Web Application

The main web application which would be the primary method of accessing and managing the data for the end user needed to be responsive, reliable and scalable. As well as the core requirements, I wanted to be able to work with the technologies and tools I have always worked with (ASP.NET, C#, Visual Studio etc.). Happily for me, there is a great Windows Azure SDK Toolkit available with tools for Visual Studio, which makes creating applications and services that run in Azure an absolute snap.

Using the built in project templates that come with the Azure SDK and tools I was quickly able to create an Azure Web Role, used for hosting front end applications behind IIS, within which we could create the web application itself. From this point, where you have your Azure project created, it becomes business as usual from a development perspective, with the same old familiar ASP.NET pages and techniques you would always use, which meant that it was very easy for us to start writing the application even though it was to be hosted on a different platform than we would normally use.

The big advantage to hosting our application in Azure is the ability to scale at short notice. Should demand increase, you can simply log into your Management Portal and increase the number of instances of your application that are available to cope with the increased load. Should the demand drop back again, you can simply reduce the number of instances running back to a more suitable level. The notion of this rapid and responsive ‘spinning up’ and ‘spinning down’ within Azure is probably my favourite feature and the reason that Azure first grabbed my attention.

The Service

We needed to expose our data to allow it to be consumed by other platforms, as well as our web application. Initially this was to only be our Windows Phone 7 application (which we will talk about in more detail later in this series), but it is likely that other platforms may wish to access this data in the future. For this reason we decided to implement a WCF service to allow the required flexibility and for our data to be passed out as needed in an efficient manner. The WCF service was configured to have a couple of different endpoints, allowing us to expose data to both the Windows Phone application, returning our complex data types representing our data (such as customers and tasks) and also as a plain JSON output upon a RESTful request from platforms such as JavaScript.

Testing

From a testing perspective, I only have more good things to say about the SDK and the tools. There is a set of very capable emulators that work with zero config within Visual Studio. This allowed us to run the application in a ‘cloud-like’ environment and ensure that the components were working together correctly. This was especially true with the storage emulator, which allowed testing of our code to create and access Azure Tables.

Deployment

Deployment was my only real niggle with Azure development. There were a couple of routes available to me to get the solution into Azure. The first was to package the solution within Visual Studio, which produced two package files, and then to log into the Azure Management Portal and manually setup and upload these packages in order to deploy them. The second, more favourable option, is an automated deployment from within Visual Studio, however this option is only available to those with top-end Visual Studio editions (Ultimate I believe) and still require some manual configuration within your Management Portal. Therefore for many people I believe that the deployment procedure could be streamlined considerably. I also encountered an issue with the configuration of my application which was still configured to use local development storage whilst I was attempting to deploy and therefore causing the operation to fail. Unfortunately, the error message was incredibly vague and unhelpful, which could be improved.

Summary and What’s Next?

When all is said and done, the experience of developing an application to be hosted within Azure was on the whole a straight-forward and positive experience. I think that the small issues I encountered when deploying would not be enough to prevent me from recommending Azure to others.

At this point we now had a working core application running in the cloud, with the ability to serve data to a variety of platforms and scale when necessary. Next we needed to make it useable, look good and just more exciting for the end user in general and this will be discussed in a dedicated series of blog posts on MSDN in the coming weeks.

 

Author Bio

Gary Pretty
Deputy Head of Programming, Mando Group
http://www.mandogroup.com

Gary Pretty is the Deputy Head of Programming at Mando Group, a leading digital agency specialising in creating enterprise web sites and RIAs. Gary works with technologies across the Microsoft stack, including Windows Azure, Sharepoint, ASP.NET and Windows Phone. Gary can be found on twitter @GaryPretty.

 

(Source : http://blogs.msdn.com/b/ukmsdn/archive/2012/01/20/using-windows-azure-to-create-microfinance.aspx )

Sending emails from Windows Azure using Exchange Online web services

Microsoft AzureThere already have been several blog posts (e.g. 123) about why and how to send emails from an Azure-hosted application.

I just wanted to summarize the essence and show some code on how to send email from Azure code via Exchange Online web services if you have an Exchange Online email subscription.

Turns out I was able to register a nice domain for my Exchange Online trial: windowsazure.emea.microsoftonline.com  Winking smile

So, here is the essential code snippet to send an email via EWS (Exchange Web Services) by leveraging the EWS Managed API 1.1 (get the download here):

var service = new ExchangeService(ExchangeVersion.Exchange2007_SP1);
service.Url = new Uri(
  "https://red002.mail.emea.microsoftonline.com/ews/exchange.asmx");
service.Credentials = new WebCredentials(userName, password);

var message = new EmailMessage(service);
message.ToRecipients.Add("joe@doe.com");
message.From = new EmailAddress(
  "foobarbaz@windowsazure.emea.microsoftonline.com");
message.Subject = "Hello EMail - from Windows Azure";
message.Body = new MessageBody(BodyType.HTML, "Email from da cloud :)");

message.SendAndSaveCopy();

In the code above I am sending the email via the EWS host for Europe – you may need different URLs for your location:

Asia Pacific (APAC): https://red003.mail.apac.microsoftonline.com
Europe, the Middle East, and Africa (EMEA): https://red002.mail.emea.microsoftonline.com
North America: https://red001.mail.microsoftonline.com

Hope this helps.

(source : http://weblogs.thinktecture.com/cweyer/2010/12/sending-emails-from-windows-azure-using-exchange-online-web-services-bpos-for-the-search-engines.html )

Ten Basic Troubleshooting Tips for Windows Azure

Microsoft AzureThe last few posts I’ve talked a LOT about configuring diagnostics. Much of that comes not because I love pretty graphs, but because I end up working with customers who are troubleshooting problems with applications running on Windows Azure.

Here is MY list of recommendations to help things run a little smoother:

  1. Keep your diagnostics account separate from your production account. This will help with performance of both production and diagnostics since they won’t be competing for the same storage account.
  2. Make sure your storage account is in the same data center as your compute. I know. Just saying.
  3. Make sure you collect the right set of performance counters AND check that you are actually collecting data. Make sure you are collecting the .Net 4.0 counters for ASP.NET where applicable.
  4. Use either the .wadcfg or PowerShell scripts I’ve talked about here to configure diagnostics. Hard coding it will overwrite any changes you make when an instance restarts.
  5. Knowing and understanding your baseline workload is important. You should look at your performance on a regular basis, and over a period of time.
  6. To troubleshoot, you can enable RDP and perform an upgrade of your service. You can then RDP into specific instances to troubleshoot.
  7. When you are working with Microsoft’s product support, try not to delete old deployments. Once you do it makes finding a root cause more difficult. You can always VIP swap them out and leave them running while they troubleshoot.
  8. Having more instances running means more people can look at the problem at the same time.
  9. Check the status of the service at http://www.microsoft.com/windowsazure/support/status/servicedashboard.aspx
  10. Invest in a diagnostics data viewing tool, such as Cerebrata, or grab a free trail of ManageAxis by following the rabbit hole from the Cloud Cover Show.

 

(source : http://www.davidaiken.com/2011/11/15/ten-basic-troubleshooting-tips-for-windows-azure/ )