Enable Disk Clean-up

It seems in Windows Server latest versions the good old disk clean up tool is not enabled by default. If you just want it back you can run the below commands in a command prompt to copy the required files.

Copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe C:\Windows\System32\

Copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui C:\Windows\System32\en-US\

Then create a shortcut pointing to the Disk Clean up tool found in the following path.

C:\Windows\System32\CleanMgr.exe

I did try this on Windows Server 2008 R2 and hope it works as it is or with slight changes on other versions of Windows as well.

Configuring SQL Server Instance for Azure Development Storage

If you have not configured Azure Development Storage to use your SQL Server, then while running your application targeted for Azure you will see an error similar to the following.

“Windows Azure Tools: Failed to initialize Development Storage service. Unable to start Development Storage. Failed to start Development Storage: the SQL Server instance ‘localhost\SQLExpress’ could not be found. Please configure the SQL Server instance for Development Storage using the ‘DSInit’ utility in the Windows Azure SDK.”

To overcome this you need to run the DSInit command using Windows Azure SDK Command Prompt.

Step 1 – Start the Windows Azure SDK Command Prompt.

Step 2 – Type DSInit /sqlinstance:. on the prompt and press enter.

The dot (.) at the end denotes the local SQL Server instance running on your machine. DSInit command details are as follows.

Syntax: DSInit [/sqlinstance:<SQL server instance>] [/forceCreate] [/user:<Windows account name>]

Description: Initialize the development store for usage by Reserving http ports for the blob, table and queue services for the current user, and Creating the database needed by the blob and queue services

Options: sqlinstance : the name of the SQL Server instance on the local machine that should be used for Development Storage. The default is SQLExpress. Use "." for unnamed instance. forceCreate : recreate the database even if it already exists. user : user for whom ports are to be reserved. By default it is the current user.

.

After doing the configurations it will display a success screen similar to the following.

Then when you run your Azure ready application the Azure Development Storage and Azure Development Fabric will get started and notify you on your system tray as shown below.

After a while your application will also start without complaining if it is Azure ready.