Discover more sharepoint 2013 Farm

Dear all,
We have three sharepoint 2013 Farm ( test , staging ,PROD ). I have discovered test Farm after modify microsoft.sharepoint.foundation.library.mp with test server , after that when i change
the test to staging server in config file staging farm will get discover however test will get move off ( disappear ). my question is how to discover two or more farm , we are having different credential for each farm.
Thanks,
Sengo

Hello,
See if the following link helps you.
http://blogs.technet.com/b/mgoedtel/archive/2012/01/07/sharepoint-2010-multi-farm-monitoring.aspx
Thanks,
Tom
Kind Regards, Tom Ziegler | http://www.sccmguy.com | Twitter @Tom_Ziegler

Similar Messages

Need to Setup Project Server in existing SharePoint 2013 farm

Hi
I have already SharePoint 2013 farm having 4-WFE Servers, 2-Application Servers, 3-dedicated Search Servers, 2-DB servers (Clustering enabled). Now I want to add one more App server having Project Server 2013 in this existing farm environment so Please
check the below steps. Please let me know If I am wrong in the approach.
Need to install PS 2013 on all the WFE, Applications and Search Servers.
Need to Run Sharepoint wizard on all the servers one by one. (Is it mandatory to run wizard on each server or should run only on application servers only)
The project Server service should run only on application servers.
Regards, Pankaj Waghmare - MCTS | Consultant

Hello,
Those steps are correct for high level :) One thing you might need to do is after installing Project Server on all the servers is apply the same CU / SP to Project Server as SharePoint (using the Project Server equivalent patch) so Project Server and SharePoint
are patched at the same level. I would do this after installing PS2013 and before you run the wizard on each server.
I would ensure you test this on a non prod farm first and ensure you have a roll back plan in place.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Backup Sharepoint 2013 Farm with SQL 2012 "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 Farm with SQL 2012 "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find confirmation anywhere.
Regards,
John

Per this thread
http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup, no it does not look like this is supported.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

What are the best practices for audit report for SharePoint 2013 farm ?

Hello,
I am looking for the best practices for audit reporting in SharePoint 2013 farm.Can anyone please provide me checklist/tools/guidelines on same ?
your help will be much appreciated.
Thanks and Regards,
Dipti Chhatrapati

This is quite open ended question. A sharepoint farm should be well maintained as per :
1. Microsoft's recommendations on : Topology, Hardware and Software requirements, Operational procedures and most important Capacity guidelines:
http://technet.microsoft.com/en-us/library/ff758645(v=office.15).aspx
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx
2. Organisation's IT policies and procedures : Farm Configuration, Workload and monitoring
http://technet.microsoft.com/en-us/library/ff758658(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ee748651(v=office.15).aspx
3. Industry best practices
I would suggest to start thinking over these lines and create a plan for your Sharepoint farm.
You can then create powershell scripts to run these reports at certain frequency to find the changes, any deviation from the standard and health of the entire farm.
Hope this helps!!
I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)

NLB for SharePoint 2013 farm ?

Hello All,
I have a very simple three-tier SharePoint 2013 farm which its architecture consists of: (1 DB Server, 1 Application Server, and 1 Web Front-End Server) which all are running on Windows Server 2008 R2.
I now need to add another (Second) Web Front End server.
Steps that I know:
A) Following the installation instructions on: (http://technet.microsoft.com/en-us/library/cc261752(v=office.15).aspx), especially: Connect to a server farm page: Connect to an existing server farm.
B) Question-1: After completing the installation steps, Should I run the SharePoint 2013 Products Configuration Wizard on the Application server (The server that hosts Central Administration)? Or, No need to do so?
After that, I will have 2 Web Front-End servers, and I will need to configure load balancing. I found some articles to set up load balancing on a SharePoint farm using the OOTB Windows Server network load balancing (NLB) feature.
Question-2: Is this adequate and powerful enough? Or, Do you recommend any other third NLB solutions (Reasonable price)?
Thank you !

You do not need to run the Config Wizard on the App server. Windows NLB isn't great. It doesn't know about service status (e.g. if IIS is up or not), but it will 'do the job' for a few hundred to low thousands of users. Load balancer appliances are not
necessarily cheap, but BigIP products are popular.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Deploying Project Server 2013 to an Existing SharePoint 2013 Farm

We recently deployed the following for our new SharePoint 2013 farm:
2 SQL server (alwaysOn config)
2 application servers
2 WFE
1 SQL for Dedicated Search
2 WFE for Dedicated Search
2 Applications Servers for Dedicated Search.
After purchasing a company that uses Project 2013 heavily we are now looking at deploying Project 2013 using our new 2013 SharePoint farm. My question is what is the recommended additional servers that would needed to be deployed to the existing farm?
Thanks,
Ric

Ric,
It really depends on what your current dataset is, and what the load on your SharePoint Server/Project Server. Technically, Project Server can just sit on top of your WFE and App Servers for SharePoint. You do not need a complete separate server group
for Project Server alone, unless there is a special reason to do so.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Replace FE and APP server in SharePoint 2013 farm

Hello,
We have to replace the front-end web and app server from a SharePoint 2013 farm. The farm only has 1 FE, 1 APP and 1 SQL server. As the FE and APP were wrongly patched and have unsupported software installed there's no way of getting all servers
at same version level and to succesfully run the Product Configuration Wizard. The database server is ok but we have to replace the 2 other servers.
Is there any documented procedure to perform this migration/reinstall?
Thanks!
Martin

for first approach.
1- go to central admin and add all roles you need for the server that will stay
2- log into the server you will remove then run configuration wizard and choose disconnect from farm
you will have now one server, you can clean it up and keep it or later remove it when u have the new one
3- to add new server
https://technet.microsoft.com/en-us/library/cc261752.aspx
Kind Regards,
John Naguib
Senior Consultant
John Naguib Blog
John Naguib Twitter
Please remember to mark this as answered if it helped you

Single SharePoint 2013 Farm for two geographical locations

Dear All,
I want your expert advise and suggestion on an "Architecture" for Deploying SharePoint 2013 in multiple geographical locations. I have read every line in article:http://technet.microsoft.com/en-us/library/gg441255%28v=office.15%29.aspx before posting
this question, for the following scenario:
Scenario:
Two locations, say, Loc1 and Loc2.
SharePoint Farm = Collection of SharePoint servers connected to the same Configuration DB.
WFE1 will be in Loc1 and WFE2 will be in Loc2 (and connected to the same config DB i.e. same Farm).
App1 will be in Loc1 and App2 will be in Loc2 (and connected to the same config DB i.e. same Farm).
Users from Loc1 will be directed to WFE1 and Users from Loc2 will be directed to WFE2.
App1 will run services and service applications consumed by web applications specific to Loc1.
App2 will run services and service applications consumed by web applications specific to Loc2.
I can implement all of the above.
Now question is "How to provide local flavor for back end SQL?"
suppose, I configure "Active-Active" SQL clustering SQLNode1 at Loc1 and SQLNode2 at Loc2, how do I specify that web applications meant for Loc1 are fetched from SQLNode1 and web applications meant for Loc2 are fetched from SQLNode2.
Users in Loc1 are not interested in web applications meant for Loc2 and vice-versa. Currently we are having Two (2) different farms at each location, but going forward we want to consolidate so that "Infrastructure maintenance" is minimized and
investment in third party solutions can be leveraged by both locations.
Naveed.DG MCITP, MCTS -SharePoint 2010 Administrator "Vote As Helpful" If it helps!!

How far away are these SharePoint servers away from each other? Remember that regardless of where a SharePoint server is, it must be able to write to the active instance of the Configuration database, and must have that 1ms timing.
Active-Active SQL clusters has never been mentioned, as far as I'm aware, in TechNet documentation. I'd consider this scenario unsupported unless you talked to PSS otherwise.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

WebSite replication to other machines SharePoint 2013 Farm

Hi all,
I have done a basic install and configure a SharePoint 2013 with two front end (FE), three application servers (app1, app2, app3) and one SQL 2012 cluster.
When I tried to import a SP 2010 site from app1 and test on this server it works. later in the day, I tried on FE1 and FE2, none of them work. I did check IIS on FE server and didn't see the site I tried to import is there.
Please help. What did I miss?
Thanks.

Is that like all the services in WFE(IIS,web and Sharepoint foundation webapplication under Manage services on server) are running?
Do you see other sites in IIS of wfe?
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Possible to use both Tabular and Multidimentinal with same SharePoint 2013 farm?

I would like to build SharePoint 2013 based reporting portal with Power View as visualization tool.
Is it possible to install both Tabular and Multidimentional to same physical server?
Is it possible that some Power View reports use tabular and others multidimentional?
Could above requirement work in production environment? Anybody tried?
Kenny_I

Hi Kenny_I,
According to your description, you are going to create a PowerView report using SQL Server Analysis Services Multidimensional database or SSAS tabular model as data source in SharePoint 2013, now what you want to know is that is it possible to install both
Tabular and Multidimensional to same physical server? And is it possible that some Power View reports use tabular and others Multidimensional?
Of course we can install both Tabular and Multidimensional to same physical server that had SharePoint 2013 installed. In my tested environment, I have installed all of them on the same server. And we can use tabular model and others Multidimensional database
on individual PowerView report. However, it seems that we cannot use both tabular model and others Multidimensional database on the same Powerview report.
Even though we can install both Tabular and Multidimensional to same physical server, however in the production environment, the recommendation is that install them on different server, it will beneficial to troubleshooting the issue when some issue occur
on the environment.
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

SSRS deployment in Sharepoint 2013 FARM

When I was deploying SSRS in my SP2013 QA environment with 4 servers (2 App and 2 WFE) , I deployed it on 1 Application server (that has CA) and on completion, the SSRS Site Collection Features were missing in the farm. Deployed on
the other App server and both WFE and now SSRS Site Collection Features is available. I have not found any Microsoft document that indicated on which servers to install SSRS in a FARM.
I am now planning PROD SP2013 Farm deployment where I have 2 App servers and 2 WFE. Do I install SSRS on all 4 servers or just the App Servers or just the WFE servers ? Is it needed on all 4 servers in the farm?
SQL server instance supporting the SharePoint Farm is on a SQL server, and not on any of the servers in the Farm.
Thanks
MP

You only need the SSRS Service installed on a single server in the farm. You do need to deploy the SSRS Add-in that matches your SSRS service to all of the other farm members, though (http://msdn.microsoft.com/en-us/library/gg492257.aspx).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Adding a 2nd SharePoint 2013 Farm to the domain

hello.
in my production domain environment i have a SharePoint farm consisting on a single SQL server and a SharePoint server, sadly this has a few underlying issues, so in isolation i have built a new FARM and now want to migrate it into the production domain,
but i still want the other FARM operational for now so users can continue to use it.
i need to configure some exchange integration, external web access and HTTPS for the new environment i just want to check that the farms wont interact with each other and its safe to do this?
the only issue i can see is that central admin has the same web URL on both farms, would it be best to change the URL via AAM on the new environment so not to cause a conflict?
many thanks
Gordon

thank you
also the servers are an early version of the production system (originally built on a server with VM workstation and migrated to ESXI host thus they were left over in a functional state) i am using these because its significantly faster than building a whole
new farm from scratch, i have transferred the WSS_Content DB to it, its all work now but sadly share the same names and ip's as the production system.
how can i change the server names and IP's on the new systems so not to break SharePoint.
many thanks
Gordon

Cross Farm Search in SharePoint 2013

We have a SharePoint 2013 on premise Farm i.e A,we are planning to add 2 more SharePoint 2013 farms i.e B,C.We want to a to implement cross farm search,Following are my queries
1)Is it possible to search contents of other 2 farms from a third farm.I am little confused regarding consuming farm and publishing farm.
please provide me the suggestion as well as the link for the setting

There is a detailed post of MSDN for achieving the correct trust configuration between two farms to enable cross farm search:
MSDN: Configure trust for search between two SharePoint Server 2013 farms
Thanks, Ransher Singh, MCP, MCTS | Click Vote As Helpful if you think that post is helpful in responding your question click Mark As Answer, if you think that this is your answer for your question.

SSL Certificate to apply on more web application - SharePoint 2013

Hi,
based on your experiences, I'd like to know which SSL certificates are good in order to apply them for more web applications in a SharePoint 2013 farm. Saying a good SSL certificate I intend a SSL certificate not more expensive. The idea is to buy one
certificate with 1 or 2 year licence and use it for two, three, ... web applications.
Fe, I've a look to Thawte certificates but I don't find any info talking about the possibility to apply one certificate for more web applications.
Any suggests to me, please?

A single-host certificate applies to one host, or a single Web Application using Path-based Site Collections.
A SAN certificate applies to multiple, limited number of hosts for use with multiple Web Applications using Path-based Site Collections (or in a limited fashion, Host-named Site Collections).
A Wildcard certificate applies to an unlimited number of hosts, or an unlimited number of Web Applications using Path or Host-named Site Collections.
You want a wildcard, unless you have a good reason to not want a wildcard.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

What needs to be done to rebuild a current Sharepoint 2010 Server farm to work as a Sharepoint 2013 Server farm?

Hello Community
    Currently I have a Sharepoint 2010 Server farm.
    One server contains the database and DNS server
because it is the the domain controller.
    The other server Contains the Sharepoint 2010 Server software
and is the the application server where applications such as Metadata,
UPs, etc, reside (including web applications with sites built with the UI).
    Now I am going to change to Sharepoint 2013 Server because currently
there is no newer version of Sharepoint available.
    I am ready to rebuild the current Sharepoint 2010 farm configuration into
a Sharepoint 2013 Server farm from scratch.
    The question is what do needs to be added and\or changed to make the current
Sharepoint 2010 Server farm configuration work as a Sharepoint 2013 Server farm?
    Thank you
    Shabeaut

There is no direct in-place uprade method for SharePoint 2010 to 2013. You need to create a new SharePoint 2013 farm from scratch and attach service and content databases to upgrade them. Check out Upgrade
to SharePoint 2013 for more information about the process.
If you have another server, you would install SharePoint 2013 on this. If you don't, you'll need to remove SharePoint 2010 from your existing server and then install SharePoint 2013. Check out Hardware
and software requirements for SharePoint 2013 before starting to make sure your server meets the minimum requirements for SharePoint 2013:
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013 or SharePoint Foundation 2013.
12 GB memory
64-bit, 4 processor cores
80 GB for system drive
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Discover more sharepoint 2013 Farm

Similar Messages

Maybe you are looking for