Active Directory operation failed on *DomainController*. This error is not retriable. Additional information: Insufficient access rights to perform the operation.

When you try to move a mailbox from Exchange 2007 to Exchange 2010,  following error occured:

Error:
Active Directory operation failed on *DomainController*. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

The user has insufficient access rights.

Exchange Management Shell command attempted:
’*OUStructure*’ | New-MoveRequest -TargetDatabase ‘Mailbox Database 1985885663′ -BadItemLimit ‘-1′

To resolve this error…..by editing the Advanced Security Settings for that user,

  • Open Active Directory Users and Computers
  • Find the user of which the mailbox error occured
  • Open  the properties of the user and go to the security tab (if this is not available, choose view and then advanced features in the AD users and computers under  MMC)
  • Click on [Advanced]
  • Check the box at the bottom which says “Include inheritable permissions from this object’s parent” and then click [OK] twice.
Error fixing

Then try to move it and it will work…

Activating Product Key – Exchange 2010

Activate the product key for Exchange Server 2010 (for each role installed)..otherwise you can run it for 119 days…!!!!

To activate the same, from the Exchange Management console of 2010, right pannel, you will see “Enter Product Key”…and enter the product key which comes with it…!!

Exchange 2010 – Manage CAS role – Access is denied error – HResult = -2147024891

ERROR: An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891

After installing Exchange 2010 server in an Exchange 2007 server environment may get some funny error results. After the installation Exchange 2010 , open the Exchange management console, you nee to go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and here you will receive the following error message.

So let run the “Get-OwaVirtualDirectory” in powershell and you will get the following result

From the power Shell command prompt .. Run

[PS] C:\Windows\system32>Get-OwaVirtualDirectory

An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
    + CategoryInfo          : NotInstalled: (<ExchangeServer2007>\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
   , IISGeneralCOMException
    + FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory

Above command reads the Active Directory objects to see all the registered OWA virtual directories. The virtual directories you retrieve are the virtual directories from Exchange 2010,  but also from Exchange 2007. Next it connects to these directories and needs admin rights. This is the problem. Exchange 2010 creates a few new groups and one of them is Exchange Trusted Subsystem. Exchange Trusted Subsystem is automatically added to the local administrators group of the Exchange 2010 server but not on the Exchange 2007 servers. 

RESOLUTION :  All you need to do is add the Exchange Trusted Subsystem to the local administrators group on the Exchange 2007 CAS servers and restart the server, including the new 2010 H&C Server.

Now  run the “Get-OwaVirtualDirectory” in powershell we see:

[PS] C:\Windows\system32>Get-OwaVirtualDirectory

Name                                    Server                                  OwaVersion
—-                                    ——                                  ———-
Exchange (Default Web Site)             <ExchangeServer2007>                                 Exchange2003or2000
Public (Default Web Site)               <ExchangeServer2007>                               Exchange2003or2000
Exadmin (Default Web Site)              <ExchangeServer2007>                                 Exchange2003or2000

owa (Default Web Site)                  <ExchangeServer2010>                                 Exchange2010

 

Microsoft SharePoint Workspace 2010 – New turn

SharePoint Workspace 2010 is the new name for and succeeds Microsoft Office Groove 2007. SharePoint Workspace 2010 is a client application that provides fast, any-time interactive access to document libraries and lists on Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010. SharePoint Workspace 2010 also provides options for creating Groove peer workspaces and Shared Folder workspaces. SharePoint Workspace 2010 is more versatile than Microsoft Office Groove 2007 and can be integrated with Microsoft SharePoint Server 2010 or can run independently. Microsoft SharePoint Workspace 2010 provides a client for Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 that enables real-time synchronization of desktop content with SharePoint documents and lists. SharePoint Workspace 2010 also provides options for creating Groove collaboration workspaces and synchronized shared folders. By using SharePoint Workspace 2010, information workers can easily synchronize online and offline content with a designated SharePoint site or collaborate with external partners and offsite team members through shared workspaces. SharePoint Workspace 2010 is included with Microsoft Office Professional Plus 2010.

Key features of SharePoint Workspace 2010 include the following:

A choice of workspace types:

  • SharePoint workspaces — Provide direct bi-directional synchronization of library and list content between a SharePoint site and a workspace on an individual client computer. Creation of a SharePoint workspace enables individual SharePoint users to check out and check in SharePoint library documents from their local computers, bring SharePoint documents and lists to their computers where they can work online or offline, and synchronize local content with a SharePoint site. When an individual client establishes a connection with a SharePoint server, synchronization occurs at regular intervals when the client is online. When a client cannot connect to a SharePoint site, the user can easily take work offline to make updates. The updated documents are automatically synchronized with SharePoint document libraries and lists when the user reconnects. This interface offers an efficient and satisfying alternative to browser access of SharePoint. Unlike other workspace types, the SharePoint workspace is a personal synchronized copy of a SharePoint site.
  • Groove workspaces — Provide a rich and secure peer collaboration environment that supports synchronization of content among peer client computers that host a shared workspace. Creation of a Groove workspace enables SharePoint Workspace users to quickly form teams and automatically synchronize online or offline contributions with fellow team members. A full set of collaboration tools lets team members schedule meetings, hold discussions, and share work with trusted partners around the world. Support for communications under various network conditions and across firewalls facilitates timely and effective collaboration.
  • Shared Folder workspaces — Support Windows folder sharing among clients. Creation of a Shared Folder workspace lets information workers share the contents of a common folder in a designated Windows Explorer directory.
  • Easy setup   Windows users can easily download and run SharePoint Workspace 2010 without IT assistance.
  • Offline and online collaboration   Information workers can easily synchronize online and offline work, through a SharePoint workspace, Groove workspace, or Shared Folder workspace. Content is synchronized dynamically among online collaboration points and updates are transmitted immediately when an offline client comes back online. When an offline client reconnects, SharePoint Workspace automatically adds offline contributions to the workspace and applies workspace updates to the previously offline client.
  • Integration with Windows logon   SharePoint Workspace 2010 uses Windows logon credentials to authenticate users so that a separate logon is not necessary.
  • Common file dialog boxes   Windows technology enables Microsoft Office 2010 users to directly open and save files in SharePoint Workspace.

When you install Microsoft Office 2010 package, you will get a program, which is Sharepoint workspace 2010, which is the replacement of Grove and the installation as follows

If you have a SPS domain in your domain network, use your own login credential only.

Once this is done, click Internet Explorer and open your SPS webpage. Under Site Action, Click Sync to SPS workspace

Once the Sync is completed, you can now use your doman SharePoint Site offline and online.

For Setting modification, use the File menu and do the needful

Operational Restrictions
SharePoint Workspace operates with a recommeded maximum number of synchronized documents – 10,000. Synchronizing extremely large document libraries, such as a Document Center, is not supported.

SharePoint Workspace also has limited support for metadata extensions to the document library. BDC Fields based on Business Connectivity Services – tagging documents based on external datasources – is not supported, and libraries that use BDC field definitions cannot be synced to Workspace. On the other hand, Managed Metadata fields (MMS) can be included in synchronized libraries. SharePoint Workspace is able to view, but not modify, field values based on MMS term stores.

To Download SharePoint Workspace 2010: Groove Web Services Software Development Kit, Click here.

Enjoy!!!

Old public folder – How to remove from Exchange server

It is difficult to delete old public folder from EMC. How to do it, use the ADSIEDIT to clear the old ones.

Right click on the folder you want to delete from CN=Exchange Administrative Group, CN=Databases,  and click delete. The go to Active directory Sites and Services and initiate the replication across the domain.

Go to EMC and refresh.

Thats it.

Exchange server 2010 – Symantec 2010 – DAG Backup failed – Scenario/Solution

Here is a typical scenario of a DAG backup failure from Symantec.

If you come across an email alert from the Backup administrator like below,

Not to be panic…click on the attachment and see what the error is..and it should be like below

Then go to details…

Exchange server 2010 DAG backup failed!!! ohhhhhh.. Try to ping the DAG IP address. If no response, Logon to Mailbox server, and open Failover cluster manager.

Remember, DAG’s basics is on clustering. Click on Cluster events

Goto to the Services -> click on Cluster Services and then click Restart.

This will happen when the mailbox server faces “Dirty Shutdown” or Network connection lost.

View user mailbox size from Outlook

Adding attachment size limit in Outlook through Exchange 2010 EMC

Common for entire organization, from the mail box server, from EMC, under Organization, Mailbox->Select database, Properties, do the following

Here i mentioned about 20MB attachments to send and receive by the users. The problem here is that, it take a bit time to receive/send because of the high size. So be careful and be patient.

When you do this default setting on the organization level, each users mailbox will have the following (User mailbox database defaults)

If you want to over write this policy to certain users, go to the users mailbox settings, Storage quotas and edit as below. 

First Uncheck the “Use mailbox database defaults and insert the value as you want. This settings will override the defaults.

Thats all folks!!!

Exchange 2010 Architecture Poster

To download the Exchange 2010 Architecture Poster, click here  Image size  in 36″ x 24″

To download the Exchange Server 2010 Architecture Poster (PDF).

For Transport architecture diagrams, see Exchange 2010 Transport Architecture Diagrams Available for Download.

Thanks to Microsoft Exchange Team for this

Changing your domain password in OWA

In the previous edition of OWA and Exchange server 2007, there was a problem for users to change their password…because the loss of the IISADMPWD virtual directory as a supported feature in Windows Server 2008/IIS 7.0. This prevented OWA users with expired passwords from being able to change their password and log on. This was a problem for many OWA users ; especially remote/mobile users with non-domain-joined computers..From Exchange Server 2010 Service Pack 1 and Exchange Server 2007 Service Pack 3 (running on Windows Server 2008 or Windows Server 2008 R2) onwards, they have a new feature that will allow users with expired passwords to change their password. This also works for users who have their accounts configured to change password on next logon.

Use this procedure to enable it on Exchange 2007 SP3 and Exchange 2010 SP1 Client Access servers. If you are using a CAS Array, you must perform these steps on each CAS in the array.

  1. On the Client Access Server (CAS), click Start > Run and type regedit.exe and click OK.
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\MSExchange OWA.
  3. Right click the MSExchange OWA key and click New > DWord (32-bit).
  4. The DWORD value name is ChangeExpiredPasswordEnabled and set the value to 1.
    Note: The values accepted are 1 (or any non-zero value) for “Enabled” or 0 or blank / not present for “Disabled”
  5. After you configure this DWORD value, you must reset IIS. The recommended method to reset IIS is to use IISReset /noforce from a command prompt.

NOTE : User can’t use a User Principal Name (UPN) (eg: myname@domain.com) in the Domain\user name field in the Change Password window like below. It should be domain\myname

Once you done with it, click submit…make sure that your new password should match with the domain password policy.