We would like to introduce a new WFE in the existing SharePoint 2007 Farm, due to the business requirement, which already has 8WFEs and separate servers for Index, Query & admin. what would be the best approach to follow ?
Can you tell a bit more about the farm setup? Especially regarding SQL server.
A rule of thumb is that you should not have more than 5 WFE per SQL server instance. Going beyond that the WFE will put too much stress on the SQL server, and actually degrade performance. I also seem to remember something about a support limit of 8 WFE, but im not certain.
EDIT: ok i found the soft limit for WFE on TechNet:
Web server/database server ratio: 8* Web servers per database server The scale out factor is dependent upon the mix of operations.
I have a MOSS 2007 farm with two WFE, one index and a SQL cluster. For some network reason, we need to change the IP addresses of the WFE. Would this affect the farm in any way?
I want to create a new SharePoint 2010 farm using PowerShell. I use the following command: New-SPConfigurationDatabase When issuing this command (and providing the needed parameters) I get the following error: New-SPConfigurationDatabase : This SharePoint farm currently has pending upgrades. The cmdlet New-SPConfigurationDatabase cannot be executed until the upgrade is completed. When running the "SharePoint 2010 Products Configuration Wizard" I'm able to create a farm. I have a freshly installed Windows Server 2008 R2 with SQL 2008 R2 on the same box (it's a demo box
new files (rules out WSP as the problem). Restarted OWS Timers on both WFE Restarted both Machines Verbose Logging The one difference here is that on the server farms that work, you see individual..., we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server...We have a server farm that is having issues deploying WSPs. The odd thing is that the server goes through all the motions of deploying the WSPs with no errors. That is, the job is scheduled
I've a timer job which I want to run only once per day, for the entire farm. How do I Deploy it in a multiple WFE environment? Do I run the stsadm -o deploysolution command in every WFE, or just the one where I want to run it? Where should I activate the feature? Should it be activated only from a particular WFE? What should be the value of the SPJobLockType?
In order to develop SharePoint 2007 workflows in Visual Studio 2008 on 64 bit, I would create a new (non-SharePoint) Workflow project. Then, I would add the appropriate onWorkflowActivated activities... to modify all the existing activities without problems. Now, I am starting a new workflow project and I performed my normal routine, but the SharePoint activites were not on the Toolbox. I enabled all items to be shown and the SharePoint Items were greyed out (Assembly version 18.104.22.168, not the tab for 14). I unloaded the project and compared it to a project created with 2008, and I was missing
When I go to manage service applications in Central Administration and try to create a new service application like: New > Create a new service application, the link isn't active. My issue is I would... Application? Business Data Connectivity Service Enabling this service provides the SharePoint farm with the ability to upload BDC models that describe the interfaces of your enterprises' line... migrated WSS v3 to SharePoint Foundation 2010 and then installed Search Express 2010 on top of it. I am logged in with an account that has full farm administration access. Update 2: I migrated WSS
these documents should replace 2 of the existing documents from the original 5 - so that only 5 documents are ever displayed to Martin or John. John must not be able to see the original 2 documents that have been replaced. A small amount of luck is that an administrator will specify which new document should ‘replace’ an existing document from the originals. Over time I would be required to add more documents and and users, providing the same functionality of ‘replacing’ certain documents for certain users. How would you do this? My first thought was creating roles and configuring the roles
have 200 sites using that template. Now the customer realize that they need two new content types on that library. Oh, and they will need those content types on the existing sites as well. I might have misunderstod something about content types or just misconfigured the library, but so far the only way I have been able to add those new content types on existing sites have been through a powershell script. Is this just a feature in SharePoint 2007 that I'll have to get used to, or have I missed a crucial point?
When a new server is added to a farm will SharePoint automatically synchronise the machine key such that view state will work across the farm, or is a manual operation required?