Free Cookies for Linux & Windows

There are many third software would help you for this you may try their demo it works fine, but the full version would cost you around $200 which is costly

But i was having alot of trouble then i buy one of them.

I would help you doing this but i can only recieved files since i may not install the software at your PC and ask me to remote desktop to and install on your PC because the licences,

Please fell free to contact me if you need help. I proven to restore OST 10GB size.

regards,

Sim

#Get Organizational Limits
Get-TransportConfig

#Set Orhanizational Limits
Set-TransportConfig -MaxSendSize 20MB -MaxReceiveSize 20MB -MaxRecipientEnvelopeLimit 300

#List Send Connectors
get-sendconnector

#List Send Connectors with details (using Format-List/FL)
Get-SendConnector | FL

#Set Send Connector Message Size Limit for a specific connector
Set-SendConnector -Identity “Default Internet Connector” -MaxMessageSize 20MB

#Set Send Connector Message Size Limit for all connectors
Get-SendConnector | Set-SendConnector -MaxMessageSize 20MB

#List Receive Connectors
Get-ReceiveConnector

#List MaxMessageSize for all Receive Connectors
Get-ReceiveConnector | FL MaxMessageSize

#Set MaxMessageSize for a specific receive connector
Set-ReceiveConnector -Identity “EX-2K7\Default EX-2K7″ -MaxMessageSize 20MB

#Set MaxMessageSize for All Receive Connectors
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 20MB

#Get MaxSendSize and MaxReceiveSize Mailbox Limits for a user
Get-Mailbox BAndersen | FL MaxSendSize,MaxReceiveSize

#Set MaxSendSize and MaxReceiveSize Mailbox Limits for a user
Set-Mailbox -Identity BAndersen -MaxSendSize 40MB -MaxReceiveSize 40MB

Overview
Microsoft Exchange Server 2010 Beta helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.

* Flexible and reliable – Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company’s unique needs and a simplified way to keep e-mail continuously available for your users.

* Anywhere access – Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications – e-mail, voice mail, instant messaging, and more – from virtually any platform, Web browser, or device.

* Protection and compliance – Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company’s communications and meeting regulatory requirements.

This software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use this software. There is no product support for this trial software. You are welcome to participate in the forums to share your trial experiences with others and to ask for advice.

Top of page
System Requirements

* Supported Operating Systems: Windows Server 2008; Windows Vista 64-bit Editions Service Pack 1

* Operating System for Installing Management Tools: The 64-bit editions of Windows Vista® SP1 or later, or Windows Server® 2008.

* PC – x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) or AMD processor that supports the AMD64 platform

Additional requirements to run Exchange Server 2010 Beta

* Memory – Minimum of 4 gigabytes (GB) of RAM per server plus 5 megabytes (MB) of RAM recommended for each mailbox

* Disk space

o At least 1.2 GB on the drive used for installation

o An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install

o 200 MB of available disk space on the system drive

* Drive – DVD-ROM drive, local or network accessible

* File format – Disk partitions formatted as NTFS file systems

* Monitor – Screen resolution 800 x 600 pixels or higher

Exchange Server 2010 Beta Prerequisites
If these required prerequisites are not already installed, the Exchange Server 2010 Beta setup process will prompt and provide links to the installation locations; Internet access will be required if the prerequisites are not already installed or available on a local network.

* Microsoft .NET Framework 3.5

* Windows PowerShell v2

* Windows Remote Management

Actual requirements will vary based on system configuration and specific features installed. For more detailed system requirements, please refer to the Exchange Server 2010 Technical Documentation Library.

For a list of Windows Server 2008 requirements,
visit http://technet.microsoft.com/windowsserver/2008.
To Download this Beta version visit: Download Microsoft Exchange 2010

I have been working on Exchange server at home for a little while, and today I decided that I wished to take my testing a stage further which involved removing my current, very basic installation of Exchange 2007 from the server I have been working with.

Before I ran the Exchange 2007 Setup utility I removed all of my 1000 Exchange mailboxes from the OU that I had setup in my test lab using the following command: Get-Mailbox -Server IX -ResultSize Unlimited | Remove-Mailbox

I then disabled the Administrators accounts mailbox using the following command: disable-mailbox administrator

I then deleted the instance of the Offline Outlook Address Book that I had been using in the ESM, along with the additional Exchange Databases and Storage groups, as I hadn’t been using any connectors I did not have to find or remove these.

It was at this point that I thought I would remove Exchange from the server, so I went to “Add Remove Programs” in the Control Panel and selected Exchange 2007 and then Remove.

The setup process began, and as expected performed its initial inspection of whether the Exchange installation was suitable for removal – but when checking the Mailbox role setup failed with the following error message;

Mailbox Role Prerequisites

Failed

Error:

Uninstall cannot proceed. Database ‘Public Folder Database’: The public folder database specified contains folder replicas. Before deleting the public folder database, remove the folders or move the replicas to another public folder database.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=EN&v=ExBPA.3&id=b6e3b32a-8848-46cb-9567-72288ac15f60

I thought ok, no management interface in this version of Exchange for Public Folders, so there must be a management interface command that will work, so I opened up my trusty friend Google and did a search and found the following commands:

Get-PublicFolder -server IX “\” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server IX -Recurse -ErrorAction:SilentlyContinue

Get-PublicFolder -Server IX “\Non_Ipm_Subtree” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server IX -Recurse -ErrorAction:SilentlyContinue

Both commands seemed to run fine (obviously I might not see any specific processing errors due to the “SilentlyContinue” switch) – however when I returned to Remove Exchange I ran into exactly the same error message.

I suspected that perhaps some replicas had been missed by the Management Command – but I was running short of time and really needed to remove the Exchange Installation from the Machine so I thought – perhaps I could just remove the reference to the Public Folder from Active Directory.

So I broke out my trusty copy of ADSI Edit (which can be downloaded from here) and navigated to the following entry:

CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=,DC=

It was then I re-ran Exchange setup, and on this occasion it worked perfectly.

Procedure
To use the Exchange Management Console to configure Exchange 2007 to accept e-mail for more than one authoritative domain

1.

Configure the accepted domain entry by following these steps:
1. Open the Exchange Management Console. Expand the Organization Configuration node, and then click Hub Transport. Click the Accepted Domains tab in the results pane.
2. In the action pane, click New Accepted Domain… The New Accepted Domain wizard appears.
3. On the New Accepted Domain page, type a name to identify the accepted domain entry. In the Accepted Domain field, type the SMTP domain name. Select Authoritative Domain. E-mail is delivered to a recipient in this Exchange organization. Click New. On the Completion page, click Finish.
2.

Configure an e-mail address policy for the authoritative domain by performing the steps in this section that meet the objectives of your scenario.

To change the primary (reply to) e-mail address assigned to recipients, and keep the existing e-mail address as a secondary e-mail address, follow these steps:
1. Open the Exchange Management Console. Expand the Organization Configuration node, click Hub Transport. Click the E-mail Address Policies tab in the results pane. Select the e-mail address policy that you want to modify, click Edit in the action pane.
2. On the Introduction page, click Next.
3. On the Conditions page, click Next.
4. On the E-mail Addresses page, click Add. In the SMTP E-mail Address dialog box, select the option under E-mail address local part that determines how the recipient’s e-mail address alias will be generated. In the E-mail address domain field, use the drop-down menu to select an accepted domain entry from the list. Click OK.
5. On the E-mail Addresses page, select the new address entry and then click Set as Reply. The e-mail address entry is displayed in bold type to indicate that it is now the primary, or reply to, address for the recipients to which this e-mail address policy applies. Click Next.
6. On the Schedule page, select an option to specify when the e-mail address policy will be applied and the maximum length of time that the task is permitted to run. Click Next.
7. On the Edit E-mail Address Policy page, click Edit to save the changes to the policy and apply it to affected recipients.
8. On the Completion page, click Finish.

To create additional e-mail addresses that will be used as the primary e-mail address for a filtered set of recipients, follow these steps:
1. In the action pane, click New E-mail Address Policy… The New E-mail Address Policy wizard appears.
2. On the Introduction page, type a name for the E-mail Address Policy. Select an option under Include these recipient types to determine to which recipient types this e-mail address policy will be applied. Click Next.
3. On the Conditions page, in the Step 1 box, select the condition that will be used to filter the recipients to which the policy is applied. For example, you can select Recipient is in a Company to apply the policy to only recipients whose properties identify a specific company affiliation. In the Step 2 box, click the underlined value to specify the value that the filter must match. For example, if you selected Recipient is in a Company, click the word “specified”. The Specify Company dialog box opens. Type a company name and then click Add to add the company name to the list of names that the recipient’s Company attribute must match in order to have this policy applied to them. If you add multiple entries, the recipient attribute must match only one entry to meet the filter conditions. Click OK to close the dialog box, and then click Next.
4. On the E-mail Addresses page, click Add. In the SMTP E-mail Address dialog box, select the option under E-mail address local part that determines how the recipient’s e-mail address alias will be generated. In the E-mail address domain field, use the drop-down menu to select an accepted domain entry from the list. Click OK. The e-mail address entry is displayed in bold type to indicate that it is now the primary, or reply to, address for the recipients to which this e-mail address policy applies. Click Next.
5. On the Schedule page, select an option to specify when the e-mail address policy will be applied and the maximum length of time that the task is permitted to run. Click Next.
6. On the New E-mail Address Policy page, click New to save the policy and apply it to affected recipients.
7. On the Completion page, click Finish.

Exchange 2007 has continued to improve upon its Anti Spam features with each version of the product. In this article I want to focus on installing and configuring the antispam agent on a hub transport server.
By default the agents are not installed on the hub role since this server is intended to be a down stream server behind an Exchange Edge Server. Throughout the article you will see that some features can be manged via EMC and a number of features must be managed via EMS.

Installing Anti Spam Agents
By default the Anti Spam agents are not installed on the hub servers ***these must be installed on each hub that you want to utilze the agents ****

Open EMC
Organizational Configuration
Select the Hub Transport Server

As you can see there is no reference to the anti spam agents

Lets go ahead and install the Agents”

1. Open EMS
2. you can change to the directory or input the path to the powershell script (I chose to change to the directory) Change to C:\progroam files\Microsoft\Exchange Server\Scripts (assuming install directory is default)
3. ./install-AntiSpamAgents.ps1

After the agents are installed the Transport Service needs to be restarted

Lets go back to EMC–Organizational Configuration — Hub Transport

We now have an Anti Spam Tab with a number of items to configure

CONFIGURATION:
Now that we have installed our Anti Spam Agents lets take a look at what we can configure. Some configuration can only be done from EMS and some can be done from both EMS and EMC.
Content Filtering
IP Allow List
IP Allow List Providers
IP Block List
IP Block List Providers
Recpient Filtering
Sender Filtering
Sender ID
Sender Reputation

Content Filtering:
When the Content Filter agent is enabled on a computer, the Content Filter agent filters all messages that come through all Receive connectors on that computer. Only messages that come from external sources are filtered. External sources are defined as non-authenticated sources that are considered anonymous Internet sources.

http://technet.microsoft.com/en-us/library/bb124739.aspx

Content filter provides us with 3 tabs that we can configure
1. Custom Words
2. Exceptions
3. Action