TMG Beta 3 Exchange Edge Subscription
- Hi
Please can someone advise if Exchange Edge Subscription is fully implemented in Beta 3. I am getting an error when trying to export the Edge Subscription files from the TMG console.
Thanks
Douks
Réponses
I found a solution. Simple really - it looks like the install wizard for BETA 3 stopped the exchange and forefront services & never restarted them. I can't remember if I rebooted the vm before trying to configure edge via TMG, but having started all the services the subscription file is created fine. I've subequently rebooted a couple of times & services start OK now.
Douks- Marqué comme réponseDouks lundi 15 juin 2009 14:22
Toutes les réponses
- I have the same problem
- I also have the same problem : "Microsoft Forefront TMG Managed Control Service on server <hostname> is not responding" but it work after a couple of days without doing anything?! Perhaps the installation of the Microsoft Forefront for Exchange Server is for something.
I found a solution. Simple really - it looks like the install wizard for BETA 3 stopped the exchange and forefront services & never restarted them. I can't remember if I rebooted the vm before trying to configure edge via TMG, but having started all the services the subscription file is created fine. I've subequently rebooted a couple of times & services start OK now.
Douks- Marqué comme réponseDouks lundi 15 juin 2009 14:22
- It looks like it is similar the issue reported in TMG beta 3 release notes.
Did you install Exchange Edge and FSE before or after TMG install?
From Release notes
Exchange Edge
After you install Forefront TMG and configure an e-mail policy, if you install the Exchange Server Edge Transport Role or Forefront Security for Exchange (FSE), the ISAManagedCtrl service fails. This does not occur if you install the Edge Transport Role or FSE before installing Forefront TMG. To install the Edge Transport Role or FSE after installing Forefront TMG and configuring an e-mail policy:
1. At a command prompt, type:
net stop isamanagedctrl
2. After the service stops, install the Edge Transport Role and FSE.
3. At the command prompt, type:
net start isamanagedctrl
Bala Natarajan [MSFT]| Sr. Support Escalation Engineer | CSS Security -TMG Beta support team | Email: bala.natarajan@microsoft.com | Office 425.704.4626 Bing it on bing.com - Hi Bala I read the release notes before installation and was aware of the prerequisites being similar to beta 2. My scenario was I already had edge & fse installed on my TMG beta 2 test rig. To install beta 3, I simply removed beta 2 & then installed beta 3 & went through the configure email policy wizard. I guess it looks like a similar issue, but importantly I haven't had to install the edge or fse components again to get it working - just start the services! Thanks Douks
- Hi Thanks for the update. This something i will take as feedback for future upgrade scenarios to include specific instructions on upgrade of other integrated components
Thanks
Bala Natarajan [MSFT]| Sr. Support Escalation Engineer | CSS Security -TMG Beta support team | Email: bala.natarajan@microsoft.com | Office 425.704.4626 Bing it on bing.com The Problem still exists, but all services are up and running. i installed edge bevor installing TMG.
any other idea, what to do?
thanks.- sorry, i found the answer myself... after several hours of work:
do it in the powershell.. it works, but it doesn't work from GUI. - What do you mean, Martin?
to start the service?
I have a similar problem related to "someone" (i can't give the name....) installed FSE with TMG and Edge up and running......
Is there any method to fix this?...
Thanks
Diego Castelli- ModifiéDiego Castelli lundi 20 juillet 2009 08:18eheh
- No, to configure the subscription..... but....
i have now the subscription, anything seems to work... but....
edge replays, that there is no way to relay outside. i didn't find any solution that will work. at moment, our exchange delivers via isa 2006 :-(
