When you run this command, aren't you just forcing it to run right away so you
don't have to wait until it runs when scheduled? We do this all the time with
Xch2k7.
That's the way I always understood it. Unless 2010 is different...
Educate me as necessary.
: )
Regards,
Don Guyer
Catholic
Theoretically, you should never HAVE to run the cmdlet. Exchange is supposed to
be smart enough to do this for you.
That is why the cmdlet is gone in Exchange 2013.
Sent from my Windows Phone
From: Guyer, Don
Sent: 2/5/2013 3:54 PM
To: MS-Exchange Admin Issues
Ahhh, thank you as usual, MBS!
Regards,
Don Guyer
Catholic Health East - Information Technology
Enterprise Directory Messaging Services
3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073
email: dgu...@che.orgmailto:dgu...@che.org
Office: 610.550.3595 | Cell: 610.955.6528 | Fax:
I read this article along with the other requirements and this creates the
on the client. The KB 2632409 is to allow this to be created on the
Exchange server. I really do not want to go an modify individual client
workstations/profiles when the should work at the server level.
Thanks for the
So you are actually trying to do two things at once?
[1] Move your mailbox servers to virtual,
[2] Move your mailbox server storage to new storage?
From: Candee [mailto:can...@gmail.com]
Sent: Tuesday, February 5, 2013 2:11 PM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 DAG move to new
Then I think you are doing it the hard way.
Move the mailbox databases, DISMOUNT (or stop MSExchangeIS) on the passive
server, mount both the new storage and the old storage at the same time, copy
from old to new, remove the old storage, remap the new storage to the proper
drive letters (or
Oh, for this to work you CANNOT change the folder structure whatsoever. And
stop the MSFTE service too.
For example
Robocopy D:\ G:\ /S /E /COPYALL
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Tuesday, February 5, 2013 2:32 PM
To: MS-Exchange Admin Issues
Awesome - thank you!
On Tue, Feb 5, 2013 at 2:39 PM, Michael B. Smith mich...@smithcons.comwrote:
Oh, for this to work you CANNOT change the folder structure whatsoever.
And stop the MSFTE service too.
** **
For example
** **
Robocopy D:\ G:\ /S /E /COPYALL
Michael,
is this documented somewhere?
I can't seem to find it (my Google-Fu is weak today).
I will have to be able to convince the team.
Thanks again!
Candee
On Tue, Feb 5, 2013 at 2:39 PM, Michael B. Smith mich...@smithcons.comwrote:
Oh, for this to work you CANNOT change the folder
Test it. Create a new, very small DAG. Create a mailbox. Perform the move
as outlined. See if the test DAG/mailbox are still happy, happy. If so,
then team will be convinced, no?
On Tue, Feb 5, 2013 at 4:10 PM, Candee can...@gmail.com wrote:
Michael,
is this documented somewhere?
I can't
hmmm...
Maybe.
=)
On Tue, Feb 5, 2013 at 4:23 PM, Doug Hampshire dhampsh...@gmail.com wrote:
Test it. Create a new, very small DAG. Create a mailbox. Perform the move
as outlined. See if the test DAG/mailbox are still happy, happy. If so,
then team will be convinced, no?
On Tue, Feb 5,
More than once, all I can say is apple's implementation of activesync is pure
sh!t.
Several ways to handle this
- block them all:)
- Use logparser to deduce which actual version and block it
- Use logparser to see who's device, if not specific to a version, as mb
problems can cause this
12 matches
Mail list logo
