Richards blog

Once you have download SharePointServer.exe, you will need to extract the files from the executable. From the command prompt run: SharePointServer.exe /extract:c:\sp2010\ This will extract the installation files. Second, you need to 'enable' a Windows 7 installation. In order to do this, you will need to edit one of the configuration files. Navigate to C:\sw\sp2010\Files\Setup and add the following line to the bottom on the config.xml (before the closing Configuration tag). <Setting Id="AllowWindowsClientInstall" Value="True"/> You should be good to go IF YOU HAVE SQL SERVER 2008 R2. If you are running SQL Server 2012, you will need SharePoint Server 2010 SP1.

It seems the best things in life come in pairs: If you have a ValidateAntiForgeryToken annotation in your controller, you need to have a @Html.AntiForgeryToken() in your view.

I encountered this problem today while setting up a SharePoint 2013 Development environment. The solution is to run a simple command: "C:\Program Files\Oracle\VirtualBox\VBoxManage" setextradata [vmname] VBoxInternal/CPUM/CMPXCHG16B 1 For example, my Virtual Box was called SP2013, so my command was: "C:\Program Files\Oracle\VirtualBox\VBoxManage" setextradata SP2013 VBoxInternal/CPUM/CMPXCHG16B 1

I recently installed a test environment on my Windows 7 laptop [using New-SPConfigurationDatabase] but I was unable to add a new Web Application. I created a new user, added it to the Local Administrators group. Two issues were apparent: A. I could not add a new Farm Administrator as 'I needed Local Administrator rights' [from the ULS] B. I could not create a new Web Application [due to security trimming] The solution lies in the OOTB Administrator account that is provisioned in the Windows 7 installation; it is deactivated by default. I activated the account and, presto, used its credentials to perform all the required activities.