Tag Info

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


5

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


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


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

(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

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

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.


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

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


3

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


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

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

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


2

Running SharePoint 2010 using local accounts. Check out the following articles: Single Server Complete Install of SharePoint 2010 using local accounts Tips for building SharePoint 2010 base VM images More on Google.


2

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


2

If you haven't already done so, you may also need to add the dbcreator and securityadmin server roles to your user in SQL Server. Have you looked at the SharePoint logs (in the "12 hive") and the Windows Event Viewer on both servers already? They are helpful in diagnosing configuration issues.


2

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


2

The advantages of multiple instances are limited in the scenario you've given. You are correct in what you're implying - that you could simply have one farm, with no content deployment. Editors could see unpublished content, and other users see published. Or, as the document you linked to says, you could have one instances and deploy to a different site ...


2

There is no problem removing a WFE if you can handle the load with a single server. The only thing you are sacrificing is resilience since if that single server fails you will be offline.


2

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


2

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


2

Take a look at HP's Sizer tool for SharePoint. The one for 2007 has long been a staple in any farm sizing exercise, and they have now made the 2010 version 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, I don't ...


2

If your web application has a seperate host header, then just point the DNS directly to that WFE instead of going through your load balancer


2

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



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