SkyDrive is now called OneDrive

Microsoft has been forced to change there cloud based storage platform SkyDrive to OneDrive, this is due to Rupert Murdoch’s empire. It seems BSkyB which is only known as Sky in the UK could provide a similar product.

I find it funny they have not asked Microsoft to rename their Skype product aswell as this too provide similar functions around telephone services, as Skype clearly as the the SKYpe in the name.

Over the past few years Microsoft has come up with some really decent products with very suitable names, it’s just a shame they are being forced to rebrand due to other companies worrying about competition that doesn’t directly compete. Metro was a brilliant name for the Windows 8 UI, similar to SkyDrive.

NServiceBus Introduction

A quick introduction to NServiceBus can be found on their step-by-step guide, make sure you download and run the installer first being configuring your example solution.

Some things to note:
1. The install will configure RavenDB which is accessible through http://localhost:8080 on your machine

2. They missed a step in the step-by-step guide where you have to create a “PlaceOrderHandler.cs” file under the Ordering.Server project.

3. Configure RavenDB to allow Annonymous Access, in the Raven.Server.exe.config file under C:\Program Files\NServiceBus.Persistence.v4

Change

<add key="Raven/AnonymousAccess" value="Get" />

To

 <add key="Raven/AnonymousAccess" value="All" />

SkyDrive Pro No Longer Supports SharePoint 2010

So if my previous rant about SkyDrive going in the wrong direction I’ve found our recently that the latest version of SkyDrive Pro now won’t sync with SharePoint 2010 Document Libraries. This can only mean Microsoft are pushing you to upgrade to SharePoint 2013 which I agree is a move worth making but there are many companies out there that simply take time to complete this upgrade.

SkyDrive Pro supporting SharePoint 2010 syncing was really useful so why remove it? Stupid if you ask me!

Configure Drives for Servers

Below is the standard I follow when configuring drives for servers, it helps structure files for future management if needed. The below includes drives for running a SQL Server too.

C – OS and system level files. Only
D – Program files for all apps (including SQL Server)
S – Instance level files/SQL Server system databases and log files typically (except for TempDB) (note.. If I have multiple instances, I won’t make 4 of these.. I’d put all SQL binaries for all instances on S in most situations, with the folders providing the separation)
F – Data files for user databases
L – Log file drive for user databases
T – TempDB
X – Backup drive (though in a lot of cases I elect to stream a backup across to a network drive, not paying for a copy after the backup and I’m immediately backing up to storage someplace else.)