MM&M UG UK

does anyone know how to 'fix' this?

I deleted the Default OAB, then it got recreated with the same greyed out option. I am in a transition environment 2003 /2007.

Thank you in advance.

Ioana

Hi,

For web distribution to work the OAB needs to be generated on the 2007 server. Is that the case?

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

 

Yes, Nathan, that is the case. If i move the OAB from E2003 to E2007, then the web box is greyed out. So I deleted that and recreated it on E2007 and now i can select the web distrib box.

So i guess this is it: the OAB needs to be recreated on E2007?

Thank you for getting back to me.

Ioana

Strange!

It certainly should work without being recreated.

How did you move the OAB?

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

In E2003 System Manager: View System Folders > OAB Properties > Replication tab > added the name of the E2007 server.

Then,

In E2007 Mgmt Console > Org Config > Mailbox Role > OAB tab > r-click OAB > Move to name of new E2007 server.

If i do the above, I do not get a web distrib box - could it be becs i installed E2007 with the option for pre-Outlook 2007 clients?

I also get an error in Outlook if I try to download the OAB, although i can see it in IIS VS & on the C:\ drive of the E2007 server.

Do i need to install a valid certifcate in order to get this to work? Could OAB not dowload becs the certificate i use is the one E2007 ships with?

Many thanks in advance for your help in de-mistifying these weird issues...

Ioana

Just a quick note to add: i have added the autodiscover A record in the DNS....

Hmmm.

Certainly getting the certs right is important. Internally I believe it should work with the default cert but  I would suggest getting the URLs for Autodiscover and the various vdirs all setup along with the cert with SANs added.

Not really sure why that is not working. Have all the servers got replicas of all the OAB system folders? and is replication working

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

this is the thing... a have some problems with the Public Folders replication too. I have added the new E2007 to the PFs in E2003 System Manager, then I also added it in the E2007 Mgmt Console.

I have also done Move All Replicas from E2003. Then I also ran the E2007 script.

Then I checked the PF Instances on E2003 Sys Mgr, but nothing happens. I should see the size of the PFs in E2003 going down, shouldn't I?

But nothing happens... From Outlook, I can see the PF hierarchy but the folders content is empty...

I have also run Update-PublicFolder command from E2007...

Any ideas?

Ioana

Ouch!

That sounds like you kind of did everything you could think of...... ;)

Not sure what state it will be in now, and must admit Public Folders are not one of my most favorite areas!

Do you have any error messages in event logs?

Maybe worth turning up logging.

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

Hi Nathan,

PF replication is working fine now, slowly but surely. What I had wrongly setup was a smart host on the Default Receive E2007 Connector. As soon as I removed that, and then restarted IIS on E2003, PF replication started to work!

Here is how to get to the settings of the connector, on E2007 Mgmt Console:

Server Config > Hub Transport > Network Tab > Receive mail from remote servers that have these IP addresses. Here i had the IP of a smart host. I replaced that with IP 0.0.0.0 and Mask 255.255.255.255

However, I am now thinking is that right???? Shall I take it that that need to create another connector that will have the IP of the smart host???

No news re OAB, but i will look at that next and post back.

Thanks for your help Nathan. Much appreciated!

Ioana

That's a good find!

Have you still got the default receive connectors?

 

Client servername

Default servername

 

If so then the default one should work fine with the settings you now  have.

 

Just wondering why did you change them? and also are we definitely talking about receive connectors as usually the send connector would have a smart host.....?

 

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

I set the Smart Host on the Default Receive connector just for testing. I thought it was a new security feature.

So it seems these two connectors are for internal communications only and should not be altered...

The IP of the smart host was indeed one outside our network range, hence the block on the receive connector.

ioana  

That would indeed make sense.

I would recommend creating another connector if you want to do this type of lock down for real.

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk