Exchange /hosting fiasco : is someone actively using on-premise Exchange 2010 SP1 with WSP ?

Question

Hello,

after Exchange /hosting-mode fiasco (one thinks such things cannot happen with a company so big as Microsoft is and yet...) and no news about WSP support for Exchange 2010 SP2 yet, I'd like to know if anyone is actively using WSP to manage Exchange 2010 SP1 on-premise.

Sticky topics stating that on-premise Exchange won't be supported with WSP suddenly all disappeared with no warning, no explanations, nothing at all.

So I wonder if WSP works with Exchange 2010 SP1 on-premise.

Thank you for your help.

Answer 1

I am. Works Great.

---

Omar Armenteros Virtuworks

Answer 2

I am. Works Great.

---

Omar Armenteros Virtuworks

Thank you. Any special suggestion ? Can I simply follow documentation to implement ?

Thank you again for your help.

Answer 3

Hi All

Im looking for some one to help me with setting up up WSP for Hosted Exchange :-)  I have installed WSP and the Server components .. Just need to configure the settings etc so i can go into production mode .. please contact me at [e-mail] ... :-)

 

Cheers

Andy

Answer 4

we are starting in the hosting business this month, and i am running with exchange sp1 for about 15 days, no problems so far, we have a few customers testing our services and so far it's good

i have only some minor problems, but that's mainly because i don't know the platform so good. my problem at the moment is making WSP automatically create the OWA (webmail) and the ECP (exchange control panel) to all customers/clients

i managed to make the DNS to create/work automatically, but i think the problem is mapping the IIS virtual directories.

any thoughts would be apreciated :-)

Answer 5

Luis - sounds like your using the /HOSTING Switch. If you are, start all over. You cannot change the mode of your installation to ON-PREMISE which is what you need to do. Microsoft has discontinued the HOSTING Switch.

---

Omar Armenteros Virtuworks

Answer 6

Hi, what is strange is from this article:

Microsoft is working closely with these vendors:

• Parallels Automation Microsoft Exchange Service Module
• Ensim Unify Service Provider Edition
• Cortex control panel from Citrix for delivering hosted Exchange
• Extend ASP for hosting Exchange

Since WSP is a "MS" product they should also work on WSP you could think.

Answer 7

So which is the most cost effect and good solution for Hosted Exchange managing the multi tenant , resellers and end clients .

Answer 8

To me efficient and on time support matters, plus time to market approch of new feactures and enhancement of the industry. WSP is free but it lacks mentioned components as per my survey. so i will suggest a vendor / solution partner that grow as per the growth of industry and help you in the issues you and your client faces right on time and accuratly.

Answer 9

Hello,

after Exchange /hosting-mode fiasco (one thinks such things cannot happen with a company so big as Microsoft is and yet...) and no news about WSP support for Exchange 2010 SP2 yet, I'd like to know if anyone is actively using WSP to manage Exchange 2010 SP1 on-premise.

Sticky topics stating that on-premise Exchange won't be supported with WSP suddenly all disappeared with no warning, no explanations, nothing at all.

So I wonder if WSP works with Exchange 2010 SP1 on-premise.

Thank you for your help.

It is quite clear that /hosting mode going to be no more supported and WSP recommended to be used with /hosting mode. WSP had implemented Exchange segregation based on Microsoft's guidance that was never recommended by Microsoft and hence its never going to be entertained by Microsoft even in paid support for WSP or under Exchange support channel. In short, Microsoft has fallen back completely to support Exchange 2010 segregation which is implemented in WSP and the only support that would have been provided by Microsoft for Exchange 2010 SP1 in case of /hosting mode which is discontinued too. So, the only solution for all those using /hosting mode is to switch to on-premise mode.

Answer 10

Abid, I agree. That's the only sane thing to do.

However, I'm worried because Microsoft confirmed that SP2 will change things again to better support multi-tenancy in on-premise version. So we will surely need another major upgrade and WSP will need to be changed to support that. Given its current status, I'm not that confident about such upgrade. We'll see.

As topic starter, I'd like to confirm that we had to deactivate our /hosting installation and reverted back to on-premise Exchange 2010 SP1, which works quite fine in WSP, except for alleged incompatibilities between WSP codebase (based on .NET4.0) and Exchange 2010 SP1 support up to v3.5SP1. That required us to implement a proxy installation which is explained on CodePlex. Sort of a hack, though, but it seems to work.

I wanted to confirm that, so anyone interested could know.

Answer 11

I have installed SP2 now in my production environment with no changes to WSP and everything is functioning without an issue. We will be working on getting support for the new addressbook segregation next. I can confirm that following the same directions as you need to in SP1 will work in SP2 as well, seems whatever changes were made in SP2 do not affect any portion of the API WSP uses. We have placed this configuration in production

---

Omar Armenteros Virtuworks

Answer 12

I have posted a fork of the source code project with changes required to enable addressbook policy support in SP2 in an on-premise installation of Exchange. you can find it here.

http://websitepanel.codeplex.com/SourceControl/network/Forks/Virtuworks/ExchangeSP2research

It needs to be compiled and ran as framework 3.5 as described here.

http://websitepanel.codeplex.com/wikipage?title=How%20To%20Run%20Hosted%20Solution%20Services%20with%20WebsitePanel%20v1.2.0

This code does not check for Exchange version, this still needs to be added so placing this code in a non-sp2 on-premise environment will fail.

For existing organizations you will need to manually create address book policys named "orgname Address Policy" and apply them to all existing users which is a pretty simple task using EMC i was able to do about 30 organizations in about 1 hour of work. It can be scripted though.

This code only adds the functionality to create, delete and apply address book policies to new users from the point of it's deployment.

---

Omar Armenteros Virtuworks

Answer 13

I have installed SP2 now in my production environment with no changes to WSP and everything is functioning without an issue. We will be working on getting support for the new addressbook segregation next. I can confirm that following the same directions as you need to in SP1 will work in SP2 as well, seems whatever changes were made in SP2 do not affect any portion of the API WSP uses. We have placed this configuration in production

---

Omar Armenteros Virtuworks

Hello Omar,

are you using WSP with Exchange 2010 SP2 in a multitenant environment?

 

I'm interested to this.....