Forwarding email sent to a group

  • From: "Amy Kohler" <akohler@xxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 17 Feb 2006 14:14:26 -0500

Hello all,

I have a request from our HR Manager to have a copy of emails sent to
management groups also sent to her.

She doesn't want her name on the members list though. Does any one know
of a workaround?

 

  _____  

From: Bruce J. Rose [mailto:brose@xxxxxxxxxxx] 
Sent: Friday, February 17, 2006 11:32 AM
To: [ExchangeList]
Subject: [exchangelist] Info and ActiveSync problem

 

http://www.MSExchange.org/

I have just upgrade a 2000 domain with 2 2000 domain controllers,
Exchange is installed one of the domain controllers.  I moved fsmo roles
to the exchange to upgrade it to windows 2003 it has Exchange2003
installed.  Preformed the adprep/forest and domain then let system sync
for a day, oh yea fully patched before upgrade.  Upgraded to windows
2003 went smooth, then patched 2003, then install sp2 for exchange.  All
this went good which was good being it 3:00am.  I got one problem
thought I cannot get activesynce to work, I have a user trying to
activsync his treo via work pc but he gets the exchange server does not
have permission to synchronize with your current settings.  We are not
using ssl or forms based authentication.  The Access Tab of ActiveSync
properties under Exchange Virtual server are grayed out. Anyone seen
this?   Any help is appreciated.

 

Thanks Bruce

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
akohler@xxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx 

Other related posts: