Sorry, we can’t sync this library because it’s hosted on a SharePoint 2010 Server. For more information, please get in touch with your help desk.

Nooooooooooooooo!!!
Sorry, we can’t sync this library because it’s hosted on a SharePoint 2010 Server. For more information, please get in touch with your help desk.

Nooooooooooooooo!!!

SharePoint 2013 Service Pack 1 Pulled

Update

The KB article for SP1 (KB2817429) has been updated with the following:

We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.

SharePoint Server 2013 Service Pack 1 appears to have been pulled from the Microsoft Download Center.

The timing is slightly off, as clients have been requesting this patch lately as its been available for a bit now. I’ve had a few quibbles with Service Pack 1, particularly the poor implementation of registry permissions and general provisioning problems with Service Applications. Its nothing that can’t be overcome, but hopefully the Product Group can clean it up when the patch reappears.

Thanks to Anders Rask for pointing it out and tweeting it up.

Quick PowerShell Snippet - BITS Transfer Status with Progress

BITS Transfers are fun. They can be asynchronous, sometimes intelligent, and far more resilient than a traditional WebClient download.

As asynchronous transfers are occurring in the background, it can be helpful to monitor their progress. The following snippet allows us to do just that, outputting the progress on any current BITS transfers with a status (or JobState) of Transferring.

User groups, kangaroos, and SharePoint Migrations

I had the pleasure of presenting at not one, but two (!!) user groups in Australia this past week to discuss the pitfalls of migrating to SharePoint 2013 and all the things that go wrong along the way.

First up, the Sydney SharePoint User Group located in the heart of the CBD. Sydney is my home away from home for the next few years, and I’m very grateful to the organisers for giving me the opportunity to come out.

The following day, after a quick train ride and some kangaroo sightings, it was off to Canberra for the Canberra SharePoint User Group. There were some projector issues, but I do hope that everyone that attended got something out of the session.

Determining Core Counts in Azure PowerShell the Easy Way™

In the past, to retrieve the number of cores in use in a given Azure subscription (or to retrieve the maximum number of cores available), we had to jump through some hoops to get the information we needed.

One method was to loop through ALL of the Services and then ALL of the Virtual Machines provisioned and maintain a running count of the consumed cores (Ex. Windows Azure compute cores and you. Not only is this tedious, it’s no longer necessary!

A new parameter has been introduced to the Get-AzureSubscription cmdlet called ExtendedDetails. By executing the cmdlet with the ExtendedDetails parameter, you’ll see not only the CurrentCoreCount and MaximumCoreCount, but also some metrics around the number of services you’re consuming (Cloud Services, Storage Accounts, etc.).

Get-AzureSubscription -ExtendedDetails output

If you’ve been executing scripts to provision environments that consistently fail due to lack of cores, a quick check of the output of the Get-AzureSubscription cmdlet could save you some time.