Today, as a result of our effort to better align security and protection solutions with the workloads and applications they protect, Microsoft is announcing changes to the roadmaps of some of the security solutions made available under the Forefront brand.
For collaboration protection, SharePoint and Lync Servers will continue to offer the built-in security capabilities that many customers use to protect shared documents. For remote access, DirectAccess and Routing and Remote Access Server (RRAS) VPN in Windows Server 2012 provide secure remote access for Windows and cross-platform clients, as well as cross-premise access through site to site VPN. Forefront Unified Access Gateway (UAG) 2010 also continues to provide secure application publishing and cross-platform SSL VPN remote access for a range of mobile devices. We will continue to provide maintenance and support for the following Forefront solutions through the standard Microsoft support lifecycle (see chart below), but the discontinued Forefront offerings will no longer be available for purchase as of Dec. 1, 2012.
It is important to note that there are no significant changes to the Forefront Identity Manager or Forefront Unified Access Gateway roadmaps. These solutions continue to be actively developed. Forefront UAG 2010 SP2 was released in August 2012 and Forefront Identity Manager 2010 R2 was release in June 2012. If you have any questions about these changes, please contact your Microsoft or partner sales representative.
The Forefront Product Teams
Really terrible and very stupid mistake. I can say Microsoft now acknowledge that they just loose in security battle. Next, they will loose in Messaging and collaboration battle and starting from this stupid mistake.
Microsoft forces me to renew Forefront for 3y (the same length of my volume contract), but now I will not be able to use what I have paid with Exchange 2013 or SharePoint 2013?! Will Microsoft give me my money back?
I guess it is time to get better acquainted with squid.
This should shed some light on the issue hal2020.com/.../goodbye-forefront-it-was-nice-knowing-you
Shame, I finally got the hang of TMG rules, spent at least 100 hours on configuring various TMG servers, 1 week course on ISA 2006 and exams. It has been a much used product and essential part of the network. At least Microsoft could recommend a replacement.
It was great line of firewalls
I was using it from ISA 2000 till TMG, so abset :(
UAG can handle reverse proxy and other publishing. But protecting our network by preventing users from hitting malicious sites, inspecting SSL traffic, etc, that was all TMG, and the main reason we've deployed it.
Can anyone name an alternative product that accomplishes the forward proxy and NIS functions of TMG??
Wow. I was not looking forward to reading this. I have been a very proud user of TMG as far back when it was just called ISA. I often laughed at the poor list of features offered by other vendors and how many MORE options I had with my own firewalls. Now I am forced to look at other firewall solutions like Cisco ASA because of this. What a bummer!
Personally, I think you've made a huge mistake with the discontinuation of TMG. Many, many SMEs relay heavily on the functionality that this fine product provided and you're leaving customers in a major bind by eliminating it. While there may be other options, many people want to remain as fully Microsoft as possible and, as of late, you're making that increasingly difficult.
I realize that the TMG decision is a done deal, but if anyone with any sanity comes back around to rethink it, this is one that should be reversed.
Been with tmg since isa 2000. Always defended it when getting into discussions or arguments with "hardware" firewall admins or management. Now it looks like I have to eat crow. Going to be really embarrassing when it comes up in the next management meeting. Thanks a lot for killing a great product and one of the coolest Microsoft technologies. :(
I am sorry for you, ISA developers. You did a good job there.
Go and make a startup, fund it through the kickstarter and I will be your number one backer.
Almost three weeks have passed since Microsoft dropped this news on this Blog. This news only is bad enough. But this silence since then is even worse, I do not know what to tell my customers.
Please name us an alternative to do forwarding proxy with integrated authentication (just to name one feature)
Many thanks to all of you who has done very great work for writing the ISA/TMG code. It is very sad to hear that your company does not see your effort. But in these days, if some products does not have enough invoice that product will be kick out. And I believe, with TMG, there has been not enough deployments, even those who has used it are more than happy for the product.
But I have to say, this looks very strange. You basically say: "We do not care of TMG customers anymore, and it is much better for us and you to go some other vendor than Microsoft."
Shall we start looking for some other vendors for other products as well, like replace Office with LibreOffice?
Bad decision Microsoft.
ps. Great idea from Adam, could you TMG team build TMG2012 and took our money when Microsoft don't need them.
I need to upgrade our ISA 2006 back-end. What do I do now for inbound publishing reverse proxy and outbound proxy server? I need a solution that can be virtualised, there are any competing products that can do the job?
Please don't do this to us. We're not going to rely on the cloud and datacenters located around the world.
MS might be better at privacy than Google on privacy but given the track record of Office365, and the false reporting of downtime (I've had recent Office365 downtime which has never been recognised as such despite the tickets telling me that such and such an Exchange serve was down for several hours).
I'd rather know it's my own problem than have to put up with Microsoft faking performance. Look at the recent problems with FPE updates - scary!