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 think the problems you will need to look at will be from a load balancer and DNS perspective. These are the areas where you may encounter some issues. If you are using a physical appliance for load balancing, you will have to make sure that it still functions properly after the changes. This may require you to update IP addresses manually or allow time for the new IP addresses to resolve. You don't mention if your load balanced IP will change as well, but if it does, then your end users will have a (however brief) period where the IP address is not updated in their DNS cache.
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?
added another server to the farm, moved the central admin with the stsadm tool, and removed the old server from the farm. Here is what I have tried: Deployed to two other farms: successfully deployed..., 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
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 ?
We are finding recently, with our wsp deployments, that on some of the WFE/APP servers in our farm that the assembly contained in the WSP, which should be gaced, is updating some servers but not all. Almost like the assembly in the GAC is locked on some servers but not others.
I have successfully configured a SharePoint farm of 4 nodes but I got intermittent database connection failure errors. I have to restart SharePoint services and IIS to fix the database errors. Mostly... in this Farm" and it shows me two warnings. I am wandering if the second warning has anything to do with these intermittent database errors. And, I want to know how can I solve these warnings. Warning 1...: Thanks for your reply. I understand about the first warning and I just left it as it is. However, same set of services are running on each WFE not sure what is different let me show you what
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
I am installing SharePoint 2010 single farm on my 64bit Win7 Ultimate development machine. After a lot of pain and apparent success of the installation, I am not finding the "Farm Configuration Wizard" on the "Configuration Wizards" page of Central Administration. Looking for reasons why and things to check to make it show up.
for each stage of ILM certificate creation failure). The system is a multi (3) server farm: WFE Windows 2008 64Bit SharePoint 2010 APP (UPS and UPS Sync Running Here) Windows 2008 64Bit SharePoint... server are starting and are using the FARM account. The ILMMA and MOSS- folders are NOT present in %Programfiles%\Microsoft Office Servers \14.0\Synchronization Service\MaData. A similiar thread... failed. The login is from an untrusted domain and cannot be used with Windows authentication. UPDATE Switching to mixed mode authentication (?) on SQL fixed these problems. I then ensured a bunch
SharePoint provides an option in Create New WebApplication page that says Restart IIS Automatically. This restarts IIS on all servers of the farm. What can I do to trigger this programmatically from my Application Page (ASP.NET)? Is there a timer job for this? Is there anything in the API? do I have to create "iisreset" process and pass it the name of servers?