Is it possible to add WSS as front end and MOSS as server?
No, it's not possible to mix WSS and MOSS in the same farm. Furthermore, all servers must be at the same patch level etc.
Im not sure i understand this question.
MOSS is build on top of WSS -you can see WSS as the foundation of SharePoint (this is also what it is called in the new version 2010 of the product).
hth Anders Rask
We have 3 front-end servers each running multiple web applications. Each web application has an in memory cache. Recreating the cache is very expensive (>1 min). Therefore we repopulate it using a web service call to each web application on each front-end server every 5 minutes. The main problem with this setup is maintaining the target list for updating and the cost of creating the cache... in memory cache across multiple front-end servers?
that existed prior to the upgrade. This is also the case in a retract,delete,add,deploy scenario. Note: Our server topology has changed over time. Our Central Admin machine reached its End of Life, so we... (Server2). Added it to the old server (Server1). Deployed the WSP. On the Solution Management page, two of the three front ends deployed successfully (Server1+Server3). I ended up having to remove and re...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 am using SharePoint 2007 Server x64 on Windows Server 2008 x64. I create a new SharePoint web application with a new site collection at the root of the web application. I select the template "publishing portal" for the site collection. I have also enabled anonymous access. Now the basic function is fine, except that I do not know how to change the first front page (i.e. the page showed to end... on the site collection for the forms authentication logon page to work from Office SharePoint Server. Contact your administrator to have anonymous access enabled in Central Administration and IIS. Manage
I have a few Content Types that inherit from a base Content Type. These are all wrapped up as part of my solution. I wondered, as it is possible to add additional columns to a child Content Type using FieldRefs, is it possible to remove a column for the child Content Type that is specified in the parent Content Type? It can be done on the front-end but I wondered if I could do it as part of my deployment?
I have custom web.config functionality that uses Linq to merge elements into a web.config based on a template file. I would like to use this in a feature so I can get it to merge all web.configs in a load balancing environment. I know there is something called SPWebConfigModification, but the extent of the elements to add is large and I need it to be more dynamic like the template solution. I know I could run it on each front end server, but it would be better in a feature or solution. Is there a way to get access to the web.config in a feature in SharePoint 2007?
I'm using Search Server Express + WSS 3.0. I wanna crawl external public web sites. One site is : http://www.av.se/ When I try a full crawl it is throwing: http://www.av.se Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. Local sites and other public sites are getting crawled OK. What is wrong with that sit? Can you add it on Content sources and try a full crawl for testing?
We have a SharePoint server farm that has both Windows 2003 and Windows 2008 servers as front end. Has anyone else tried this configuration? Is it supported?
I created an application in SharePoint, lets call it http://example.com/ and a site collection with the "Empty Site" template. Since I'm using it locally in a virtual machine in host-only mode, I had to edit my host file to add 127.0.0.1 example.com Now, whenever I access this website, I cannot click on "Site Action". All it does is add a # at the end of the URL. Since I'm in a host-only VM, i cannot change the DNS to make it work (that's the way we fixed it for a dev server).
what do you think about deploying the SharePoint IIS web sites to a Shared file location (\\Fileserver\WWWRoot\Application1 for example) in contrast with deploying a copy locally to each Web Front End server (c:\inetpub\wwwroot\application1 for example). Deploying locally to WFEs can usually take time to copy physical files to the different WFEs and we make efforts in making them synched and sometimes we have problems because the two servers are not exactly the same and so on. Are there any problems with the approach of deploying a Sharepoint IIS web site on a shared location path?