Hot answers tagged

8

What kind of issues are you experiencing? If a NLB is in place, you can still hit an individual server and load the SP site bypassing the NLB (you'll need to make sure the site has alternate access mapping set for the server name). But if you want to remove it, it should be straight forward, hop onto that box and uninstall SharePoint, it'll take it out of ...


8

You cannot install two sharepoint farm 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 farm. This solutions is not recommended for the production farm


6

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 ...


6

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.


5

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


5

I was looking for the same information, and just found the answer here. Here are the steps: Launch regedit.exe 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 ...


4

(1) How do I transfer the Central Admin site from being hosted on the old server to the new server? You do that via the SharePoint 2010 Products Configuration Wizard. Remove the CA from the old server, then add it (again via the wizard) to the new one. Here it is explained in a little more detail: ...


4

Run the configuration wizard and disconnect the server from the farm. You may be able to run NewSID and change the identity of the machine and then re-join the domain. You certainly want to create a new farm for the test environment.


4

If you want to completely stop a SharePoint farm there is a useful list of services within the Move all databases (SharePoint Foundation 2010) article. Obviously (as you have requested) this will mean that ALL SharePoint activity will cease: "To stop the farm On the server that is running the Central Administration Web site, in the Services snap-in, stop ...


4

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 ...


4

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 ...


4

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, ...


4

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


4

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 ...


3

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 ...


3

This article will be helpful : http://technet.microsoft.com/en-us/library/cc261752.aspx


3

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, ...


3

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 ...


3

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. ssp.example.com hello.example.com test.example.com that and oviously the correlating ip's and port number ect , as you can see its not sites or site collections ...


3

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 ...


3

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, ...


3

When you add a new server to your farm you have to run either PSConfig or Powershell to provision SharePoint services. In Powershell you run Install-SPService You still need to define which services will actually run on the server. Essentially, your custom service would follow the same process, install on new server, than start the service.


3

What is it that you hope to accomplish by taking SharePoint offline? Quiescing the farm will prevent SharePoint from serving end-users so you can install features and so forth. Stopping the services goes another step beyond that. In fact, you will not be able to install features if all of the SharePoint services have been stopped. The procedure is the ...


3

From http://www.muhimbi.com/blog/2009/05/how-to-reliably-detect-moss-or-wss-at.html /// <summary> /// Method to find out if a SharePoint installation is MOSS or WSS 3.0 /// </summary> public static bool IsMOSS() { SPFeatureDefinitionCollection features = SPContext.Current.Site.WebApplication.Farm.FeatureDefinitions; if ...


3

Central Administration > Manage servers in this farm (under System Settings) Configuration database version of 14.xxx is 2010 and 12.xxx is 2007 SharePoint Products Installed will show you the product.


3

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.


2

You have a Single Server farm and would like to migrate SharePoint server to a new domain Old Domain: FABRIKA.CONTOSO.COM New Domain: CONTOSO.COM Step 1: Preparations before migrating servers: 1.Check if the SharePoint Central Administration’s Application Pool is running under Network Service or using a Domain Account To verify: ...


2

Back up your Content DBs (if an all in one box), flatten the system and rebuild from scratch. SharePoint environments can be quite disposable in a way - it is often far faster to rebuild a web front end than to troubleshoot an issue. Farms can also be rebuilt from backups sometimes much faster than troubleshooting issues like these.


2

Simple answer of this question is: Farm Administrator is the father and Site Collection administrators the kids. Farm Administrator have full control on SharePoint farm; can create services applications, Web Application, manage quota, deploy solutions, configure the farm level settings, run PowerShell scripts etc. While site collection administrators, only ...


2

The command below always helped me to take backup of entire farm. Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -Force Source: here and here If you want a script which will take backup regularly, I'll suggest you to check this script. It's for SharePoint 2010 but I don't see any reason for it to not work with SharePoint ...



Only top voted, non community-wiki answers of a minimum length are eligible