I have been running WSS3 in a VMware server VM for almost two years. 1GB RAM, 1 CPU. About 5 heavy users, 15 medium users, and 30 light users. MSDE back end, one content db that is over 40GB. No serious complaints about performance.
I'm in the planning phase of upgrading to MOSS'07 with a SQL back end. All as VMs on ESX. The default file size limit is 50MB, and MS recommends not changing. This can be a limiting factor for some files. Recommend that content DBs not be more than 15G to get acceptable restore times. Get the administrators guide and read the chapter on search a couple of times. If you have to reindex your search it can overload your system, CPU and storage. There are ~6 things that kick off a reindex...know what they are. Search is off by default because of the gotchas. Make sure you have everything configured like you want it before turning it on (info from the MOSS class I took earlier this year) Robert On Thu, Nov 13, 2008 at 2:16 PM, Bob Fronk <[EMAIL PROTECTED]> wrote: > I am gearing up to deploy SharePoint Server 2007. The main goal is to > help eliminate "Outlook as a file transport", but eliminate the 100's of > file shares we have. But I also know there is much more to the product. > > > > I would appreciate replies from those that have deployed SharePoint or have > SharePoint experience on what your deployment experience was and what you > would or wouldn't do again. > > > > Also, anyone have SharePoint running in a VM? > > > > As I type this, I am loading up a test server to experience the install > process and do some testing. > > > > Thanks for any info. > > > > Bob Fronk > > [EMAIL PROTECTED] > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
