Exchange 2010 CAS proxy to Exchange 2013 CAS: Use the following link to open this mailbox with the best performance:

Hello,
I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
and moved one mailbox [ Test user ] to Exchange 2013.
When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
    Use the following link to open this mailbox with the best performance: with link to 2013 OWA...
What is wrong ?
I've checked and changed settings by:
Get-OwaVirtualDirectory, Set-OwaVirtualDirectory
[PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
Server                        : EX10
Name                          : owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
RedirectToOptimalOWAServer    : True
LegacyRedirectType            : Silent
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://ex10.contoso.com/owa
ExternalUrl                   : https://ex10.contoso.com/owa
[PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
Server                        : EX13
Name                          : owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
RedirectToOptimalOWAServer    : True
LegacyRedirectType            : Silent
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://ex13.contoso.com/owa
ExternalUrl                   :
best regards Janusz Such

Hi Janusz Such,
Based on my knowledge, CAS proxy can only from later version to previous version.
Some like CAS2013 to CAS2010/2007, CAS2013 to CAS2013. 
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

  • I have an imac bought late 2013, can i use it as a display for the new mac pro? I also want to use windows 8 on it, would this work with parallels or bootcamp?

    I have an imac bought late 2013, can i use it as a display for the new mac pro? I also want to use windows 8 on it, would this work with parallels or bootcamp?

    Yes, it supports target display mode. Windows can be run with either Parallels or Boot Camp.

  • I am unable to burn any info-photo ect on to a disk. I have a 27" I mac mid 2010 version. I put in a disk, hit burn, it runs for about 3 mins and ejects the disk sayiny there was an error with the drive and will not restart.

    am unable to burn any info-photo ect on to a disk. I have a 27" I mac mid 2010 version. I put in a disk, hit burn, it runs for about 3 mins and ejects the disk sayiny there was an error with the drive and will not restart.

    The optical drive has probably failed. It's a fairly common thing with these slim SuperDrives. Does it read any discs you put into it? You can try resetting the SMC and pram but I'll be surprised if it helps.
    To reset the SMC
    Shut down the computer.
    Unplug the computer's power cord.
    Wait fifteen seconds.
    Attach the computer's power cord.
    Wait five seconds, then press the power button to turn on
    Resetting PRAM and NVRAM
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.

  • I just bought a new 2013 Honda civic and my iPhone 4S won't pair with the cars Bluetooth device but it did on other people's iPhones; I have no other Bluetooth devices on my phone. Any suggestions?

    I just bought a new 2013 Honda civic and my iPhone 4S won't pair with the cars Bluetooth device but it did on other people's iPhones; I have no other Bluetooth devices on my phone. Any suggestions?

    I have to ask,
    Are you making sure you are in park before attempting the sync?   The car won't allow you to do it in motion, whether or not you're the passenger.

  • Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

    We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
    alex serdyukov

    Hi Alex,
    As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
    Cumulative Update 8 for Exchange Server 2013
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 OWA usage in Exchange 2013

    Hi,
    I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
    Before Migration we want below things to keep in mind...
    1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
    2. Can i use my Existing Exchange certificate to get the above goal done ?
    3. What will be the steps and pre-requsite to achieve the Goal ?
    An Early reply would be appreciated !! 
    Amit

    Hi Amit 
    First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
    Configure external  DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
    Ensure that you are having a seperate name for CAS array from external ews url
    Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
    Authentication for OUtlook Anywhere should be - NTLM
    for OWA exchange 2010 - FBA and windows 
    Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users 
    You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
    Apply a new certificate with all the required site names included in Exchange 2013 CAS.
    Whats more you can refer my blog as well 
    http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
    Cheers :)
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Migrating an Exchange 2010 Generated OAB to Exchange 2013

    Hello,
    I'm trying to find some information on how to migrate the offline address book from Exchange 201o to Exchange 2013, but I'm having a lot of trouble finding anything at all that is of any use, so I was hoping the experts here might be able to offer some advice.
    I have an environment where all mailboxes are on Exchange 2010. Recently I introduced Exchange 2013 into the environment, so we have a co-existence situation. At the moment we run a multi-tenant system that has over 1600 OABs, all assigned to various customers
    using Address Book Policies. Soon, I will be starting to migrate mailboxes to 2013, so I was looking at what closing down activity is necessary to remove 2010, with one of the tasks being the transferral of the OAB. I understand the arbitration mailbox bit
    and how it works on 2013, equally I understand the 2010 bit and how that works, but it's the transition from using a 2010 OAB to using a 2013 OAB that I don't understand. From what I've read to date it seems like the only option might be to totally recreate
    the OABs in 2013. Surely this can't be the only way, can it? This is going to be a mammoth task for me if that's the case. Can I therefore just ask whether anyone knows anything about this in something other than a basic almost default environment where everyone
    only uses a single OAB and its an easy task?
    I have seen another post here in the forums about this:
    http://social.technet.microsoft.com/Forums/en-US/121f282c-1ff4-401d-9257-5dfbf17d4a5c/going-from-exchange-2010-to-exchange-2013-what-about-my-2010-oab?forum=exchangesvrgeneral
    I didn't fully understand the answer though. In the article above it states:
    "NO you don't have to move, all OAB's have already been created and stored in your OABGEN mailbox and are safe there Updating 12 times a day. The way OABs are stored has changed and its even better. all OABs have gone into <Default Offline
    Address Book 2013>."
    But that still doesn't detract from the fact that whether there's any kind of sync going on or not, I still have 1600+ OABs generated by a 2010 server, and either I can't uninstall the last 2010 server because of that, or I delete the OAB, in which case
    I lose the OAB anyway. Or is the articles trying to state that I don't need multiple OABs because it's all in the default, and that even if I use multiple ABPs then each one should use the default OAB? That doesn't sound right.
    I have tested doing it the manual way in a lab (by that I mean creating a new OAB in 2013, then replacing a test user's OAB in the ABP assigned to them). That seems to work, but I don't want to have to do it that way for everyone if I can avoid it.
    Any help would be much appreciated on this. 

    Ok, so I think I've got an answer to my own question here. Based on my own testing to find out how easy it would be to have to do a delete/recreate of the OABs in 2013 (given that I have over 1600 ABPs and corresponding OABs in a multi-tenant environment),
    I've got this:
    Identify ABPs and which 2010 OABs they use using Get-AddressBookPolicy
    Identify which address lists the 2010 OABs use using Get-OfflineAddressBook
    Create new OABs (maybe same name but putting '2013' on the end or something)
    Switch the OAB defined in the ABP using Set-AddressBookPolicy with the -OfflineAddressBook parameter
    Have I got that right? So actually, not too hard really (if I'm right of course), because I don't have to build any new GALs or ALs based on specific extensionAttribute values, because it's not necessary.

  • Decommission Exchange 2010 but keep Hybrid Excahnge 2013

    All,
    We have finished migrating all users from our Exchange 2010 server to Office 365. We will retain the Exchange 2013 server that was installed during the hybrid configuration for mailbox management, relaying etc. There are no plans to store any many locally
    on this server.
    Questions:
    1. Should the arbitration mailboxes be moved from the 2010 server to the 2013 server? Or can they be removed?
    2. Are there any other considerations that need to be taken into account before uninstalling the 2010 sever?
    Thanks

    Yes, you should move the arbitration mailboxes - they are organizational mailboxes, not mailbox database mailboxes.
    Make sure all Exchange resources and operations hosted on this server have been moved to your Exchange 2013 system before you remove Exchange from this server.  If you try to remove Exchange (in either the GUI or the command line) and something is
    still using this server, you will be alerted that something is still using the server and will be told what it is.
    HTH ...

  • Exchange 2010 and UM on Exchange 2013

    Hello,
    We are going to migrate from Exchange 2010 to Exchange 2013 in a few month, but we want to add UM right now. Can I add UM 2013 now and build everything else later?
    Thank you.
    Thank you. Eric.

    What I'm a little foggy on is if the mailbox needs to be on a 2013 mailbox server for the 2013 UM server to properly deliver the voicemail item. 
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications
    Once the SIP connection is pointed to 2013, it will handle both the 2013 and 2010 Mailboxes in the Dial Plan, yes.
    and dont forget to move the System Mailbox to 2013:
    http://technet.microsoft.com/en-us/library/dn169226(v=exchg.150).aspx
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 dag migration to exchange 2013 help

    If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
    I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
     A  B  -------------- C D
    Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
    A1 ----------- C1
    B ------------- D
    Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
    A1 B1 ----------- C1 D1
    Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
    Anand_N

    Hi,
    When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
    to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
    Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
    Migrating an Exchange 2010 DAG to Exchange 2013
    http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Export Mailbox from Exchange 2010 and Import to Exchange 2007

    Hello,
    I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
    Exchange 2007 mailbox. Is it supported ?
    The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
    Thank you,
    Luca
    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
    New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
    New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
    Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
    the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
    Does anyone have any other solutions or
    workarounds to this. I've got over 900 mailboxes I need this for due to an
    acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
    the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

  • Exchange 2010 Unable to Assign Full Access Permissions using a Security Group

    I've been running into this issue lately.  I cannot seem to use groups to allow full access to mailboxes.  When I add them from the EMC, it will show up when you go to "Manage Full Access Permission...".  After waiting a day and even restarting
    the Information Store service, the permissions do not take effect.  When I view the msExchDelegateListLink attribute of the mailbox account, the group is not listed.
    When I grant a user full permission, it works and updates the attribute.  However, on occasion when I revoke the full access permission for a user is doesn't always remove that user from the msExchDelegateListLink attribute.  So the mailbox
    will still appear in Outlook, but the user isn't able to see new emails.
    Any ideas on what may be going wrong?
    Environment:
    Exchange Server 2010 SP1 Standard
    Windows Server 2008 R2 Standard
    Outlook 2010 SP1 (tried without SP1 as well)
    I was looking over Add-MailboxPermission on Technet (http://technet.microsoft.com/en-us/library/bb124097.aspx) and I noticed that it doesn't mention adding groups.  Is this not possible?

    I never got a proper fix.
    I worked around it by creating a script which gets the members of an AD Mail Enabled security group, and updates the full access based on the groups members.
    Here's a script I'm running every hour which updates permissions. It's probably not the most efficient script ever, but it works. It has several benefits
    1. Managers of the distribution group can add/remove mailbox members using OWA or through the address list
    2. New members of groups are added to FULL Access Permissions
    3. Members removed from the groups are removed from FULL access permissions
    4. Automapping works :)
    5. Maintains a log of access added / removed / time taken etc.
    Obviously I have had to remove domain related information, replace with whatever your domain requirements are, and PLEASE debug it properly in your environent first, don't complain to me if it wipes out a load of access for you or something like that!
    It takes about 5 minutes to run in my environement. Some formatting seems to have got messed up on here, sorry. I hope it is of use!
    # Mailbox Permissions Setter for Exchange #
    # v1.1 #
    # This script will loop through all mailboxes in Exchange and find any where #
    # the type is 'SHARED'. These should be determined to be a GROUP/SHARED mailbox #
    # and access to these mailboxes are controlled by a single ACL, e.g. 'ACL_Shared_Mailbox'. #
    # This script will add any members of these ACLs directly to the Full Access Permissions #
    # of the mailbox and also remove them if they no longer need the access. #
    # Script created by Jon Read, Technical Administration
    # Recent Changes
    # 15/11/2012
    # 1.1 Added exclusions for ACLs that we don't want automapping to happen for
    # 12/11/2012
    # 1.0 Initial script
    #Do not change these values
    Add-PSSnapin *Ex*
    $starttime = Get-Date
    $logfile = "C:\accesslog.txt"
    $logfile2 = "C:\accesslog2.txt"
    $totaladditionstomailboxes = 0
    $totalremovalsfrommailboxes = 0
    $totalmailboxesprocessed = 0
    $totalmailboxesskipped = 0
    # Exclude any ACLs that shouldn't be processed here if they are used for a non-standard purpose and
    # we don't want FULL access mapping to happen. Seperate array values with commas
    $ExcludedACLArray = "DOMAIN\ACL_ExcludedExample"
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-Output "#----------------------------------------------------------------#" >> $logfile
    Write-Output "# Mailbox Permissions Setter for Exchange #" >> $logfile
    Write-Output "# v1.1 #" >> $logfile
    Write-Output "#----------------------------------------------------------------#" >> $logfile
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-output "Start time $starttime ">> $logfile
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    # Set preferred DCs and GCs
    $preferredDC = "preferredDC.domain"
    $preferredGC = "preferredGC.domain"
    Write-Output " PreferredDC = $preferredDC ">> $logfile
    Write-Output " PreferredGC = $preferredGC " >> $logfile
    Set-ADServerSettings -PreferredGlobalCatalog $preferredGC -SetPreferredDomainControllers $preferredDC
    # The first part of this will ADD permissions to the mailbox, reading from an associated ACL.
    # Check for all mailboxes where the type is SHARED. These are the only ones we would
    # want to apply group mailbox permissions to.
    foreach ($mailbox in get-mailbox -resultsize "unlimited" | where-object {$_.RecipientTypeDetails -eq "SharedMailbox"})
    $totalmailboxesprocessed = $totalmailboxesprocessed + 1
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-Output "|-------------------------------------------------------" >> $logfile
    Write-Output "| MAILBOX ADDITIONS: $mailbox " >> $logfile
    Write-Output "|-------------------------------------------------------" >> $logfile
    $mailbox=$mailbox.ExchangeGuid.ToString()
    # For each of them, get the distribution list applied to the mailbox (Starting DOMAIN\ACL_)
    # We then need it to be turned into a string to use later.
    #Declared $changes as 0. if this is set to 0 at the end of the mailbox job, we know no changes were made.
    $changes = 0
    foreach ($distributiongroup in get-mailbox $mailbox | Get-MailboxPermission | Where-Object {$_.User -like "DOMAIN\ACL_*" })
    $skipACL = 0
    #Get the distribution group and put the name in a useable format
    $distributiongroup=$distributiongroup.user.tostring()
    Write-Output "Found ACL $distributiongroup" >> $logfile
    # Check if this distribution group needs to be excluded and if it shouldn't be processed
    # then move onto the next ACL. This will stop FULL access being granted if the mailbox is
    # used for a non-standard purpose. See the start of this script
    # for where these are excluded (ExcludedACLArray)
    foreach ($ACL in $ExcludedACLArray )
    if ($distributiongroup -eq $ACL)
    $skipACL = 1
    Write-Output "ACL $distributiongroup is excluded so skipping mailbox " >> $logfile
    $totalmailboxesskipped = $totalmailboxesskipped + 1
    if ($skipACL -eq 0)
    # Get each user in this group and for each of them, add try to add them to full access permissions.
    foreach ($user in Get-DistributionGroupMember -identity $distributiongroup)
    # Get the user to try, convert to DOMAIN\USER to use shortly
    $user="DOMAIN\" + $user.alias.ToString()
    # Check to see if the user we have chosen from the ACL group already exists in the full access
    # permissions. If they do, set $userexists to 1, if they do not, leave $userexists set to 0.
    # Set $userexists to 0 as the default
    $userexists = 0
    foreach ($fullaccessuser in get-mailbox $mailbox | Get-MailboxPermission)
    # See if the user exists in the mailbox access list.
    # Change $fullaccessuser to a useable string (matching $user)
    $fullaccessuser=$fullaccessuser.user.tostring()
    if ($fullaccessuser -eq $user)
    $userexists=1
    # Break out of foreach if the user exists so we don't unnecessarily loop
    break
    # Now we know if the user needs to be added or not, so run code (if needed) to add
    # the user to full access permissions
    if ($userexists -eq 0)
    Add-MailboxPermission $mailbox –user $user –accessrights "FullAccess"
    Write-Output "Added $user " >> $logfile
    $changes = 1
    $totaladditionstomailboxes = $totaladditionstomailboxes + 1
    #Now repeat for other users in the ACL
    #if changes were 0, then log that no changes were made
    if ($changes -eq 0)
    Write-Output "No changes were made." >> $logfile
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-Output "---------------------------------------------------------------------------------" >> $logfile
    Write-Output " FINISHED ADDING PERMISSIONS" >> $logfile
    Write-Output "---------------------------------------------------------------------------------" >> $logfile
    Write-Output " " >> $logfile
    # The second part of this will REMOVE permissions from the mailbox, reading from an associated ACL.
    ## Check for all mailboxes where the type is SHARED. These are the only ones we would
    ## want to apply group mailbox permissions to.
    foreach ($mailbox in get-mailbox -resultsize "unlimited" | where-object {$_.RecipientTypeDetails -eq "SharedMailbox"})
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-Output "|-------------------------------------------------------" >> $logfile
    Write-Output "| MAILBOX REMOVALS : $mailbox " >> $logfile
    Write-Output "|-------------------------------------------------------" >> $logfile
    $mailbox=$mailbox.ExchangeGuid.ToString()
    #Declared $changes as 0. if this is set to 0 at the end of the mailbox job, we know no changes were made.
    $changes = 0
    # For the current mailbox, get a list of all users with FULLACCESS, and then for each of them
    # check if they exist in the ACL
    foreach ($fullaccessuser in get-mailbox $mailbox | Get-MailboxPermission | Where-Object {$_.Accessrights -like "FullAccess" })
    # Get the security identifier (SSID) of the FULLACCESS user to store for later.
    $fullaccessuserSSID=$fullaccessuser.user.SecurityIdentifier.ToString()
    $fullaccessuser=$fullaccessuser.User.ToString()
    #If user needs to be excluded then skip this bit
    #Users added or removed will only start with 07 (07$, 07T, so only run if the user starts with this.
    #This stops it trying to remove NT AUTHORITY\SELF and other System entries
    if ($fullaccessuser -like "DOMAIN\07*")
    # Set $userexists to be 0. if we find the use user needs to remain, then change it to 1.
    $userexists=0
    # Check if this user exists in the ACL, if not, remove.
    foreach ($distributiongroup in get-mailbox $mailbox | Get-MailboxPermission | Where-Object {$_.User -like "DOMAIN\ACL_*" })
    $distributiongroup=$distributiongroup.user.tostring()
    #Write-Output "Found associated distribution group $distributiongroup" >> $logfile
    # Get each user in this group and for each of them, See if it matches the user in the mailbox.
    foreach ($user in Get-DistributionGroupMember -identity $distributiongroup)
    # Get the user to try, convert to DOMAIN\USER to use shortly
    $userguid = $user.Guid.ToString()
    $user="DOMAIN\" + $user.alias.ToString()
    if ($fullaccessuser -eq $user)
    $userexists=1
    #we have found the user exists so no need to continue
    break
    # If userexists = 0, then they are NOT in the ACL, and should be removed from
    # the full access permissions. Run the code to remove them from full access.
    #CONVERT FULLACCESSUSER TO GUID AND REMOVE $FULLACCESSUSERGUID NOT $USERGUID
    if ($userexists -eq 0)
    Remove-MailboxPermission -Identity $mailbox –user $fullaccessuserSSID –accessrights "FullAccess" -Confirm:$false
    Write-Output "Removed $fullaccessuser " >> $logfile
    $changes = 1
    $totalremovalsfrommailboxes = $totalremovalsfrommailboxes + 1
    # if changes = 0, no changes were made to this mailbox, so log this fact.
    if ($changes -eq 0)
    Write-Output "No changes were made." >> $logfile
    #Put the time in a displayable format
    $endtime = Get-Date
    $runtime = $endtime - $starttime
    $runtime = $runtime.ToString()
    $runtime1 = $runtime.split(".")
    $totaltime = $runtime1[0]
    Write-Output " " >> $logfile
    Write-Output " " >> $logfile
    Write-Output "|-------------------------------------------------------------------------------------- " >> $logfile
    Write-Output "| SCRIPT COMPLETE : STATS " >> $logfile
    Write-Output "|-------------------------------------------------------------------------------------- " >> $logfile
    Write-Output "| Total Mailboxes Processed : $totalmailboxesprocessed " >> $logfile
    Write-Output "| Total Additions : $totaladditionstomailboxes " >> $logfile
    Write-Output "| Total Removals : $totalremovalsfrommailboxes " >> $logfile
    Write-Output "| Total Mailboxes Skipped due to ACL : $totalmailboxesskipped " >> $logfile
    Write-output "| Start time : $starttime ">> $logfile
    Write-output "| End time : $endtime ">> $logfile
    Write-Output "| **END OF RUN** - Elapsed time : $totaltime " >> $logfile
    Write-Output "|---------------------------------------------------------------------------------------" >> $logfile
    Write-Output " " >> $logfile

  • Exchange 2010 - Moving mailbox database from exchange 2010 server to another exchange 2010 server

    Hi,
    I have a current existing exchange server running on 2008 R2. apparently the partition that holds the mailbox database is getting full and i need to move some user mailboxes to another environment ( exchange 2010 running on 2008 R2). i transferred some users
    successfully to the new location, but am not able to transfer the rest. I am getting the errors:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    Erastus XXXXX
    Failed
    Error:
    The queue in 'MBX2010_STAFF' database already contains a move request for 'Erastus XXXXX', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD
    replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5 -IncludeReport | fl'. If you believe this to be an abandoned move request,
    you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5'.
    Exchange Management Shell command attempted:
    'xxxxxxxx.co.ke/Training Department/XXXXXXX/XXXXXXX/Erastus XXXXX' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
    Elapsed Time: 00:00:00
    AND
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:01
    George XXXXX
    Failed
    Error:
    Service 'net.tcp://win-u5bjh2oamaa.xxxxxxxxx.co.ke/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=207]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
        Lid: 32881   StoreEc: 0x80070005
        Lid: 50035 
        Lid: 64625   StoreEc: 0x80070005
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 56503 
        Lid: 12716   StoreEc: 0x80070005
        Lid: 20794 
        Lid: 28474   StoreEc: 0x80070005
        Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
        Lid: 1750    ---- Remote Context End ----
        Lid: 23354   StoreEc: 0x80070005
        Lid: 25913 
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80070005
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80070005
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80070005
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80070005
    Exception details: MapiExceptionNoAccess (80070005): MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=207]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
        Lid: 32881   StoreEc: 0x80070005
        Lid: 50035 
        Lid: 64625   StoreEc: 0x80070005
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 56503 
        Lid: 12716   StoreEc: 0x80070005
        Lid: 20794 
        Lid: 28474   StoreEc: 0x80070005
        Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
        Lid: 1750    ---- Remote Context End ----
        Lid: 23354   StoreEc: 0x80070005
        Lid: 25913 
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80070005
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80070005
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80070005
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80070005
    Exchange Management Shell command attempted:
    'xxxxxxxxxx.co.ke/Training Department/xxxxxx/xxxxxxx/George xxxxxxx' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
    Elapsed Time: 00:00:01
    I have all the proper rights.
    YOUR ASSISTANCE WILL BE HIGHLY APPRECIATED. THANX :)

    0x80070005 is pretty standard access denied entries.  I would start digging into ACLs on a handful
    of mailboxes.
    Is there another Admin that can give it a shot to test their permissions vs yours?
    - If you find my post to be helpful, or the answer, please mark it appropriately. Thank you.
    Chris Ream

  • Unable to connect to Exchange 2010 Management console after - Exchange 2010 SP3 Rollup 7

    We have been having issue with our Exchange Server 2010's Transport Service failing due to a database corruption. I was hoping that maybe applying the Roll-up 7 for Exchange might fix this issue, however after applying the patch we are unable to start the
    MSExchangeMailboxAssistants "Error 1053: The service did not respond to the start or control request in a timely fashion."
    Then I notice that we were unable to connect to the Management Console or through PowerShell. 
    Event 1000, Application Error
    Faulting application name: MSExchangeMailboxAssistants.exe, version: 14.3.210.2, time stamp: 0x53e2bf34
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
    Exception code: 0xe0434f4d
    Fault offset: 0x000000000000940d
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    PowerShell error:
    Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Could not load file or assembly 'Microsoft.Exchange.Man
    agement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name va
    lidation failed. (Exception from HRESULT: 0x8013141A)"
    At C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1:75 char:92
    + $typeLoadResult = [Microsoft.Exchange.Configuration.Tasks.TaskHelper]::TryLoadExchangeTypes <<<< ($ManagementPath, $t
    ypeListToCheck)
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : DotNetMethodException

    Hi,
    Please try the following steps to narrow down the issue:
    1. Uninstall and reinstall .NET package in Exchange server.
    2. Under location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG, took a copy of Machine.Config.default, renam it to Machine.config and copy it under this path again.
    3. Do IIS reset by running iisreset from a Command Prompt window.
    4. Reboot the server and verify whether the Exchange services are started.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Is any one having audio glitches with the new iMac 2013 (fusion drive)no matter what audio interface they are using?, is any one having audio glitches with the new iMac 2013 (fusion drive)no matter what audio interface they are using?

    Hello I recently purchased a new imac 2013 with fusion drive about five weeks ago I am currently using sounddevices usb-pre2 as my audio interface every 2 to 3 minutes i get audio glitches in the audio whether its itunes or the internet doesn't matter I checked on the internet evey on says its the fusion drive.it *****, I wonder if an update can fix this???

    Have you read for possible solutions over in the "More Like This" thread over here?----------------------->

Maybe you are looking for