Thursday, August 8, 2013

SharePoint 2013: Standalone installation with local accounts

If u try to install SharePoint without a Domain, u might face the Problem, that SharePoint Products and Configuration Wizard stops with the following error after passing database Access account:

"The specified user MACHINENAME\Username" is a local account. Local accounts should only be used in stand alone mode."

Are we unable to install SharePoint 2013 with local accounts for real? I mean in production this would def. make no sense, but for a development or test Environment it can make sense in certain cases.

The trick here is to precreate the SharePoint_Config database with Power Shell. Use the following command:

> New-SPConfigurationDatabase

This creates all necessary databases and u can run Configuration Manager after with the option “Connect to existing farm”, sure u can successfully setup SharePoint then with local accounts on a single machine.

As this is one of the most time consuming parts of the Setup, u can go for a coffe now. it will take some time...

Windows Server 2012: Akamai Download Manager

If you have a new Installation of Windows Server 2012 and you want to download stuff to install from Microsoft Download Center, u might experience Problems with Akamai Download Manager.

Akamai Download Manager is activated as ActiveX in IE, but first needs to be downloaded. The download is linked to an Akamai Url, without trusting this Url, your unable to download Binaries.

Add the following Url to trusted site and your happy again without using Chrome or FF, or any other strange Browser:


Windows Azure: Trial - VM's deleted after expiration

Today I wanted to reactivate an expired Trial of a Windows Azure hosted VM. As I’m motivated to pay for this Service, I thought I can just go to the account Management, add my credit Card data and would be ready to reactivate my SharePoint Installation.

I checked my available Services and discovered, that my VM was deleted somehow. I checked then if my Image is still in the Gallery, by luck it was. I decided to set up a new VM and attach the existing disk. I was able to create the new VM and attach existing disk. While provisioning the following error appeared:

 “A lease conflict occurred with the blob <blob url>” 

It seems that in the service configuration, my machine is still registered and based on the naming convections my VM could not be recreated. So how to recreate a new machine with the same disk?

There is a Manual how to redeploy a deleted machine, but it didn’t help in my Case.

I found another article which involves power shell to delete the existing lease, unfortunately this didn’t work for me also.

The error I received after running this script was, that my storage account is not properly linked to my account.

If all of the above steps didn’t help, only Microsoft Azure Support can help u. But remember, u need to buy the technical support option. The billing guys won’t help you… welcome in the cloud ;-)
Summary: Add payment Details before your Trial expires, or u might loose ur work.