Exchange Team blog got an upgrade!
We are excited to announce that Exchange Team blog got an upgrade! We wanted to enrich the experience of visiting our blog site, as well as wanted to improve the site design and add several features to the site. Firstly, you will notice that we are now hosted at the different URL, and our new home is at: http://msexchangeteam.com/ The new "main" RSS 2.0 feed link is: http://msexchangeteam.com/rss.aspx Then, you will notice that the whole site got a visual overhaul, hopefully it is more pleasing to view. Hope you like it! Few other things that are brand new: - The Videos section of the blog. Here we will be placing different videos that we will be recording occasionally - things like short interviews with members of Exchange product group, demos of something cool in Exchange and so on. Who knows, some Exchange party video might make it up there too! - The ability to add attachments to blog posts; no more posting of scripts in the body of the post (which can cause formatting and syntax issues later). All of the "old" links RSS links and feeds should keep on working (so the redirection is in place from old http://blogs.technet.com/exchange to new http://msexchangeteam.com/. We plan to keep this redirection in place for a good while, but just to make sure - you might want to update your RSS clients to point to the new URL so you can keep on getting your dose of Exchange-related goodness without any interruptions in the future! As always, feedback is welcome. Look out for more new features and improvements we are planning! - Exchange Team Blog crewWhy is OOF an OOF and not an OOO?
Here's an interesting historical question - when we say Out of Office, why does it sometimes get shortened to ‘OOF’? Shouldn’t it be ‘OOO’? Inside Microsoft, ‘OOF’ means not just the message which says you’re Out of Office, but it has grown to mean the act of being Out of the Office too - so you’ll get people putting sticky notes on their door saying ‘OOF Thurs & Fri’ or even people verbally saying things like, "Oh, Kevin’s OOF on vacation for the rest of the week’. I suppose that sounds better than "Oh, Kevin’s OOO on vacation ..." OOF was a command used in the days of Microsoft’s Xenix mail system, which set a user as ‘Out of Facility’ - ie Out of the Office. The usage of the term ‘OOF’ just stuck, as did the term ‘Little r’ (e.g. on an email sent to a distribution list, "Who wants to go to the cinema tonight? Little ‘r’ if you’re interested", meaning reply just to me) - as preserved in Outlook with CTRL+R for Reply, and CTRL+SHIFT+R (aka Big R) for Reply All. Ewan DaltonOutlook REST API beta and Outlook REST API v2.0 Deprecation Notice
Today we are announcing thedeprecation ofthe Outlook REST API betaandOutlook REST API v2.0and that they will be decommissioned on November 30, 2022. Once past this date, the services will be retired, and developers may no longer access them.How does your Exchange garden grow?
One question we often get asked when talking to customers contemplating an Exchange upgrade or a switch from a competitor’s mail system is, "how many users per server can Exchange handle?" Nowadays, that’s an open question - it very much depends on what kind of users you have, what kind of storage you’re using and how powerful your servers are. When Exchange 4.0 was released in 1996, a decent server might have had 256Mb of RAM and a 90MHz Pentium processor, with maybe a handful of GBs of SCSI disk in the box and possibly a DAT tape drive. Users’ mailboxes might have been in the 10-20Mb size range, and the average user sent or received only a small amount of email per day. At that time, server sizing was pretty much a function of how much computing horsepower you could afford - the CPU power, disk size & speed and memory capacity available (along with the all-important user profile) would determine the number of users per server, and arbitrary decisions would be made about maximum message sizes, mailbox size etc. Now, it’s possible to buy even mid-range servers that will cope with many thousands of users, and the bottleneck has moved down to the storage level in many instances as user mailboxes have grown in size and we send and receive far more mail, and many larger messages too. We’d be interested in hearing anecdotes about particularly unusual messaging environments you might have - how large do your servers grow? What’s the biggest mailbox you’ve ever seen (assuming you’re not restricting with quotas)? How much data does your total Exchange system manage? What’s the biggest single database - etc, etc... you get the picture. Some factoids to get you started... if you have anything along these lines, please post a comment: - One customer (who is part of the Exchange Technology Adoption Program) sets no limit on message sizes internally - and one time saw a single message with attachments totaling 2.4Gb in size! (which Exchange delivered! - the recipient’s mailbox quota was instantly blown apart though...) - The largest single Exchange 5.5 Public Folder Information Store I’ve come across was 800Gb in size - There’s a limit of 1,000 Exchange 2000/2003 servers in an org - has anyone come close, or hit that limit? - One customer deploys around 250,000 Exchange users per server and has over 9,000,000 users in total (you guessed it, they’re an ISP) - The most heavy user of public folders in the world (that we know about) has about 1,500,000 public folders containing around 8Tb of data So come on: let’s hear your war stories - post a comment with your amazing data :) - Ewan DaltonMicrosoft Ignite 2020 - One Week Away!
In about a week from today Microsoft Ignite 2020 gets underway. It’s quite a bit different this year but the one thing you can be certain of is we have lots of new and interesting content for you to enjoy. This post is to highlight the Exchange, Outlook and Bookings sessions we have created and curated for your viewing pleasure. The links won’t be live until the event starts, but we wanted to give you a peek into what to expect.Exchange and SameSite Updates
The Stable release of the Google Chrome web browser scheduled for release beginning February 17, 2020 features a change in how cookies are handled. Microsoft is committed to addressing this change in behavior in its products and services before the February 4, 2020 rollout date to ensure our customers are minimally impacted.Exchange "12" has a new name!
With Beta 2 approaching, Exchange "12" needed a name. I know the suspense has been killing everyone. Well the wait is finally over: Exchange Server 2007 If you keep hearing the team talk about "E12" , "12", or "Exchange 12" - please understand - it's all the same thing. It just takes a while for us to adjust. Thanks! - Terry MyersonMEC Check: Are You Registered?
Just 8 ½ weeks until the Microsoft Exchange Conference 2014 kicks off in Austin, Texas! We’re putting the finishing touches on sessions, speakers, content, parties, and all of those wonderful and quirky touches that make MEC different from any other conference. If you haven’t registered yet, now is the time, because hotels are filling up fast and your chance to win rock star treatment ends on Feb 10. Here are the key things to know about MEC 2014: When March 31st to April 2nd Where Austin, Texas, the live music capital of the world. Who A diverse group of folks who all share a passion for Exchange. We’ll have an all-star lineup of executive speakers, joined by planeloads of people from the Exchange engineering team, plus MVPs, partners, and customers from across the globe. What We have 100 unique sessions planned, including new formats like Experts Unplugged sessions where you can hear experts give unscripted answers to your toughest questions, and a Future Look @ session series where upcoming Exchange features will be disclosed in detail for the first time. Why Whether you are a MEC veteran or a first-timer, it’s the best possible way to take your Exchange skills, knowledge, and connections to the next level. Want more details? Check out www.iammec.com or watch some of the MEC 2012 keynote to get a taste of the type of experience you can only get at MEC. After you register, be sure to join the conversation on Twitter by following @MEConf and using the #iammec hashtag. We’ll see you in Austin! The Exchange Team
