Exchange 2007 command shell "move-mailbox" parameters

I am using Exchange 2007 command shell for the first time because I need to circumvent a "baditemlimit" issue with moving a few mailboxes from the GUI.  Command shell rocks when it comes to granular Exchange needs; I just have two questions:

1. What is the metric used for <RetryInterval> and <RetryTimeout>? (I'm assuming seconds)
2. Is there a parameter I can use for setting a delay for the move? (i.e: I want to move it, but not until later tonight when the user is out of the mailbox)

I have been looking through Technet and other forums with no luck .  Heres the most useful URL I've found (which is basically 'get-help -full')
http://technet.microsoft.com/en-us/library/aa997599.aspx

Here's the code I'm attempting assuming seconds for timeout metric and allowing for up to 1000 bad items to skip:

Move-Mailbox -Identity 'user@company.com' -TargetDatabase 'server\storage_group\database' [-BadItemLimit 1000] [-DomainController 'domain_controller'] [-GlobalCatalog 'gc_server'] [-RetryTimeout 28800] [-RetryInterval 30]  

Now, Im just missing a parameter for delaying it until evening hours so I can have the move occur while I'm at my son's t-ball game. :)

Some help?
LVL 2
somoteitbeAsked:
Who is Participating?
 
-alvin-Connect With a Mentor Commented:
i don't think there's an option via command line to schedule it.  i would script it and run it via scheduled tasks.  have fun at the t-ball game.
0
 
somoteitbeAuthor Commented:
Okay, thanks! that's good to know.  How about question 1 then?  Was I right about the "minutes"?
0
 
-alvin-Connect With a Mentor Commented:
not entirely sure, but from what i can google the RetryTimeout and the RetryInterval both use Microsoft.Exchange.Data.EnhancedTimeSpan which equates to dd.hh:mm:ss.  try searching for EnhancedTimeSpan.  good luck.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
somoteitbeAuthor Commented:
I'm on it. Thanks alvin.
0
 
somoteitbeAuthor Commented:
Good call on the scripting and scheduled task.  This will work nicely.  As far as the Retrytimeout and RetryInterval parameters, I went with the defaults and left these options out.  Thanks for the guidance.
0
 
somoteitbeAuthor Commented:
Thanks alvin; the scripting idea will work nicely.  The RetryTimeout and RetryInterval metrics: I left them to default.  It looks like I was messing with stuff that was unecessary, but after further research as you suggested - looks like you are right.  good call(s).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.