Powershell Command for public folder permissions

 

If you want to replicate all permissions which parent public folder have to all child PFs, then you need to run following powershell script

adduserstopfrecursive.ps1 -toppublicfolder "<Parent Public Folder Name" -user "<User or group name>" -permissions –<permissions>

for example:

adduserstopfrecursive.ps1 -toppublicfolder "\SALES" -user "PFOwners" –permissions owner

BlackBerry Permissions Configuration on Exchange 2007

If you are planning to install Blackberry services in your environment then you have to consider permissions required by BB on Exchange setup.

BB required following set of rights in order to perform operations on user mailboxes;

1. Send-As permissions on user mailboxes.

2. Receive-As permissions on mailboxes.

3. Ms-Exch-Store-Admin permissions.

You have to provide the above permissions to blackberry service accounts; following is the method for doing this;

Step one:

Provide View only Admin rights to BlackBerry Service Account

get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin

Step Two:

Provide Send-As, Receive-As and MS-Exch-Store-Admin to BlackBerry service Account.

get-mailboxserver <mail_server_name> | add-adpermission –user BESAdmin –accessrights ExtendedRight –extendedrights Send-As, Receive-As, ms-Exch-Store-Admin

Microsoft Exchange Server Build numbers and release dates

Following is the list of all exchange server versions released by Microsoft with their build numbers and release dates for reference;

Version	Build Number	Release Date
Microsoft Exchange Server  4.0	4.0.837	Apr-96
Microsoft Exchange Server  4.0 (a)	4.0.993	Aug-96
Microsoft Exchange Server  4.0 SP1	4.0.838	May-96
Microsoft Exchange Server  4.0 SP2	4.0.993	Aug-96
Microsoft Exchange Server  4.0 SP3	4.0.994	Nov-96
Microsoft Exchange Server  4.0 SP4	4.0.995	Apr-97
Microsoft Exchange Server  4.0 SP5	4.0.996	May-98
Microsoft Exchange Server  5.0	5.0.1457	Mar-97
Microsoft Exchange Server  5.0 SP1	5.0.1458	Jun-97
Microsoft Exchange Server  5.0 SP2	5.0.1460	Feb-98
Microsoft Exchange Server  5.5	5.5.1960	Nov-97
Microsoft Exchange Server  5.5 SP1	5.5.2232	Jul-98
Microsoft Exchange Server  5.5 SP2	5.5.2448	Dec-98
Microsoft Exchange Server  5.5 SP3	5.5.2650	Sep-99
Microsoft Exchange Server  5.5 SP4	5.5.2653	Nov-00
Microsoft Exchange 2000 Server	6.0.4417	Oct-00
Microsoft Exchange 2000 Server (a)	6.0.4417	Jan-01
Microsoft Exchange 2000 Server SP1	6.0.4712	Jul-01
Microsoft Exchange 2000 Server SP2	6.0.5762	Dec-01
Microsoft Exchange 2000 Server SP3	6.0.6249	Aug-02
Microsoft Exchange 2000 Server post-SP3	6.0.6487	Sep-03
Microsoft Exchange 2000 Server post-SP3	6.0.6556	Apr-04
Microsoft Exchange 2000 Server post-SP3	6.0.6603	Aug-04
Microsoft Exchange Server  2003	6.5.6944	Oct-03
Microsoft Exchange Server  2003 SP1	6.5.7226	May-04
Microsoft Exchange Server  2003 SP2	6.5.7638	Oct-05
Microsoft Exchange Server  2007	8.0.685.24 or 8.0.685.25	Dec-06
Microsoft Exchange Server  2007 SP1	8.1.0240.006	Nov-07

*Source Microsoft TechNet

Shrinking SQL 2000, 2005 Databases

 

If you ever run in a situation like you have only MBs of space left on production SQL servers and your transaction logs are growing bigger and bigger and you want to claim disk space immediately then you might need to run following command

Backup log <Database name> with no_log

This command is not recommended to run in normal circumstances and after this you are not able to recover your database point in time. if you have proper backups configured then you don’t need to run this command because after each full backup the transaction logs are automatically truncated. Also in case you have log shipping configured then this command will break your log shipping sequences. Only use if you don’t have any space left on physical disk and you don’t have any other alternatives available.

if you don’t required point in time recovery then change your database recovery model to ‘Simple’ doing this will ensure that your transaction log will not get bigger.

The above command will not reclaim disk space, you have to run DBCC shrink statement or go to the SQL management studio and manually shrink log file.