I work at a charity foundation and we have a low budget for hardware, but we have four servers as follows:1-Windows 2003 R2 Active directory and SQL Server Standard.2-Exchange server 2007 on 64-bit Windows 2003 R2.3-Exchange edge server.4-ISA Server 2006.We have a maximum of 50 users. I would like to install Sharepoint Server 2007 on the Exchange Box which is a Core 2 duo and has 4GB RAM...Besides the problem with the OWA site and sharepoint sites, are there any other problems or disadvantages that i should be aware of ?? If so is it better to install a virtual server like Vmware on the exchange box and install Sharepoint on a virtual server? or just try to get that extra server box???...Any help is appreciated .....Thanks

You can install SharePoint and Exchange on the same box but as you have mentioned you will have to be carefull how you setup your web sites so OWA and SharePoint both work but also SharePoint elements like Incoming E-Mail will not work as Exchange is already using port 25. Personally I would always put SharePoint on a seperate box if nothing else than to have better backup/restore capabilities but also SharePoint and Exchange are very important business applications in their own right and seperate servers gives you that control for those business needs. Exchange and SharePoint will fight over that 4Gb or Ram and even with 50 users I susepct that memory would become a potential bottleneck. Steev Smith

Thanks,What about the virtual machine idea?

Sure you can run SharePoint in a virtual envoironment , youshould use Virtual server in production as Microsoft have stated they would support this. However you are still going to have your resources issue if you try to run both applications on the one box. It will ultimately become a bottleneck as more people use both sharepoint and continue to use their mailboxes. I suppose the real question to ask first though is how many of those 50 users are ever concurrent. If only 10 of those users where ever on at the same time then you probably could get away with the resources issue. Doesn't solve the backup / restore issue though if the server dies as you now have both Applications down. No Silver Bullet I am afraid , always a trade off. Steve Smith

Thanks very much,I have one last question.. for developong applications for sharepoint using Sharepoint designer and visual studio they require sharepoint services.. do i need to install them on the same server that has sharepoint on???

Not being a developer I am not 100% sure so I will get my developer colleague to jump in on this one. Steve Smith

Hi, Strictly speaking you don't need to. VS.NET & SPD can sit on an desktop machine, and then develop remotely. However, this is a pain in the neck when it comes to deployment, permissionsand debugging etc. I much prefer having a VPC with a standalone install of WSS or MOSS which has SPD & VS.NET installed on it aswell. You can use this to develop, deploy and debug. Use another testing machine to double check your logic etc, and then finally package everything up e.g. Web Parts, Site Definitions, Features etc as a WSP, and then hand that file to the Administrators. That way, Developers won't get any blame for changing anything on the Live Server. Hope this helps. Brett Lonsdale

Exchange 2007 and Sharepoint 2007 can be installed on the same server but you may run into issues with Sharepoint accepting incoming emails/calendar confirmation. There is a workaround but a bit cumbersome to configure. Incoming email setting in MOSS requires the Windows SMTP service which interferes with Exchange's own SMTP service when installed on the same server. A workaround would be to have the Windows SMTP service listen to a different port, then create a Send Connector in Exchange specifically for Sharepoint that sends Sharepoint emails to it. The Exchange Send Connector port needs to also be changed (using PowerShell) so it doesn't send on port 25. There are other steps that also need to be done in addition.. - Configuring 2ndary IP address for NIC - A record that points to new IP (such as sharepoint.yourdomain.com) - Setup Windows SMTP for a Sharepoint subdomain (using alternate port) - Setting up mailbox in Exchange to receive sharepoint requests (ex. HRCal@yourdomain.com) - Create mail contact (ex. HRCal@sharepoint.yourdomain.com) - Forwarding mailbox to mail contact that has subdomain email address (ex. forward HRCAL@yourdomain.com to HRCal@sharepoint.yourdomain.com) We received this request from a client and had it working in the test lab. Luckily we moved them over to SBS2008 so this was no longer needed. There are security issues to consider when doing this as well as time it takes to configure. IMHO, A more cost effective solution would be going with SBS2008.

Hi, I am currently in the process of migrating the server for my small company. We have aren't likely to have more than 20ish users on the server at the same time. My boss would like to transition our server from Windows Server 2003 to Windows SBS 2008. Along with that we would like to migrate the data(if possible, if not copy/paste the important folders/data) from our exchange 2007 and sharepoint 2003 to exchange 2010 and sharepoint 2010. I have been looking around and people seem to imply that SBS 2008 would be a solution for implementing both. However nobody explains why it will work on SBS 2008 and how to implement it. Can somebody please give me an overview of what to do in order to implement and migrate both programs successfully? Thanks, Justin