Any scripts that will let me know if a mailbox has not been accessed for at
least 30 days?

accessed in what sense? receiving email, user signing on, delegate signing
on, touched by backup process....

I guess user signing on.... problem I've found is that backup process causes
Last Logon Time to reset every night (although if you don't do brick level
this may not be the case)

what's the purpose? only option I can think is to log access to Event log
and pull the info from there

regards
petal

As users quit or are laid off / fired, I am trying to find an easy way to
know if there mailbox has not been used or accessed for a month or so then
it would be safe to delete.

We are a very big company and the Exchange admin is an idiot and I need to
figure out a way to fix his mess..

Would it suffice to check the Sent folder and filter it for items newer
than 30 days?  If none are found, then at least the user hasn't sent
anything recently.

Such a script isn't too tough to do.  Look at cdolive.com for samples.

--
Ross Presser -- rpresser AT imtek DOT com
"... VB is essentially the modern equivalent of vulgar Latin in 13th
Centurary Europe. Understand it, and you can travel to places you never
heard of and still understand some people." -- Alex K. Angelopoulos

maybe OT, but I don't think that its ITs role to provide a solution to the
Business' inability to manage itself. This kind of user administration
requires that the Business informs IT (and others) - not our fault they
can't get their act together.

Best way we came up with was to charge for items like disk use and email -
if they know it's costing them they fill out forms sharpish, and periodic
evaluation of things like LastLogon and HR/Payroll records coupled with a
hefty penalty for holding dead accounts open helped further. You want good
change control in place to stop them slipping things past you (e.g. adding
additional email addresses to a mailbox, changing phone/location details)

there is no foolproof way - I'm trying to work something out with HR and
Payroll to get lists of all hires/fires on a daily basis, and include IT
procedures in the Induction and Exit Interviews, but.....

- user may have left, but someone else takes on their identity - happens a
lot with casual staff when units don't want to wait 48 hours for account
setup
- user may have left, but HR/Payroll don't even know of them in the first
place as they are paid out of capital budgets
- user may have left, but is coming back (after sick/maternity) - they get
uppity when they find they've been chopped.(m{*filter*}here is that EXMERGE (and
a good script to document user settings and archive personal areas) is your
friend)

the mailbox equates to the account so why not use the LastLogonTime for the
user? If more than 30 days, call their boss and ask where they are - that
picks up the sick/maternity brigade - and then delete if you can, else mark
somehow - I have various coded groups for sick/maternity/sabbatical/insane

regards
petal