2007
11.20
Description

This script takes a CSV file and uses the entries in the columns to create managed folders and a managed folder mailbox policy. It then sets the created policy to all mailboxes.

Usage

Save the script code below into a simple text file and name it ManagedFolderSetup.msh. Open up the Exchange Management Shell and navigate to the directory containing the file you just created. Type:

.\ManagedFolderSetup.msh C:\ManagedFolders.csv

Ensure the path specified for the CSV file is correct.

Sample Script

$newManagedFolders = @()
$existingManagedFolders = @()
$managedFolderLinks = @()

## Name of the managed folder mailbox policy to be created – change this in your script
$managedMailboxPolicy = "General Policy"

if(!($args[0]))
{
write-host "Usage: ManagedFolderSetup.msh ManagedFolders.csv"
return
}

$data= import-csv -path $args[0]

## Create Managed folder
foreach( $i in $data )
{

   $newFolder = Get-ManagedFolder | where {$_.Name -eq $i.Folder}
   if ($newFolder -ne $null) {
        $script:existingManagedFolders += $newFolder
    } else {
        $newFolder = New-ManagedFolder -Name $i.Folder -FolderName $i.FolderName -StorageQuota $i.StorageQuota
        if($newFolder -ne $null) {
              write-host "Done"
              $script:newManagedFolders += $newFolder
         } else {
              write-host "Error: Managed folder" $i.Folder "cannot be created."
            }
      }       
}

write-host "Below Managed folders already exist:"
foreach($i in $existingManagedFolders)
{
write-host $i.Name
$managedFolderLinks += $i.Identity 
}

write-host "Succesfully created below Managed folders:"
foreach($i in $newManagedFolders)
{
write-host $i.Name
$managedFolderLinks += $i.Identity
}

## Create a Managed folder mailbox policy

$newPolicy = New-ManagedFolderMailboxPolicy -Name $managedMailboxPolicy -ManagedFolderLinks $managedFolderLinks
if ($newPolicy -ne $null) {
write-host "Succesfully created below Managed folder mailbox policy:"
$managedMailboxPolicy
} else {
write-host "Error: Managed folder mailbox policy" $managedMailboxPolicy "cannot be created."
return;
}

## Set the created managed folder mailbox policy to all mailboxes
write-host "Set the created policy to all mailboxes:"
$mailboxes = get-mailbox
foreach($mailbox in $mailboxes)
{
$mailbox.Name
Set-Mailbox -identity $mailbox.Identity -ManagedFolderMailboxPolicy $newPolicy.Identity
}

  • Share/Bookmark
2007
11.20
Description

Creates a new receive connector named “receiver” and specifies a range for the remote IP address.

One-Liner

New-ReceiveConnector receiver -Bindings:10.0.0.1:25 -RemoteIPRanges 123.456.0.1-123.456.0.10

  • Share/Bookmark
2007
11.16

iPhone Vs. Windows Mobile Phone

iphone windows mobile

  • Share/Bookmark
2007
11.16

The release of Microsoft Exchange Server 2007 Service Pack 1 (SP1) brings a wide variety of new features and functionality to Exchange 2007. The list of features we have added, which can be reviewed at What’s New in Exchange Server 2007 SP1, is quite impressive. There are new deployment options, new features and improvements for each server role, improved integration with other applications, such as Microsoft Office Communications Server (OCS) 2007, and even a new, third type of continuous replication.

Continue here.

  • Share/Bookmark
2007
11.16

The purpose of this document is to help you plan, deploy, and manage Microsoft Exchange Server 2007 Unified Messaging servers. The information and procedures in this document focus specifically on the Unified Messaging features of an Exchange 2007 computer that has the Unified Messaging server role installed. This document provides information about Unified Messaging features and the tasks you must perform to plan, deploy, manage, and configure them.
This document is a compilation of the Unified Messaging white papers that are available in the Exchange Server Technical Articles section of the Exchange Server 2007 Library. Each white paper is a compilation of Unified Messaging Help topics. This document is provided as a convenience for customers who want to view the topics in print format. The content in this document applies to the original release (RTM) version of Exchange Server 2007. To read the most up-to-date Unified Messaging topics, including information about Exchange 2007 Service Pack 1, visit the Exchange Server 2007 Library.

Download here.

  • Share/Bookmark
2007
11.15

Information in this article applies to: Exchange 2003, Windows 2000

SYMPTOMS:

You removed the Exchange 2003 organization from Windows 2000 Active Directory using Exchange setup with /removeorg switch.

When you try to reinstall Exchange 2003, forestprep fails at stage “finalizing organization container creation” and it reports the following error:

A problem has been encountered in the Microsoft Exchange Forest Preparation Setup component. Canceling setup

After that it reports:

You have successfully completed setup.

At the bottom of the Exchange Server setup log (by default it is C:\exchange server setup progres.log ) the follwing error is reported:

[12:44:31] !!!!!!!!!!Setup completed successfully!
[12:44:32]  CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
           Error code 0X80004002 (16386): No interface.

CAUSE:

Exchange 2003 setup used with /REMOVEORG does not remove the Exchange container from Windows 2000 Active Directory and that prevents forestprep from completing successfully.

SOLUTION:

  1. Open Active Directory Sites and Services
  2. From the View menu select Show Services node
  3. Double click services,
  4. Select and delete Microsoft Exchange container
  • Share/Bookmark
2007
11.15

You need to give someone access to another persons mailbox (Exchange 2003 in this example)

1. In Exchange Active Directory Users and Computers, right click the user to whose mailbox you want to give access to and select properties.

faq000001-01

2. Select Exchange Advanced, then Mailbox rights

faq000001-02

3. Click on the Add button to select users or groups you want and assign them Full mailbox access permission.

faq000001-03

  • Share/Bookmark
2007
11.15

There are 2 possible causes for this

  1. Check the public folder store properties under Limits if you have any age limits set for the folder
  2. Check if you excluded the Exchange M: drive in file system antivirus scanning and backup. If you don’t exclude it antivirus and backup can cause damage to the Exchange databases.

For more details see:
Microsoft Knowledge Base Article – 328841 Exchange and antivirus software
After this is properly configured check your Exchange database integrity with ESEUTIL and ISINTEG

  • Share/Bookmark
2007
11.15

You can use the PowerShell script given below to create a status report on backup of your Exchange databases:

# =========================================================================
#
# Microsoft PowerShell Source File — Created with SAPIEN Technologies PrimalScript 2007
#
# NAME: Exchange Database Backup Report 1.0
#
#
# COMMENT: This script creates a backup status report for all the databases in your organization.
# In case the report does not fit your screen adjust the width of your PowerShell Window.
# To adjust the PowerShell window width, click the PowerShell icon on the top left corner 
# of your PowerShell window. Select Properties/Layout/Windows Size/Width and enter a greater
# value as needed. 
# =========================================================================

$OrganizationName = Get-OrganizationConfig | Select-Object -Property Name 
$Date = Get-Date -DisplayHint DateTime
Write-Host
Write-Host “Backup Status Report for All Databases in Exchange Organization” $OrganizationName.Name
Write-Host
Write-Host “Created on” $Date
Write-Host
Write-Host
Write-Host “Backup Status of Mailbox Databases”
Get-MailboxDatabase `
| where {$_.Recovery -eq $False } `
| Select-Object -Property Server, StorageGroupName, Name , LastFullBackup, LastIncrementalBackup, BackupInProgess `
| Sort-Object -Property Server, StorgageGroupName, Name `
| Format-Table -AutoSize
Write-Host
Write-Host “Backup Status of Public Folder Databases”
Get-PublicFolderDatabase `
| Select-Object -Property Server, Storagegroupname, Name , LastFullBackup, LastIncrementalBackup, BackupInProgess `
| Sort-Object -Property Server, StorgageGroupName, Name `
| Format-Table -AutoSize

  • Share/Bookmark
2007
11.15

PROBLEM

When you try to execute a PowerShell script the following error occurs:

File C:\scripts\myscript.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see ” get-help about_signing” for more details.

At line:1 char:23

+ c:\scripts\myscript.ps1 <<<<

CAUSE

By default the PowerShell execution policy is set to restricted, which does not allow the PowerShell Scripts to be run. There are 4 possible execution policies in PowerShell:

  • Restricted – the default setting, doesn’t allow any scripts to run.
  • AllSigned – only runs scripts which are signed by a trusted digital certificate
  • RemoteSigned – runs local scripts without requiring them to be trusted. Scripts downloaded from the Internet must be trusted before they can run.
  • Unrestricted – allows all scripts to run, even untrusted ones.

SOLUTION:

Use the Set-ExecutionPolicy command to “unlock” you work environment. For example if you are using a lab or learning environment you can issue the following command :

Set-ExecutionPolicy Unrestricted

IMPORTANT: This setting should not be used in a production environment because it could potentially allow scripts downloaded from internet or planted by viruses to be executed.

  • Share/Bookmark