Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am trying to answer a question for one of my certification exams which is as follows:
You have a SharePoint Server 2010 Service Pack 1 (SP1) server farm.
You have a front-end Web server and an application server.
You discover that when the application server indexes content, it takes a long time for the front-end Web server to respond to the user requests.
You need to reduce the number of items that the application server can index simultaneously.
The solution must ensure that all content is indexed.
What should you configure?
A. crawler impact rules
B. crawl rules
C. host distribution rules
D. search scopes
What is the correct answer?
The configuring the Crawler Impact rules will allow you to reduce the number of requests made by the application server to the source data (in this instance the web front end).
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am hosting and application in IIS. the application is a INTRANET APPLICATION.
Already the server has 2 application hosted in it with host names
site1.k.com and site2.k.com
k.com is my domain name.
I have give host name for my site as
site3.k.com
Do i have to make DNS entry for this.
If you have a wildcard dns entry such that <anything>.k.com goes to your server, then you don't need a specific DNS entry for site3.k.com, but it might make things easier down the road if you have it.
Of course, if you don't have the wildcard set up, and you need to have the url for site3.k.com work, then yeah, it'd be required.
Now, you mention that this is intranet ... if you have a windows server configured to broadcast that it's name is site3 via WINS service, then you might get away with not having the DNS entry, but this behavior is not reliable, because WINS may or may not route to remote sites, depending on WAN and/or VPN configurations, and will generally be a pain in the ass for support.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
When opening the "Site Web Analytics reports" page in my SharePoint 2013 website I'm getting the following message:
"A web analytics report is not available for this site. Usage processing may be disabled on this server or the usage data for this site has not been processed yet."
I did configure the usage and health data collection for my SharePoint Server and activated the reporting feature for my SharePoint website.
Still i'm not getting any web analytics data from my SharePoint website.
Is there somebody able to help me with this problem?
Edit: It seems like the database (WSS_UsageApplication) is filled with data.
I don't understand why SharePoint keeps telling me that there isn't any data available.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I found some technical articles which mentioned that i need to have three separate servers for SharePoint production environment;
- First one is for the Database,
- Second server for Application,
- and the third for the front-end.
But in my case i am planning to have only two servers one for the Database and the other for the application and front-end, will it still be valid to have two servers .Baring in mind that me deployment is considered somehow small with around 60 internal users and around 100 external users?
You can set it up this way. The difference will be in how many SharePoint Service Applications you start on each box.
In environments that have three machines you will see that the there is one box dedicated to the web front end and another that runs the desired SharePoint Applications such as Search, Excel Services, PerformancePoint etc. Since those applications are memory and processor intensive it is best to keep them on a separate machine.
Your performance may vary based on the scale of hardware in your box and how many of those Services Applications you need to kick off.
Some Service Applications can cause a lot of load and need to be finely tuned such as Excel Services and PerformancePoint. I recommend you looking into each that you plan on starting to determine if you will put too much load on your machine
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
What is proxy server exactly. What its purpose ?
there are two types of firewall: packet filters and proxies.
A proxy can have many purposes. Essentially it's a gateway that can restrict and/or log network accesses.
Maybe you're the admin of a network and you want to monitor the web traffic being accessed by company employees.
In that case you might have your client computers configured such that their web browsers / other apps are configured to access the internet through the proxy.
The proxy can then log what is being accessed - and by whom.
Proxies like squid specialise in caching frequently accessed network resources, in order to reduce bandwidth consumption.
There are many other uses, these are just a few. Hope this helps!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I want to create a SharePoint Server setup that will allow applications to be highly avaliable. Say if we have a portal in SharePoint, and I wanted to make it available always. I know it has to do with WFE. Someone guide me with article or Arch that need to be set for this.
Having multiple WFE (Web Front-ends) will make the web part of your SharePoint more reliable -- if one goes down, you can have your load-balancer stop sending requests to it. There is no way to ensure 100% uptime -- reliability is a combination of having redundancy (in hardware and services), monitoring, 24x7 staff to fix problems, etc.
Some things to look at:
Plan for Redundancy
http://technet.microsoft.com/en-us/library/cc263044.aspx
Plan for Availability
http://technet.microsoft.com/en-us/library/cc748832.aspx
There are third-party products that can help with fail-over, but I haven't used one to recommend.
See Lou's links. You can have redundant WFEs, query servers, and application servers as well as cluster your database.
Note that you cannot have a redundant index server unless you have two SSPs that basically index the same content. The query servers get the index replicated on them, so if the index server goes down you can still perform a query, the index will just not be updated until the index server comes back online. If you can't get it back online you will need to rebuild your index (full crawls).