http://www.windowsitpro.com/authors/author/author/5576977/rsscomment/5576977en-USSun, 27 May 2012 07:04:43 GMTSun, 27 May 2012 07:04:43 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/testing-google-apps-143090#commentsAnchorFri, 25 May 2012 17:31:12 GMT
Alternative title: When whoever's in New England is through with... Google Apps.]]>Dimitrios KalemisFri, 25 May 2012 17:31:12 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/testing-google-apps-143090#commentsAnchorhttp://www.windowsitpro.com/article/office-365/shared-mailboxes-office-365-142386#commentsAnchorFri, 18 May 2012 16:13:12 GMT
Great article and I can attest that Shared Mailboxes have been helpful in many of my Office 365 deployments. However, you might want to let readers know that there are some limitations to using unlicensed Shared Mailboxes in Exchange Online. Specifically, the mailbox quota cannot be more than 5GB and no personal archive mailbox is allowed. See this url (http://technet.microsoft.com/en-us/exchangelabshelp/ee441202) and note specifically the sections "Shared mailboxes in Microsoft Office 365" and "Create and configure a shared mailbox." Things get even a little bit more complex when in a Hybrid environment and you use the on-premise Exchange tools to provision a new Shared mailbox. It then becomes a multi-step process to provision the on-premise object, then to configure that object to not violate the limitations for unlicensed shared mailboxes in Exchange Online. ]]>einaaiiFri, 18 May 2012 16:13:12 GMThttp://www.windowsitpro.com/article/office-365/shared-mailboxes-office-365-142386#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorSun, 06 May 2012 18:53:18 GMT
The same challenges also face Outlook add-ins, such as work-flow tools from third-parties and from Microsoft that integrate into Outlook. As the clients [users] move away from the Outlook client, these add-ins lose value too.]]>bwadminSun, 06 May 2012 18:53:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorFri, 04 May 2012 08:39:04 GMT
The "writer" of the Slate article obviously doesn't work in a law firm. He's writing drivel that pops into a preformed style sheet that his media outlet dictates to him. So it's easy to create the content in a text editor and simply provide the text to Slate or whoever he's preparing ramblings for. Maybe he should ask his law firm if they're using a plain text editor to write his mortgage agreement, will, or any other legal document. And trust me, in the enterprise, I don't think Outlook is dying tomorrow ... features beyond e-mail like the Journal for tracking years of activities and projects or the excellent Tasks and Calendar features would take multiple apps where you can do it ALL right within Outlook 2010 without having to have one e-mail (e.g., gMail) and then Evernote for project notes, etc. People just like to make things more complicated where the integration in the Office suite gives everything the professional office needs, not some hack blogger that puts content into preformed CSS. Tony, I'm glad you noted the revenue value that Office is to Microsoft. There's media hype and then there's the reality that kingpins in the enterprise like Exchange, SQL or even Office really are. If I told all the lawyers at my firm that we're switching to gMail and an open source editor tomorrow, I guess I'd be on "early retirement". ]]>t_c_andersonFri, 04 May 2012 08:39:04 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorTue, 01 May 2012 08:06:49 GMT
Tony - here's how I got the LinkedIn connector to work. http://social.technet.microsoft.com/Forums/en-US/outlook/thread/b8c8f3de-b440-4373-b444-258baaccec0d]]>joesternTue, 01 May 2012 08:06:49 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office/death-to-outlook-142900#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server-2010/exchange-2010-sp2-custom-attributes-141780#commentsAnchorSun, 15 Apr 2012 02:52:56 GMT
Very good article.]]>Piotr PawlikSun, 15 Apr 2012 02:52:56 GMThttp://www.windowsitpro.com/article/exchange-server-2010/exchange-2010-sp2-custom-attributes-141780#commentsAnchorhttp://www.windowsitpro.com/article/performance/outlook-2007-sp2-improves-ost-performance#commentsAnchorTue, 10 Apr 2012 13:10:56 GMT
U can go for this link because my ost problem solved this application : http://www.ost2pstsoftware.com/]]>sql repairTue, 10 Apr 2012 13:10:56 GMThttp://www.windowsitpro.com/article/performance/outlook-2007-sp2-improves-ost-performance#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorWed, 04 Apr 2012 03:33:35 GMT
@Dave You Google fanboism is amazing. Google, who will index and store data from your company which could be private/sensitive. Google who offer no real direct support. Google, whose contracts are not direct, but with a 3rd party. Where sync does not work 100% with Outlook. Office document compatibility is woeful. GMail which will confuse users with labels versus folders. Seriously, I like Google products, but its not all rainbows and unicorns on their side either. Microsoft always put up their service status here: https://portal.microsoftonline.com/ServiceStatus/ServiceStatus.aspx Go and Google 500,000 GMAIL accounts go offline. All cloud services have outages, just as internal IT services do. But most internal IT services (bar banks) will never match the scale / resilience and manpower provided by cloud providers. Seriously its 2012, who "wants" to build email services internally? Its commoditised now. 365 is in use by many of our peers. We are at pilot stage. We had tried out Google, but for lots of reasons, many like the above its not a good fit. Microsoft have the client side and the cloud side. We aren't ready for "all web" and "all online" yet. If you are still having outages, suspect its not MS, but DNS which is often the issue for SMEs. But good luck with whatever you do. ]]>RommiWed, 04 Apr 2012 03:33:35 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorWed, 04 Apr 2012 03:24:57 GMT
@Dave You Google fanboism is amazing. Google, who will index and store data from your company which could be private/sensitive. Google who offer no real direct support. Google, whose contracts are not direct, but with a 3rd party. Where sync does not work 100% with Outlook. Office document compatibility is woeful. GMail which will confuse users with labels versus folders. Seriously, I like Google products, but its not all rainbows and unicorns on their side either. Microsoft always put up their service status here: https://portal.microsoftonline.com/ServiceStatus/ServiceStatus.aspx Go and Google 500,000 GMAIL accounts go offline. All cloud services have outages, just as internal IT services do. But most internal IT services (bar banks) will never match the scale / resilience and manpower provided by cloud providers. Seriously its 2012, who "wants" to build email services internally? Its commoditised now. 365 is in use by many of our peers. We are at pilot stage. We had tried out Google, but for lots of reasons, many like the above its not a good fit. Microsoft have the client side and the cloud side. We aren't ready for "all web" and "all online" yet. If you are still having outages, suspect its not MS, but DNS which is often the issue for SMEs. But good luck with whatever you do. ]]>RommiWed, 04 Apr 2012 03:24:57 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorMon, 02 Apr 2012 09:16:16 GMT
@Dave You Google fanboism is amazing. Google, who will index and store data from your company which could be private/sensitive. Google who offer no real direct support. Google, whose contracts are not direct, but with a 3rd party. Where sync does not work 100% with Outlook. Office document compatibility is woeful. GMail which will confuse users with labels versus folders. Seriously, I like Google products, but its not all rainbows and unicorns on their side either. Microsoft always put up their service status here: https://portal.microsoftonline.com/ServiceStatus/ServiceStatus.aspx Go and Google 500,000 GMAIL accounts go offline. All cloud services have outages, just as internal IT services do. But most internal IT services (bar banks) will never match the scale / resilience and manpower provided by cloud providers. Seriously its 2012, who "wants" to build email services internally? Its commoditised now. 365 is in use by many of our peers. We are at pilot stage. We had tried out Google, but for lots of reasons, many like the above its not a good fit. Microsoft have the client side and the cloud side. We aren't ready for "all web" and "all online" yet. If you are still having outages, suspect its not MS, but DNS which is often the issue for SMEs. But good luck with whatever you do. ]]>RommiMon, 02 Apr 2012 09:16:16 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorMon, 19 Mar 2012 21:07:15 GMT
I'm confused as to how you can claim success for 365 (which, in reality is more like 362 or so at this point). Albeit occurring after your publish date, I'd like to highlight yet another miserably failure of 365 for hours on end in the Australian market. However, the most grating failures happen constantly and without many even noticing since Microsoft lacks the transparency that it's biggest competitor, Google, offers. There are failures that affect a percentage of users. The MS way is to declare success and bury the story. My organization cannot access basic settings information for 2 WEEKS now. Read that again. 2 WEEKS!!! Microsoft has no clue what is going on and has no updates. Every hour is amateur hour with Microsoft and their "cloud" solutions. I will congratulate Microsoft. However, my congratulations are for their unmitigated gaul in carpet bombing Google with deceptive FUD campaigns, while failing to provide the public with any insight into the performance of their competing offerings. That takes guts.]]>DaveMon, 19 Mar 2012 21:07:15 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-142509#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-circular-logging-140787#commentsAnchorTue, 13 Mar 2012 08:42:28 GMT
Hey Tony, Perhaps it would be a good idea to include a note stressing out that when in CRCL mode logs won't be deleted from server holding the active copy if one of the servers holding a passive copy are down or otherwise unavailable. Henrik]]>HenrikWaltherTue, 13 Mar 2012 08:42:28 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-circular-logging-140787#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/mecisback-142471#commentsAnchorWed, 07 Mar 2012 07:57:44 GMT
This is great news that Microsoft have reinstated MEC! Ive never been to MEC and always wanted to go. Maybe this is a sign the good times are here again :) I have been to the Win IT Pro Connection event (in Amsterdam some years ago )and hope this will also continue as it was excellent. Look forward to some informative speeches Tony!]]>RichWed, 07 Mar 2012 07:57:44 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/mecisback-142471#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-troubleshooting-tools-142351#commentsAnchorThu, 01 Mar 2012 18:30:49 GMT
Now if they can only create an OCAT for Outlook 2011...]]>breckwThu, 01 Mar 2012 18:30:49 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-troubleshooting-tools-142351#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-ru1-cas-glitch-142293#commentsAnchorFri, 24 Feb 2012 14:19:29 GMT
As you might have noticed, the decribed behavior is not a bug - it is a design change in RU1. It was mentioned in an Article on the Exchange Team Blog on February 20th... Christian]]>cnsFri, 24 Feb 2012 14:19:29 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-ru1-cas-glitch-142293#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorThu, 23 Feb 2012 14:49:28 GMT
WOW is all I can say! I am not soothsayer but I would dare to say PowerShell isn't going away and I would also hazard a guess Mr. Redmond has his finger on the pulse of MS better than murat. :-) I am not a big fan of the command line either and so far I have taken one PowerShell course and did fine until it came to writing my scripts. I am not a programmer so scripting has never been easy for me but I am smart enough to know at some point I will have to get better at writing them. Concerning upgrades, IMO and experience, upgrading is and always has been a BAD idea. I have always started out clean even if it meant re-installing everything from scratch. Much less time consuming in the end... Keep up the good work Tony! ]]>Michael RoeserThu, 23 Feb 2012 14:49:28 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/learn-microsoft-certified-master-accreditation-142058#commentsAnchorWed, 01 Feb 2012 16:33:54 GMT
Hi Tony - we will actually have upcoming webcasts on ALL of the MCM programs. SharePoint and SQL already have theirs scheduled as well - you can track all of these events at the search keyword-based link https://msevents.microsoft.com/cui/SearchDisplay.aspx?kwdAny=advcert . ]]>bgeoffroyWed, 01 Feb 2012 16:33:54 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/learn-microsoft-certified-master-accreditation-142058#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorMon, 30 Jan 2012 05:57:45 GMT
@hunterpaw, I'm glad that you have had a good experience with your MVP lead. As I make the point in the article, the MVP program depends on the contribution of people. Where MVPs, product groups, and MVP leads do the right thing and work together, it creates a very positive and worthwhile experience for all concerned. Where MVPs don't connect with the product groups for whatever reason or where an MVP lead is merely checking in the hours while they wait for their next job in Microsoft, things go awry. I think that Rob Eisenberg did his best to communicate with his MVP leads but clearly things didn't happen the way that they should. My experience will MVP leads has varied. Some are excellent, some aren't. Just like people really...]]>TRedmondMon, 30 Jan 2012 05:57:45 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorFri, 27 Jan 2012 15:10:22 GMT
I recieved the MVP award in October. MVP awardees are encourages to participate in a number of opportunities. I quickly found out that there are some MVPs that participate in interaction with Microsoft. private MVP discussions, and fellow MVPs and there are those that do not participate. If someone has issues with the Microsoft MVP program they should report them to their MVP Lead. I have found that my MVP Lead to be very responsive and helpful. Cooperation is a two-way process. Perhaps if he had reported his issues to his MVP Lead the Lead would have known him.]]>hunterpawFri, 27 Jan 2012 15:10:22 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorFri, 27 Jan 2012 11:20:08 GMT
@Mike, good points. I absolutely agree with your observations about Joe Richards. He makes his contribution in a very meaningful and obvious way by generating and maintaining tools that make life easier for Active Directory administrators. There's huge value immediately apparent there. Other MVPs make their contributions using their own skills and talents. Some are very good and dogged at answering questions in online forums, others write about their experience to explain the technology, others are fantastic trainers or lead local interest groups. I have no difficulty with any of these contributions. I do have a problem when I see an MVP whose value can't be asserted in a clear and obvious sense and there are just too many of these folks around to make me think that the issue is limited to one or two. Hence I think that there's a need to benchmark contribution in a meaningful sense to ensure that MVP status actually means something rather than being an arbitrary recognition from Microsoft. And yes, happy to discuss at the summit!]]>TRedmondFri, 27 Jan 2012 11:20:08 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorFri, 27 Jan 2012 07:39:32 GMT
I think there are some valid points that you are making here Tony but the one that I think Rob harped on a bit too much is the "all MVPs are not created equal" You don't need to be a rocket scientist to figure that out. Are all MVPs supposed to be created equal or have the same skill sets in a particular discipline? In Active Directory I consider Joe Richards one of the best guys around and sort of like an online mentor through his posts and conversations we have had. We are both DS MVPs but that doesn't mean I think I'm equal to Joe or better than him. I do my part in the community but like everyone else I'm also learning new things daily. Joe then is so humble that he rates himself low compared to legends inside Microsoft with AD http://blog.joeware.net/2008/08/11/1420/ This is not unique to the MVP program, this goes on everywhere in life. There are over 400 NBA players but only a few with the skills of Libran James or Kobe Bryant. There was only one Michael Jordan. We don't see that as some sort of bad thing, the other NBA players are also qualified but they are not all Michael Jordan. We see this in the military too. I was in the Army in the early/mid-90's. However these guys in Special Forces like the Navy SEALS or Army Rangers were in my opinion better than me however we were all in the service...were we all supposed to be equal? The examples can go on and on in any industry. Maybe we can meet and talk about this at the summit this year :) Thanks Mike ]]>mkline718Fri, 27 Jan 2012 07:39:32 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/problems-mvp-program-141877#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-pst-141568#commentsAnchorSun, 22 Jan 2012 11:52:52 GMT
I do trust Office 365... If only because if it goes bust, I have an OST containing all of my really urgent email and can always work offline to export the data to a PST if I had to. As for the stuff in an archive, if problems occur I can wait for Microsoft to sort the issue out and then get back to the archive. After all, what you put into an archive is there just in case you need it and that shouldn't be "now" (at least, I hope not). TR]]>TRedmondSun, 22 Jan 2012 11:52:52 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-pst-141568#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-pst-141568#commentsAnchorWed, 18 Jan 2012 07:31:06 GMT
Good insights. Now do you trust Office365 enough to delete all of your remaining copies of those PST files? :-) ]]>bwadminWed, 18 Jan 2012 07:31:06 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-pst-141568#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-mvps-141806#commentsAnchorFri, 13 Jan 2012 01:21:29 GMT
MVPtweets.com is another way to discover what's new in the Microsoft MVPs world. MVPtweets.com displays tweets in real time from 1,170+ Microsoft Most Valuable Professionals, from Community Program Managers and from #MVP12, #MVPchat and #MVPbuzz hashtags. http://www.MVPtweets.com ]]>JM2CFri, 13 Jan 2012 01:21:29 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-mvps-141806#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorThu, 05 Jan 2012 01:41:21 GMT
tony, you are right, I frequently write against PowerShell. But I'm not the only one. Don Jones frequently mentions about people who are reluctant to work with PowerShell as in his last post: ", I've heard from a dozen or more organizations that are starting internal projects to automate specific tasks using PowerShell. Try as they might, these organizations haven't been able to get their team up to speed quickly enough. In most cases, it's because they've got their IT folks so overworked already that there's just no bandwidth; in a couple of cases their team has been... well, let's call it "reluctant." Why are they reluctant Tony? Is it because they are dumb, or lazy, or somewhat? No, they are not. They are just shocked with the PowerShell: It is contrary to all they and we know or accustomed to. For the in-place upgrade: Microsoft succeeded to upgrade 16-bit Windows 3.0 installations to 32-bit Windows 95, 16 years ago. Now, we have difficulty to understand why we can not do the same. Microsoft Research people could find a way for this upgrade. But , instead of doing this, they are dealing with hot issues like communication over fingertips or surface computer. ]]>murat yildirimogluThu, 05 Jan 2012 01:41:21 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorWed, 04 Jan 2012 16:02:44 GMT
@Murat. Words fail me. This contribution plus your other frequent rantings on the same topic makes me believe that you must be the only person on the face of the planet who hasn't yet understood that Microsoft's investment in PowerShell is not going to be junked in the near future. PowerShell is incredibly powerful and is now all-pervasive. For the sake of your career and perhaps your future happiness you had better become at least somewhat acquainted with PowerShell. As to in-place upgrades, that's in the past too. There's no point in crying over issues that have been debated and decided upon. Instead, understand that future versions of Exchange will be deployed on new hardware and plan accordingly. TR]]>TRedmondWed, 04 Jan 2012 16:02:44 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorWed, 04 Jan 2012 09:31:16 GMT
Murat, On the contrary PowerShell is the future. Embrace it baby or be left behind! A real Sys or Exchange admin can simply not do without PowerShell. Give it a try! You maybe surprised how easy it is. Inplace Exchange upgrades were flaky at best. It was a 'hold your breath and hope for the best' experience! With the advent of 64-bit computing in-place upgrades were not physically possible from 32-bit Exchange apps like Exchange 2003. ]]>RichWed, 04 Jan 2012 09:31:16 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorTue, 03 Jan 2012 10:16:54 GMT
Tony, your comments are generally out-of-this world and this one is not an exception. First, we, the real system admins in this world, like to upgrade, instead of installing new servers and migrate mailboxes whenever a new version is released. Up until Exchange 2007, the usual practise had been in-place upgrading: It was cheap (you use your current servers) and fast (there was no need to move mailboxes back-and-forth). Now, Exchange 2007 and 2010 do not allow us to do in-place upgrade. It is just a shame. I don't like it but I think next version also will not allow upgrading (and I'm sure Microsoft execs will have many excuses to justify it). PowerShell is another thing you are wrong. For the time being, Microsoft applies pressure to us to use it, but most of the people just don't like it and when they use it, they use it blindly (just googling the right command and apply it). My crystall ball says this PowerShell has no future and it is not a bad thing. Nobody should invest in PowerShell. ]]>murat yildirimogluTue, 03 Jan 2012 10:16:54 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/exchange-2012-141740#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-ecosystem-141531#commentsAnchorWed, 28 Dec 2011 07:50:15 GMT
MachSol Inc., a Microsoft Gold Partner is first ever to announce support for Microsoft Exchange 2010 SP2 in coming release of MachPanel. So, If you have not deployed Exchange 2010 yet, than we suggest you to make a wise decision by avoiding /hosting mode and configuring Exchange 2010 SP2 on-premises deployment. MachPanel is the industry leading control panel for Shared and Enterprise Hosting that fully supports Microsoft Exchange, SharePoint, CRM 2011 and OCS/Lync etc. http://blog.machsol.com/microsoft-exchange/microsoft-exchange-2010-sp2-support-with-machpanel]]>cloudtechWed, 28 Dec 2011 07:50:15 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-ecosystem-141531#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-141130#commentsAnchorWed, 28 Dec 2011 07:48:37 GMT
MachSol Inc., a Microsoft Gold Partner is first ever to announce support for Microsoft Exchange 2010 SP2 in coming release of MachPanel. So, If you have not deployed Exchange 2010 yet, than we suggest you to make a wise decision by avoiding /hosting mode and configuring Exchange 2010 SP2 on-premises deployment. MachPanel is the industry leading control panel for Shared and Enterprise Hosting that fully supports Microsoft Exchange, SharePoint, CRM 2011 and OCS/Lync etc. http://blog.machsol.com/microsoft-exchange/microsoft-exchange-2010-sp2-support-with-machpanel]]>cloudtechWed, 28 Dec 2011 07:48:37 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-141130#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorFri, 16 Dec 2011 02:34:19 GMT
This is good informative article.]]>kelvinpl80Fri, 16 Dec 2011 02:34:19 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorTue, 13 Dec 2011 15:39:24 GMT
This is a wonderful article. I hope your PPT presentation had fewer grammatical errors: "....on the CIO Update web site entitled Top 10 Reasons to Dump PowerPoint. "]]>PHWiestTue, 13 Dec 2011 15:39:24 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-litigation-hold-141560#commentsAnchorMon, 12 Dec 2011 06:28:22 GMT
I was very encouraged to find this site. I wanted to thank you for this special read. I definitely savored every little bit of it. Ealing Taxi ]]>avrilsmithMon, 12 Dec 2011 06:28:22 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-sp2-litigation-hold-141560#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorMon, 12 Dec 2011 04:48:40 GMT
Tony, Microsoft states you should enable Circular Logging (there, I said it) when using "Native Data Protection" in Exchange without proper backups. "To prevent a buildup of log files, you enable circular logging for your replicated databases." http://technet.microsoft.com/en-us/library/dd876874.aspx#FleMaiPro ]]>Michel de RooijMon, 12 Dec 2011 04:48:40 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorWed, 07 Dec 2011 12:24:27 GMT
So is keeping the separation of logs and database still the better option to use?]]>CajuntankWed, 07 Dec 2011 12:24:27 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-2010-sp2-debut-141487#commentsAnchorTue, 06 Dec 2011 13:48:39 GMT
Probably, most people that are using trusted SSL certificate will find it as a relieve, that the Renew Certificate wizard has been finally "fixed". It used to generate a binary encoded CSR (Certificate Signing Request), which is unusable with most trusted CA: http://www.netometer.com/samples/snapshots/pre-SP2-renew-SSL.png Note, the "binary encoded" switch in the command executed by the wizard, in the snapshot above. In SP2, you can use the wizard and renew your trusted SSL certificate, without any problem: http://www.netometer.com/samples/snapshots/SP2-renew-SSL.png Note, the removed binary encoded switch in the command, which results in the default Base64 CSR that you need. http://www.netometer.com/samples/snapshots/SP2-request-SSL.png]]>NetoMeterTue, 06 Dec 2011 13:48:39 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-2010-sp2-debut-141487#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-2010-sp2-debut-141487#commentsAnchorTue, 06 Dec 2011 13:30:19 GMT
Probably, most people that are using trusted SSL certificate will find it ]]>NetoMeterTue, 06 Dec 2011 13:30:19 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/exchange-2010-sp2-debut-141487#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-passwords-expiring-141205#commentsAnchorMon, 05 Dec 2011 17:25:05 GMT
Microsoft should seriously consider a dual-authentication mode for the enterprise version where passwords can be set not to expire.]]>Ian RayMon, 05 Dec 2011 17:25:05 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-passwords-expiring-141205#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/project-plan-features-exchange-server-2010-73/exchange-server-2010/exchange-server-2010-archiving-140655#commentsAnchorSun, 04 Dec 2011 23:39:42 GMT
One very important thing missing from your article is the fact that not all Outlook 2010 SKUs can utilize archiving. We found this out the hard way. We took ALL the precautions mentioned in your article but did not expect this at all. Most of our users have Outlook as a result of Microsoft Office that was purchased through an OEM when we got their computer. The rest have it from Office Standard 2010 through Volume Licensing. Unfortunately, Archiving isn't supported on either of these versions of Outlook. Archiving is only available on the following versions of Outlook. It's been a huge expense for us to have to purchase another version of Outlook for all of our users just so they can have Archiving. Outlook retail licenses Outlook 2010 stand-alone Outlook 2007 stand-alone Outlook 2007 included with Microsoft Office Ultimate 2007 Outlook volume licenses Outlook 2010 stand-alone Outlook 2010 included with Microsoft Office Professional Plus 2010 Outlook 2007 stand-alone Outlook 2007 included with Microsoft Office Professional Plus 2010 Outlook 2007 included with Microsoft Office Enterprise 2007 Reference http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx?redir=0]]>kaplantruckingSun, 04 Dec 2011 23:39:42 GMThttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/project-plan-features-exchange-server-2010-73/exchange-server-2010/exchange-server-2010-archiving-140655#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-passwords-expiring-141205#commentsAnchorMon, 28 Nov 2011 16:17:58 GMT
It's been pointed out to me that the new version of the Office 365 sign-in assistant supports password expiration notification. Phew! 32-bit version: http://g.microsoftonline.com/0bd00en-us/568 64-bit version: http://g.microsoftonline.com/0bd00en-us/569 ]]>TRedmondMon, 28 Nov 2011 16:17:58 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-passwords-expiring-141205#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/microsoft-certified-master-141336#commentsAnchorMon, 28 Nov 2011 09:09:25 GMT
There's no doubt that the MCM training is worth the cost based on the quality of the information, the access to members of the Exchange development group, and the ongoing contact with others who attend a rotation. However, the value is entirely gained by the individual and an organization might have a different view. Jeff's points about future versions of Exchange are good. MCM training delivers huge value for whatever version of Exchange is covered at the point when someone visits Redmond. It probably also lays a good foundation for future releases, but there will always be change and even complete rewrites in a new version of Exchange and anyone who wants to become an MCM-Exchange will have to continue to keep their knowledge refreshed to stay at the same level over time.]]>TRedmondMon, 28 Nov 2011 09:09:25 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/microsoft-certified-master-141336#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/microsoft-certified-master-141336#commentsAnchorWed, 23 Nov 2011 17:56:50 GMT
I'd like to point out that my rotation (September 2011) was the first to include three days of unique and intensive Office365 content. We covered all the different types of migrations and mixed environments. This is the same content that will be offered to other MCMs as a follow-up course in the near future. Since this is an article focusing on the cost of MCM training, it should be noted that the follow-up courses and upgrades (for example, E15) are extra. However, I can tell you that the information learned here is second to none. It's also important to mention that the relationships you make during your rotation and the MCM distribution group are beyond value. As an MCM, I can bounce ideas and questions off the best minds in the Exchange world. This is something you just don't get with any other training.]]>jguilletWed, 23 Nov 2011 17:56:50 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/microsoft-certified-master-141336#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorFri, 18 Nov 2011 17:16:40 GMT
Well, I'm not a great fan of lagged database copies because the process of data recovery from a lagged copy is completely non-automatic and therefore prone to error. I prefer to make use of some of the intelligent snapshotting that storage vendors have available today. And anyway, even if technology provides a technical answer to the issue of data protection, it still doesn't address the business and audit requirements that often determine that backup copies are required. TR]]>TRedmondFri, 18 Nov 2011 17:16:40 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorFri, 18 Nov 2011 10:08:18 GMT
Assuming you 1) place logs and databases on separate disks 2) have atleast 3 DAG copies with circular logging turned on 3) include lag copy I don't see why native protection could not replace traditional backups. The key is providing enough space for lagged transaction logs and since it can only be lagged to a max of 14 days, to ensure that is enough time to satisfy company policies around backup retention. Jeff]]>jsgirottoFri, 18 Nov 2011 10:08:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-2010-transaction-logs-cherished-141242#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorThu, 17 Nov 2011 17:46:34 GMT
Microsoft is definitely heading in the right direction with the Office 365 troubleshooter tool, however Kim makes a good point in that this will lead to confusion for the inexperienced user and should only be used by IT support staff. If you engage a microsoft online partner and have the migration completed by professionals, you should not experience that many issues as office 365 is pretty streamlines. CTX Solutions are offering free Office 365 migration/implementation services, so you have no excuse http://www.ictinabox.co.uk/office365.html]]>jamie.costaThu, 17 Nov 2011 17:46:34 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorWed, 16 Nov 2011 01:04:23 GMT
@Kim121, I agree with you that this tool could lead inexperienced users into some confusion. However, on the upside it's good to see Microsoft investing in tools that help to troubleshoot problems and we can expect that future versions will be both more intelligent and comprehensive. At least, that's what I hope. TR]]>TRedmondWed, 16 Nov 2011 01:04:23 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorTue, 15 Nov 2011 11:53:47 GMT
I think this will lead to more confusions and error to unexperienced users. They should stick to search engine capabilites for easier results. ]]>kim121Tue, 15 Nov 2011 11:53:47 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorMon, 14 Nov 2011 09:50:24 GMT
last windows update: no more Error on closing the Exchange console]]>Luis LopesMon, 14 Nov 2011 09:50:24 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorFri, 11 Nov 2011 18:25:26 GMT
Every new platform discovers new ways of consuming IT resources...]]>TRedmondFri, 11 Nov 2011 18:25:26 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorFri, 11 Nov 2011 11:20:18 GMT
I thought cloud solutions were supposed to free up IT resources.]]>Ian RayFri, 11 Nov 2011 11:20:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-troubleshooter-141203#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorMon, 07 Nov 2011 12:50:52 GMT
@highlander257: I anticipate that you will have to put the PSTs onto network file shares on Windows servers, if only because the Mailbox Replication Service (MRS) will process the imports - and it doesn't work with Novell. @info: I heard that Microsoft will be able to scan PCs for errant PSTs. However, the truth of the statement will be seen when the software is released.]]>TRedmondMon, 07 Nov 2011 12:50:52 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorFri, 04 Nov 2011 09:39:03 GMT
Tony, Do you know if the Microsoft PST tool will work on Novell Netware File servers, because all of the users pst's are on novell netware file servers??]]>highlander257Fri, 04 Nov 2011 09:39:03 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorThu, 03 Nov 2011 07:06:18 GMT
Tony- It sounds like MS is only importing network PST's and does not mention being able to import desktop PST's which may still leave large oppotunities for 3rd party importing software since desktop PST's are scattered wildly in a lot of organizations. Do you know if desktop PST's are part of its planned functionality?]]>InfoThu, 03 Nov 2011 07:06:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server-2010/exchange-pst-capture-tool-141134#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorSat, 29 Oct 2011 06:04:37 GMT
I think your advice to practice is right on. It's so easy to detect when a presenter does not know their material well because they have thrown some slides together. We'll have to see what happens next week at Connections!]]>TRedmondSat, 29 Oct 2011 06:04:37 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorThu, 27 Oct 2011 09:45:09 GMT
I have to argue that PowerPoint is not the problem. The presenter is the problem. If the presenters at your conference are smart enough to be there, they're smart enough to know -- or investigate as you have -- what makes a great presentation (what makes the presenter look good/smart). While your points are valid, I think your article would have been more useful had they been more solution-oriented. "Design your presentation to encourage your audience to take notes. Science shows that people learn more with this activity. That means writing an insightful headline with a very appropriate graphic will go a lot further than a slide full of bullet points." Or, "Practice. Practice. Practice. Your audience will figure out in a heart beat that you created your slides during your flight on the way to the presentation." Sandy Microsoft Office PowerPoint MVP P.S. I've seen the HP template. It is a monster for the everyday user. ]]>pptwizThu, 27 Oct 2011 09:45:09 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorWed, 26 Oct 2011 19:44:37 GMT
I recently underwent presentation training at work, and got heavily dinged for my slides being too wordy. Since the nature of the presentations I give tends to be technical/educational, I had a hard time wrapping my brain around that criticism, however it really has changed the way I put together a deck, and I think results in a better experience for the audience. I was told I go should go without slides whenever possible, but I agree that isn't really viable in many circumstances. One of the best takeaways from the training was the introduction (for me, at least) of what happens when you hit the B key while in a slideshow - it turns the projector display off so you can talk without the distraction of the slides.]]>MissyKosWed, 26 Oct 2011 19:44:37 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/word/powerpoint-140989#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorTue, 25 Oct 2011 11:55:35 GMT
While the Exchange Powershell is clearly powerful, so is C, Java and Assembly. Doesn't mean I want to change careers to a developer. heres to hoping MS gives us a few more GUI options...]]>BrentologistTue, 25 Oct 2011 11:55:35 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/cloud-application-reviews-140707#commentsAnchorSat, 15 Oct 2011 13:17:03 GMT
I agree that reviews provide a snapshot of features and functionality at a particular point in time. More importantly, the good reviews put this information in context with the author's experience and views about how the suites will develop over time to give readers a perspective of how the suites might fit with the IT strategy of their companies. However, I still hold to my belief that the current application suites are a tad immature for much more informed comment and that it will take us some time to figure out just what suite is best when assessed against many different criteria - features, operational, support, SLA, and so on. TR]]>TRedmondSat, 15 Oct 2011 13:17:03 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/cloud-application-reviews-140707#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-plan-140802#commentsAnchorFri, 14 Oct 2011 10:33:10 GMT
In the article you mentioned the "migration from public folders to Office 365." If you open thethe linked Microsoft document, the in the document properties the title is actually, "Google Apps Competitive Discussion Guide." Thought that was an interesting twist! ]]>bwadminFri, 14 Oct 2011 10:33:10 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-plan-140802#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-plan-140802#commentsAnchorFri, 14 Oct 2011 10:32:14 GMT
In the article you mentioned the "migration from public folders to Office 365." If you open thethe linked Microsoft document, the in the document properties the title is actually, "Google Apps Competitive Discussion Guide." Thought that was an interesting twist! ]]>bwadminFri, 14 Oct 2011 10:32:14 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/office-365-plan-140802#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/cloud-application-reviews-140707#commentsAnchorThu, 13 Oct 2011 13:09:15 GMT
The question of "better" or "worse" is hard to answer, especially since the suites in the market are so different, and as you said, keep evolving so fast. But reviews can tell you if one suite or the other is an immediate fit. Reviews can also make you aware of the broad direction in which the suite is going. ]]>pankajunkThu, 13 Oct 2011 13:09:15 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/cloud-application-reviews-140707#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-achieves-sla-performance-140773#commentsAnchorTue, 04 Oct 2011 08:17:01 GMT
Tony, I am confused. You give kudos to Google for achieving 99.984% and 99.99% availability. You also mention the two major Office365 incidents. You then go on to say "...I think that Office 365 will prove to be much more reliable over the long term." On what do you base this opinion? You did not mention the duration of the two major Office365 outages, nor did you mention that for one of the outages Microsoft did not acknowledge a problem for over 90 minutes. And while alluding to the ongoing performance and reliability of BPOS, you provide no indication that Microsoft has learned lessons and improved operations for Office365. In fact, the early troubles for Office365 indicate that Microsoft still has difficulty managing a multi-tenant environment. Office365 is a package of "2010" generation servers running as virtualized systems on shared hardware. Exchange 2010 and its security architecture are fundamentally single-tenant in design. Until Microsoft can figure out how to run a multi-tenant cloud using with a single-tenant architecture (think square peg and round hole), you should not expect the reliability of Office365 to improve. Looking at the reasons behind outages provides insight into future performance (http://cumulusglobal.com/cms/friday-thought-all-outages-are-not-equal). ]]>afalconTue, 04 Oct 2011 08:17:01 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-achieves-sla-performance-140773#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-achieves-sla-performance-140773#commentsAnchorMon, 03 Oct 2011 16:26:18 GMT
I noticed only two Google Apps for Business outages - calendaring for about 30 minutes and docs list for approximately an hour. Calendar outage I noticed when my iPhone reminded me of a meeting but my Google Calendar window didn't pop up a notice simultaneously. When trying to access the calendar online, it was not working. No big deal... had to go to the meeting anyway, and by the time the meeting was over, so was the outage. The docs list outage was more frustrating. It happened shortly after I returned from lunch. I wanted to search for a particular string and match it to documents, but the docs list would not open. I ended up having to use the Google Site I created to run through the documents one by one to search for the keyword. By the time I became very frustrated with this and had moved on to other tasks, the docs list popped back up and I could again perform a quick search. These two instances aside, I have had rock-solid performance with Google Apps. Some workers feel more comfortable being able to blame the flakiness of local file servers and email servers on IT employees... but after years of dealing with multi-day outages on local servers, 30 minutes to an hour being the new big deal outage is quite welcome.]]>Ian RayMon, 03 Oct 2011 16:26:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-achieves-sla-performance-140773#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorMon, 03 Oct 2011 12:33:58 GMT
The JOY? While I do see that many new options become available with Powershell I do not agree that it's a "simple" replacement for the former GUI consoles. Your argument that all it takes is a little learning isn't exactly true. If you are to be proficient at it then you need to know the scripting language. To be fair we all should have at least some background in how script work but even if you do, there are still many commands, objects, arguments, etc. that are specific to Exchange. In other words, a lot to learn. Saying that you can find someone elses examples to use is a cop out on MS part. What are they pretending to be - open source? I've had more than one simple management issue that resulted in a great deal of time doing research to get it entered just right when the MS example didn't work. It isn't rocket science or even having to learn a complete programming language but to say it's simple to learn is absolute BS. Really I think MS went too far in removing some basic day to day operational controls from the GUI. Your example is supposed to show how easy it is to use PS instead but I say it proves just the opposite. While it may be nice in some environments to have the ability to do what you are describing, the script you give certainly isn't short and simple compared to what could take about 5 mouse clicks in a GUI and is a basic need for an admin. By all means, keep Powershell, it does add some great access to the server but quit gutting the GUI. I can only assume MS is either too lazy to program the GUI or they are trying to push the part time admin into succumbing to cloud based managed services. ]]>MRMon, 03 Oct 2011 12:33:58 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorMon, 03 Oct 2011 12:01:57 GMT
The JOY? While I do see that many new options become available with Powershell I do not agree that it's a "simple" replacement for the former GUI consoles. Your argument that all it takes is a little learning isn't exactly true. If you are to be proficient at it then you need to know the scripting language. To be fair we all should have at least some background in how script work but even if you do, there are still many commands, objects, arguments, etc. that are specific to Exchange. In other words, a lot to learn. Saying that you can find someone elses examples to use is a cop out on MS part. What are they pretending to be - open source? I've had more than one simple management issue that resulted in a great deal of time doing research to get it entered just right when the MS example didn't work. It isn't rocket science or even having to learn a complete programming language but to say it's simple to learn is absolute BS. Really I think MS went too far in removing some basic day to day operational controls from the GUI. Your example is supposed to show how easy it is to use PS instead but I say it proves just the opposite. While it may be nice in some environments to have the ability to do what you are describing, the script you give certainly isn't short and simple compared to what could take about 5 mouse clicks in a GUI and is a basic need for an admin. By all means, keep Powershell, it does add some great access to the server but quit gutting the GUI. I can only assume MS is either too lazy to program the GUI or they are trying to push the part time admin into succumbing to cloud based managed services. ]]>MRMon, 03 Oct 2011 12:01:57 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorFri, 30 Sep 2011 11:22:17 GMT
Since Powershell is a object orientated language, there is no reason for it not to have a GUI.]]>OrmanFri, 30 Sep 2011 11:22:17 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorWed, 28 Sep 2011 14:06:02 GMT
Tony, yes I have a problem with PowerShell. It is a quantum leap in the wrong direction. I like command line indeed but not PowerShell. Command line commands must be short, easy to understand and easy to remember, easy to implement. Power is not short; typical commands covers a line, frequently more than one line. They are not easy to understand and remember. They are not easy to implement either. Almost generally, you must search, to find the proper command first and then to learn the syntax. I think PowerShell has no future. So, I may attend your PowerShell courses, with pleasure. Just if I am to be paid!]]>murat yildirimogluWed, 28 Sep 2011 14:06:02 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-ready-to-tackle-outlook-140634#commentsAnchorWed, 28 Sep 2011 12:44:43 GMT
Like all analysts, Gartner likes to get their name out there into the public gaze because it helps them to sell reports, consulting, subscription fees, and conferences. Sometimes it's good to make a splash with a couple of well-chosen remarks that reporters can pick up and create a story and I think that's what happened here. On the other hand, Gartner might well believe this stuff. If so, it would be interesting to debate against them.]]>TRedmondWed, 28 Sep 2011 12:44:43 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-ready-to-tackle-outlook-140634#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorWed, 28 Sep 2011 12:40:19 GMT
Have a look at the latest blog post by Don Jones where he explains that PowerShell is not a command line language. It resembles CLIs at times because that's how you invoke PowerShell via consoles such as EMS. However, the essential point here is that all Exchange management is built on top of PowerShell and that (to me at least) is a damn good reason to get to know it. Murat, insulting myself and Jeffrey Snover might make you feel happy but it really does you no good. If you stay embedded in ignorance I fear that your career will go nowhere. On the other hand, folks like Jeffrey Snover can look back on long and tremendously inventive careers where they made a huge difference to computing. You haven't, so enjoy your state of mind.]]>TRedmondWed, 28 Sep 2011 12:40:19 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorWed, 28 Sep 2011 12:36:35 GMT
You're correct that you can use Performance Monitor to view the counters but that wasn't the point I was making. There is no equivalent feature in EMC or ECP (Microsoft's management tools for Exchange; performance monitor is a general purpose tool for Windows). The point here is that you can use PowerShell to extract and report information relatively easily about some interesting data concerning Exchange servers. Furthermore, if you don't want to write the code, there's a fair chance that someone else will have done it for you. Murat, you really seem to have a problem around PowerShell. Maybe you should come to an Exchange 2010 Maestro training event so that Paul Robichaux and I can help you understand its true value for Exchange administrators? TR]]>TRedmondWed, 28 Sep 2011 12:36:35 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorTue, 27 Sep 2011 04:22:47 GMT
Tony, you must be surely joking when you say "Theres no equivalent function in any of Microsofts management tools provided for Exchange so this is an example of how some relatively straightforward code can add real value. " The scripts seems to take the info from the performance counters and you can observe these numbers using the built in Performance Monitor console. I checked and saw that the counters are MSExchange OWA\Current Unique Users and MSExchange RPCClientAccess\Active User Count. So, There IS an equivalent console that gives the info this cryptic script delivers.]]>murat yildirimogluTue, 27 Sep 2011 04:22:47 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/joy-powershell-exchange-administrators-140623#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorThu, 22 Sep 2011 16:57:43 GMT
First of all, the syntax examples that you've selected do not represent those that most Exchange administrators will use. I also disagree with the assertion that you have to resort to EMS on a frequent basis to do "serious work". Like any tool, you use EMS to do the work where the tool makes sense. For example, processing a set of mailboxes to generate a report of mailbox sizes. This has to be done in EMS because there isn't an option in the EMC or ECP GUIs. Routing any PowerShell commands through WMI will always require torturous code because WMI was never designed to be accessed by PowerShell. However, the only time that you need to use WMI with Exchange is to access Exchange 2003 objects as both Exchange 2007 and Exchange 2010 support PowerShell natively. As more and more Windows components support PowerShell, you'll have to use WMI less and less and that's a good thing. As Don points out, Microsoft understands that some PowerShell syntax could be clarified and streamlined. They plan to do this in PowerShell 3.0 and the next major release of Exchange will probably support PowerShell 3.0, so we get a gain there. You then comment about commands changing frequently. This has been the case with technology since the dawn of IT. In the case that you cite, the change is necessary for two reasons. First, to replace the need to install Outlook on Exchange mailbox servers. Second, to align the command names with the other mailbox manipulation tasks performed by the Mailbox Replication Service (MRS). There's logic here. And anyway, how hard is it to get up to speed with a few commands? Finally, your assertion that New-MailboxImportRequest doesn't work is just laughable. There are situations when PSTs that contain corrupt or very large items can't be imported but generally the cmdlet works as advertised. Certainly this has been my experience. So to make a leading statement with zero backup data is just plain silly.]]>TRedmondThu, 22 Sep 2011 16:57:43 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorThu, 22 Sep 2011 16:45:55 GMT
@Murat, The examples that you have selected are not representative of the PowerShell commands that most Exchange administrators would need to use in day to day production. Routing any PowerShell through WMI is unnatural and only happens because a lot of Windows does not provide PowerShell modules to allow direct access. Thus, you have to route through WMI and experience the tortuous syntax that the mix and match of two very different languages demand. But you don't have to use WMI to manage Exchange 2007 or Exchange 2010 objects because these versions offer native PowerShell support. You only have to resort to WMI if you need to manage Exchange 2003 through the shell. And as Exchange 2003 was never designed to be managed through the shell, you end up with a mess. As Don Jones has pointed out, Microsoft recognizes that current PowerShell syntax can be cleaned up and they are doing this in PowerShell 3.0. Exchange will likely support PowerShell 3.0 in its next major release, so I think that's a good thing. Finally, commands changing as products evolve is something that has happened since the dawn of technology. The example you select is a very good illustration of how Microsoft is attempting to put order on PowerShell commands for Exchange. The Import-Mailbox and Export-Mailbox cmdlets had to be replaced because they depend on running Outlook on an Exchange server to be able to access PST contents. And while it's true that Microsoft could simply have updated the cmdlets with new code to call the provider used by New-MailboxExportRequest and New-MailboxImportRequest, they elected to change the name of the cmdlets to match those used for the other mailbox manipulation cmdlets processed by MRS running on the CAS. I don't see this as a bad thingl. Your assertion that New-MailboxImportRequest doesn't work "for most of the time" is laughable. The cmdlet works. Not all the time (old PSTs containing old items cause problems), but it does work.]]>TRedmondThu, 22 Sep 2011 16:45:55 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorThu, 22 Sep 2011 14:47:41 GMT
sorry Tony, I didn't think "crazy" was rude but I know it is now. Tony, there is a GUI console, you are right. But you can do only trivial things with it. If you want some serious tasks you are allways routed to command shell. Command shell is cryptic. Look at the following commands from Don Jones: Get-Service | Where-Object -filterScript { $_.Status -eq 'Running' } Gsv | Where { $_.Status -eq 'Running' } get-wmiobject -class win32_networkadapterconfiguration | where-object { (get-wmiobject -class win32_networkadapter -filter "physicaladapter=true" | select -expand name) -contains $_.description } The first command lists the running services. The second one is PowerShell 3.o version of that command. Third command lists the physical network adapters. Don't take it wrong: Third command covers more than one line but it must be written on the same line. Don't you think they are cryptic? Besides this, commands change frequently. For example, Exchange 2007 had import-mailbox cmdlet but Exchange 2010 SP1 had new-mailboximportrequest. Do you know what? new-mailboximport cmdlet does not work for most of the times and it is well-known fact.]]>murat yildirimogluThu, 22 Sep 2011 14:47:41 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorThu, 22 Sep 2011 10:37:48 GMT
@Murat, Well, the Exchange developers give you both EMC and ECP if you want to work with a GUI. There are reasonably few instances where you have to use the shell. The point is that you can use EMS if you want to automate common tasks - and that there are tons of examples how to use EMS in productive ways. I'll be writing on this topic very soon. I also disagree that EMS is cryptic. The commands are named in a reasonably predictable fashion (gee, what is Set-Mailbox likely to do?) and once you learn the naming convention, you should have no difficulty mastering the shell. As to your comment about Jeffrey Snover, you're entitled to your opinion but you don't have to be rude. And as I type this, I wonder why I even bothered to respond to someone who obviously doesn't know how to be civil and restrained in their commentary. Have a nice day.]]>TRedmondThu, 22 Sep 2011 10:37:48 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorThu, 22 Sep 2011 07:02:55 GMT
Tony, I don't think PowerShell is a progress. And I have good reasons to think like that. First, we are Windows guys, not command line oriented Linux guys. We had been completing our tasks using GUI tools and it was just good. For us, real people in the trenches, the task is important and to complete a task as quickly as possible is more important. For these two reasons, GUI is good and sufficeintent.Up until this PowerShell mess. PowerShell is bad because it is not easy, intuitive, productive. For any non-trivial task you must refer to Google and make a search, learn a cmdlet and its cryptic usage. And after you used this cmdlet, you just forget it. Next time, you Google it again. Last year, I implemented the upgrade of the mail system for a big government office in my country. Switch was from Exchange 2003-2007 to 2010. I used dozens of PowerShell commands. None of them was in my mind and after the process none of them is in my mind either. It's shame because I'm an experienced systems engineer. And now, thousands of new cmdlets are coming. I think Snover is just crazy. And so you are.]]>murat yildirimogluThu, 22 Sep 2011 07:02:55 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/powershell-gift-giving-exchange-140470#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-ready-to-tackle-outlook-140634#commentsAnchorTue, 20 Sep 2011 08:52:35 GMT
Tony, A really well written and authoritative response to the Gartner coverage yesterday. I wanted to take time and write a similar analysis, thank you for handling it. That needed to be said. Like you, I'm left wondering what influences Gartner is this regard. Feels like naked pandering to Google, but to what end? Nice job, I look forward to following your blog in the future. -S]]>GaittenTue, 20 Sep 2011 08:52:35 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-ready-to-tackle-outlook-140634#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorFri, 16 Sep 2011 12:40:51 GMT
Well, I disagree that Exchange is too large and complex. I think the product has evolved to meet the needs of customers - mostly enterprise customers at this stage. But that's probably OK because I think that most of the small to medium businesses that use on-premises Exchange today and who possibly are confused by the power and range of Exchange will move to Office 365. Customers that stay with the on-premises version will have specific reasons to do so and will be prepared to invest the time necessary to tweak Exchange to meet their needs. As to the in-place upgrade argument, I don't buy the need for this to happen at all. There has been too many changing parts (including a transition to 64-bit Windows OS) to make it practicable to engineer a high-quality in-place upgrade process that is capable of catering for the huge array of environments into which Exchange is deployed. Of course, everyone is entitled to their own views... TR]]>TRedmondFri, 16 Sep 2011 12:40:51 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/email/blasted-bcc-140471#commentsAnchorFri, 16 Sep 2011 12:39:24 GMT
Although this may not be the intention, I find that using "BCC" can be underhanded and sneaky (at least the way some people employ the feature). For me, a more forthcoming way to communicate is to forward the message directly to the recipient, separately. That accomplishes two things: FIrst you can explain why you are forwarding the message to the recipient. Secondly it avoids the reply-all issue that you describe above. ]]>bwadminFri, 16 Sep 2011 12:39:24 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/email/blasted-bcc-140471#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorFri, 16 Sep 2011 02:24:08 GMT
The problem isn't the complexity of Exchange, it is the flawed architecture of having MMC dependent in any way, shape or form on IE! It no doubt harkens back to that flawed decision by Microsoft to integrate the browser into the Operating System. It has bitten them many times, here is just another example. I agree 100% with Murat on the in-place upgrade, or lack there-of with Exchange. How does that approach reduce cost of ownership for businesses? Doesn't happen in IBM/Lotus Domino architecture.]]>ccontessaFri, 16 Sep 2011 02:24:08 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorWed, 14 Sep 2011 07:44:13 GMT
Tony, you say "Gaps in coverage are regrettable but probably inevitable over the lifetime of a very complex and very large product". maybe the real reason is this: Exchange is very complex and very large. Most probably too complex and too large. There hasn't ever a need to be so complex and so large. E-mail should have been like utilities: you turn the tap and water flows. Exchange has not been simple and easy to implement, to use, to maintain, starting with Exchange 2007. There are too many roles, too many command line commands, too many dependencies. Everything is too much. And you get so little. It is just contrary to what Microsoft claims "Do more with less". What can be done now? The main idea behind the Exchange Server must be changed. The structure must be simple: simple to implement, simple to operate, simple to maintain. And Microsoft must remember in-place upgrade again: For the last two versions of Exchange, you can't do in-place upgrade. ]]>murat yildirimogluWed, 14 Sep 2011 07:44:13 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/strange-case-ie9-mmc-exchange-light-appears-tunnel-140523#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/bad-week-cloud-microsoft-google-suffer-outages-140501#commentsAnchorMon, 12 Sep 2011 10:38:35 GMT
Perhaps the cloud is better than some internal IT departments and each organization should remember that nothing is perfect when considering how best, if at all, to leverage it. This is a reminder that no system, platform or technology is 100% immune to problems and in the interconnected world, there are always multiple points of failure with very few exceptions. While software and systems can be improved, whats missing here is the notion that people and policies they follow can also be improved to avoid problems. Chris Rich Product Manager NetWrix Corporation NetWrix is #1 for Change Auditing: Simple, Lightweight, Affordable]]>ChrisMon, 12 Sep 2011 10:38:35 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/bad-week-cloud-microsoft-google-suffer-outages-140501#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-regains-offline-capabilities-threat-exchange-online-140419#commentsAnchorFri, 02 Sep 2011 14:51:14 GMT
The comments are as always very well put. However, we must also take into account that GMail (paid version, but so is office 365) can also be used with Outlook with pretty much the same functionality with Google sync. The offline gmail is an extra option not yet matched by Microsoft.]]>resciosFri, 02 Sep 2011 14:51:14 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-regains-offline-capabilities-threat-exchange-online-140419#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-regains-offline-capabilities-threat-exchange-online-140419#commentsAnchorThu, 01 Sep 2011 10:10:53 GMT
I've been an Outlook user for 11 years and a GMail user for 4. From a user perspective GMail has had a better value proposition than Outlook since 2007. GMail loads fast, works well, and is accessible from every internet connected device. Getting offline access back is just gravy. I had the previous offline functionality and rarely used it.]]>David SmithThu, 01 Sep 2011 10:10:53 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/gmail-regains-offline-capabilities-threat-exchange-online-140419#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/hardware/reflections-hprsquos-announcements-140308#commentsAnchorWed, 31 Aug 2011 10:28:18 GMT
Autonomy may turn out to be a complete bust for HP. Some independent industry analysts are asking some searching questions over the relationship between Autonomy's marketing and the reality of its products: http://blogs.forrester.com/leslie_owens/11-08-26-what_is_autonomy_without_its_marketing http://www.realstorygroup.com/Blog/2215-Another-look-at-the-Autonomy-IDOL-OEM-business ]]>Jerry GWed, 31 Aug 2011 10:28:18 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/hardware/reflections-hprsquos-announcements-140308#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/auditing-administrator-actions-with-exchange-2010-129720#commentsAnchorSun, 28 Aug 2011 15:24:58 GMT
Is it possible to forward all audit logs to new mailbox in exchange 2010 sp1 exchange 2010 sp1 adminaudit log mailbox has hidden by defualt, is it possible to forward all log entired from hidden mailbox to new audit mailbox Please suggest.]]>manoSun, 28 Aug 2011 15:24:58 GMThttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/auditing-administrator-actions-with-exchange-2010-129720#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorWed, 17 Aug 2011 12:57:15 GMT
Tony, to make things work again, many people from the Exchange team must be fired, starting from the managers. A new and fresh management is needed desperately. ]]>murat yildirimogluWed, 17 Aug 2011 12:57:15 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorWed, 17 Aug 2011 12:08:33 GMT
Adding 'mmc.exe' (yes, a filename) to the Trusted Sites list in IE9 worked as a solution for me. Btw, the TMG 2010 management console also has problems with IE9. I had to change some settings in the TabsHandler.htc file to get it to work with IE9. See http://blogs.technet.com/b/asiasupp/archive/2011/04/29/internet-explorer-9-ie9-and-forefront-tmg-2010.aspx for more info on that. Ashley]]>FlensjeWed, 17 Aug 2011 12:08:33 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorhttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorWed, 17 Aug 2011 10:40:31 GMT
This affects much more than just servers, Tony. The majority of users affected are those who run the Exchange 2010 management tools from remote Windows 7 machines with IE9 installed. In a lot of managed environments, IE9 was pushed out to desktops and users don't have the option of simply uninstalling it. It also doesn't help that Microsoft is now pushing IE9 as an Imporant update through WSUS. I've been in contact with the Exchange and Internet Explorer 9 team since April. My contacts say that a fix will be included in a Q4 service update for IE9. For many, like me, that is far too late. See my blog for further info: http://www.expta.com/2011/04/issue-with-ie9-and-exchange-2010.html Jeff Guillet, [MVP] ]]>jguilletWed, 17 Aug 2011 10:40:31 GMThttp://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/exchange-server/why-cant-microsoft-ie9-work-exchange-management-console-140165#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorTue, 09 Aug 2011 14:18:40 GMT
First off, I dont recommend patching/upgrading to anyone unless the patch contains the feature or fix needed to address a current problem or need. That said, I feel the greatest point to take away here is that the group acknowledged the problem and worked quickly to resolve it while explaining what they were going to do moving forward to prevent it from happening again. For most, this gives them many points for sustaining positive customer relationships. Its always best to acknowledge mistakes and work hard to correct them swiftly and completely. Chris Rich Product Manager, NetWrix Corporation NetWrix is #1 in Change Auditing: Simple, Lightweight, Affordable www.netwrix.com ]]>ChrisTue, 09 Aug 2011 14:18:40 GMThttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorFri, 05 Aug 2011 01:29:45 GMT
I agree - it was bewildering the setup. we actually have Lotus Domino on site too - it was embarassing - how could i say Exchange was better? sure, features are great - but management? Why is Exchange still using it's own DB? all our other other MS products are using SQL.(SCCM, SCOM, MOSS, ...) not gmail though, surely murat? hotmail?]]>MarkFri, 05 Aug 2011 01:29:45 GMThttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorFri, 29 Jul 2011 02:25:20 GMT
Exchange team loast our confidence long time ago when they released Exchange 2007. The main problems with it were: 1) Lack of upgrade: You couldn't in-place upgrade your existing Exchange 2003 installation. 2) Complexity: While Exchange Server had been allways easy to install and operate, Exchange 2007 was a nightmare from a management point of view. It had too many roles while Exchange 2003 had two simple roles. 3) emphasize on command prompt: While Exchange 2003 and prior versions rely on graphical user interface, Exchange 2007 necessitated the use of a queer command prompt. Now, my suggestions for the Exchange Admins are like that: Switch to gmail. If you have less than 10 users, switching is free. If you have more than 10 users switching is less expensive and easier. Switch and forget the mess 2007-2010 brought. ]]>murat yildirimogluFri, 29 Jul 2011 02:25:20 GMThttp://www.windowsitpro.com/article/exchange-server-2010/microsoft-works-regaining-user-confidence-software-fiascos-140000#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server/office-365-deployment-options-135867#commentsAnchorWed, 06 Jul 2011 02:11:59 GMT
Our non profit is migrating away from BPOS and the cloud in general. Our experience with BPOS was terrible. MS needs to understand service level agreements and train their people about what they mean. Our experience with MS support was not just bad, but amateur. ]]>Wed, 06 Jul 2011 02:11:59 GMThttp://www.windowsitpro.com/article/exchange-server/office-365-deployment-options-135867#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/auditing-administrator-actions-with-exchange-2010-129720#commentsAnchorFri, 06 May 2011 18:04:19 GMT
Very good article Tony. I have read a lot of the documentation on this in TechNet but makes serval things clear that I was not sure about.]]>mmarth1Fri, 06 May 2011 18:04:19 GMThttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/auditing-administrator-actions-with-exchange-2010-129720#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/compliance/a-first-look-at-exchange-2010-100934#commentsAnchorSat, 27 Nov 2010 23:39:18 GMT
Hi Tony,
Lucky me i found your website. I’m planning to implement exchange 2010 clustering in our company. On the previous previous of exchange 2003, exchange 2007 it requires enterprise for the exchange as well as the operating system.Kindly give me an advice what are the requirements fo implementing exchange 2010.Thanks in advance Waple02]]>MenesesSat, 27 Nov 2010 23:39:18 GMThttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/compliance/a-first-look-at-exchange-2010-100934#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/exchange-server-2010/Exchange-2010-SP1-Upgrade-125644#commentsAnchorWed, 03 Nov 2010 13:23:31 GMT
Certainly SP1 has shown its imaturity amongst Microsoft services packs. We had three nicely operational Exchange servers with DAG working like a tunned clock. It all came down to halt when SP1 was applied to the servers where we lost all three servers due to not being able to communicate with each other. This was the most unfortunate event an administrator could face. Exchange SP1 has waaayyy lot more to get the buy-in from its clients and I’m sure SP2 can take care of SP1 by next year.]]>AbramoWed, 03 Nov 2010 13:23:31 GMThttp://www.windowsitpro.com/article/project-plan-planning-exchange-server-2010-71/exchange-server-2010/Exchange-2010-SP1-Upgrade-125644#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/exchange-2010-mrm-implementing-new-retention-policies#commentsAnchorWed, 18 Aug 2010 08:42:53 GMT
From what I understand, the example provided does not work. After working with people in the technet forums, it seems that the Move action does not work with RPT’s, only Personal Tags.
I myself was unable to get it to work, and after changing the RPT on the Inbox action from MoveToDeletedItems to DeleteAndAllowRecovery, it worked.]]>cmogliaWed, 18 Aug 2010 08:42:53 GMThttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/exchange-2010-mrm-implementing-new-retention-policies#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/exchange-2010-mrm-implementing-new-retention-policies#commentsAnchorWed, 18 Aug 2010 08:35:53 GMT
From what I understand, the example provided does not work. After working with people in the technet forums, it seems that the Move action does not work with RPT’s, only Personal Tags.
I myself was unable to get it to work, and after changing the RPT on the Inbox action from MoveToDeletedItems to DeleteAndAllowRecovery, it worked.]]>cmogliaWed, 18 Aug 2010 08:35:53 GMThttp://www.windowsitpro.com/article/project-plan-features-exchange-server-2010-73/exchange-server/exchange-2010-mrm-implementing-new-retention-policies#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-migrate-exchange-server-2010-72/email/moving-mailboxes-the-exchange-2010-way103651#commentsAnchorSun, 07 Mar 2010 15:48:13 GMT
The approach I take (in Exchange 2007) is to use Scheduled Tasks using a PowerShell script that takes its list of mailboxes from a CSV file.

Its nice to see that Anil still has an active mailbox. Maybe that explains why Tony doesn’t look really happy in his mug shot. (’;

Thanks for the, as always, enlightening article,
don
]]>donSun, 07 Mar 2010 15:48:13 GMThttp://www.windowsitpro.com/article/project-plan-migrate-exchange-server-2010-72/email/moving-mailboxes-the-exchange-2010-way103651#commentsAnchorhttp://www.windowsitpro.com/article/project-plan-migrate-exchange-server-2010-72/email/moving-mailboxes-the-exchange-2010-way103651#commentsAnchorSat, 06 Mar 2010 18:38:17 GMT
The approach I take (in Exchange 2007) is to use Scheduled Tasks using a PowerShell script that takes its list of mailboxes from a CSV file.

Its nice to see that Anil still has an active mailbox. Maybe that explains why Tony doesn’t look really happy in his mug shot. (’;

Thanks for the, as always, enlightening article,
don
]]>donSat, 06 Mar 2010 18:38:17 GMThttp://www.windowsitpro.com/article/project-plan-migrate-exchange-server-2010-72/email/moving-mailboxes-the-exchange-2010-way103651#commentsAnchor