RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Damien Solodow
Yep. Sent from my Galaxy S®III Original message From: Heaton, Joseph@Wildlife joseph.hea...@wildlife.ca.gov Date: To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Subject: RE: Exchange 2010 SP3, SP2 RU6 released... Management console installs? You

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Senter, John
So the big question, does Exchange 2010 SP3 contain all of the fixes in SP2 RU6??? The documentation states it contains all fixes before its release, but SP2 RU6 has the same release date. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, February 12, 2013 5:39 PM To:

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Kretche, Peter
Any schema changes? Not seeing anything in the KB but don't want a surprise. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: February 12, 2013 06:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP3, SP2 RU6 released... Yes: CAS, HT, MT, UM, MB If you have ET, do them

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Michael B. Smith
Does 2010 SP3 have schema changes? Yes. Does 2010 SP2 UR6 have schema changes? No. Does 2007 SP3 UR10 have schema changes? No. The current servicing model for 2007 and 2010 does not allow for schema changes in URs. It does allow for schema changes in SPs. (And, in the future for 2013, in CUs.)

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Paul Gordon
As is becoming depressingly common with MS's documentation, the wording isn't completely precise, and leaves room for ambiguity. The release notes (http://technet.microsoft.com/en-us/library/jj965774%28v=exchg.141%29.aspx) explicitly state: 1. Exchange 2010 SP3 makes updates to the

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Paul Gordon
A colleague has now installed SP3 in a test lab, on what was previously an SP2 environment, and confirms that it absolutely DOES perform additional schema changes. I don't yet know what the new schema version number is though. P. From: Paul Gordon [mailto:paul_gor...@hotmail.com] Sent: 13

Re: Is New-MailboxExportRequest available in Exchange 2010 SP1

2013-02-13 Thread Todd Lemmiksoo
Thanks, learn new things everyday in Exchange. On Tue, Feb 12, 2013 at 11:35 PM, Heaton, Joseph@Wildlife joseph.hea...@wildlife.ca.gov wrote: Actually, by default, no one has the rights for that cmdlet. You have to manually add people using that Mailbox Import Export role. Then, close and

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Tobie Fysh
Here in the UK the following is showing: Exchange Server 2013 15137 15449 13236 Maybe need a refresh somewhere ;-) From: Paul Gordon [mailto:paul_gor...@hotmail.com] Sent: 13 February 2013 16:43 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP3, SP2 RU6 released... A colleague

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Michael B. Smith
Does restarting MsExchangeTransport do anything at all? What do your queues look like? From: Reimer, Mark [mailto:mark.rei...@prairie.edu] Sent: Wednesday, February 13, 2013 3:28 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 SP1 EdgeTransport.exe eating up all memory Subject says it

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Leedy, Andy
“Curiously, Exchange 2010 SP2 RU6 contains an ActiveSync loop fix: http://support.microsoft.com/kb/2783771 So those iOS6.1 “loop” issues may not be entirely Apple’s fault…” Can anyone confirm if RU6 resolves the excessing logging issue…. http://support.microsoft.com/kb/2814847 ?? -Andy

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Shanks, Brandon C
No… that is an entirely different issue. Brandon From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Wednesday, February 13, 2013 2:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP3, SP2 RU6 released... “Curiously, Exchange 2010 SP2 RU6 contains an ActiveSync loop fix:

RE: Exchange 2010 SP3, SP2 RU6 released...

2013-02-13 Thread Michael B. Smith
It does NOT. From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Wednesday, February 13, 2013 3:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP3, SP2 RU6 released... “Curiously, Exchange 2010 SP2 RU6 contains an ActiveSync loop fix: http://support.microsoft.com/kb/2783771

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Reimer, Mark
Restarting the Transport will drop the memory, for a few minutes. Queues: There is a queue called submission. I didn't know how to check/look at the queues (I'm learning Exchange). Anyway, it had 3 messages, each over 1 GB. I asked the user to delete the messages, and also I had to stop

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread KevinM
Emails over 1GB ? were they sent from outlook 2003 that does not care about exchange sending limits, or do you have no size limits ? From: Reimer, Mark [mailto:mark.rei...@prairie.edu] Sent: Wednesday, February 13, 2013 1:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Michael B. Smith
There ya go. You probably want to set some limits. :) From: Reimer, Mark [mailto:mark.rei...@prairie.edu] Sent: Wednesday, February 13, 2013 4:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory Restarting the Transport will drop the memory,

RE: Calendar Repair Assistant

2013-02-13 Thread Shanks, Brandon C
It seems much better behaved post SP1. The main issue we faced was notifying end users to expect changes to their calendars when we first started running it. Brandon From: Rhett Thatcher [mailto:rthatc...@stlawu.edu] Sent: Wednesday, February 13, 2013 4:21 PM To: MS-Exchange Admin Issues

RE: Calendar Repair Assistant

2013-02-13 Thread Michael B. Smith
I think at SP2 UR3 and later, it's pretty stable. It performs as advertised. From: Rhett Thatcher [mailto:rthatc...@stlawu.edu] Sent: Wednesday, February 13, 2013 5:21 PM To: MS-Exchange Admin Issues Subject: Calendar Repair Assistant Look for advice, any input or comments appreciated. We have

RE: Offline Address Book, Public Folder Database

2013-02-13 Thread Michael B. Smith
This should NOT be necessary if you have properly removed the public folder databases on your Exchange 2003 servers. And I wouldn’t recommend doing this anyway. I’d suggest creating a NEW Default Offline Address List and removing the old one, to ensure that EVERYTHING gets created properly.

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Reimer, Mark
I thought by not setting any, the default of 10MB would be enforced. Not true? Mark From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, February 13, 2013 3:05 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory There ya go.

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Reimer, Mark
No, it was Outlook 2010. I have no defined size limits. I thought the default of 10MB would be enforced. Mark From: KevinM [mailto:kev...@wlkmmas.org] Sent: Wednesday, February 13, 2013 3:05 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Michael B. Smith
Unless (as KevinM implied) you are running Outlook 2003. Seems more likely that you do not have limits where you think you do... From: Reimer, Mark [mailto:mark.rei...@prairie.edu] Sent: Wednesday, February 13, 2013 5:46 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1

RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory

2013-02-13 Thread Reimer, Mark
Yup. A bit more research (Googling) caught me with no limits. That has been fixed now. :). Mark From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, February 13, 2013 3:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 SP1 EdgeTransport.exe eating up all memory