Skip to search.

Breaking News Visit Yahoo! News for the latest.

×Close this window

exchange2007

The Yahoo! Groups Product Blog

Check it out!

Group Information

? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

Messages

Advanced
Messages Help
Messages 902 - 931 of 2005   Oldest  |  < Older  |  Newer >  |  Newest
Messages: Show Message Summaries Sort by Date ^  
#902 From: "kjk3lly" <kjk@...>
Date: Fri Aug 1, 2008 1:26 pm
Subject: Re: Exchange 2003 Front-End with Exchange 2007 backend
kjk3lly
Send Email Send Email
 
My Apologies I meant to say direct push (Active Synch). Sorry about that.
I did however find some decent info on my deli ma.
http://technet.microsoft.com/en-us/library/bb885041(EXCHG.80).aspx


--- In exchange2007@yahoogroups.com, "Michael B. Smith" <michael@...>
wrote:
>
> Before I go into anything else: OMA is not a feature of Exchange
2007. If
> you need that - stop right now! :-P
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCITP:SA,EMA/MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of kjk3lly
> Sent: Thursday, July 31, 2008 10:24 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Exchange 2003 Front-End with Exchange 2007
backend
>
>
>
> Does anyone know if it is possible to run a Exchange 2003 Front-End
> server with a Exchange 2007 Server as a back-end "type" server with
> HUB, Mailbox, CAS roles installed.
>
> My deli ma is this.....
> I now have a Exchange 2003 server that is both used for OWA and
> Mailboxes. (Single Server for Org)
>
> I want to Migrate to Exchange 2007 but in order to do so I need to
> make sure users can still use OWA, OMA, etc.
> Once mailboxes are moved to the Exchange 2007 server I'm under the
> impression that the server that is now used for OWA (Without being a
> front-end server) will not proxy to the Exchange 2007 server once
> mailboxes are moved to it. My thought is I could install a new
> Exchange 2003 Front-End server and the server would be able to proxy
> back to both the Exchange 2007 and Exchange 2003 server. Just while
> the migration takes place. Is this possible? Not googling much info on
> this one.....
>
> Suggestions?
>

#903 From: Devin Ganger <DevinG@...>
Date: Fri Aug 1, 2008 5:21 pm
Subject: RE: Re: Exchange 2003 Front-End with Exchange 2007 backend
devinganger
Send Email Send Email
 
In order for a single front-end/CAS box to serve up both Exchange 2003 and
Exchange 2007 mailboxes, it *must be* on a separate box from the Mailbox role.
Once you put the CAS and Mailbox roles on the same physical server, that CAS
instance *cannot* access legacy Exchange mailbox servers.

You cannot use a down-level Exchange front-end/CAS server to talk to more recent
Exchange mailbox servers. The CAS/front-end server must be running at least the
most current version of Exchange that you have in your organization. That's why,
when you deploy service packs, you should almost always deploy them on front-end
servers and CAS servers first.

If you absolutely have to do this, I recommend building the new Exchange 2007
server with MBX, CAS, and HT roles, then standing up a temporary CAS-only
server. Carefully document and test your configuration on this CAS box so that
you can duplicate the configuration on the combined Exchange 2007 server.
Repoint your firewall rules to this temporary CAS box once you've tested it and
everything is working. Then, you can migrate your mailboxes over to the Exchange
2007 box. Once they're gone and the 2003 box has been decommissioned, you can
reconfigure the CAS role on the mailbox server, repoint the firewall rules, and
decommission the temporary CAS server.

--
Devin L. Ganger, Exchange MVP      Email: deving@...
3Sharp                             Phone: 425.882.1032
14700 NE 95th Suite 210             Cell: 425.239.2575
Redmond, WA  98052                   Fax: 425.558.5710
(e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/

> -----Original Message-----
> From: exchange2007@yahoogroups.com
> [mailto:exchange2007@yahoogroups.com] On Behalf Of kjk3lly
> Sent: Friday, August 01, 2008 6:26 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Re: Exchange 2003 Front-End with Exchange
> 2007 backend
>
> My Apologies I meant to say direct push (Active Synch). Sorry about
> that.
> I did however find some decent info on my deli ma.
> http://technet.microsoft.com/en-us/library/bb885041(EXCHG.80).aspx
>
>
> --- In exchange2007@yahoogroups.com, "Michael B. Smith"
> <michael@...>
> wrote:
> >
> > Before I go into anything else: OMA is not a feature of Exchange
> 2007. If
> > you need that - stop right now! :-P
> >
> >
> >
> > Regards,
> >
> >
> >
> > Michael B. Smith
> >
> > MCITP:SA,EMA/MCSE/Exchange MVP
> >
> > http://TheEssentialExchange.com
> >
> >
> >
> > From: exchange2007@yahoogroups.com
> [mailto:exchange2007@yahoogroups.com] On
> > Behalf Of kjk3lly
> > Sent: Thursday, July 31, 2008 10:24 AM
> > To: exchange2007@yahoogroups.com
> > Subject: [exchange2007] Exchange 2003 Front-End with Exchange
> 2007
> backend
> >
> >
> >
> > Does anyone know if it is possible to run a Exchange 2003 Front-
> End
> > server with a Exchange 2007 Server as a back-end "type" server
> with
> > HUB, Mailbox, CAS roles installed.
> >
> > My deli ma is this.....
> > I now have a Exchange 2003 server that is both used for OWA and
> > Mailboxes. (Single Server for Org)
> >
> > I want to Migrate to Exchange 2007 but in order to do so I need
> to
> > make sure users can still use OWA, OMA, etc.
> > Once mailboxes are moved to the Exchange 2007 server I'm under
> the
> > impression that the server that is now used for OWA (Without
> being a
> > front-end server) will not proxy to the Exchange 2007 server once
> > mailboxes are moved to it. My thought is I could install a new
> > Exchange 2003 Front-End server and the server would be able to
> proxy
> > back to both the Exchange 2007 and Exchange 2003 server. Just
> while
> > the migration takes place. Is this possible? Not googling much
> info on
> > this one.....
> >
> > Suggestions?
> >
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

#904 From: "kjk3lly" <kjk@...>
Date: Sat Aug 2, 2008 6:46 pm
Subject: Re: Exchange 2003 Front-End with Exchange 2007 backend
kjk3lly
Send Email Send Email
 
Nice Solution. I think my only option would be for the Temporary CAS
server to be a Virtual Server to prevent buying more hardware. I don't
think the bosses would go for that.

Thanks! Sounds like that should work nicely.


--- In exchange2007@yahoogroups.com, Devin Ganger <DevinG@...> wrote:
>
> In order for a single front-end/CAS box to serve up both Exchange
2003 and Exchange 2007 mailboxes, it *must be* on a separate box from
the Mailbox role. Once you put the CAS and Mailbox roles on the same
physical server, that CAS instance *cannot* access legacy Exchange
mailbox servers.
>
> You cannot use a down-level Exchange front-end/CAS server to talk to
more recent Exchange mailbox servers. The CAS/front-end server must be
running at least the most current version of Exchange that you have in
your organization. That's why, when you deploy service packs, you
should almost always deploy them on front-end servers and CAS servers
first.
>
> If you absolutely have to do this, I recommend building the new
Exchange 2007 server with MBX, CAS, and HT roles, then standing up a
temporary CAS-only server. Carefully document and test your
configuration on this CAS box so that you can duplicate the
configuration on the combined Exchange 2007 server. Repoint your
firewall rules to this temporary CAS box once you've tested it and
everything is working. Then, you can migrate your mailboxes over to
the Exchange 2007 box. Once they're gone and the 2003 box has been
decommissioned, you can reconfigure the CAS role on the mailbox
server, repoint the firewall rules, and decommission the temporary CAS
server.
>
> --
> Devin L. Ganger, Exchange MVP      Email: deving@...
> 3Sharp                             Phone: 425.882.1032
> 14700 NE 95th Suite 210             Cell: 425.239.2575
> Redmond, WA  98052                   Fax: 425.558.5710
> (e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/
>
> > -----Original Message-----
> > From: exchange2007@yahoogroups.com
> > [mailto:exchange2007@yahoogroups.com] On Behalf Of kjk3lly
> > Sent: Friday, August 01, 2008 6:26 AM
> > To: exchange2007@yahoogroups.com
> > Subject: [exchange2007] Re: Exchange 2003 Front-End with Exchange
> > 2007 backend
> >
> > My Apologies I meant to say direct push (Active Synch). Sorry about
> > that.
> > I did however find some decent info on my deli ma.
> > http://technet.microsoft.com/en-us/library/bb885041(EXCHG.80).aspx
> >
> >
> > --- In exchange2007@yahoogroups.com, "Michael B. Smith"
> > <michael@>
> > wrote:
> > >
> > > Before I go into anything else: OMA is not a feature of Exchange
> > 2007. If
> > > you need that - stop right now! :-P
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Michael B. Smith
> > >
> > > MCITP:SA,EMA/MCSE/Exchange MVP
> > >
> > > http://TheEssentialExchange.com
> > >
> > >
> > >
> > > From: exchange2007@yahoogroups.com
> > [mailto:exchange2007@yahoogroups.com] On
> > > Behalf Of kjk3lly
> > > Sent: Thursday, July 31, 2008 10:24 AM
> > > To: exchange2007@yahoogroups.com
> > > Subject: [exchange2007] Exchange 2003 Front-End with Exchange
> > 2007
> > backend
> > >
> > >
> > >
> > > Does anyone know if it is possible to run a Exchange 2003 Front-
> > End
> > > server with a Exchange 2007 Server as a back-end "type" server
> > with
> > > HUB, Mailbox, CAS roles installed.
> > >
> > > My deli ma is this.....
> > > I now have a Exchange 2003 server that is both used for OWA and
> > > Mailboxes. (Single Server for Org)
> > >
> > > I want to Migrate to Exchange 2007 but in order to do so I need
> > to
> > > make sure users can still use OWA, OMA, etc.
> > > Once mailboxes are moved to the Exchange 2007 server I'm under
> > the
> > > impression that the server that is now used for OWA (Without
> > being a
> > > front-end server) will not proxy to the Exchange 2007 server once
> > > mailboxes are moved to it. My thought is I could install a new
> > > Exchange 2003 Front-End server and the server would be able to
> > proxy
> > > back to both the Exchange 2007 and Exchange 2003 server. Just
> > while
> > > the migration takes place. Is this possible? Not googling much
> > info on
> > > this one.....
> > >
> > > Suggestions?
> > >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

#905 From: Devin Ganger <DevinG@...>
Date: Sat Aug 2, 2008 9:04 pm
Subject: RE: Re: Exchange 2003 Front-End with Exchange 2007 backend
devinganger
Send Email Send Email
 
This is a great time to use a virtual server, honestly, especially if you don't
have too many user mailboxes to migrate and it'll be happening quickly.

--
Devin L. Ganger, Exchange MVP      Email: deving@...
3Sharp                             Phone: 425.882.1032
14700 NE 95th Suite 210             Cell: 425.239.2575
Redmond, WA  98052                   Fax: 425.558.5710
(e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/


> -----Original Message-----
> From: exchange2007@yahoogroups.com
> [mailto:exchange2007@yahoogroups.com] On Behalf Of kjk3lly
> Sent: Saturday, August 02, 2008 11:46 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Re: Exchange 2003 Front-End with Exchange
> 2007 backend
>
> Nice Solution. I think my only option would be for the Temporary
> CAS
> server to be a Virtual Server to prevent buying more hardware. I
> don't
> think the bosses would go for that.
>
> Thanks! Sounds like that should work nicely.
>
>
> --- In exchange2007@yahoogroups.com, Devin Ganger <DevinG@...>
> wrote:
> >
> > In order for a single front-end/CAS box to serve up both Exchange
> 2003 and Exchange 2007 mailboxes, it *must be* on a separate box
> from
> the Mailbox role. Once you put the CAS and Mailbox roles on the
> same
> physical server, that CAS instance *cannot* access legacy Exchange
> mailbox servers.
> >
> > You cannot use a down-level Exchange front-end/CAS server to talk
> to
> more recent Exchange mailbox servers. The CAS/front-end server must
> be
> running at least the most current version of Exchange that you have
> in
> your organization. That's why, when you deploy service packs, you
> should almost always deploy them on front-end servers and CAS
> servers
> first.
> >
> > If you absolutely have to do this, I recommend building the new
> Exchange 2007 server with MBX, CAS, and HT roles, then standing up
> a
> temporary CAS-only server. Carefully document and test your
> configuration on this CAS box so that you can duplicate the
> configuration on the combined Exchange 2007 server. Repoint your
> firewall rules to this temporary CAS box once you've tested it and
> everything is working. Then, you can migrate your mailboxes over to
> the Exchange 2007 box. Once they're gone and the 2003 box has been
> decommissioned, you can reconfigure the CAS role on the mailbox
> server, repoint the firewall rules, and decommission the temporary
> CAS
> server.
> >
> > --
> > Devin L. Ganger, Exchange MVP      Email: deving@...
> > 3Sharp                             Phone: 425.882.1032
> > 14700 NE 95th Suite 210             Cell: 425.239.2575
> > Redmond, WA  98052                   Fax: 425.558.5710
> > (e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/
> >
> > > -----Original Message-----
> > > From: exchange2007@yahoogroups.com
> > > [mailto:exchange2007@yahoogroups.com] On Behalf Of kjk3lly
> > > Sent: Friday, August 01, 2008 6:26 AM
> > > To: exchange2007@yahoogroups.com
> > > Subject: [exchange2007] Re: Exchange 2003 Front-End with
> Exchange
> > > 2007 backend
> > >
> > > My Apologies I meant to say direct push (Active Synch). Sorry
> about
> > > that.
> > > I did however find some decent info on my deli ma.
> > > http://technet.microsoft.com/en-
> us/library/bb885041(EXCHG.80).aspx
> > >
> > >
> > > --- In exchange2007@yahoogroups.com, "Michael B. Smith"
> > > <michael@>
> > > wrote:
> > > >
> > > > Before I go into anything else: OMA is not a feature of
> Exchange
> > > 2007. If
> > > > you need that - stop right now! :-P
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > Michael B. Smith
> > > >
> > > > MCITP:SA,EMA/MCSE/Exchange MVP
> > > >
> > > > http://TheEssentialExchange.com
> > > >
> > > >
> > > >
> > > > From: exchange2007@yahoogroups.com
> > > [mailto:exchange2007@yahoogroups.com] On
> > > > Behalf Of kjk3lly
> > > > Sent: Thursday, July 31, 2008 10:24 AM
> > > > To: exchange2007@yahoogroups.com
> > > > Subject: [exchange2007] Exchange 2003 Front-End with Exchange
> > > 2007
> > > backend
> > > >
> > > >
> > > >
> > > > Does anyone know if it is possible to run a Exchange 2003
> Front-
> > > End
> > > > server with a Exchange 2007 Server as a back-end "type"
> server
> > > with
> > > > HUB, Mailbox, CAS roles installed.
> > > >
> > > > My deli ma is this.....
> > > > I now have a Exchange 2003 server that is both used for OWA
> and
> > > > Mailboxes. (Single Server for Org)
> > > >
> > > > I want to Migrate to Exchange 2007 but in order to do so I
> need
> > > to
> > > > make sure users can still use OWA, OMA, etc.
> > > > Once mailboxes are moved to the Exchange 2007 server I'm
> under
> > > the
> > > > impression that the server that is now used for OWA (Without
> > > being a
> > > > front-end server) will not proxy to the Exchange 2007 server
> once
> > > > mailboxes are moved to it. My thought is I could install a
> new
> > > > Exchange 2003 Front-End server and the server would be able
> to
> > > proxy
> > > > back to both the Exchange 2007 and Exchange 2003 server. Just
> > > while
> > > > the migration takes place. Is this possible? Not googling
> much
> > > info on
> > > > this one.....
> > > >
> > > > Suggestions?
> > > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

#906 From: Jason Sherry <Jason.Sherry@...>
Date: Sun Aug 3, 2008 2:04 pm
Subject: RE: Archiving in Outlook Web Access (OWA)
izken69
Send Email Send Email
 

If you want real archiving, not the move to PST archiving that Outlook does, that does not use PSTs and helps to eliminate PSTs you need to look at a 3rd party solution.  The 3rd party solution don’t require client side changes or end-user to do anything for archiving to work.

 

From a technology and performance perspective Mimosa’s NeaPoint (http://www.mimosasystems.com) solution.  It’s may not be the cheapest but you get what you pay for J

 

 

Jason Sherry - http://jasonsherry.org

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of [randi]
Sent: Thursday, July 03, 2008 8:16 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Archiving in Outlook Web Access (OWA)

 

Dear All,

I want to ask, how is usually the best way to give Archiving for user
who never set up Outlook on his computer, but they always Open their
email from outlook web access.

And I found that they can not do Archiving their inbox item from OWA.
Is there anyway I can do to help them archiving their inbox item so
they are able to send and receive email from their mailbox without
being notice that their mailbox are full and they can't do send/
receive mail.

Thank you.

Best Rgds,

Randi Darmawan


#907 From: Devin Ganger <DevinG@...>
Date: Sun Aug 3, 2008 11:24 pm
Subject: RE: Archiving in Outlook Web Access (OWA)
devinganger
Send Email Send Email
 

That didn't take long! ;)

 

--

Devin L. Ganger, Exchange MVP      Email: deving@...

3Sharp                             Phone: 425.882.1032

14700 NE 95th Suite 210             Cell: 425.239.2575

Redmond, WA  98052                   Fax: 425.558.5710

(e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Jason Sherry
Sent: Sunday, August 03, 2008 7:04 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] Archiving in Outlook Web Access (OWA)

 

If you want real archiving, not the move to PST archiving that Outlook does, that does not use PSTs and helps to eliminate PSTs you need to look at a 3rd party solution.  The 3rd party solution don’t require client side changes or end-user to do anything for archiving to work.

 

From a technology and performance perspective Mimosa’s NeaPoint (http://www.mimosasystems.com) solution.  It’s may not be the cheapest but you get what you pay for J

 

 

Jason Sherry - http://jasonsherry.org

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of [randi]
Sent: Thursday, July 03, 2008 8:16 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Archiving in Outlook Web Access (OWA)

 

Dear All,

I want to ask, how is usually the best way to give Archiving for user
who never set up Outlook on his computer, but they always Open their
email from outlook web access.

And I found that they can not do Archiving their inbox item from OWA.
Is there anyway I can do to help them archiving their inbox item so
they are able to send and receive email from their mailbox without
being notice that their mailbox are full and they can't do send/
receive mail.

Thank you.

Best Rgds,

Randi Darmawan

 


#908 From: "Wayne Small" <wayne@...>
Date: Thu Jul 31, 2008 10:33 pm
Subject: RE: ActiveSync with E2007 and mulitple servers.
waynesmall2000
Send Email Send Email
 

Hey guys – I sent this over a week back now but it only looks like it made it to the list this week after I rebooted my server – very strange.  Any thoughts on the issue below?

 

Regards,
Wayne Small  [SBS-MVP]
MCT, MCSE+I, MCSE 2000

SBSfaq.com Pty Ltd

Interested in what I have to say - check out more on my blog? http://blog.sbsfaq.com
Co-author of Advanced Windows Small Business Server 2003 Best Practices

For all the answers on Microsoft's Small Business Server- check out www.sbsfaq.com

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Wayne Small
Sent: Wednesday, 23 July 2008 4:11 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] ActiveSync with E2007 and mulitple servers.

 

I’ve deployed E2007 to one of my client sites. We have headoffice with ISA 2006 in front of an Exchange 2007 CA server and another CA/MBX server within the same site. We have multiple CA/MBX servers spread across other sites behind this configuration all connected via a WAN.  OWA works fine for users across all sites. ActiveSync however only works for user with mailboxes stored on the headoffice site.  I can’t find any real reference to modifications that I might need to do to the remote sites to make them work and their configuration looks to be the same as the CA/MBX server in the headoffice site.  What I see is on the mobile device, it prompts for the users password each time I try to sync, if I enter it, it requests it again and again.  Any clues guys on what / where I need to look please?

 

Regards,
Wayne Small  [SBS-MVP]
MCT, MCSE+I, MCSE 2000

SBSfaq.com Pty Ltd


Interested in what I have to say - check out more on my blog? http://blog.sbsfaq.com
Co-author of Advanced Windows Small Business Server 2003 Best Practices

For all the answers on Microsoft's Small Business Server- check out www.sbsfaq.com

 


#909 From: "martywestra" <marty@...>
Date: Fri Aug 1, 2008 2:30 am
Subject: Re: Accept mail without FQDN
martywestra
Send Email Send Email
 
I totally understand that without the domain name it is not a valid
email address and if this was an internet facing server, I probably
wouldn't even think about doing it.  I just figured if I could do it
in Exchange 2000, maybe I could do it in 2007.

Interesting that the reason I could do it in 2000 was because of a
design flaw.

Thanks,
Marty Westra
Electronic Systems, Inc.

--- In exchange2007@yahoogroups.com, "Michael B. Smith" <michael@...>
wrote:
>
> I actually got into a HUGE argument on this topic on an RFC SMTP
mailing
> list in the early Exchange 2003 timeframe..
>
>
>
> Anyway, the behavior of Exchange 2000 and 2003 was a design flaw.
Based on
> the default recipient policy, they would take an address without a
host
> portion and append the default SMTP address and then do that lookup
(that
> was the impact - the actuality was quite a bit more complicated
than that).
>
>
>
> That behavior was broken for non local delivery and that particular
area was
> one of the areas rewritten for Exchange 2007 and the problem was
corrected.
>
>
>
> As Ed said - fix your email addresses.
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCITP:SA,EMA/MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of martywestra
> Sent: Thursday, July 24, 2008 10:40 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Accept mail without FQDN
>
>
>
> I recently migrated from Exchange 2000 to Exchange 2007. Exchange
> 2000's SMTP server would allow email addressed to just the person's
> login name without the FQDN. We have alot of automated emails using
> Blat that I would rather not change that are emailing without the
> FQDN. This Exchange server is not directly attached to the Internet.
>
> Here's an example of my Exchange 2000 SMTP session:
> 220 x1.electronicsi.com Microsoft ESMTP MAIL Service, Version:
> 5.0.2195.6713 ready at Thu, 24 Jul 2008 09:03:30 -0500
> helo bob
> 250 x1.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 250 2.1.0 automatedemail@...
> <mailto:automatedemail%40electronicsi.com....Sender>  OK
> rcpt to: marty
> 250 2.1.5 marty@... <mailto:marty%40electronicsi.com>
>
> Here's an example of my Exchange 2007 SMTP session:
> 220 x2.electronicsi.com Microsoft ESMTP MAIL Service ready at Thu,
24
> Jul 2008 09:26:07 -0500
> helo bob
> 250 x2.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 501 5.1.7 Invalid address
>
> Any ideas how I can get this same functionality on Exchange 2007?
>
> Thanks,
> Marty Westra
> Electronic Systems, Inc.
>

#910 From: "martywestra" <marty@...>
Date: Fri Aug 1, 2008 2:49 am
Subject: Performance Issues on the client
martywestra
Send Email Send Email
 
I recently migrated from Exchange 2000 to 2007.  I have everything
migrated except my Public Folders (I may have some other questions
about that too) but today's issue is that I have some performance
issues on the client side when opening and sending attachments and
sometimes switching between a plain text message and HTML message in
the preview pane.  Near as I can tell, it appears that the
Win2k/Office XP workstations have no performance issues.  Windows
XP/Office XP are the workstations with issues.

We have 1 Windows 2003 DC that has Exchange 2007 and Blackberry
Professional Server on it.  It's got all the FSMO roles and is the
only Global Catalog.  We also have 3 Windows 2000 DCs.  One of those
DCs has Exchange 2000.  On the client side, we currently have a
mixture of Windows 2000 and Windows XP.  Everyone has Office XP.

I installed a trial version of Quest Software's Spotlight on
Exchange.  Everything stays in the green except memory is in the
orange, which I understand that store.exe will use whatever memory it
can find for caching.  After a few minutes of running, I start to get
a bunch of clients that have an RPC latency > 2 seconds.

Does anyone have any suggestions on how to get my performance back up
to an acceptable level?

Let me know if you need any additional information.

Thanks,
Marty Westra
Electronic Systems, Inc.

#911 From: Jamie Young <jyoung@...>
Date: Thu Jul 31, 2008 12:06 pm
Subject: RE: Public Folder Replication from Exchange 2003 to 2007 not working
no_rem0rz
Send Email Send Email
 

Wow – I just figured this posting got lost…

Thanks for the feedback, but after re-creating the routing connectors on the 2003 server, then recreating through the powershell, still nothing was going. It wasn’t until I woke up and remembered the SMTP connector on the 2003 server was sending mail through a gateway server (which wasn’t allowed to send to the 2007 by default) did I realize where I goofed up. Removed the setting in the connector (after I had already manually moved the public folder content) and then replication occurred the way it should… and of course left me with 2 sets of public folders. Guess 2 is better than none.

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Mike Lagase
Sent: Thursday, July 31, 2008 6:18 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] Public Folder Replication from Exchange 2003 to 2007 not working

 

Have you also created a routing group connector between 2003 and 2007 to allow these messages to get routed between the servers? If no, see http://technet.microsoft.com/en-us/library/aa997292(EXCHG.80).aspx on how to implement this.

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Ed Crowley
Sent: Thursday, July 31, 2008 12:17 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] Public Folder Replication from Exchange 2003 to 2007 not working

 

You've added a replica on the Exchange 2007 server for each folder, right?  How long have you waited?  Replication can take a while.  Do you see any public folder replication messages in the SMTP queue?  Has the hierarchy replicated (as evidenced by the get-publicfolder cmdlet)?

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of James Young
Sent: Wednesday, July 23, 2008 12:06 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Public Folder Replication from Exchange 2003 to 2007 not working

I am not seeing the public folders appear on the 2007 server. I have
gone into each folder and set it to replicate and changed the time
parameters - I can move mailboxes and I can create new public folders
on the 2007 server... but the ones on the 2003 server just do not want
to play nice. Any ideas?


#912 From: "Martin Blackstone" <mblackstone@...>
Date: Sun Aug 3, 2008 11:33 pm
Subject: RE: Archiving in Outlook Web Access (OWA)
maritnblacks...
Send Email Send Email
 

That’s what she said.

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Devin Ganger
Sent: Sunday, August 03, 2008 4:24 PM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] Archiving in Outlook Web Access (OWA)

 

That didn't take long! ;)

 

--

Devin L. Ganger, Exchange MVP      Email: deving@...

3Sharp                             Phone: 425.882.1032

14700 NE 95th Suite 210             Cell: 425.239.2575

Redmond, WA  98052                   Fax: 425.558.5710

(e)Mail Insecurity: http://blogs.3sharp.com/blog/deving/

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Jason Sherry
Sent: Sunday, August 03, 2008 7:04 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] Archiving in Outlook Web Access (OWA)

 

If you want real archiving, not the move to PST archiving that Outlook does, that does not use PSTs and helps to eliminate PSTs you need to look at a 3rd party solution.  The 3rd party solution don’t require client side changes or end-user to do anything for archiving to work.

 

From a technology and performance perspective Mimosa’s NeaPoint (http://www.mimosasystems.com) solution.  It’s may not be the cheapest but you get what you pay for J

 

 

Jason Sherry - http://jasonsherry.org

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of [randi]
Sent: Thursday, July 03, 2008 8:16 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Archiving in Outlook Web Access (OWA)

 

Dear All,

I want to ask, how is usually the best way to give Archiving for user
who never set up Outlook on his computer, but they always Open their
email from outlook web access.

And I found that they can not do Archiving their inbox item from OWA.
Is there anyway I can do to help them archiving their inbox item so
they are able to send and receive email from their mailbox without
being notice that their mailbox are full and they can't do send/
receive mail.

Thank you.

Best Rgds,

Randi Darmawan

 


#913 From: "Michael B. Smith" <michael@...>
Date: Mon Aug 4, 2008 8:41 pm
Subject: RE: Re: Accept mail without FQDN
swngdnz
Send Email Send Email
 

Yeah, well, pretty much all of transport, which includes SMTP, was rewritten for exchange 2007.

 

In fact, almost everything but the backend (the store) is now managed code in 2007.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of martywestra
Sent: Thursday, July 31, 2008 10:30 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Re: Accept mail without FQDN

 

I totally understand that without the domain name it is not a valid
email address and if this was an internet facing server, I probably
wouldn't even think about doing it. I just figured if I could do it
in Exchange 2000, maybe I could do it in 2007.

Interesting that the reason I could do it in 2000 was because of a
design flaw.

Thanks,
Marty Westra
Electronic Systems, Inc.

--- In exchange2007@yahoogroups.com, "Michael B. Smith" <michael@...>
wrote:
>
> I actually got into a HUGE argument on this topic on an RFC SMTP
mailing
> list in the early Exchange 2003 timeframe..
>
>
>
> Anyway, the behavior of Exchange 2000 and 2003 was a design flaw.
Based on
> the default recipient policy, they would take an address without a
host
> portion and append the default SMTP address and then do that lookup
(that
> was the impact - the actuality was quite a bit more complicated
than that).
>
>
>
> That behavior was broken for non local delivery and that particular
area was
> one of the areas rewritten for Exchange 2007 and the problem was
corrected.
>
>
>
> As Ed said - fix your email addresses.
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCITP:SA,EMA/MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of martywestra
> Sent: Thursday, July 24, 2008 10:40 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Accept mail without FQDN
>
>
>
> I recently migrated from Exchange 2000 to Exchange 2007. Exchange
> 2000's SMTP server would allow email addressed to just the person's
> login name without the FQDN. We have alot of automated emails using
> Blat that I would rather not change that are emailing without the
> FQDN. This Exchange server is not directly attached to the Internet.
>
> Here's an example of my Exchange 2000 SMTP session:
> 220 x1.electronicsi.com Microsoft ESMTP MAIL Service, Version:
> 5.0.2195.6713 ready at Thu, 24 Jul 2008 09:03:30 -0500
> helo bob
> 250 x1.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 250 2.1.0 automatedemail@...
> <mailto:automatedemail%40electronicsi.com....Sender> OK
> rcpt to: marty
> 250 2.1.5 marty@... <mailto:marty%40electronicsi.com>
>
> Here's an example of my Exchange 2007 SMTP session:
> 220 x2.electronicsi.com Microsoft ESMTP MAIL Service ready at Thu,
24
> Jul 2008 09:26:07 -0500
> helo bob
> 250 x2.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 501 5.1.7 Invalid address
>
> Any ideas how I can get this same functionality on Exchange 2007?
>
> Thanks,
> Marty Westra
> Electronic Systems, Inc.
>


#914 From: "Michael B. Smith" <michael@...>
Date: Mon Aug 4, 2008 9:08 pm
Subject: RE: Performance Issues on the client
swngdnz
Send Email Send Email
 

So….does anything besides Spotlight say that your performance isn’t acceptable? Or did you install Spotlight because you were having performance issues and you were trying to identify them?

 

Have you looked at more granular information – like processor utilization, memory usage (page faults most interestingly), and disk queuing on the Exchange server?

 

I’m a traditionalist and generally believe in starting at the bottom and working up, instead of the other ‘way round.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of martywestra
Sent: Thursday, July 31, 2008 10:50 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Performance Issues on the client

 

I recently migrated from Exchange 2000 to 2007. I have everything
migrated except my Public Folders (I may have some other questions
about that too) but today's issue is that I have some performance
issues on the client side when opening and sending attachments and
sometimes switching between a plain text message and HTML message in
the preview pane. Near as I can tell, it appears that the
Win2k/Office XP workstations have no performance issues. Windows
XP/Office XP are the workstations with issues.

We have 1 Windows 2003 DC that has Exchange 2007 and Blackberry
Professional Server on it. It's got all the FSMO roles and is the
only Global Catalog. We also have 3 Windows 2000 DCs. One of those
DCs has Exchange 2000. On the client side, we currently have a
mixture of Windows 2000 and Windows XP. Everyone has Office XP.

I installed a trial version of Quest Software's Spotlight on
Exchange. Everything stays in the green except memory is in the
orange, which I understand that store.exe will use whatever memory it
can find for caching. After a few minutes of running, I start to get
a bunch of clients that have an RPC latency > 2 seconds.

Does anyone have any suggestions on how to get my performance back up
to an acceptable level?

Let me know if you need any additional information.

Thanks,
Marty Westra
Electronic Systems, Inc.


#915 From: Chris Scharff <chris_scharff@...>
Date: Mon Aug 4, 2008 10:26 pm
Subject: RE: Re: Accept mail without FQDN
m1_scharff
Send Email Send Email
 

Well 5 or 10 years plenty of MTAs accepted mail without a fully qualified rcpt to:. Spammers were big fans of it as well. Most MTAs now ship either with this functionality removed or disabled out of the box.

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of martywestra
Sent: Thursday, July 31, 2008 9:30 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Re: Accept mail without FQDN

 

I totally understand that without the domain name it is not a valid
email address and if this was an internet facing server, I probably
wouldn't even think about doing it. I just figured if I could do it
in Exchange 2000, maybe I could do it in 2007.

Interesting that the reason I could do it in 2000 was because of a
design flaw.

Thanks,
Marty Westra
Electronic Systems, Inc.

--- In exchange2007@yahoogroups.com, "Michael B. Smith" <michael@...>
wrote:
>
> I actually got into a HUGE argument on this topic on an RFC SMTP
mailing
> list in the early Exchange 2003 timeframe..
>
>
>
> Anyway, the behavior of Exchange 2000 and 2003 was a design flaw.
Based on
> the default recipient policy, they would take an address without a
host
> portion and append the default SMTP address and then do that lookup
(that
> was the impact - the actuality was quite a bit more complicated
than that).
>
>
>
> That behavior was broken for non local delivery and that particular
area was
> one of the areas rewritten for Exchange 2007 and the problem was
corrected.
>
>
>
> As Ed said - fix your email addresses.
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCITP:SA,EMA/MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of martywestra
> Sent: Thursday, July 24, 2008 10:40 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Accept mail without FQDN
>
>
>
> I recently migrated from Exchange 2000 to Exchange 2007. Exchange
> 2000's SMTP server would allow email addressed to just the person's
> login name without the FQDN. We have alot of automated emails using
> Blat that I would rather not change that are emailing without the
> FQDN. This Exchange server is not directly attached to the Internet.
>
> Here's an example of my Exchange 2000 SMTP session:
> 220 x1.electronicsi.com Microsoft ESMTP MAIL Service, Version:
> 5.0.2195.6713 ready at Thu, 24 Jul 2008 09:03:30 -0500
> helo bob
> 250 x1.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 250 2.1.0 automatedemail@...
> <mailto:automatedemail%40electronicsi.com....Sender> OK
> rcpt to: marty
> 250 2.1.5 marty@... <mailto:marty%40electronicsi.com>
>
> Here's an example of my Exchange 2007 SMTP session:
> 220 x2.electronicsi.com Microsoft ESMTP MAIL Service ready at Thu,
24
> Jul 2008 09:26:07 -0500
> helo bob
> 250 x2.electronicsi.com Hello [xxx.xxx.xxx.221]
> mail from: automatedemail
> 501 5.1.7 Invalid address
>
> Any ideas how I can get this same functionality on Exchange 2007?
>
> Thanks,
> Marty Westra
> Electronic Systems, Inc.
>


#916 From: "martywestra" <marty@...>
Date: Tue Aug 5, 2008 2:04 am
Subject: Re: Performance Issues on the client
martywestra
Send Email Send Email
 
Michael,

Thanks for the reply.  Funny you should mention to start at the
bottom and work your way up.

The one thing that Spotlight does not show is network utilization.  I
do my backup across the wire and noticed that they were taking
FOREVER to complete.

Logged into the switch and found that there were more CRC errors than
actual good packets transmitted.  Moved the server to another port on
the switch and everybody's happy!

I successfully decommissioned my Exchange 2000 server as well as
another 2000 DC/DHCP/DNS server this weekend.  Little bit of fallout
this morning, but glad this project is over.

Thanks to everyone for their help,
Marty Westra
Electronic Systems, Inc.
Sioux Falls, SD

--- In exchange2007@yahoogroups.com, "Michael B. Smith" <michael@...>
wrote:
>
> So..does anything besides Spotlight say that your performance isn't
> acceptable? Or did you install Spotlight because you were having
performance
> issues and you were trying to identify them?
>
>
>
> Have you looked at more granular information - like processor
utilization,
> memory usage (page faults most interestingly), and disk queuing on
the
> Exchange server?
>
>
>
> I'm a traditionalist and generally believe in starting at the
bottom and
> working up, instead of the other 'way round.
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCITP:SA,EMA/MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of martywestra
> Sent: Thursday, July 31, 2008 10:50 PM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Performance Issues on the client
>
>
>
> I recently migrated from Exchange 2000 to 2007. I have everything
> migrated except my Public Folders (I may have some other questions
> about that too) but today's issue is that I have some performance
> issues on the client side when opening and sending attachments and
> sometimes switching between a plain text message and HTML message
in
> the preview pane. Near as I can tell, it appears that the
> Win2k/Office XP workstations have no performance issues. Windows
> XP/Office XP are the workstations with issues.
>
> We have 1 Windows 2003 DC that has Exchange 2007 and Blackberry
> Professional Server on it. It's got all the FSMO roles and is the
> only Global Catalog. We also have 3 Windows 2000 DCs. One of those
> DCs has Exchange 2000. On the client side, we currently have a
> mixture of Windows 2000 and Windows XP. Everyone has Office XP.
>
> I installed a trial version of Quest Software's Spotlight on
> Exchange. Everything stays in the green except memory is in the
> orange, which I understand that store.exe will use whatever memory
it
> can find for caching. After a few minutes of running, I start to
get
> a bunch of clients that have an RPC latency > 2 seconds.
>
> Does anyone have any suggestions on how to get my performance back
up
> to an acceptable level?
>
> Let me know if you need any additional information.
>
> Thanks,
> Marty Westra
> Electronic Systems, Inc.
>

#917 From: "howard_post2000" <howard_post2000@...>
Date: Thu Aug 7, 2008 12:34 am
Subject: OAB error in Outlook 2007 with new Exchange 2007 install
howard_post2000
Send Email Send Email
 
We've completed a new exchange 2007 install and configuration and are
getting an OAB error on the client in Outlook 2007. Outlook locks up
and dispalys "Downloading offline address book". The OAB does not
download.  After time outhe emails do come in however.
Has anyone run into this? Any suggestions on how to fix this would be
greatly appreciated

#918 From: Jim McBee <jmcbee@...>
Date: Sun Aug 17, 2008 8:23 pm
Subject: RE: OAB error in Outlook 2007 with new Exchange 2007 install
jimmcbee_2000
Send Email Send Email
 
This is a pretty generic message.  What version of Outlook?  Is the OAB set up for Outlook 2003 clients?  Is AutoDiscover working for Outlook 2007 clients?  
 
 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of howard_post2000
Sent: Wednesday, August 06, 2008 2:35 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] OAB error in Outlook 2007 with new Exchange 2007 install

We've completed a new exchange 2007 install and configuration and are
getting an OAB error on the client in Outlook 2007. Outlook locks up
and dispalys "Downloading offline address book". The OAB does not
download. After time outhe emails do come in however.
Has anyone run into this? Any suggestions on how to fix this would be
greatly appreciated


#919 From: "martywestra" <marty@...>
Date: Sat Sep 13, 2008 3:56 am
Subject: Full Access to Mailboxes
martywestra
Send Email Send Email
 
All,

I've got a perplexing issue.  I recently migrated from Exchange 2000 to
Exchange 2007.

I've granted Full Access permissions to all mailboxes to a subset of
our IT department by using the following commands:

Get-Mailbox | Add-MailboxPermission -User MIS -AccessRights FullAccess
and
Get-MailboxDatabase | Add-ADPermission -User MIS -AccessRights
GenericAll -ExtendedRights Receive-As

There are still some mailboxes that our group can not access.  If I use
the EMC and look at the Full Access Permissions, it shows <Domain>\Self
and <Domain>\<our IT group>.  I've tried removing the IT group and re-
adding it but that does not help either.  I have other mailboxes that
have the EXACT same security settings and they work just fine for me,
but not another member of the group.

If I create a new user and add <Domain>\<our IT group> to the Full
Access permissions, everything works fine.

Has anyone run into this issue or have any suggestions on how to fix it?

Thanks,
Marty

#920 From: "plevine23" <plevine23@...>
Date: Sun Sep 14, 2008 2:47 am
Subject: public folder issue
plevine23
Send Email Send Email
 
we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil

#921 From: "Ed Crowley" <curspice@...>
Date: Sun Sep 14, 2008 6:52 am
Subject: RE: public folder issue
edcrowley
Send Email Send Email
 
This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil


#922 From: Jim McBee <jmcbee@...>
Date: Sun Sep 14, 2008 7:55 am
Subject: RE: public folder issue
jimmcbee_2000
Send Email Send Email
 
Ed makes a very good point.  One thing you should verify, though is that e-mail is making its way between the E2K3 and E2K7 servers.  The public folder hierarchy and the contents replicate via e-mail.
 
Jim


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Ed Crowley
Sent: Saturday, September 13, 2008 8:52 PM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil


#923 From: phil levine <plevine23@...>
Date: Mon Sep 15, 2008 1:21 pm
Subject: RE: public folder issue
plevine23
Send Email Send Email
 
i created a mailbox store on the PF server just to verify mailflow and it works in both directions. i checked the routing group connectors and they do allow public folder referrals.

--- On Sun, 9/14/08, Ed Crowley <curspice@...> wrote:
From: Ed Crowley <curspice@...>
Subject: RE: [exchange2007] public folder issue
To: exchange2007@yahoogroups.com
Date: Sunday, September 14, 2008, 2:52 AM

This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.
Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."
 


From: exchange2007@ yahoogroups. com [mailto:exchange200 7@yahoogroups. com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@ yahoogroups. com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil



#924 From: "Charles Bradley Giles" <exchange@...>
Date: Thu Sep 4, 2008 2:23 pm
Subject: Active Sync with 2008 server/2007 Exchange
brad51560
Send Email Send Email
 
This firm has had a contractor install 2008 server with exchange 2007
into a 2k3 server network. It was running but too many problems to
mention. They moved the 2007 to a 2003 server and worked out most of
the bugs. Then installed some recent patches 2 days ago and now no
Active Sync devices work. Even a new user on the 2008 server or the
2003 server or a new device changes anything. I believe this is yet
another new undocumented "Feature" Microsoft does not have a patch for
yet and is deeply embedded in the AD on the 2008 server.



    Any recent issues that may be similar or you think are related
would be appreciated. I will either suggest decommissioning the 2008
server first after disconnecting it from the network for 3 to 4 days
and / or hacks on the registry and Global, Enterprise AD changes.



    R we having fun yet? Yes we love this stuff…



Thanks,

Charles B. Giles II

#925 From: "Ed Crowley" <curspice@...>
Date: Mon Sep 15, 2008 10:54 pm
Subject: RE: public folder issue
edcrowley
Send Email Send Email
 
Referrals don't affect replication, just whether Outlook will cross routing groups to look for content.
 
Are there any public folder replication messages in the queues?
 
Did you add the new server as a replica on all folders, including the system folders for OAB, free/busy and organizational forms (if you use that one)?

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of phil levine
Sent: Monday, September 15, 2008 6:21 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

i created a mailbox store on the PF server just to verify mailflow and it works in both directions. i checked the routing group connectors and they do allow public folder referrals.

--- On Sun, 9/14/08, Ed Crowley <curspice@mvps.org> wrote:
From: Ed Crowley <curspice@mvps.org>
Subject: RE: [exchange2007] public folder issue
To: exchange2007@yahoogroups.com
Date: Sunday, September 14, 2008, 2:52 AM

This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.
Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."
 


From: exchange2007@ yahoogroups. com [mailto:exchange200 7@yahoogroups. com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@ yahoogroups. com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil



#926 From: "Mike Lagase" <mike@...>
Date: Tue Sep 16, 2008 9:49 am
Subject: RE: public folder issue
lagase
Send Email Send Email
 

What does get-publicfolder –recurse show you on the 2007 side? If it shows nothing, then replication is busted as you should at least see the hierarchy at this point. If you haven’t already, I would turn on message tracking on the 2003 side and see if any PF replication messages are being generated. If there are no folders listed on the 2007 side, check to see if they “are” making it to the 2007 server and if they are being delivered locally to the 2007 PF store using message tracking. I would also check to see if any messages are being queued like Ed mentioned.

 

Also check out these references for all your PF replication troubleshooting needs.

http://msexchangeteam.com/archive/2006/01/17/417611.aspx

http://msexchangeteam.com/archive/2006/01/19/417737.aspx

http://msexchangeteam.com/archive/2006/01/23/417974.aspx

http://msexchangeteam.com/archive/2008/01/10/447843.aspx

 

 

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Ed Crowley
Sent: Monday, September 15, 2008 6:55 PM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

 

Referrals don't affect replication, just whether Outlook will cross routing groups to look for content.

 

Are there any public folder replication messages in the queues?

 

Did you add the new server as a replica on all folders, including the system folders for OAB, free/busy and organizational forms (if you use that one)?

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of phil levine
Sent: Monday, September 15, 2008 6:21 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

i created a mailbox store on the PF server just to verify mailflow and it works in both directions. i checked the routing group connectors and they do allow public folder referrals.

--- On Sun, 9/14/08, Ed Crowley <curspice@...> wrote:

From: Ed Crowley <curspice@...>
Subject: RE: [exchange2007] public folder issue
To: exchange2007@yahoogroups.com
Date: Sunday, September 14, 2008, 2:52 AM

This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 

 


From: exchange2007@ yahoogroups. com [mailto:exchange200 7@yahoogroups. com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@ yahoogroups. com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil

 


#927 From: "appi_0" <appi_0@...>
Date: Tue Sep 16, 2008 3:47 pm
Subject: Mail notification when an e-mail arrives to public folder
appi_0
Send Email Send Email
 
Hi Guys,
i got a strange problem here, i have setup a mail notification on a
public folder to a group of internal users.all it does is  when a new
mail arrives into public folder an e-mail will be sent to a group of
users letting them know that an e-mail is arrived into the public
folder.i have achived this one by setting a rule using a folder
assistant--->reply with [TEMPLATE], where i mentioned the group of
users who needs an alert when an e-mail arrives into this public
folder. everything worked upuntil last month, just before i have for an
holiday and now the problem is if anybody sends an e-mail to this
public folder, offcourse it is sending an alert to the group of users i
mentioned in the rule PLUS it is sending the same alert message to the
actual sender of that mail, which is annoying.can anybody sugest what
might be happening here.i ahve deleted the rules and recreated them
back but still the same. i have even restarted the server, but no
vail.any idea?

many thanks
REDDY

#928 From: "Ed Crowley" <curspice@...>
Date: Tue Sep 16, 2008 4:12 pm
Subject: RE: public folder issue
edcrowley
Send Email Send Email
 
Good point, and I would have gotten to this after getting confirmation of replicas being set and of no held up replication messages. 
 
You first need to see the hierarchy, and then the content.  With no hierarchy, there'll be no content.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Mike Lagase
Sent: Tuesday, September 16, 2008 2:50 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

What does get-publicfolder –recurse show you on the 2007 side? If it shows nothing, then replication is busted as you should at least see the hierarchy at this point. If you haven’t already, I would turn on message tracking on the 2003 side and see if any PF replication messages are being generated. If there are no folders listed on the 2007 side, check to see if they “are” making it to the 2007 server and if they are being delivered locally to the 2007 PF store using message tracking. I would also check to see if any messages are being queued like Ed mentioned.

Also check out these references for all your PF replication troubleshooting needs.

http://msexchangeteam.com/archive/2006/01/17/417611.aspx

http://msexchangeteam.com/archive/2006/01/19/417737.aspx

http://msexchangeteam.com/archive/2006/01/23/417974.aspx

http://msexchangeteam.com/archive/2008/01/10/447843.aspx

From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of Ed Crowley
Sent: Monday, September 15, 2008 6:55 PM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

Referrals don't affect replication, just whether Outlook will cross routing groups to look for content.

Are there any public folder replication messages in the queues?

Did you add the new server as a replica on all folders, including the system folders for OAB, free/busy and organizational forms (if you use that one)?

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of phil levine
Sent: Monday, September 15, 2008 6:21 AM
To: exchange2007@yahoogroups.com
Subject: RE: [exchange2007] public folder issue

i created a mailbox store on the PF server just to verify mailflow and it works in both directions. i checked the routing group connectors and they do allow public folder referrals.

--- On Sun, 9/14/08, Ed Crowley <curspice@mvps.org> wrote:

From: Ed Crowley <curspice@mvps.org>
Subject: RE: [exchange2007] public folder issue
To: exchange2007@yahoogroups.com
Date: Sunday, September 14, 2008, 2:52 AM

This isn't an easy thing to diagnose.  The first thing you should do is verify that you have mailflow between the servers.  Create a mailbox store, if necessary, and a test mailbox and verify tha tyou can send mail between the two servers.  You can also use the Test-Mailflow cmdlet.  Also, run the Best Practices Analyzer.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."


From: exchange2007@ yahoogroups. com [mailto:exchange200 7@yahoogroups. com] On Behalf Of plevine23
Sent: Saturday, September 13, 2008 7:48 PM
To: exchange2007@ yahoogroups. com
Subject: [exchange2007] public folder issue

we recently upgraded from 2003 to 2007 and added a seperate server for
public folders. my problem is that none of the public folders are
replicating from 2003 to 2007. i've tried pfdavadmin and adding a
replica as well as adding a replica from both the ESM in 2003 and the
public folder piece of EMC. Anyone have any ideas or have seen this
before? what should i look for? thanks.

phil


#929 From: "Ed Crowley" <curspice@...>
Date: Tue Sep 16, 2008 4:23 pm
Subject: RE: Mail notification when an e-mail arrives to public folder
edcrowley
Send Email Send Email
 
That's the way a reply works.  Have you tried a Forward rule instead?  I'd really like to see a rule that generates a completely new message based on a template, but that's not in the box.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of appi_0
Sent: Tuesday, September 16, 2008 8:47 AM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Mail notification when an e-mail arrives to public folder

Hi Guys,
i got a strange problem here, i have setup a mail notification on a
public folder to a group of internal users.all it does is when a new
mail arrives into public folder an e-mail will be sent to a group of
users letting them know that an e-mail is arrived into the public
folder.i have achived this one by setting a rule using a folder
assistant--->reply with [TEMPLATE], where i mentioned the group of
users who needs an alert when an e-mail arrives into this public
folder. everything worked upuntil last month, just before i have for an
holiday and now the problem is if anybody sends an e-mail to this
public folder, offcourse it is sending an alert to the group of users i
mentioned in the rule PLUS it is sending the same alert message to the
actual sender of that mail, which is annoying.can anybody sugest what
might be happening here.i ahve deleted the rules and recreated them
back but still the same. i have even restarted the server, but no
vail.any idea?

many thanks
REDDY


#930 From: "appi_0" <appi_0@...>
Date: Tue Sep 16, 2008 4:51 pm
Subject: Re: Mail notification when an e-mail arrives to public folder
appi_0
Send Email Send Email
 
forward works fine, but as u know it only forwards the message
ratherthan sending only an alert message.when i initially setup
a 'reply with' it didn't send a reply to the sender i think, if i
remember correctly.any idea?


--- In exchange2007@yahoogroups.com, "Ed Crowley" <curspice@...>
wrote:
>
> That's the way a reply works.  Have you tried a Forward rule
instead?  I'd
> really like to see a rule that generates a completely new message
based on a
> template, but that's not in the box.
>
> Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
> "There are seldom good technological solutions to behavioral
problems."
>
>
>
>   _____
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of appi_0
> Sent: Tuesday, September 16, 2008 8:47 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Mail notification when an e-mail arrives to
public
> folder
>
>
>
> Hi Guys,
> i got a strange problem here, i have setup a mail notification on a
> public folder to a group of internal users.all it does is when a
new
> mail arrives into public folder an e-mail will be sent to a group
of
> users letting them know that an e-mail is arrived into the public
> folder.i have achived this one by setting a rule using a folder
> assistant--->reply with [TEMPLATE], where i mentioned the group of
> users who needs an alert when an e-mail arrives into this public
> folder. everything worked upuntil last month, just before i have
for an
> holiday and now the problem is if anybody sends an e-mail to this
> public folder, offcourse it is sending an alert to the group of
users i
> mentioned in the rule PLUS it is sending the same alert message to
the
> actual sender of that mail, which is annoying.can anybody sugest
what
> might be happening here.i ahve deleted the rules and recreated them
> back but still the same. i have even restarted the server, but no
> vail.any idea?
>
> many thanks
> REDDY
>

#931 From: "Ed Crowley" <curspice@...>
Date: Tue Sep 16, 2008 11:25 pm
Subject: RE: Re: Mail notification when an e-mail arrives to public folder
edcrowley
Send Email Send Email
 
I don't mean to be rude, but I think your memory is inaccurate.

Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
"There are seldom good technological solutions to behavioral problems."

 


From: exchange2007@yahoogroups.com [mailto:exchange2007@yahoogroups.com] On Behalf Of appi_0
Sent: Tuesday, September 16, 2008 9:52 AM
To: exchange2007@yahoogroups.com
Subject: [exchange2007] Re: Mail notification when an e-mail arrives to public folder

forward works fine, but as u know it only forwards the message
ratherthan sending only an alert message.when i initially setup
a 'reply with' it didn't send a reply to the sender i think, if i
remember correctly.any idea?

--- In exchange2007@yahoogroups.com, "Ed Crowley" <curspice@...>
wrote:
>
> That's the way a reply works. Have you tried a Forward rule
instead? I'd
> really like to see a rule that generates a completely new message
based on a
> template, but that's not in the box.
>
> Ed Crowley MCITP MCSE+I MCSE+M MCTS MVP
> "There are seldom good technological solutions to behavioral
problems."
>
>
>
> _____
>
> From: exchange2007@yahoogroups.com
[mailto:exchange2007@yahoogroups.com] On
> Behalf Of appi_0
> Sent: Tuesday, September 16, 2008 8:47 AM
> To: exchange2007@yahoogroups.com
> Subject: [exchange2007] Mail notification when an e-mail arrives to
public
> folder
>
>
>
> Hi Guys,
> i got a strange problem here, i have setup a mail notification on a
> public folder to a group of internal users.all it does is when a
new
> mail arrives into public folder an e-mail will be sent to a group
of
> users letting them know that an e-mail is arrived into the public
> folder.i have achived this one by setting a rule using a folder
> assistant--->reply with [TEMPLATE], where i mentioned the group of
> users who needs an alert when an e-mail arrives into this public
> folder. everything worked upuntil last month, just before i have
for an
> holiday and now the problem is if anybody sends an e-mail to this
> public folder, offcourse it is sending an alert to the group of
users i
> mentioned in the rule PLUS it is sending the same alert message to
the
> actual sender of that mail, which is annoying.can anybody sugest
what
> might be happening here.i ahve deleted the rules and recreated them
> back but still the same. i have even restarted the server, but no
> vail.any idea?
>
> many thanks
> REDDY
>


Messages 902 - 931 of 2005   Oldest  |  < Older  |  Newer >  |  Newest
Add to My Yahoo!      XML What's This?

Copyright © 2010 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines NEW - Help