Out of interest, why is your client moving?
With mailboxes that large, I can only imagine the Outlook sync has issues at best.
Company's tend to like support because it gives them someone to blame, not because it actually provides support or makes them more money. It is generally about middle managers playing politics trying to protect themselves, not about doing what is best for the business - either in cost or in ability to support the products. How often do you see commercial support actually being worth the money (outside of hardware support contracts?)
I couldn't imagine running an LOB application or anything mission-critical without proper support. If it goes down, the company's losing thousands of dollars per hour. I'm not going to put a post up somewhere in hopes that someone'll give me the appropriate answer in a reasonable timeframe.
Looking for tool to do an internal audit of Microsoft licensing for a client. What do you guys recommend.
Take a look at the Microsoft Assessment Planning Toolkit (MAP). It's what's recommended by Microsoft. It uses WMI for scanning, so you'll want to make sure you have the firewall exceptions for it enabled.
An RPO/RTO question is a lot more difficult to answer than one might expect. I'm sure that Alex and Scott have a linty of questions that can make it easier, but for a company that hasn't ever looked at these questions before it's likely they have no real understanding of how to answer these requests.
When I first started with my company I was told that we could live without our brand new EHR for 6 days (the downtime the vendor told us we'd suffer if we had a total server failure). The vendor at the time refused to provide installation media/files (they built then shipped the servers to us) and all we had for backups were SQL level backups.
I approached the board with a plan to provide better options, but at that near day one the board stated that 6 days of downtime considering the current setup was acceptable. Of course I nearly passed out that this consider I'd been supporting their phones for the past 4 years and they were nearly unbearable when their phones wouldn't sync for a day to their calendars.
Fast forward a year and a few minor outages later, the tune changed and we could now only afford one day of downtime, so they approved the purchase of Appasure, and we reduced our downtime to a few hours.
Back to the point at hand, if the Docs in technobabble's case haven't experienced downtime in the past they will have unrealistic expectations of either uptime or tolerable downtime.
For RTO, the easiest way to ask it is, "If X fails, how long can the business be without it before it severely impairs the business?" For some folks, it's a few hours, or even more than a day. For others, it's less. For RPO, it's, "If we need to roll back to backups, how far back can we recover to in an emergency without causing undue data loss?" Most folks are ok with the previous night's backup, but not quite everyone. The longest it's ever taken me to determine RPO/RTO has been about 30 minutes.
hi I m doing a migration for a client that is moving from google apps to office 365. So far so good but I ve just checked their mailboxes size and some ( about 8-10 out of 45 ) are about 35-40 Gb in size. They want to move to the mid size business not the E plan ...
as far as size is concerned they are aware they will need to reduce the size of the mailbox soon ( as 50Gb ) limitation.
Is there anything to watch out for when migrating such a massive mailbox ? I m not sure how much time it will take or if it would be easier to do it staged ? any pointers much appreciated !! ;o)
Pity, if they went EOP2 or E3, they'd have unlimited archive storage.
Oh, heck no! There's no way I'm dealing with tickets off-hours unless it's a major work-stoppage emergency. Emergencies happen, sure, put those fires out. Sometimes after-hours maintenance comes up, and sure, I'll do what's needed.
Except for timelines (which I try not go give), my word's spot-on.