can i create a mailbox remotely(not at the exchange server)? by make use of
powershell?

thanks.

tony

Hey all,
Hope someone can assist with this one.
History: C volume ran out of space on our server. Imaged C and D volumes to
externally connected hard drive. Resized partitions on primary array (RAID5)
and imaged them back. Forgot to disconnect the "Image" drive before booting
and OS booted to it. During that process, renamed old C and D partitions on
RAID5 array to F and G. Couldn't log in as it was unable to find correct
pathame to local database (this is a DC and single 2k3 Exchange server by
the way).

Intsalled parallel copy of 2003, loaded hive from original OS and renamed
reg keys per Microsoft's knoledgebase articles when drive letters get
changed. Fixed issue, booted up normally, and could log in. Now we can't log
into OWA. Getting prompt to authenticate, but returns HTTP/1.1 503 Service
Unavailable.

Followed numerous MS recommdations for resetting virtual directories,
rebuidling metabase, restored folders on C partition from backup (except
Windows directory), followed directions for checking values in database
using ADSIEdit and still correct it.

Hello,

I would like to know how does Exchange 2007 handles the attachmets ? We have
some users that send emails with attachments to the whole company as part of
their job. Do Exchange save only one copy and keep track of recipients by
pointers or every recipient gets a copy ??

Thank you in advance for your help.

Edmundo.

Exchange Help:
--------------------------------------------------------------------------------------------------
For servers that have both the Hub Transport server role and the Mailbox
server role installed, the only way to remove the server name from the
Received: headers of the outgoing message is to use the Remove-ADPermission
cmdlet to remove the Ms-Exch-Send-Headers-Routing permission from the
security principals that use the connector. This action will remove all the
Received: headers from the message as the message leaves the Hub Transport
server. We recommend that you don't remove the Received: headers for
internal messages, because the Received: headers are used for maximum hop
count calculations
---------------------------------------------------------------------------...

Again me and again I am an old problem
It looks like last time (the past 2 times) is not rated seriously whole
situation,
And so, from my previous posts
(microsoft.public.exchange.admin, EdgeTransport.exe took 98%% CPU time, Sent
5/15/2008)
(microsoft.public.exchange.admin, Exchange Server message size limits, Sent
5/19/2008)

One can conclude that the problem was in that the user was MaxSendSize:
unlimited and MaxReceiveSize: unlimited

What has been taken into account and all users rigidly exhibited both
setting 10Mb

And so all the same thing happen again!
User sent ~700Mb and HUB Transports die, as described in previous two posts.
But now user has MaxSendSize: 10Mb and MaxReceiveSize: 10Mb

What is the problem this time?
It seems that it is Exchange BUG.