Why does en-CA work on the first ::Parse() and en-GB fail? Weird. No, use yyyy-mm-dd.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Joseph L. Casale [mailto:[email protected]] Sent: Monday, January 30, 2012 12:57 PM To: MS-Exchange Admin Issues Subject: RE: New-MailboxExportRequest issues Sorry for getting back late: [PS] C:\>(get-culture) |fl Parent : en LCID : 4105 KeyboardLayoutId : 4105 Name : en-CA IetfLanguageTag : en-CA DisplayName : English (Canada) NativeName : English (Canada) EnglishName : English (Canada) TwoLetterISOLanguageName : en ThreeLetterISOLanguageName : eng ThreeLetterWindowsLanguageName : ENC CompareInfo : CompareInfo - 4105 TextInfo : TextInfo - 4105 IsNeutralCulture : False CultureTypes : SpecificCultures, InstalledWin32Cultures, FrameworkCultures NumberFormat : System.Globalization.NumberFormatInfo DateTimeFormat : System.Globalization.DateTimeFormatInfo Calendar : System.Globalization.GregorianCalendar OptionalCalendars : {System.Globalization.GregorianCalendar, System.Globalization.GregorianCalendar} UseUserOverride : True IsReadOnly : False [PS] C:\>(get-culture).DateTimeFormat AMDesignator : AM Calendar : System.Globalization.GregorianCalendar DateSeparator : / FirstDayOfWeek : Sunday CalendarWeekRule : FirstDay FullDateTimePattern : MMMM-dd-yy h:mm:ss tt LongDatePattern : MMMM-dd-yy LongTimePattern : h:mm:ss tt MonthDayPattern : MMMM dd PMDesignator : PM RFC1123Pattern : ddd, dd MMM yyyy HH':'mm':'ss 'GMT' ShortDatePattern : dd/MM/yyyy ShortTimePattern : h:mm tt SortableDateTimePattern : yyyy'-'MM'-'dd'T'HH':'mm':'ss TimeSeparator : : UniversalSortableDateTimePattern : yyyy'-'MM'-'dd HH':'mm':'ss'Z' YearMonthPattern : MMMM, yyyy AbbreviatedDayNames : {Sun, Mon, Tue, Wed, Thu, Fri, Sat} ShortestDayNames : {Su, Mo, Tu, We, Th, Fr, Sa} DayNames : {Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday} AbbreviatedMonthNames : {Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec, } MonthNames : {January, February, March, April, May, June, July, August, September, October, Novem ber, December, } IsReadOnly : False NativeCalendarName : Gregorian Calendar AbbreviatedMonthGenitiveNames : {Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec, } MonthGenitiveNames : {January, February, March, April, May, June, July, August, September, October, Novem ber, December, } [PS] C:\>[System.DateTime]::Parse("15/01/2012") January-15-12 12:00:00 AM [PS] C:\>$culture = new-object System.Globalization.CultureInfo( "en-ca" ) [PS] C:\>[System.DateTime]::Parse("15/01/2012", $culture) January-15-12 12:00:00 AM So the safest least ambiguous way is to write a date as follows "January-15-12 12:00:00 AM"? This seem to be accepted fine by Search-Mailbox, but not New-MailboxExportRequest, it accepted the input but the job failed. Search-Mailbox -Identity User -SearchQuery "Received:< $('January-15-12 12:00:00 AM') and Sent:< $('January -15-12 12:00:00 AM')" -SearchDumpster -EstimateResultOnly New-MailboxExportRequest -Mailbox User -ContentFilter {(Sent -lt "January-15-12 12:00:00 AM") -and (Receive d -lt "January-15-12 12:00:00 AM")} -FilePath "\\server\share\test.pst<file:///\\server\share\test.pst>" Fails... Thanks for help! jlc ________________________________ From: Michael B. Smith [[email protected]] Sent: Monday, January 30, 2012 7:24 AM To: MS-Exchange Admin Issues Subject: RE: New-MailboxExportRequest issues Can you run these for me? (Any PowerShell window, doesn't have to be EMS.) (get-culture) | fl (get-culture).DateTimeFormat Thanks. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
