I understand that we do not want to install SP2013 and Exhcnage 2013 on the same box in production environments, but my question is about a development VM.
Is it possible to install these two servers successfully on the same box. I have tried, but so far the Exchange install does not appear to complete successfully and I don't know if it is because of something I'm missing or if there is something that prohibits them running together.
It seems that your Exchange Setup failed so first things first is to use Exchange Server Setup to completely remove the non-functioning Exchange.
It's preferred to remove SharePoint also.
After that, install Exchange Server first, then SharePoint. Then do some additional work (see links below) to configure them. If Exchange Setup continues to fail, seek for other solutions.
However, I strongly suggest you install separate VMs to host Exchange and SharePoint on separate OS installations.
Reference:
Installing Sharepoint on the same server as Exchange and Remote Web Access (IIS – Sharepoint -RWA – OWA Conflicts)
Can be Install Exchange Server 2010 and SharePoint 2010 on the same server without any conflict?
It won't differ very much between Exchange and SharePoint 2010 and 2013 so the links above should also apply.
Related
I'm trying to migrate our existing TFS 2008/SharePoint installation to TFS 2012/SharePoint 2010. If I do it without SharePoint it all works OK, but if I try and include SharePoint it fails.
At the moment I'm starting from scratch and including SharePoint.
I've run the Configure Extensions for SharePoint Products Wizard, restored the TFS 2008 databases, run STSADM from the command line, and now I'm attempting to run the TFS 2012 Upgrade Wizard: it fails at the, Configure the Server Running SharePoint step with the error "TF250004: The SharePoint Products installation is either corrupt or is not valid. Verify that SharePoint Products is a supported version and is functioning properly, and then try again."
Can someone please advise me what I've done wrong?
It seems that your TFS server can't detect you SharePoint .
Where is your Sharepoint server, is it running on the same computer with TFS server or on another machine?
With your upgrade ,did you change your hardware or use the same hardware as before.
Accroding to your description, you didn't mention whether you need to upgrade your SharePoint. You should finish SharePoint upgrade before your TFS server upgrade.And match TFS upgrade requirements https://msdn.microsoft.com/en-us/library/vstudio/dd631912(v=vs.120).aspx
You should also pay attention to your sharepoint permission.I suggest you use a "Full Permission" Account in sharepoint which interact with TFS .For your reference:http://social.msdn.microsoft.com/Forums/sr/tfsadmin/thread/ea2ef379-dd14-4e23-86e6-fbc156e430d8
I eventually unchecked the "Configure SharePoint Products for Use with Team Foundation Server" option to exclude SharePoint during the upgrade and then manually configured SharePoint after the upgrade, overcoming a host of problems along the way.
Is following scenario possible?
We have got TFS 2013 installed as a standard single server. This server has got the SQL db.
We have got SharePoint 2013 installed on another machine.
Now we want to integrate TFS 2013 with SharePoint 2013 along with SSRS and SSAS for reports, etc.
Please guide whether this is possible or we need to install TFS via Advanced mode again?
No problem, you can integrate your existing TFS single server deployment with your external SharePoint server assuming you have the necessary permissions.
MSDN: Verify your SharePoint installation
https://msdn.microsoft.com/library/dd578601(v=vs.120).aspx
MSDN: Set up remote SharePoint
https://msdn.microsoft.com/library/hh548140(v=vs.120).aspx
Cheers
Adding SSRS and SSAS is relatively simple too and can be on the same server as TFS or a different one.
MSDN: Add a report server
https://msdn.microsoft.com/en-gb/library/dn148128.aspx
Martin Hinshelwood has a couple of useful blog posts on this subject too:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
*sorry for the multiple answers, new account and SO doesn't trust me to post 5 links yet! :)
I've been looking around TFS 2013 screenshots and I notice how it look like it's implemented over Sharepoint 2013...
So, when i install TFS 2013, do I get a full blown sharepoint (with central admin and everything), just a site collection (a "light" version of it) or none (meaning if, i want a web interface, i have point to my sharepoint and say "use that one")???
PS: Since i'm in a corporate environment i don't have a spare machine to just install it and check it for myself, and other documentation don't make this clear...
TFS has its own web-based interface (TFS Web Access) that isn't based on SharePoint. It also has the ability to integrate with SharePoint which will cause SP-based Project Portals to be created with every Team Project (this is in addition to TFS Web Access).
When you install TFS you can choose to have the TFS Install install/configure SharePoint Foundation, or you can point it to a pre-existing SP Foundation or Enterprise environment.
SharePoint Foundation 2013 can be installed with TFS, if you specify that in the installation.
Reference
SharePoint Products requirements for Team Foundation Server
Does it work if both sharepoint foundation and sharepoint server installed in a single machine?
No.
Have you thought of using Virtual Machines (such as Hyper-V or VirtualBox) to do this?
Looking at the way you tagged your question, the answer is that it depends.
If you are talking about the same SharePoint version (Foundation 2010 and Server 2010 for example), then just install Server and you'll have everything that Foundation offers as well because SharePoint Server includes SharePoint Foundation. SharePoint Server just adds more services on top of what Foundation provides. There is no need to install both.
If you are talking about having Foundation 2007 and Server 2010, for example, where there are fundamentally different versions of SharePoint being installed, then no, install these on different servers as different Farms.
I am following the Microsoft tutorial for creating my first sharepoint 2013 app.
(http://msdn.microsoft.com/en-us/library/fp142379.aspx )
I have installed on a windows 2008 R2 Server Sharepoint 2013 RTM, done all the farm config stuff RTM, and installed all of Visual Studio 2012 ultimate and update 1 and restarted the server.
I have also followed the instructions for "How to: Set up an on-premises development environment for apps for SharePoint" which is at http://msdn.microsoft.com/en-us/library/fp179923.aspx (I have to do this as our dev environment has no internet access)
I have got to the point where running Visual Studio as an Administrator I have named it and chosen "sharepoint-hosted" and validated the server and clicked finish (Step 5).
Instead of getting the next step where I open the AppManifest.xml file I get a message saying "An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed. Microsoft Web Developer Tools and Microsoft Exchange Web Services"
I have checked VS setup and web developer tools is definetely installed (the only option I have would be to remove it)
Any help would be greatly appreciated. I know Im a noob here (this is my first post) but I have googled this and searched stack exchange and found nothing that helps me.
Got it after a few trial and errors
With an offline install you have to download the Exchange Web Services component. I had downloaded "EwsManageApi" and installed that.
As the error message specifically refers to Exchange Web services, I looked at other versions and tried the older 1.1 and the 32 bit version, but they didn't work either, ** until ** I relised in my haste that I installed using the default settings (which is for the current user) and not for all users of the machine.
So installing EwsManagedApi32 for all users on a 64 bit server does the trick (for me)
I tried reinstalling the EWS Managed API for All Users, but that didn't solve it for me. In the end the solution was simple:
Just uninstall BOTH the EWS Managed API and the Microsoft Office Developer Tools for Visual Studio 2012. After that reinstall ONLY the Office Developer Tools. This time the Web Platform Installer will ensure the correct EWS Managed API is also installed.
I also wrote a small blog about this problem:
https://leonzandman.com/2013/02/07/prerequisite-components-error-when-creating-a-visual-studio-2012-sharepoint-2013-app-project/
Answer for the year of 2014:
Install Microsoft Exchange Web Services Managed API 2.1 (the latest version I can find at this time).