I've installed ms exchange 2010 but without small biz server (we're on win 2008 server), there's no pop3 connector anymore. Anyone know of a good open source alternative?
Seems to be working with MS Exchange 2010 and successfully tested with 2013. I can make no statement about the stability yet. It seems more or less inactive.
http://www.pop2owa.com/
There is but it's disabled by default !!! See: http://technet.microsoft.com/en-us/library/bb124934.aspx
Related
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.
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 have a couple of Excel Add ins. If I move to Office 365, will these add ins be available ? Is there any development support(VSTO) for Office 365 ?
I to have been curious about the answer to this, so went looking online. From the following site, I'd say the answer is no. It looks like developing for Office 365 is more along the lines of SharePoint development.
http://blogs.msdn.com/b/donovanf/archive/2011/06/29/office-365-developer-guidance-and-resources.aspx
I have seen advertisements online for products such as this... http://www.ocxt.com/products that look like they could provide a possible solution for taking a vsto application to the web.
I think things have moved on substantially since this question was asked. Microsoft seem to be fully committed to the Add-in approach with Office 2013 and the equivalent VSTO tooling available in VS2012.
The Office Dev Center home page has Office 2013 and VSTO Add-ins written all over it.
This MSDN Blog Post also clearly shows Add-ins are still part of the strategy.
Until the full capabilities of Desktop MS Office are available in a browser, I can't see this situation changing.
If you mean Office 365 installed on client PC then there is no issue with VSTO Add-ins. Our Chem4Word Add-in is using Office 2010 VSTO and happily works with 2010, 2013, 2016, 2019, O365.
If you mean Office 365 on-line then you have to redesign them using the Office 365 Javascript API
I've just tried out TFS 2010 today, along with Project 2010 and VS 2010. Only Later realized that without Sharepoint, TFS is only configured as Basic. This reduces it's functionality as oppose to what I've seen during VS2010 product launch. Sadly I can't find any alternative but to get a trial copy of Sharepoint to see if it serve my purpose. Well, apparently Sharepoint only comes with x64 edition. I'm not formatting any machine to x64 just to give this a try. So, after some reading up, I found that Project Server is actually based on Sharepoint. Now I wonder is whether TFS can be configure to connect to Project Server?
If it's possible, would the setting be much different that Sharepoint's?
And what am I missing from this setup as oppose to Sharepoint's?
Based on Sharepoint != Sharepoint. I think that Project Server is just a subset of Sharepoint functionality. Also, basing Project on Sharepoint allows for some really tight integration into your portal. To answer your question, I don't think you still will get your fully featured TFS without Sharepoint Proper.
FYI - Sharepoint 2007 (or 3.0 or whatever it is) is not x64 only, but will run on x86. TFS 2010 will go full feature on 2007
Sharepoint 2007 Trial
To answer what you are missing:
Reports
Project Portal
TFS Web Access
That's about it. You still get 90% of the features with your current deployment without SharePoint. Tommy is right about MOSS 2007, it comes in 32-bit and will give you all features. Project Server runs on top of SharePoint as a shared service provider. Traditionally MS releases a power toy to integrate TFS with Project Server. They said they would go over this at TechEd, which just happened about a week ago.
Also, I suspect the integration with Project Server 2010 will be better, but then you will have to run SharePoint 2010 :(
In my opinion, TFS has enough to run most projects by itself and you can use the client version of MS Project for critical path anaylsis, etc.
Use Windows Sharepoint Services for Windows 2003 & Windows 2008:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb400747.aspx
For Windows Server 2008 sp2 and Windows Server R2, use SharePoint Foundation 2010:
http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en
Both are free.
I'm not formatting any machine to x64
just to give this a try.
Why not use VMWare Server, Hyper-V, Virtual Box or some other virtualization software to run the pre-made demo/trial/lab VHD's - no formatting, no installation, no setup, more hair.
Link
I haven't touched sharepoint in years. If I want to setup a development environment to get up to speed, what options do I have? I don't have an MSDN license, is there anyway I can get up and running for free? (for development only)
You need a Windows 2003 Server (or 2008 Server, but I have no experience with that), no way around that. You can then of course use Visual C# 2005 Express and the SHarepoint Services 3.0 if that's your target.
If you want to do development on Sharepoint 2007, you have to buy a Sharepoint 2007 license, which has a pretty hefty fee attached to it.
As a SQL, SQL 2005 Express works fine for development.
There is a good Article how to set up Sharepoint on a Single Server:
http://blogs.msdn.com/martinkearn/archive/2007/03/28/how-to-install-sharepoint-server-2007-on-a-single-machine.aspx
You CAN use a Trial Version of Windows 2003 and Sharepoint 2007 though if it's only needed for a limited time (i believe the Trials run 180 days).
There is no way you can have a MOSS 2007/WSS 3.0 development for free but a Microsoft Action Pact is so cheap to get. :)
There is a nice blog to read to get the requirements and the steps to get a full MOSS 2007 image up and running here : How to Create a MOSS 2007 VPC Image: The Whole 9 Yards.
The action pack is fantastic value, you can use the Windows Server from that, as well as SharePoint Enterprise / Standard.
If you're just (re-)starting out in SharePoint development, there's a lot of value in just using WSS 3.0 and not (yet) using MOSS 2007. The basic vocabulary is going to be exactly the same at the development level, and you can accomplish a huge amount without ever feeling like you need MOSS to learn.
You could always download the Sharepoint trial VM here and then install the express version of visual studio.
You can download an Office SharePoint Server VHD from Microsoft. This allows you to run a virtual Windows Server & SharePoint Server on your personal machine using Virtual Server.
I recently went through this process and wrote a blog article describing how to setup a virtual Office SharePoint Server.