Thoughtsofanidlemind's Blog

[...] always happy to hear of a good source, so reply to this post to let me know your suggestions! Follow Tony @12Knocksinna Twitter handle Blog Content Paul Robichaux http://paulrobichaux.wordpress.com/ [...]

[...] coming in Office 365 allows for better planning and preparation, and that can’t be a bad thing. Follow Tony @12Knocksinna [...]

[...] more that I work with EAC, the more gaps I find. It’s a bit like Exchange 2000 all over again… Follow Tony @12Knocksinna [...]

[...] Exchange. Period. I can’t pretend that I will be as productive in August. Vacation beckons. Follow Tony @12Knocksinna [...]

[...] hierarchies spanning tens of thousands of folders and some that have hundreds of thousands of public folders. Clean-up could take some time. You might wonder why any company would have so many public [...]

[...] Following up the post about migrating public folders to the modern version introduced in Exchange 2013, an entry in a TechNet forum asked whether [...]

[...] A page appeared on TechNet on February 24, 2014 titled “Limits for Public Folders.” Not much news there, I thought, we all know that public folders have limitations, [...]

[...] the initial fuss about the limitations that recently emerged for Exchange 2013’s modern public folders has subsided (but just a little), cooler minds turn to thinking about why these limitations [...]

[...] ’ll encounter on an Exchange server. Of course, EMS is very different when it comes to Exchange Online running in Office 365. One of the reasons why companies sign up for Office 365 is so that [...]

[...] Cloud-based email services such as Exchange Online bring a great deal of value to the table. A service delivered for a fixed known cost that is [...]

[...] resources is handled behind the scenes. In fact, there are some strange oddities about how Exchange Online populates recipients into address lists that are documented in KB2955640. The new address [...]

[...] All current versions of Exchange 2013 (up to and including CU6) and Exchange Online (Office 365) contain a bug that can compromise the ability of companies to comply with [...]

[...] “There isn’t a part of the core Exchange Server that is not shipped to our on-premises customers. We don’t have a special Exchange that runs in the cloud.” The meaning here is [...]

[...] , and refine software. Eventually the software might be in good enough shape to deliver to on-premises customers and if so, it can be slipstreamed into a cumulative update or new version. In addition, [...]

[...] that has some consequences for those who offer alternate hosted services as well as on-premises customers. And it’s all to do with the level of integration that Microsoft is now building into [...]

[...] server products creates some issues for hosting companies (other than Office 365) and on-premises customers. At least in the case of Exchange, Microsoft uses the same code base for its cloud and on- [...]

[...] using Office 365 for my business and working with many companies who are quite happy with on-premises Exchange. I agree with Scott’s assertion that messaging engineers and administrators need to [...]

[...] Outlook Web App (OWA) that aren’t yet in on-premises Exchange, all of which underlines the growing functionality gap that has appeared between the cloud [...]

[...] 2013, and Outlook 2013 (and some of the problems that exist). The process of configuring on-premises Exchange and SharePoint to make site mailboxes work is horrible and I’d like to see changes [...]

[...] that his intended session covering off-boarding techniques for moving from Office 365 to on-premises Exchange 2013 would have been interesting, if not popular with those who are cloud-centric. There [...]

[...] on the number planning to be at each. Here are the top 10 MEC sessions to date. Monday 10:30 Exchange Server 2013 Architecture: mailbox and client access Ross Smith IV 548 Monday 14:45 Exchange Server [...]

[...] recommends that you set up “a temporary virtual machine (VM) to use for your first Exchange Server 2013 deployment,” something that caused me to splutter on my cornflakes. The [...]

[...] of new mail. Possibly because it was the only reliable protocol available to connect to an Exchange server at the time, RIM used MAPI to interface their servers to Exchange and monitor mailboxes. A [...]

[...] was to be discontinued. Read on to find out why this development was unexpected. Talking Exchange Server with Microsoft’s Perry Clarke (Dec 17): After collecting lots of questions it was time [...]

[...] might crash. For instance, some reports indicate that transient disk errors on virtualized mailbox servers can generate crashes that cause mailboxes to be quarantined. The solution here was to move [...]

[...] being virtualized? Does it mean that a single CAS is virtualized? Or all CAS and no mailbox servers? Or all Exchange servers in an organization? It’s absolutely certain that virtualization is [...]

[...] .exe.config) in the \Exchange\V15\Bin directory on multi-role or mailbox servers (for Exchange 2010, the configuration file is in the \V14\bin directory on multirole or [...]

[...] Exchange 2013 only runs EMS cmdlets to execute operations such as mailbox creation on mailbox servers. After the configuration files are deployed and the scripting agent is enabled, [...]

[...] that are in use within the organization. For example, this code forms a collection of user mailboxes, then uses that collection to scan for all the mobile devices that have partnerships [...]

[...] step along the path to allowing administrators to script the correct configuration of user mailboxes as they were created and was, in my mind, a very good thing. So I remain puzzled and [...]

[...] in the source mailbox. Search-Mailbox is often to remove unwanted items that arrive into user mailboxes. This is done by adding the –DeleteContent switch to a command. Clearly you should not rush [...]

[...] under. As with any utility that has the ability to open and extract information from user mailboxes, you also need to pay attention to privacy and ensure that access is controlled at all [...]

[...] sides. And who needs that stuff in archives anyway? 2TB seems like such a good size for a mailbox database (August 12): How big should a mailbox database be? Well, that all depends on your appetite [...]

[...] ’s most annoying and confusing error message (Feb 18). Have you tried to remove a mailbox database from Exchange 2010 or Exchange 2013? If so, you might have had the intense pleasure of [...]

[...] in Exchange 2007 and Exchange 2010 to force a closure of the current transaction log for a mailbox database and the subsequent replication to servers that host database copies. It is not used in [...]

[...] ,600 seconds, or six hours. Note that the Store may create a separate registry key for every mailbox database on a server. The entries corresponding to a specific database are identified with the GUID [...]

[...] , this time to afflict ActiveSync users whose mailboxes were still on an Exchange 2007 mailbox server. Maybe they should be using a more modern server? Or perhaps these bugs shouldn’t [...]

[...] is used to enable or disable a format. By default, all known formats are enabled when a mailbox server is installed. For example, to disable any attempt to index information for JPEG images, you’d [...]

[...] this is because the Exchange 2013 CAS doesn’t do very much at all and relies on the mailbox server role to execute the remote PowerShell commands used to manage Exchange. Absolutely spot-on. [...]

[...] setting, so it is obviously important to have the same configuration file in place on every mailbox server so that the same behavior happens throughout the organization. You do not have to put the [...]