Oh no, Michael, in all seriousness, my sarcasm was not, nor would it ever be, directed towards you personally. You have saved my bacon more than once, and are very much appreciated.
I think some of my frustration is with the project that we in the State of California are being forced into. The original intent was to consolidate e-mail for the entire state, and to cut costs of each department running their own. Great idea. However, implementation is a nightmare. Microsoft O365 is what we're going to, but here's the catch. They are treating the entire state as one company. The problem with that, is that we are about 160 separate departments, each with our own users, etc. So, when you treat us as one company, how do you allow, for instance, me, to manage my users within Exchange. If you give me access to EMC, EMS or ECP, then I can make changes that could potentially affect other departments as well as my own. Well, we can't have that. So they're taking that access away from all departmental Exchange Admins. For me to create a mailbox, I have to go into ADUC, and use the Attribute Editor, and manually manipulate about 6 or 7 different attributes. An automatic sync happens every 30 minutes, and the creation gets processed back at Microsoft, in either San Antonio, or Chicago. Which could take up to a few hours. If I make a typo during that process? Well, I have to fix it, and wait another few hours for the process to happen again. They are giving us a very rudimentary "admin" interface, in which we can do about 10 different things: Export a mailbox to PST Add/Remove Mailbox Permission Add/Remove Delegate Activesync - Enable/Disable Activesync - Apply Policy OWA - Enable/Disable Apply Retention Policy Group Admin (create or modify cross-forest distribution lists) Live Meeting Admin - If you paid for this service (we did not) Contact Admin - allows us to add, edit or delete Contacts within the system. That's it. That's what I can directly affect. Anything beyond that, I have to call the Helpdesk for the mail system, and wait. The SLA's vary, but with the track record of the organization that's actually going to be doing the work, the wait time will be hours, days and for some things possibly weeks. Oh, and as far as saving money? Umm, no. We're not completely in the system yet, but I've spoken to someone who's department is, and he's saying his costs went from about 30k per year for running Exchange in-house, to a cool half million now. Yippee! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, February 06, 2013 12:59 PM To: Heaton, Joseph@Wildlife; MS-Exchange Admin Issues Subject: RE: Reconnect Exchange 2010 mailbox I appreciate the irony. But please do not shoot the messenger. :) Also, Clean-MailboxDatabase does not perform well "at scale". In Microsoft's perspective that means, when you have mailbox databases containing many thousands of mailboxes. That being said, there _IS_ a way in Exchange 2013 to simulate Clean-MailboxDatabase and have it perform well at scale. Whenever I have a few minutes, I plan on writing it up. :) From: Heaton, Joseph@Wildlife [mailto:joseph.hea...@wildlife.ca.gov] Sent: Wednesday, February 6, 2013 12:38 PM To: MS-Exchange Admin Issues Subject: RE: Reconnect Exchange 2010 mailbox Now that's funny. Exchange is "supposed" to be smart enough, so whether it is or not, we're going to take away the tool you could use to make sure it happens... Awesome. From: Michael B. Smith [mailto:michael@smithconscom<mailto:mich...@smithcons.com>] Sent: Tuesday, February 05, 2013 6:19 AM To: Heaton, Joseph@Wildlife; MS-Exchange Admin Issues Subject: RE: Reconnect Exchange 2010 mailbox 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 Subject: RE: Reconnect Exchange 2010 mailbox 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 Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: dgu...@che.org<mailto:dgu...@che.org> Office: 610.550.3595 | Cell: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. -----Original Message----- From: Tom Miller [mailto:tmil...@sfgtrust.com] Sent: Monday, February 04, 2013 4:10 PM To: MS-Exchange Admin Issues Subject: RE: Reconnect Exchange 2010 mailbox That was it. I saw in an MS support forum that the Clean-Mailboxdatabase db_name is needed for immediate access. Supposedly fixed in the current rollup (I'm not on it). Thank you, Tom -----Original Message----- From: Rupprecht, James R. [mailto:jimruppre...@ku.edu] Sent: Monday, February 04, 2013 1:18 PM To: MS-Exchange Admin Issues Subject: RE: Reconnect Exchange 2010 mailbox Run Clean-MailboxDatabase against the database that hosts the reconnected mailbox. Jim Rupprecht KU Information Technology ----- Original Message ----- From: Tom Miller [mailto:tmil...@sfgtrust.com] Sent: Monday, February 04, 2013 11:40 AM To: MS-Exchange Admin Issues Subject: Reconnect Exchange 2010 mailbox We have an account that was disabled accidentally. I recreated the account in ADUC, and used the "reconnect" option in the EMC. However, when I go into the account on OWA, the web page states that the account is disabled, but it is not. Anyone have any suggestions? Tom --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto: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<mailto: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<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto: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<mailto: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<mailto: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<mailto: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
