We have an overweight an bloated email account on Exchange 2007 running on a SBS 2008 which needs emptying, but not deleting. unfortunately there was no monitoring in place and now it's slowing the entire network down (another long story)...
What would be the easiest and most efficient way to remove all emails from the offending email account please?
Thanks
You need to grant access and setup shell scripts in Exchange Management Shell. Just use these shell commands to make your job easier.
http://community.spiceworks.com/how_to/show/892-delete-emails-in-exchange-2007
Related
Does Red-Gate SQL Compare need to be installed on On-Premise Database Server to run powershell scripts that are set for automation? I have Red-Gate on my local machine, and I am asking this question to figure out if i need to install it to server because that will determine if i need to buy another license.
There are subtleties in licensing that are best discussed in person with Redgate Sales. It will depend on whether you are the only user contributing to the database changes and triggering the automation, what 'user' will be running the automated process (is it you, or will it be drive by a service account?) If you contact sales#red-gate.com (or your Redgate account executive) they will be able to advise you on your options.
I'd like to automate several FileMaker tasks using Windows Task Scheduler. It looks like step scripts are the way to go, but I'm not sure. I'd like to run tasks, say exporting for example, several times per day, but WITHOUT opening the FileMaker GUI. Is that possible? Any tips you have would be great. Thanks.
It's possible to initiate a Filemaker script using a schedule server script with Filemaker Server. However, if the database is not hosted using Filemaker server, or not open using Filemaker Pro (sounds like your situation), then there is no active engine able to actually perform the calculations (script steps, etc). The database has to be running somewhere to initiate and perform any scripts.
If the database is hosted using Filemaker Server then it is pretty easy to setup a scheduled script that will run at a designated time. If you don't have a license of Filemaker Server some Filemaker cloud hosting providers have monthly plans that are relatively cheap ($20/month with unlimited connections), and they'll work with you to setup a scheduled script (for free).
The best way to automate FileMaker tasks is to use FileMaker Server which has scheduled scripts. Of course it is more expensive than standalone version of FileMaker Pro.
If you automate tasks on a local FileMaker file, you can not avoid starting FileMaker and opening the file.
FileMaker has a limited support for VBScript, you can run FileMaker, open file and run a FileMaker Script from VBScript and add that script to Windows Task Scheduler.
This is not preferable way, but if you have no other option, this may be handy.
in Task Scheduler, Create a task
on Action tab, choose
"Start Program"
on the next screen, point to FileMaker Pro exe file, typically it is in C:\Program Files\Filemaker Pro\FileMaker.exe
Add argument:
"fmp://hostName/fileName.fmp12?script=scriptName¶m=optionalScriptParameters"
please read more here http://www.filemaker.com/help/12/fmp/en/html/sharing_data.16.7.html about url schema. This will vary depending on whether you are hosting your file on FileMaker Server or opening it locally.
Note: avoid having spaces or special characters in script name.
Save the task. Reopen task properties and save your windows account credentials, so that the task may run without you having to login.
either save FileMaker login credentials upon login (if your FM version allows), or pass credentials through fmp url (as described in the link above), or go to FileMaker file options, and use credentials in "Log in using": (which is not secure and not recommended).
I am using this method to automatically send emails with PDF attachments, since FileMaker server does not let you Export Records as PDF (not until v.16) on server scripts.
We are working on a project that will require us to determine the exact role of an Exchange server through WMI, using Perl. It looks as if there was a WMI namespace for Exchange that was deprecated some time ago (possibly with 2003?). Is there a way to query through WMI to determine the role of an individual server for Exchange 2007/2010/2013?
No, WMI is not supported in versions of Exchange starting with Exchange 2007. Per Development technologies for earlier versions of Exchange, the Exchange Management Shell is the recommended replacement for WMI -"Exchange Management Shell commands that work with versions of Exchange starting with Exchange 2007 replace the WMI providers in Exchange 2003. Because Exchange Management Shell commands that enable you to control Exchange servers, storage groups, databases, and users are easier to use than the corresponding WMI providers and objects, you can easily migrate your applications to Exchange Management Shell commands." Hope that helps!
Let's say I would like to check some user mailbox properties from within PowerShell. I can run the script in Exchange Management Shell but the problem is that I have no guarantee that the end user will be running the script directly on Exchange or a machine with any Exchange tools. So, I can tell the end user to just run the script in the PowerShell (not EMS) and encode importing pssesion into the script.
However, here comes the main problem of mine, I cannot hard-code the server name into the script (it will be used in many different environments) and I would like to avoid asking the end user to provide the Exchange Server name for the pssesion.
Is there any way to obtain the Exchange Server name automatically with just vanilla PowerShell (no EMS, etc.)? The script will be ran by users with domain admin privileges, most likely there will be no Outlook on the machines (so no MAPI profiles configuration), if that is of any help.
I'm not sure how portable this is (it works on my E2K7 setup, but your mileage may vary)...
You can look in AD to get a list of exchange servers by doing something like the following:
$exchangeServers = [ADSI]"LDAP://contoso.com/CN=Exchange Servers,OU=Microsoft Exchange Security Groups,DC=contoso,DC=com"
$exchangeServers.Member
In my environment, this lists all of the exchange server computer accounts, plus a few other groups, but it's a starting point.
I have a Microsoft Exchange account through my college, and my mailbox is very close to full. I'd like to download the messages to my local machine and archive them so that I can access them later if needed.
It seems to me that I should do something using POP3, but I have no idea where to start.
Note: I am currently using Ubuntu 11.04, but I can boot into Win7 if necessary.
Use Outlook to connect to the mailbox and either expliiclty copy messages to a PST file or use AutoArchive feature to move the old message to an archive PST file.
There is a free product called MailStore that should do the trick. Find it at http://www.mailstore.com