34 C
Dubai
Tuesday, May 6, 2025
Home Blog Page 103

How to Solve Disk space issues on Your Exchange Server (Event 2013)

Bigger is better, and one place where that axiom holds special significance is with mailbox sizes. Gone are the days of tiny mailboxes and quotas to enforce that. Everything is moving to email and every one of your users needs more space.

If your Exchange Server is connected to a SAN, it’s easy to provision more space as mailbox sizes continue to grow, but if you are running Exchange 2010 with directly attached storage (DAS) you are going to reach the point where there’s just no more space to be added, and as volumes start to reach their limits, you start to see your system log fill with event ID 2013-“disk is at or near capacity. You may need to delete some files.” Exchange archiving is a great way to reduce the size of mailboxes without requiring users to delete content, but it needs another mailbox database for storage. If your Exchange Server is out of space, there’s no place for Exchange archiving to move messages, and buying another Exchange license just for a server to store archives may be excessive, or even out of your budget.

Exchange 2010 made great improvements in performance and its use of disk, and the new vision of large mailboxes combined with cheap storage, seemed like a great way to go for many companies. But as mailboxes grew, it started to take longer and longer to perform database backups, and when necessary, restores. Spreading the largest consumers across multiple databases helped with that, but all that messaging content is still sitting on disks in some Exchange database. As more business processes start to use (or depend upon) an email component, disk consumption continues to climb, and sooner or later, servers begin to throw event 2013s as they run low on space. Once an admin adds as much disk space as the server can handle, they find themselves in a tough spot.

And that’s where email archiving solutions come into play. Giving you the option to supplement or even replace Exchange archiving, email archiving solutions provide another way for users to store and access their older email content, enabling administrators to offload storage from their Exchange Servers. Email archiving solutions work with Exchange, seamlessly plugging in so that users won’t even notice, and enabling admins to easily set up rules to move content from the active Exchange mailbox to the archive storage. Email archives keep the older content online and available to users, but without consuming the costly disk space that Exchange databases prefer, and without a need to purchase another Exchange 2010 license.

So here’s how to solve the 2013’s on your Exchange Server without having to delete a single message or buy another Exchange Server license:

1. Deploy an email archiving solution

2. Integrate it with your existing Exchange infrastructure

3. Migrate older content to the email archive.

You get immediate relief for your Exchange Server, your users don’t lose any content at all, and can start taking rebalancing your existing mailbox databases now that you have breathing room. Email archiving is a great add on, that can take your Exchange archiving to the next level. Check out email archiving softwares today.

This guest post was provided by Casper Manes on behalf of GFI Software Ltd. Read more on how to improve your Exchange archiving.
All product and company names herein may be trademarks of their respective owners.

How to apply a Policy or Mailbox Settings automatically while Creating a mailbox in Exchange 2010

Lets say I want to apply something default when I Create mailbox in my organization

Its bit easy to do using scripting agents

In this example I am applying Address book policy for newly created users automatically , you can add some more commands as per your requirement

Step 1:

Copy the Below Code

<?xml version=”1.0″ encoding=”utf-8″ ?>
<Configuration version=”1.0″>
<Feature Name=”MailboxProvisioning” Cmdlets=”new-mailbox,enable-mailbox”>
<ApiCall Name=”OnComplete”>
if($succeeded) {
Set-Mailbox $provisioningHandler.UserSpecifiedParameters[“Alias”] –AddressbookPolicy “Policy Name
}
</ApiCall>
</Feature>
</Configuration>

Step 2:

Save as “ScriptingAgentConfig.xml

Step 3:

Copy the File in the below location

Default: “C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents”

Step 4:

Enable-CmdletExtensionAgent "Scripting Agent"

image

Now Try creating a mailbox . It should apply the address book policy automatically

In the Same Format you can add some more commands or you can replace the existing ones

For Sample Code you can check in the Below location

C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml.sample

 

How to Remove a Corrupted User Profile from the Registry

After Deleting a User profile Completely – some time we get this event on issue with creating a fresh profile.

Where it stops Creating a new profile on the server

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: Date
Event ID: 1511
Task Category: None
Level: Warning
Keywords: Classic
User: User
Computer: Computer
Description: Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off

Step1:

Open – Regedit

Go to this location

Take a Registry Backup – Recommended – Right Click Export And Save it

You can find Guids with .bak Extension where you can remove those

HKLM\SOFTWARE\Microsoft\Windows NT\ CurrentVersion\ProfileList

image

Log of and Log in back

User profile should Create without any issues

 

How to Install Microsoft® SQL Server® 2008 R2 SP1 on Windows server 2008 R2

Download —

Microsoft® SQL Server® 2008 R2 SP1 – Express Edition

Run the Setup – Click on New Installation or Add Features of an existing installation

image

 

Choose Ok

image

 

Accept

 

image

 

Choose Next

image

 

Choose Next

 

image

Choose Next

image

Choose Next

Choose Mixed Mode

Enter the Password

image

image

 

 

Great !!

You have installed Microsoft® SQL Server® 2008 R2 SP1 on Windows server 2008 R2 Successfully !

Microsoft Releases – Update Rollup 4 for Exchange Server 2010 Service Pack 2 (KB2706690)

Fixes for Update Rollup 4 for Exchange Server 2010 Service Pack 2 (KB2706690)

  • 2536846(http://support.microsoft.com/kb/2536846/ )Email messages sent to a mail-enabled public folder may be queued in a delivery queue on the Hub Transport server in an Exchange Server 2010 environment
  • 2632409(http://support.microsoft.com/kb/2632409/ )Sent item is copied to the Sent Items folder of the wrong mailbox in an Exchange Server 2010 environment when a user is granted the Send As permission
  • 2637915(http://support.microsoft.com/kb/2637915/ )”550 5.7.1″ NDR when an email message is sent between tenant organizations in a multi-tenant Exchange Server 2010 environment
  • 2677727(http://support.microsoft.com/kb/2677727/ )MRM cannot process retention policies on a cloud-based archive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization
  • 2685001(http://support.microsoft.com/kb/2685001/ )Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
  • 2686540(http://support.microsoft.com/kb/2686540/ )Journal report is not delivered to a journaling mailbox in an Exchange Server 2010 environment
  • 2689025(http://support.microsoft.com/kb/2689025/ )Performance issues when you use the light version of Outlook Web App in an Exchange Server 2010 environment
  • 2698571(http://support.microsoft.com/kb/2698571/ )Some email messages are not delivered when you set the MessageRateLimit parameter in a throttling policy in an Exchange Server 2010 environment
  • 2698899(http://support.microsoft.com/kb/2698899/ )Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environment
  • 2700172(http://support.microsoft.com/kb/2700172/ )Recipient’s email address is resolved incorrectly to a contact’s email address in an Exchange Server 2010 environment
  • 2701162(http://support.microsoft.com/kb/2701162/ )User A that is granted the Full Access permission to User B’s mailbox cannot see detailed free/busy information for User B in an Exchange Server 2010 environment
  • 2701624(http://support.microsoft.com/kb/2701624/ )ItemSubject field is empty when you run the Search-MailboxAuditLog cmdlet together with the ShowDetails parameter in an Exchange Server 2010 environment
  • 2702963(http://support.microsoft.com/kb/2702963/ )The “Open Message In Conflict” button is not available in the conflict notification message in Exchange Server 2010
  • 2707242(http://support.microsoft.com/kb/2707242/ )The Exchange Information Store service stops responding on an Exchange Server 2010 server
  • 2709014(http://support.microsoft.com/kb/2709014/ )EdgeTransport.exe process crashes intermittently on an Exchange Server 2010 server
  • 2709935(http://support.microsoft.com/kb/2709935/ )EdgeTransport.exe process repeatedly crashes on an Exchange Server 2010 server
  • 2713339(http://support.microsoft.com/kb/2713339/ )Multi-Mailbox Search feature returns incorrect results when you perform a complex discovery search in an Exchange Server 2010 environment
  • 2713371(http://support.microsoft.com/kb/2713371/ )Throttling policy throttles all EWS applications in Exchange Server 2010
  • 2719894(http://support.microsoft.com/kb/2719894/ )The Microsoft Exchange RPC Client Access service consumes 100 percent of CPU resources and stops responding on an Exchange Server 2010 Client Access server
  • 2723383(http://support.microsoft.com/kb/2723383/ )Incorrect time zone in a notification when the Resource Booking Attendant declines a meeting request from a user in a different time zone in an Exchange Server 2010 environment
  • 2724188(http://support.microsoft.com/kb/2724188/ )A subject that contains colons is truncated in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2726897(http://support.microsoft.com/kb/2726897/ )Event 14035 or Event 1006 is logged when Admin sessions are exhausted in an Exchange Server 2010 environment

Reference link

http://support.microsoft.com/kb/2706690

Download –

Update Rollup 4 for Exchange Server 2010 Service Pack 2 (KB2706690)

 

Microsoft Releases – Update Rollup 8 for Exchange Server 2007 Service Pack 3

Fixes in Rollup 8 for Exchange Server 2007 Service Pack 3

  • 2699574

(http://support.microsoft.com/kb/2699574/ )

Microsoft Exchange Information Store service may stop responding when you perform a search on Exchange mailboxes in an Exchange Server 2007 environment

  • 2701037(http://support.microsoft.com/kb/2701037/ )Events 4999 and 7034 are logged and the Microsoft Exchange Information Store service crashes on an Exchange Server 2007 mailbox server
  • 2730089(http://support.microsoft.com/kb/2730089/ )Microsoft Exchange Information Store service may stop responding when you perform a search on Exchange mailboxes in an Exchange Server 2007 environment
  • 2732525(http://support.microsoft.com/kb/2732525/ )Outlook keeps prompting you for credentials and incorrectly connects to an out-of-site global catalog after you install Update Rollup 6 for Exchange Server 2007 SP3.

Reference

http://support.microsoft.com/kb/2734323

Download =

Update Rollup 8 for Exchange Server 2007 Service Pack 3 (KB2734323)

 

× How can I help you?