Exchange Disabled Users

I was asked a question the other day, and I thought I would share it and the answer with you


When disabling a user account, mailbox access from other outlook clients with permissions is obviously ‘revoked’, does this also take 3 hours?  I ask this because when I disabled a user accound today I still had access to the mailbox for probably around 3 hours after.. I have never noticed this before!?  Do you have any more information regarding this as I cannot find any on MS website, can this time period be changed at all?


These KB’s help address the issue:


326252 XADM: Exchange 2000 Mailbox Size Limits Are Not Enforced in a Reasonable <http://support.microsoft.com/?id=326252>
327378 Exchange 2000 and Exchange 2003 mailbox size limits are not enforced in <
http://support.microsoft.com/?id=327378>


The reason is that the Mailbox Cache Age Limit is set to two hours by default, so for any new restrictions on a mailbox you have to wait until the cache has expired


 

[Via Flagged Items]

Advertisements

News about MSN Desktop Search and Non-Admin wikis

Time for a couple of wiki news items that I’ve been saving up for a while.


In a “one small step†moment, I believe that the MSN Desktop Search wiki on Channel 9 is the first wiki to ever be referenced in a Microsoft help file. As you can imagine, this was quite a culture change — kudos to everyone involved in making it happen! Oh, and if you look carefully in the IFilter documentation on that site you might find a reference to future features that the MSN Desktop Search team let slip. Just a hint 🙂


And now that MSN Spaces is out of beta (with 4.5 million users already), I’m wondering how long their MSN Spaces Feedback wiki can stay as a single page. I keep getting the urge to dive in there and refactor it into several smaller pages, but so far I’ve resisted. Also, I confess that I’m curious — how long until someone else does the same thing?


Lastly, the running as non-admin wiki has been getting some nice press, both from mainstream outlets (including David Coursey at eWeek and Rob Pegoraro at the Washington Post) and from my fellow bloggers (Aali, Eric, and Dirk). Thanks guys!


Update: I almost forgot — the non-admin wiki now has an RSS feed, as all good wikis should. Keep track of updates from the comfort of your aggregator.

[Via Flagged Items]

Introducing the Microsft Exchange User Monitor (Exmon) tool

I am pleased to announce that this month's Exchange Web release contains a tool that the Exchange performance, development, and operations teams at Microsoft have used for quite some time called Exchange User Monitor (Exmon) and can be downloaded here. Exmon for the first time allows an Exchange administrator the ability to see in amazing detail the performance of an Exchange server. Shown on a user by user basis, Exmon allows you to see how much CPU, latency, network traffic, and disk each user on an Exchange server consumes. It can be run in almost realtime (minute by minute analysis) or over longer (multiple-hour) capture periods. Exmon also 'bubbles' up data sent back to the Exchange server from Outlook 2003 and higher about the user's actual experience, showing the actual RPC (network+server) latency and even the name of the process talking to the Exchange server (so you can see ActiveSync usage and other 3rd party MAPI applications). The data Exmon exposes is the 'raw' data that many of the Exchange Performance counters use in calculating the running averages.

 

Internally, this tool was used to help understand the performance of Outlook 2003 and other MAPI applications during the development of Exchange Server 2003. We use it to understand the broad impact of performance across a server, but also to troubleshoot specific performance problems with individual users. The impact to the server being 'traced' is minimal, allowing it to be run on very large servers.

 

I'd love for you to download the tool, give it a whirl, and tell us what you think. We'd love to see what use you can come up with for this data, problems you're able to solve, and conclusions you're able to make.

 

On a personal note, I recommend looking at a number of traces to 'aquaint' yourself with what's normal. Exmon data can be highly dynamic in range. It's best to use longer traces rather than smaller ones, because MAPI traffic can be very bursty, unless you're trying to look at a very microscopic level.

Chris Mitchell

[Via Flagged Items]

Blogcast: Modify Installations of Office 2003 with the Custom Maintenance Wizard

No matter what you plan for, you will always want to modify your deployment of Office after it's out in the field. The problem is that Office isn't a small application and most admins push the install to workstations over a period of time. If you think you can modify the current corporate deployment by a simple transform, think again. The easiest way to modify your deployment of Office 2003 is with the Custom Maintenance Wizard (CMW). The CMW is an application that comes with the Office 2003 Resource Kit and you can create a .CMW file which is like a .MST. There are some differences between a transform and a .CMW file and you need to know how to use them. If you do a full uninstall and then reinstall Office 2003 to make a change, you don't know the technology available to you.
Office 2003 Custom Maintenance Wizard Part 1
Have you deployed Office 2003 and need to make modifications? The CMW will allow you to make changes on the fly which will not require you to uninstall the full suite and reinstall. Save time and end user down time by using the tools designed to get the job done right the first time!
Office 2003 Custom Maintenance Wizard Part 2
Learn how to use the command line to deploy changes to your workstations. You can't use a .MSI or a transform file to make the changes for you. See how a few simple well planned steps make changes easy on the fly!

[Via Flagged Items]

ESX Performance Tuning documentation Series

An series of performance related papers for VMware's ESX Server. Pretty deep.• Isolating Performance Problems (PDF)
This paper provides an overview of the process used to troubleshoot performance problems in the ESX Server environment.

Representing Physical Machines in the Virtual World (PDF)
This paper describes the process for troubleshooting a suspected performance problem at the machine representation layer (i.e., virtual machine layer).

Using esxtop to Troubleshoot Performance Problems (PDF)
This paper describes the process for troubleshooting a suspected performance problem at the virtualization layer (i.e., the ESX Server layer) using the esxtop tool.

ESX Performance Tips and Tricks (PDF)
This paper provides [more …]

[Via Flagged Items]

Network Throughput In A VMWare Virtual Infrastructure Paper

How do you know if you are getting optimal network throughput for the applications deployed on your ESX Server? This new technical paper examines the factors you should consider, and describes how to use the netperf tool to measure network throughput so you can optimize your system.Download the technical paper here.

[Via Flagged Items]