I would expect the PoSH stuff to run DateTime.Parse or a similar method on its input -- didn't mean to imply that SQL was relevant here, or that "dd-MMM-yyyy" is SQL's most native-ish format (it is not) -- merely a format that I find easy to type, read, and which is well understood by most systems.
IMHO the most unambiguous system datetime format is the XML datetime, e.g., "2012-01-30T16:28:52.6193034Z", which contains no whitespace, and clearly shows the time part and timezone. --Steve On Mon, Jan 30, 2012 at 10:57 AM, Michael B. Smith <mich...@smithcons.com> wrote: > I agree with your concept - but I think I disagree with your choice of format. > > Search isn't built on SQL and it has a limited range of date formats it > recognizes. I have notes that say the only "universal unambiguous format" is > "yyyy-mm-dd hh:mm:ss" (with "hh:mm:ss" being optional), but I don't have a > public reference for that. > > Regards, > > Michael B. Smith > Consultant and Exchange MVP > http://TheEssentialExchange.com > > > -----Original Message----- > From: Steve Kradel [mailto:skra...@zetetic.net] > Sent: Monday, January 30, 2012 10:39 AM > To: MS-Exchange Admin Issues > Subject: Re: New-MailboxExportRequest issues > > I'd suggest going with a format that's unambiguous, and readily > accepted by both .NET and SQL: "dd-MMM-yyyy"; e.g., "30-JAN-2012". > This is my date format of choice for systems and for communicating > with an international audience. > > --Steve > > On Mon, Jan 30, 2012 at 10:18 AM, Sobey, Richard A > <r.so...@imperial.ac.uk> wrote: >> Hah! Over here in Blighty I have to use "DD/MM/YYYY" for any date up to and >> including the 12th of each month, and "MM/DD/YYYY" for the 13th and after. >> Or, I can stick to "MM/DD/YYYY" throughout the entire command. >> >> >> >> Grrr. >> >> >> >> From: bounce-9481349-8066...@lyris.sunbelt-software.com >> [mailto:bounce-9481349-8066...@lyris.sunbelt-software.com] On Behalf Of >> Michael B. Smith >> Sent: 30 January 2012 13:50 >> >> >> To: MS-Exchange Admin Issues >> Subject: RE: New-MailboxExportRequest issues >> >> >> >> Did you write dd/mm/yyyy ?? Really? Where are you? >> >> >> >> Single vs. double quotes shouldn't make any difference. >> >> >> >> Regards, >> >> >> >> Michael B. Smith >> >> Consultant and Exchange MVP >> >> http://TheEssentialExchange.com >> >> >> >> From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] >> Sent: Monday, January 30, 2012 8:41 AM >> To: MS-Exchange Admin Issues >> Subject: RE: New-MailboxExportRequest issues >> >> >> >> Right, >> Unless I misunderstand it, Sent mail is mail you send whereas Received mail >> is mail you received and I wanted both exported. >> >> No errors are thrown, it accepts it but the job reports failed when viewing >> the queue. I wasnt sure looking at the output of certain cmds versus their >> input as to which format the date should have been specified in, MM/DD or >> DD/MM as a Search-Mailbox being entered in one format returned results >> formatted in the other? >> >> The cmd that finally worked is DD/MM/YYYY in double quotes. Looking at my >> notes it was second format I tried, but somewhere along the attempts I >> switched to double quotes instead of single, who knows... >> >> Thanks! >> jlc >> >> ________________________________ >> >> From: Sobey, Richard A [r.so...@imperial.ac.uk] >> Sent: Monday, January 30, 2012 3:30 AM >> To: MS-Exchange Admin Issues >> Subject: RE: New-MailboxExportRequest issues >> >> Your Sent and Received are the same? You may also need to specify a MM:HH in >> addition to MM:DD:YYYY. >> >> >> >> Can you send the output of the command when it fails? >> >> >> >> From: bounce-9480934-8066...@lyris.sunbelt-software.com >> [mailto:bounce-9480934-8066...@lyris.sunbelt-software.com] On Behalf Of >> Joseph L. Casale >> Sent: 29 January 2012 04:10 >> To: MS-Exchange Admin Issues >> Subject: New-MailboxExportRequest issues >> >> >> >> Trying to export out sent and received items with a content filter of {(Sent >> -lt '06/28/2011') -and (Received -lt '06/28/2011')} >> This fails, whereas w/o the content filter, or with a simpler one it works. >> >> Anyone see the issue? >> >> Thanks, >> jlc >> >> Ps. Sorry for the lame sub, lyris's fault >> > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist