You cannot install two SharePoint farms on single windows server. Unless you want to create the couple of VM on servers then you can do.
Yes, you can use single SQL server instance for multiple farms. This solution is not recommended for the production farm
The only way you can do this is through Hyper-V where you create a virtual instance, install Windows Server 2012 and SharePoint Server 2013.
They can use the same database server provided that you give them different database names, but the best option is to install the new SharePoint on a SQL Server instance of its own. Such as TheOriginalDatabaseServer\...
I was looking for the same information, and just found the answer here.
Here are the steps:
For MOSS 2007, navigate to:
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS
For Sharepoint 2010, navigate to:
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS
Check the ServerRole key
Here are the valid ...
Yes it is required. The Workflow Timer Service is not just responsible for your List/Documents workflows, but also for a lot of other system related tasks. It should be started on all Sharepoint Servers including Web front ends and application, search servers. There is no harm in it running as well. If it's not busy, it wont consume resources.
The best description I've seen is Todd Klindts How to create a SharePoint 2010 farm with no GUIDs using PowerShell
If you've already created your farm you can follow his other post Getting the GUID out of the AdminContent database in SharePoint 2010
I would start by creating a service principal name for the SQL Server instance. I assume you use a default instance on the default port here:
SQL Server Instance: servername\mssqlserver
SQL Server service account: domain\sql
setspn -S MSSQLSvc/servername:1433 domain\sql
setspn -S MSSQLSvc/servername.fully.qualified:1433 domain\sql
Notice how it is ...
This issue occurs because of the Workflow Resource Management Store version value at [WFResourceManagementDB].[dbo].[StoreVersionTable] is still 18.104.22.168 despite you have installed CU3 that should work with Workflow Resource Management Store version 22.214.171.124.
To overcome this issue , you will need to make the two version identical at [WFResourceManagementDB].[...
This issue occurs if the available memory on the web server is low So
Try to restart Sharepoint search host controller in windows service to release all the leaked memory and consumed memory !
Or scale up your memory.
Also, check the following links to adjust minFreeMemoryPercentageToActiveService Configuration Setting as a permanent solution.
Everyone seems to be saying the same thing, but I have one thing to add. Yes, a stand-alone environment is, I guess, sufficient for a development environment. However, for my set-up, I mimicked a stand-alone by choosing a farm installation, but installed everything on one machine. Why? By going down the default, stand-alone route, SQL Express is installed, ...
As you need to move your SQL servers, this can and will be treated as a simple SQL server move, which requires a farm migration. This is because the domain name of the SQL server changes.
For farm migration, you can find instructions at http://technet2.microsoft.com/Office/en-us/library/42511e01-ecdd-4dc5-b06f-35aaada8a5d81033.mspx?mfr=true. Make sure you ...
As long as you name your 2010 configuration database differently than your 2007 config db, you should be fine. In general, I'd recommend making an effort to name all the databases for your 2010 farm in a way that you can easily distinguish the databases for each farm.
Or, you could create a separate database instance on your SQL Server host and point your ...
I happen to have a great exposure working with the Content Deployment in an authoring and production topology:
Authoring and production farm
The two-farm topology is a standard Internet site topology, and it is typical of topologies that are used to publish an Internet site. It includes two server farms: one to host the authoring site collection along with ...
Each SharePoint Server only logs message due to code running on it in ULS. So you'll have different content on each.
You can use the PowerShell cmdlet Merge-SPLogFile to collect information from all servers
The Backup-SPFarm command should use a network share where The service accounts, Farm accounts and SQL Server service accounts have Full Control access to the share. This is because SharePoint uses SQL commands for running parts of the backup and these execute in SQL Server's context.
I know it's an old thread but for others benefit I'm going to attempt to answer your 2nd part of the question (which does not seem to be addressed directly). There should not be any downtime for just adding a new server to the farm.
I would think that a 3 stage environment would make a lot of sense if you were developing an internet. The staging environment gives you complete control over the page authoring environment. As you indicated you have a separate set of permissions for the users involved with authoring. In addition, when the pages are approved in the staging environment, ...
Oke so this was very dumb, it turns out i had to tick the "Enable news feed on My Sites" box, in the "Setup My Sites" Menu in the user profile serve application. Now all the newsfeeds work!
The problem with the sync from Active Directory not working was due to the account used to get the information. We used a standard account to do this, and we were able ...
I would lean more for having at least two server environments - development & production. In many enterprises there is a third (or perhaps more) server environments - QA/Testing/Staging.
There is also a matter of the business industry where the IT development & deployment takes place. In certain industries like HealthCare and Financial Services, ...
when you create a webapplication in sparepoint central admin, you would then need to goto iis -> domain name -> click on "web sites".
You should be able to see a list of web applications e.g.
that and oviously the correlating ip's and port number ect , as you can see its not sites or site collections ...
Your dev, qa/staging and production farms should always be the exact same version of SharePoint, unless you are testing a Cumulative Update or Service Pack prior to deployment to production. Having them be the same version lets you simply copy content databases directly down to QA\Staging from production for testing purposes.
To get your dev environment to ...
The advice from Waqas is good, I also like to have a "Data" drive (where I store site collection backups, and other exports). This allows me to have a backup drive that is different from the Logs and the OS drive.
The farm couldn't have been 'upgraded', but the databases certainly could have. For the Content Databases, you can run the following T-SQL query:
SELECT * FROM Versions (NoLock)
That will tell you the version history in the Version column.
This is a cryptographic error. You will need to set permissions on a the crypto keys folder:
The folder is located at:
Alternatively, go into computer ...
As Qassas mentioned you have to check the resources on the server.
check which process is consuming the memory alot
stop all the services / app pool which are not being used. to free up memory
if you are not using the Search stop that service as it is biggest consumer of memory all the time.
dont create too many web application, keep single web application ...
Log files are generates every 30 minutes by default. So you can manage count of files by changing time to keep files and new file creation duration.
MSDN: You can change the interval by using Windows PowerShell with the Set-SPDiagosticConfig command. The following code snippet configures SharePoint to create a new trace log every 60 minutes.
The standalone setup is generally more than sufficient for development unless you are developing against SP2010 Enterprise only features.(as opposed to the base Foundation product).
You will save yourself a TON of hassle by having Visual Studio 2010 and SharePoint installed on the same OS (e.g. F5 to compile, run and debug all in one go) rather than using ...
I would install a new instance of SharePoint 2010 (same patch level) to the new server, with the correct service accounts etc.
Install all customisations to the new environment (eg deploy WSPs).
Then backup and restore the content databases to the new SQL server, and attach them to the farm.
SharePoint will update the URL of the new server. I would ...
Take a look at HP's Sizer tool for SP2013 or SP2016 for SharePoint. It has long been a staple in any farm sizing exercise (their SP2007 and SP2010 no longer seem to be available. Everything will be in terms of HP-branded hardware but you can easily convert to other brands.
They also have a bunch of whitepapers and guides here
70k users is a fairly big farm,...