Exchange Server 2007 SP3 Meeting "Add Rooms" Resources

Exchange 2007 SP3 on Server 2003 - We have a number of meeting rooms setup and recently an issue has come up.  Users are being asked to authenticate or the error "The address list cannot be displayed.  The connection to Microsoft Exchange
is unavailable ..." when booking the room from scheduling assistant.  The strange thing seems to be that this authentication request (or error) only occurs after a certain amount of hours (before that the meeting room list is populated and credentials
are passed without user intervention).  The user can not authenticate (even the exchange admin) with this window but when the window is cancelled or error is accepted the users can see the meeting rooms.
This is happening with each of our users, anyone have had similar issues or any insights on how to resolve?

Hi,
Does the issue only happen when users view the room mailbox's free/busy information? Please confirm whether the issue happens in OWA. 
Please run the following cmdlet to check the room calendar processing configurations:
Get-MailboxCalendarSettings room1 | fl
Get-WebServicesVirtualDirectory | FL Identity,*url*,*auth*
If there is any event logs in server, please collect some for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

  • Exchange server 2007 SP3

    Dear all,
    Presently we are using exchange server 2007 Sp3 along with windows 2008 x64 Domain controller it's working fine . But we have some issue related with
    Message Size restriction when I changed maximum msg size sent and receive  this option will applied to the mail box user taking long time how can i update this option immediately  to the end users ?
    Best Regards
    Subash 

    Hi,
    After you configure the mailbox size restriction for a mailbox, the configured limits are enforced after a period of time, but do not take effect immediately. Restarting the Microsoft Exchange Information Store service causes the configured limits to take
    effect immediately.
    Please restart the Microsoft Exchange Information Store service to check result.
    Here is a related article about this issue for your reference.
    http://technet.microsoft.com/en-us/library/bb684892(v=exchg.80).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange server 2007 SP3 Apple I PAD mail configuration

    Dear Team,
    We have Exchange server 2007SP3 it's working fine but i would like to receive my Exchange mail in my Apple IPAD from my house  . how can i configure steps ? 
    We are using Cisco VPN connect for our side users coneect fo my office network ..
    Best Regards
    Subash

    Check out the following links. They are for 2010 but the steps are the same
    http://technet.microsoft.com/en-us/library/bb124396(v=exchg.141).aspx
    http://technet.microsoft.com/en-us/library/bb201695(v=exchg.141).aspx
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Exchange server 2007 still on version 8.1 even after applying sp3

    hello,
    I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.
    I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.
    any idea about this issue?
    thank you

    Hi
    As is well known, you
    must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.
    According to your description, I suggest you should check the rangeUpper value by using ADSI Edit .  If the value was 14625. This indicates
    your schema is at Exchange 2007 SP3.
    Here is the article  for your reference:  https://supertekboy.com/2014/05/01/check-exchange-schema-objects-adsi-edit/
    Also you could re-install the patches in the following links .
    Please download and install these patches from here:
    Exchange Server 2007 Service Pack 3: https://www.microsoft.com/en-gb/download/details.aspx?id=24111
    Exchange Server 2007 SP3 Update Rollup 10 : https://www.microsoft.com/en-us/download/details.aspx?id=36708
    Hope it’s helpful to you .
    Best Regards,
    David

  • HELP - Exchange Server 2007 Transport Rule Issue

    Hi all,
    sorry if here is not the place to put my question but I did not find another forum, so if anyone can help me I appreciate.
    - I have an Exchange Server 2007 SP3 environment with 1 MBX Server and 3 CAS/HUB Servers.
    - I have created a Transport Rule that said:
    "all emails that have @test.com in BCC field are dropped off except one group can send" .
    The issue is the rule doesn´t work.
    Anyone can help me, please?
    Thanks in advance.
    Luiz

    The Exchange previous versions forums are here: 
    http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

    Hi,
    We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
    PROBLEM- The following error comes up when we try to access OWA :
    Exception
    Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
    Exception message: Object reference not set to an instance
    of an object.
    Call stack
    Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
    Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
    Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)
    Inner Exception
    Exception type: System.NullReferenceException
    Exception message: Object reference not set to an instance
    of an object.
    Call stack
    Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
    Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
    Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
    Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
    ACTION TAKEN SO FAR :
    1. Removed OWA virtual directories and recreated them again.
    2. IIS has been reset.
    3. Restarted the HUB/CAS server.
    4. Created public folder database.
    Even after doing all these activities, owa is still inaccessible. Please help.
    Regards,
    Ankur

    Hi Ankur,
    From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
    If it is a successful upgrading, please follow the steps below for troubleshooting.
    1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
    2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
    3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your 
    https://URL), check "Only redirect" box and Status code Found 302.
    4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange Server 2007 error during updating SP3

    Hi 
    My exchange server 2007 needs to update to sp3 and the OS is W2K8 Ent. During the update process, there was a prerequisite check and its failed to continue because of the following error.  
    1.Error:The Simple Mail Transfer Protocol (SMTP) service is installed on this computer. This must be removed before Setup can continue.
    2.Error:The Windows Firewall service must be started before Setup can continue.
    3.Error:Setup cannot continue with the upgrade because the 'beremote' () process (ID: 7860) has open files. Close the process and restart Setup.
    I tried to remove the SMTP but it wont uninstall from the server, and IIS is installed on the server also. 
    So, is the SMTP is dependent with IIS and how can I proceed the update now ? And also please remarks on the 3rd error.
    Thanks in advance. 

    run the servermanagercmd -q
    see the output, does it list out smtp servier in green.
    if you have previously uninstalled SMTP service, try restarting your server.
    there was another post with the same error, 
    http://social.technet.microsoft.com/Forums/en-US/7ab14bc1-1a1a-4b6c-a15a-8a13469ae1c8/exchange-2008-installer-detects-smtp-service-but-its-not-installed?forum=exchangesvrdeploylegacy
    If you find this helpful then kindly mark this as answer. Thanks.

  • Problems installing Mailbox role on Exchange Server 2010 SP3

    I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
    me the following error (from the log file):
    [05/03/2013 21:58:09.0090] [1] Executing: 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
    [05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
    Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
    [05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" 
    [05/03/2013 21:58:09.0344] [2] Process standard output: 
    [05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
    [05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
    [05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear(); 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
    [05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
    [05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
    [05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
    I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
    Thanks,
    Matt

    Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
    [02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
    '{ xxxxxxxxxxxxxxxxxxxxxxx }'
    [02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
    [02/24/2014 06:49:07.0592] [2] Process standard output:
    [02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
    [02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
    [02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
    I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
    and everything underneath it.
    My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
    After 24 hours I'll try post again - giving things time to make sure they are actually working.

  • Exchange Server 2010 SP3 test environment - email flow to/from internet

    Today I set up test environment for Exchange Server 2010 SP3 - domain controller running Windows Server 2008 R2 SP1, Exchange Server 2010 SP3 on Windows Server 2008 R2 SP1 and client computer running Windows 7 Pro SP1 x64 with Outlook Pro 2010 x64. These
    machines are VMs on vSphere 5.0 cluster made of 4 esxi 5.0 hosts.
    I have three years of experience in working with Exchange Server 2010 in my production environment but until recently I have not had enough resources to build a test environment. Does "testing" Exchange Server 2010 infrastructure have
    a real life purpose considering the fact that only internal email flow is possible since authoritative SMTP accepted domain is not hosted anywhere thus not visible to outside world. This limited email flow combined with absence of possibility to test
    ActiveSync, Outlook Anywhere, OWA from WAN, . . . really hurt and make Exchange Server rare technology that can not be tested completely before introducing something new into the production. Services that are not possible to test from the outside world are
    useless and whole point of Exchange-like technologies is availability from anywhere and from whatever device.

    I set up Internet Send Connector (by default this type of send connector uses DNS MX records to route email automatically). Having sent an email to my gmail account I did not receive it and in transport logs I saw that mx record was found successfully
    but there is the following line:
    2014-08-05T20:39:51.942Z,Internet Connector,08D17F000FE36010,1,,2a00:1450:4013:c01::1b:25,*,,"Failed to connect. Error Code: 10051, Error Message: A socket operation was attempted to an unreachable network 2a00:1450:4013:c01::1b:25"
    I tried also to send an email to my production email address (we have Symantec Messaging Gateway which is used as a smart host (antispam,antimalware,content filter appliance)) but then error is:
    2014-08-05T20:50:08.395Z,Internet Connector,08D17F000FE36019,1,,91.238.7.10:25,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 91.238.7.10:25"
    Telnet from test exchange to 91.238.7.10 on port 25 also is not working.

  • Exchange Server 2010 SP3 Databases are not mounting after the recovery process

    Hi,
    We are using Exchange server 2010 SP3 in our office. Databases are stored in an ISCSI drive mapped with the exchange. We are taking daily full backup of my Exchange server using Symantec Backup exe 2012. As a testing purpose I created a test environment
    same like my existing live environment to check the disaster recovery and backup. Thankfully disaster recovery worked well and I am able to open the exchange management console and powershell. But I am not able to mount the recovered databases ending
    with an error saying "Couldn't mount the database that you specified. Specified database: officialrecover; Error code:
    An Active Manager operation failed.........." and even I am not able to use the utility eseutil.exe to the database with an error "access to source database failed with jet error 1811". I am able to create a new database and mount
    it.
    I am using Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 in the Live environment with 3 partitions called C (279 GB), E (4.46 TB, ISCSI), F (976 GB) in my Live environment.
    For test it is Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 with 3 partitions C (240 GB), E (1.4 TB), & F (240 GB).
    Please help me with your valid comments to solve and mount the database and close the issue for ever.
    With Regards
    Jay

    Jared is correct that in essence the message is saying the DB cannot be found.
    When you restored to your recovery server are all the paths the same, i.e. if the DB existed on E:\XYZ on the production server it must be the same on the recovery server
    When you restored into the recovery site do you have AD restored into that site as well?
    For the recovery server are you using iSCSI storage for it as well?   If so am I correct to assume that you have copies of the databases just for use on this server and are not trying to reference the same instance of the DB from the production
    and test/recovery server?
    I have also seen an issue where DB's getting written to disk from Symantec mess up the header of the DB.  If you want to validate that the DB is actually intact and accessible you might want to check out our DigiScope product
    http://www.lucid8.com/product/digiscope.asp using a free DEMO license.  If it works i.e. you are able to mount in DigiScope from same location where its failing on the recovery server we know the
    DB your pointing at is good and accessible from the current path but something else is amiss in your configuration
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Project Server 2007: use cannot add lines to or recall timesheet

    I have a certain user that, for some reason, cannot use the Add Lines or Recall Timesheet function in Project Server 2007 SP3. The weird thing is, it works on another laptop, so it must be something related to the user's machine - but I'm baffled as to what
    the exact cause may be.
    There's no error what so ever - no Error On Page as is pretty common with these behaviors.
    Here's what I've tried so far:
    - Internet Explorer 8 version is supported
    - Deleted ActiveX controls, but these don't seem to be a prerequisite for Timesheets
    - IE Compatibility mode on/off
    I have no idea what else to check, and I want to make sure I've tackled everything before escalating this to SysOps for a browser/OS reinstall.

    Hi DMachiels,
    Have you tried to refresh your IE session deleting the cache (CTRL F5)?
    Also ensure that the PWA URL is include in the IE trusted sites (intranet and internet).
    Hope this helps.
    Guillaume Rouyre - MBA, MCP, MCTS

  • Hi, in our Enterprise environment, we have a single mac with Mavericks version 10.9.2 and Office for Mac 14.4.1. When setting up outlook, we are trying to connect to a mailbox on exchange server 2007.

    Hi, in our Enterprise environment, we have a single mac with Mavericks version 10.9.2 and Office for Mac 14.4.1. When setting up outlook, we are trying to connect to a mailbox on exchange server 2007. We put in the EWS details in the server field since our autodiscover function is not functioning. But still it doesn't work. There are no errors, no popups. We turned on the logging and in the logs, it says a error of -3259. We are stuck and any help will be really appreciated.

    I have a customer experiencing exactly the same issue. Their computer is running Windows 7 Pro with Office 2007 SP3. After seemingly exhausting all troubleshooting options, I backed up their data, formatted the hard drive and performed a clean install of
    Windows and all their applications. It didn't solve the problem!
    What's strange is the customer also has a laptop computer, running the same version of Outlook, and that doesn't experience any problems connecting to Office 365 on the same network.
    My next step is to send the customer a new ADSL modem/router to try.
    I have another customer on Office 365, also running Outlook 2007, and they also experience issues with emails sitting in the outbox while Outlook displays the status message “Outlook is trying to retrieve data from the Microsoft exchange server outlook.office365.com.”
    In this case Outlook doesn't freeze/stop responding, like it does for the first customer I mentioned.

  • Exchange server 2007 Service Pack problems SBS 2008

    I am Running Exchange server 2007 on Small Business server 2008 (SBS 2008). I tried to install SP2 but it fails both windows update and manually. Can anyone first advise me what version I'm currently running?
    Help / about form Exchange Management Console displays:
    Version 08.01.0436.000
    And running repair on Exchange server from programs and features displays 2007 SP1 setup. So I believe SP2 to be next I have also ran SP3 but this fails.
    Here is the end lines from a log:
    [03/05/2014 08:54:13] [0] Setup will run the task 'uninstall-msipackage'
    [03/05/2014 08:54:13] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '24b2c164-de66-44fe-b468-a46d9d5e6b31' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''  
    [03/05/2014 08:54:13] [1] Beginning processing.
    [03/05/2014 08:54:13] [1] Property 'PackageName' is 'EXCHANGESERVER.msi'.
    [03/05/2014 08:54:13] [1] Removing MSI package with code '24b2c164-de66-44fe-b468-a46d9d5e6b31'.
    [03/05/2014 09:09:01] [1] [ERROR] Unexpected Error
    [03/05/2014 09:09:01] [1] [ERROR] Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not open key: UNKNOWN\Components\7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613.  
    Verify that you have sufficient access to that key, or contact your support personnel. '.
    [03/05/2014 09:09:01] [1] [ERROR] Fatal error during installation
    [03/05/2014 09:09:01] [1] Ending processing.
    [07/05/2014 19:45:17] [0] End of Setup
    There is a registry key to match this and The administrator account used for setup has access to it i believe??? What does this log mean?

    Hi,
    This error indicated that your account missed registry permissions on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\ 7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613
    Please check whether you have permission. You can also check whether the key have permissions inherited from the Parent Key or not.
    After changing the permission, please run the setup again.
    Best Regards.

  • Exchange Server 2007 / Java issue

    We have just upgraded to Exchange Server 2007. We have a couple of web apps that add an appointment automatically to users calendars using HttpClient PostMethod. Since the upgrade this no longer works. Any ideas or suggestions?

    Hi,
    From your description, I would like to verify the following things for troubleshooting.
    1. Were you able to send and receive emails before?
    2. What type of email account is configured in Outlook?
    3. Please check if you can send and receive emails using OWA.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Grant Application Impersonation Rights for UPN on Exchange Server 2007

    Hi,
    I would like to know , how to grant application impersonation rights for UPN account in exchange server 2007 . As i am working for mailbox migration , i should have this rights . I can do impersonation rights for domain\username but not for [email protected]
    Please anyone help me , how to grant permission for [email protected]
    Big thanks in advance.
    .Thanks & Regards,
    vinoth

    Hi,
    I have a test in my environment using Exchange 2007, you can use the following cmdlet to assign Application Impersonation rights to an account using UPN.
    Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity
    [email protected] | select-object).identity -extendedRight ms-Exch-EPI-Impersonation}
    Get-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User
    [email protected] -ExtendedRights ms-Exch-EPI-May-Impersonate}
    Note: Please change the "[email protected]" to the UPN you want to use.
    Hope my clarification is helpful.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for