Finally the help of IT is here

Blog of computer solutions.

Archive for the 'Mail Servers' Category

mail servers

Protecting Exchange of mailings from within the organization

Posted by Xaus Xavier Nadal 18th on November 2011

To protect the Exchange system unapproved bulk mailings it is proposed to implement a change in each user in the organization so as to limit the number of recipients in an email.

The field of Active Directory that we use is msExchRecipLimit which It limits the number of recipients when a user sends an email.

Current scenario:

Any user in your organization can get a list of users and send an email recipient without limitation causing a potential drop in the mail service.

Future Scenario:

Exchange has a global limit for all users. (This limit will be set to "100" recipients, except VIPs users or previously defined).


1.- Communicate change management team and after his approval to the technical support that are relevant.


2.- Create script to deploy 100 addressed to all users in your organization without exception: read you on how to install Quest Active Roles tools from the following article will also introduce some useful commands in PowerShell from the following link:

Perform running a script in PowerShell as follows:


$ Users = gc c: \ allusers.txt

Foreach ($ user in $ users)




Set-QADUser $ user -includedProperties msExchRecipLimit -ObjectAttributes @ {MsExchRecipLimit = "100"}




Write-Error $_




Where c: \ allusers.txt is the list of all users in your organization that we have created previously.

This list of users can be achieved through the following command:


get-QADUser -sizelimit 0 -memberof "Domain Users" | select LogonName |Export-Csv -Path c: \ allusers.txt


Running the above script will make a modification for each user in your organization by placing a limit 100 recipients.


3. - Modify and save with another name the above script to implement the previously provided list of people who do not want to limit, VIPs, ... the exemption limit on recipients. (No limit).


$ Users = gc c: \ vipusers.txt

Foreach ($ user in $ users)




Set-QADUser $ user -includedProperties msExchRecipLimit -ObjectAttributes @ {MsExchRecipLimit = ""}




Write-Error $_




Where c: \ vipusers.txt is the list of VIPs users and unlimited users previously provided.

Running the above script made an amendment to limit recipients to "Unlimited".


4. - It shall be a procedure for each new user creation will set the recipient limit in 100 if a normal user or unlimited user if a VIP or special.


1. - Make a script that monthly check the correct implementation of these limits so as to ensure the health of our mail service.


2. - Create 2 or more groups in Active Directory with the name for example EXCHLIMIT100 y EXCHLIMIT9999, by a daily task to check if a user is a member of EXCHLIMIT9999, If it is not adding the group EXCHLIMIT100 and run the first scritp article with the list of members of this group.

I hope you find it useful.

See you soon.

tags: , , , ,
Posted by Active Directory, mail Servers, PowerShell | No Comments »

Load Simulator (Measure maximum load on Exchange)

Posted by Xaus Xavier Nadal 12th on November 2011


A link I found by accident the other day and I found it very good is the 2003 Microsoft Exchange Server Load Simulator (LoadSim) application.

I leave the link for Exchange LoadSim 2003:

With this application we can simulate the performance of MAPI clients connected to our Exchange before falling, so we can properly size the server before thousands of users who want access to our server come.

Exchange 2007 the link is as follows:

To measure performance and yields Exchange 2010 you can use the following:

Generator load for Exchange Exchange 2010:

Microsoft Exchange Server Jetstress 2010 that will measure the performance and stability of the disk subsystem load simluando Input / Output (IO) on discs

Greetings and see you soon.

tags: , , , , , , , ,
Posted by Exchange, Exchange 2007, Exchange 2010, mail Servers | No Comments »

GTranslate Your license is inactive or expired, please subscribe again!