Showing posts with label Azure. Show all posts
Showing posts with label Azure. Show all posts

2/19/2016

Azure Exams 70-532, 70-533 and 70-534 Getting an Update!

 

Working on your Azure certifications? Take a break and go look at the list of announced updates. While they are listed as being updated as of March 16th, 2016, at least some the listed changes have already been applied.

The exams:

  • 70-532 Developing Microsoft Azure Solutions
  • 70-533 Implementing Microsoft Azure Infrastructure Solutions
  • 70-534 Architecting Microsoft Azure Solutions

 

The links to the exam changes PDFs:

 

.

2/17/2016

Azure Cloud – 5TB free space

 

You have to think a little differently when working in the cloud… (and sometimes I’m easily impressed with big numbers…)

  • Created an Azure Storage File Share.
  • Went to a VM running in Azure and connected to the share.
  • 5TB free space! (per share, and you only pay for what you use!)
    image

(Disclaimer: Free space on disk, not 5TB of free ($) space.)

 

image

 

Note: Azure Shares are only usable from machines running in Azure in the same region.

 

.

2/08/2016

Azure PowerShell: New-AzureRmAutomationCredential : Input string was not in a correct format.

 

Not an obvious error message:

New-AzurermAutomationCredential -AutomationAccountName "PStest" -Name "myPsredential"

New-AzurermAutomationCredential : Input string was not in a correct format.

image

Turns out it means you already have an Azure Automation credential with that name (“myPsCredential” in this example).

 

Wasted some time google/binging that one!

.

1/14/2016

Azure: PowerShell to List All Blobs in Storage

 

I have an Azure account for development and testing purposes that I want to keep as clean as possible. Part of my routine is clearing out unneeded blobs in the Storage Accounts. To do this using the Portal UI would take a long time… so PowerShell to the rescue.

I thought there would be a quick like piped command something like this:
Get-AzureStorageAccount | Get-AzureStorageContainer | Get-AzureStorageBlob

But no such luck. There’s extra steps to access the Storage Key and to create an Azure Storage Context object needed.

# optional!
$PreviousVerbosePreference = $VerbosePreference
$PreviousWarningPreference = $WarningPreference
$VerbosePreference = "SilentlyContinue"
$WarningPreference = "SilentlyContinue"


# if not alreay logged in to your Azure account...
# Add-AzureAccount
# if more than one subscription
# Select-AzureSubscription -SubscriptionName ????

Get-AzureStorageAccount |
  foreach {

    $acct = $_.label; $storageKey = (Get-AzureStorageKey -StorageAccountName $acct ).Primary;

    $ctx = New-AzureStorageContext -StorageAccountName $acct
-StorageAccountKey $storageKey;

    Get-AzureStorageContainer -Container * -Context $ctx } |

  foreach { $container = $_.Name; $_ } |

  Get-AzureStorageBlob |

  Select {$_.context.StorageAccountName}, {$container}, name,blobtype,length |

  Format-Table -autosize

# optional!
$VerbosePreference = $PreviousVerbosePreference

Select @{label="Storage Account";expression={$_.context.StorageAccountName}},
       @{label="Container";expression={$container}},
       name,
       blobtype,
       @{label="Bytes";expression={"{0,20:N0}" -f $_.length}} |

$WarningPreference = $PreviousWarningPreference

 

And if you like pretty columns then replace the Select line with this:

Select @{label="Storage Account";expression={$_.context.StorageAccountName}},
       @{label="Container";expression={$container}},
       name,
       blobtype,
       @{label="Bytes";expression={"{0,20:N0}" -f $_.length}} |

 

There’s got to be a better way to do this. So post any better solution as a comment!

 

Total storage?

Replace the Format-Table line with “Measure-Object -Property length -Sum” and you can get a file count and total bytes. (Don’t combine this with the “pretty columns” change!)

.

2/08/2015

Instant (almost) SharePoint 2013 Farm in Azure!

 

Microsoft Azure has had a pre-configured SharePoint 2013 image for quite a while, but you still had to create a SQL Server image to make it work and then run the SharePoint wizard to create the farm. Now they have a wizard approach to quickly create a ready to use three server basic farm or a nine server high-availability farm. Just click, click, click, wait a while and start playing with SharePoint! Just the thing for evaluations, demos and development.

The three server farm includes a SQL server, a DC server and a SharePoint server. The high-availability farm includes two DC servers, three SQL server servers, two application servers and two SharePoint web servers. (This one should drain your Azure budget! Remember to turn these off when not in use.)

Details on both configurations can be found here: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-config-azure-preview/

Here's the steps to create your Azure SharePoint 2013 farm: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-azure-preview/

 

A few observations:

  • SharePoint Version: 15.0.4571.1502  (Service Pack 1 (revised))
  • License: SharePoint Server Trial with Enterprise Client Access License
  • An initial web application and site collection have been created, but you will be asked to pick the template for the top level site on the first visit.
  • None of the services applications have been installed. User Profiles, Search, etc.
  • The VMs are available via Remote Desktop.
  • SharePoint is accessible from the web, so you can test from your local PC.
  • Outgoing and incoming email has not been configured.
  • Does not include Office Web Apps server.

 

Things you will need to do to have a complete SharePoint:

  • Configure the services
  • Configure email options
  • Add one more server VM for Office Web apps

 

Now all we need is a volunteer to create the PowerShell scripts to do the final work for us!

.

Note to spammers!

Spammers, don't waste your time... all posts are moderated. If your comment includes unrelated links, is advertising, or just pure spam, it will never be seen.