Managing Multiple Azure Subscriptions from PowerShell…

2017-07-27T00:01:01+00:00 July 24th, 2014|Uncategorized|

Hi folks, Jason here again – this time with some Azure PowerShell goodness to share.

A while back I set up an Azure trial subscription.  Following Jeremy’s post last year, “How to manage Azure from PowerShell on your PC“, I was able to get PowerShell to connect to my free trial subscription, creatively named “Free Trial”.  Coretek was kind enough to provide me with an MSDN Premium license.  Since the MSDN Azure subscriptions get $99 a month in Azure credit, it was high time to switch over to that Azure account and leverage that credit!  This subscription was also creatively named… “Visual Studio Premium with MSDN”.

Once again I followed Jeremy’s steps to import the Azure Publish Settings file – this time for the new subscription.  I ran Get-AzureVM… but I wasn’t seeing any VMs for my MSDN subscription.  Take a look:

…In the above screen capture, XENAPP1 is a VM in my old, un-loved Free Trial subscription.  Running Get-AzureSubscription showed me that I did indeed have access to two subscriptions, as expected:

So that begged the obvious question… how do I connect to my VMs in my other subscription?  Well that’s easy enough to do.  Just run the following cmdlet:

Select-AzureSubscription –SubscriptionName “Visual Studio Premium with MSDN”

…of course, change the subscription name to match your own.  NOTE: the subscription name is case sensitive!

One more tip for you, Dear Reader.  If you close your Azure PowerShell window and come back, it will revert back to whatever subscription is the default subscription.  That will always be the first subscription you set up.  The fix is simply adding the –Default switch to the end of the above cmdlet.  Now that’ll be where your Azure cmdlets do their magic as you go forward.

Now when I run Get-AzureVM I get the VMs I am looking for:


Azure PowerShell Errors Pt. 2…

2017-07-27T00:01:01+00:00 July 16th, 2014|Uncategorized|

In Part 1 of this 2-part series, I showed you how to re-install in order to eliminate the errors.  But at the end of that post, you surely noticed that while I fixed one problem, I seemigly created another.  Now it appears that I have red error text because it can’t load my profile script, and tons of scripts prompting me to execute.  It looked like this:

Unexpected Azure Errors...

This is strange… because I’m fairly certain my ExecutionPolicy is set to something lower, like RemoteSigned…  Hmm.  Let’s take a look at what my *combined* policy is set at, by issuing the Get-ExecutionPolicy -List command like this:

Get-ExecutionPolicy -List

That’s strange too.  But I see now that there’s a limiting policy on the *process*, so at least I know why this is happening (by the way, ignore that Unrestricted on LocalMachine 😉 ).  Clearly, I’m shooting myself in the foot with the cumulative permissions.  So, let’s try and figure out how that restriction is getting set on my system by chasing down the PowerShell link.  Right-click on the Windows Azure PowerShell icon and choose Open File Location:

Open File Location

Then, right-click on the Windows Azure PowerShell link and choose Properties.  And guess what we find:

Windows Azure PowerShell Properties

Yes, it appears that the shortcut/tile/link has hard-coded the ExecutionPolicy of AllSigned, which means it will permit only execution of — and request your validation of — certificate-signed scripts. 

Aside: This is where I tell you that normally, using AllSigned is probably a good thing; and although I’m not making an official recommendation of lowering that setting in production, I will tell you honestly that I typically use RemoteSigned on my laptop and feel it to be sufficient for my needs. 

So with that clarification out of the way, let’s change this setting and make our life a lot easier.  To do so, change:

C:WINDOWSSysWOW64WindowsPowerShellv1.0powershell.exe -NoExit -ExecutionPolicy AllSigned -File "C:Program Files (x86)Microsoft SDKsWindows AzurePowerShellAzureShortcutStartup.ps1"

…to (you will be prompted for Administrator-level permission):

C:WINDOWSSysWOW64WindowsPowerShellv1.0powershell.exe -NoExit -ExecutionPolicy RemoteSigned -File "C:Program Files (x86)Microsoft SDKsWindows AzurePowerShellAzureShortcutStartup.ps1"

…and now things should be back to normal. 

Normal Azure Startup - Hooray!

Look!  Even my startup script runs now.  Ah…  Feel that?  It’s Azure Zen goodness…




2017-07-27T00:01:02+00:00 July 15th, 2014|News|

Lubbock, TX – July 15th, 2014 –  Texas Tech University Health Sciences Center (TTUHSC) is the fastest growing medical school in Texas, as well as one of the area’s largest healthcare providers.  In order to keep pace with their growth, they were looking for ways to leverage technology and Electronic Medical Records (EMRs).  The IT Department at TTUHSC brought in the experienced team from Coretek Services to design and implement a solution that ultimately improved patient care.

One of the biggest challenges healthcare organizations like TTUHSC face today is the time it takes to log in to multiple applications from various devices and locations. Karla Silva, Director of Clinical Systems Support at TTUHSC in Odessa, brought in Coretek because she was impressed with the clinical workflow system they designed for their location in Odessa. The result was a more efficient single sign-on system that could shorten log on times from 2 minutes to 3-5 seconds, saving clinicians 1-2 hours per day.  Additionally, Coretek’s solution helped Texas Tech comply with the approaching Meaningful Use deadlines.

According to Silva, “The technology is new in the marketplace and we wanted to partner with a firm that had successful implementations and understood clinical workflows, interactions and healthcare mandates.”  Coretek Services has helped over 100 Healthcare organizations across the country improve workflows and increase productivity.

Coretek’s Virtual Clinical Workstation provides a fully decoupled virtualized desktop, user and application delivery environment accessed via a proximity badge tap.  This allows users to roam seamlessly between their office, patient rooms, medical carts and mobile devices anywhere.  The highly flexible, virtual system incorporates Coretek’s own proprietary software along with Citrix, Imprivata and AppSense technology and provides extremely fast access to EMRs.

With the implementation of the Coretek solution, the IT organization at TTUHSC also saw improvements in resource utilization.  Jorge Caballero, TTUHSC’s Director of Infrastructure Technology said, “The big payoff comes with using VDI.  If one device fails, it’s easily replaced and the uptime and availability is better than with thin clients or PCs.  The time it takes to maintain and distribute new applications is faster, and we are getting a lot less calls about lost passwords.”


As hospitals are looking for ways to improve patient care and productivity, Coretek can customize a solution to meet their needs.  Coretek is technology agnostic and will leverage existing technology and architecture to minimize costs.  Per Ron Lisch, CEO of Coretek Services, “We are consultants first and due to our experience in healthcare, we know how to design solutions with the clinicians in mind.”

Azure PowerShell Errors Pt. 1…

2017-07-27T00:01:02+00:00 July 10th, 2014|Uncategorized|

Following up my original post from last year, “How to manage Azure from PowerShell on your PC“…

If you haven’t updated your Azure PowerShell installation in the last few months, you very well may be seeing errors that say Requested value (something) not found, like this:

Requested Value (something) Was Not Found

The first thing you should do is to go to Control Panel -> Programs, and take a look at the version of the Windows Azure PowerShell listed there.  But, I suspect that if you’re reading this, you already know it’s older and out of date…  like mine was:

Azure PowerShell Old Version

How do you fix it?  Easy.  Just re-install on top of the existing.  In fact, if you go back to my original installation post and follow the install process, it will put in the newest, correct version.  After clicking the installation link, the Web Platform Installer launches, like this:

Web Platform Installer

If you click on “options”, you’ll see what it will be installing…

Web Platform Installer Details

Upon launch, you have to allow the startup scripts to run (Why is this?  More on this in Part 2!)…

Azure PowerShell Accept message...

…and allow, and allow, and allow (again, more on this in Part 2)…

Azure PowerShell Accept and Accept...

And finally, you should be good to go.  Your Programs listing should now look more like this:

Azure PowerShell New Version

…and once again, your shell should look like it once was:

Azure PowerShell Working Again

Happy Azuring!