This wiki page is intended for each contributor who wants to create a DEV Environment. The general purpose of this document is to get a better understanding of SharePoint 2013 and its components.
↑ Back to top
It is important that we give credit where it is due.
Margriet Bruggeman is the one and only Wiki Ninja Contributor who owns this series. Just taking a moment to give credit to her.
First of all, you need to think of the hardware you require. Go for an i7 quad core processor, equivalent or higher. Also make sure you have at least 32 GB memory, since SharePoint 2013 development machines require at least 24 GB of memory. Having a RAID
0 hard disk is also a good idea.
If you have less hardware specification that were used to install the SharePoint 2010, Still you can go ahead and start your SharePoint 2013 development journey.
You can go for VM with below software:
Windows 2008 R2, SP,SQL 2008 R2 SP and Visual Studio 2012.
It works without any performance glitches(i5 quad processor) on Oracle VM and allocated the 8GB RAM for SharePoint 2013 and 8GB for host machine.
Still you are not convinced to use the VM , I would suggest to dedicate on computer / laptop (even its better on core i3 3.07 GHz and 8GB RAM )to install the trial version of the above software.
Our ideal set-up is this: Run Windows Server 2012 on Hyper-V on a Windows 8 machine. At a high level, you need to have access to the following software:
By default, Windows Server 2012 is not very dev friendly. I suggest some changes. At a high-level, do the following:
Rename the server to something short, easy to remember and easy to type. I usually go stellar with this, with names like moon, mars, and nova.
Start the virtual machine. The server manager starts automatically.
Changing Password policies
This effectively applies the new policy.
Change administrator password.
While you're there, you may as well create a couple of test user accounts test1 to test3 with passwords that are easy, never expire, and can't be changed by the users.
Convert it to workstation.
It's a good idea to make life easier for yourself and convert the server in look-and-feel to a workstation, as described at http://www.win2012workstation.com/ The web site contains a link
to the Microsoft Server Converter 2012 tool that should do the heavy lifting for you, but it's supposed to be 51 MB in size. This is ridiculously large, it should be less than 1 MB in my opinion, so we don't really trust it. The tips on the web site however
are solid. We've done the following ourselves:
Disable Shutdown Event Tracker
Adjust Folder Settings to your liking.
This is a nice place to be.
Do a couple of things:
SharePoint isn't really designed to support a split geographic installation within a farm. There is no way to overcome the SQL latency issues that develop and its not a supported scenario. Yet, there are a couple of options you can pursue:
Info taken from: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/aaf7af12-4f1a-4c28-9f0c-7f87d46ec2b1
Once you have done this, you can use this connection during the creation of your new virtual machine to ensure internet connectivity on the server. Which, for SharePoint 2013, I'd say is nothing short of an installation requirement. You can also change the
connection for existing machines by doing this:
Install Visual Studio 2012 on the virtual machine
Well, what to say? You're a developer, aren't you? What you're waiting for!
Now install SharePoint specific templates.
Install SQL Server 2012 with sp1 (At the time of writing, this is the latest version of SQL Server.)
It's possible that you get an error message similar to this: "Prerequisites keeps trying to start and failing to do so. Fails: start "Launch SharePoint preparation tool" "E:\prerequisiteinstaller.exe" /continue"
Please note that the Workflow Manager Client needs to be present on every SharePoint node in the farm.
Execute the following command:
Register-SPWorkflowService -SPSite "http://moon " -workflowHostUri "http://moon:12291 " -AllowOAuthHttp
Where: -SPSite refers to one of your site collections.
What to do when search suggestions don't show up? Run the "prepare query suggestions" timer job!
If you set up search suggestions (as described in http://technet.microsoft.com/en-us/library/jj721441.aspx ) you may notice that no suggestions drop down from the search
bar. That makes sense, because they only appear after the "prepare query suggestion" timer job has run. You can force this via PowerShell like this:
Start-SPTimerJob -Identity "prepare query suggestions"
Running SharePoint 2013 in an AD environment that can be played around with is quite high on my 'Gimme Gimme' list.
After installation was successful, the server restarts.
First of all, please get the PressurePoint Dragon for SharePoint 2013 at
http://gallery.technet.microsoft.com/PressurePoint-Dragon-for-87572ee1 to be able to simulate the specific SharePoint actions described here.
Then, go to this gallery to obtain the scripts to be able to monitor the performance counters as described on this page: http://gallery.technet.microsoft.com/PowerShell-script-for-e7085a38
Finally, you can keep track of http://www.sharepointdragons.com to keep updated with the latest info about this initiative.
The PressurePoint <Request> action equals to an HTTP GET request to a SharePoint page. The following performance counters are relevant for this type of action:
Processor Information(_Total)\% Processor Time
Mind you: This section is a work in progress and is therefore not finished yet. Because of that, the PowerShell script for this part is not yet available.
or a SharePoint installation, this page recommends the following best practices and naming conventions for service accounts:
Managed Service accounts are limited to a total of 20 characters - including the Domain Name (for example Domain\SP_Name - total characters should be less than 20)
This account should be used for running SQL Server engine and SQL Server Agent. Create inside Service Manage Accounts Container inside AD to keep it controlled. Have the following characteristics:?
This account is needed for performing high privilege jobs and (such as installing fixes, upgrades, etc.). It needs to have the following permissions:
= New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account
= New-SPServiceApplicationPool -Name AppServiceAppPool -Account
= New-SPSubscriptionSettingsServiceApplication -ApplicationPool
-Name SettingsServiceApp -DatabaseName SettingsServiceDB
= New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication
= New-SPAppManagementServiceApplication -ApplicationPool
-Name AppServiceApp -DatabaseName AppServiceDB
= New-SPAppManagementServiceApplicationProxy -ServiceApplication
From a SharePoint 2013 Management Shell prompt, execute this code.
Click App Management > Configure App URLs
In the App Domain text box, type: app.[domain name] (e.g. app.lc.corp).
In the App prefix text box, type any prefix that is used to prefix the subdomain of App urls, e.g.: lcapp.
Now, check if you can add online Apps to your SharePoint environment. But don't do this using the SharePoint System Account, otherwise you'll see a message stating: "Everything is fine, but we had a small problem getting your license. Please go back to the
SharePoint Store to get this app again etc. etc."
This is a nice example of misplaced SharePoint 2013 friendliness. Don't expect this small problem to go away by itself!