Forum Discussion

BigAnvil's avatar
BigAnvil
Level 5
14 years ago
Solved

SetEVExchangePermissions.ps1 "invalid account"

We are in the process of migrating our mailbox to Exchange 2010.  We are currently in a co-existence environment with Exchange 03 & 07.  I moved the EV System mailbox "EVault Admin" to Exchange 2010 yesterday and all jurnaling is going fine.  I followed the instructions for prerequisites but when I try to run the powershell script (with our domain name substituted):

SetEVExchangePermissions.ps1 -User domain\"EVault Admin"

All I get is "Invalid username: "domain\Evault Admin" "

The EV System mailbox is not hidden and the EV System account (same user) is not disabled.

Enterprise Vault
Information Governance

5 Replies

Sort By
  • TonySterling's avatar
    TonySterling
    Moderator
    14 years ago

    Do you actually have space in the display name and are you using quotes?

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    14 years ago

    I *think* your syntax is wrong - just trying to start my virtual machine to check.

     

    You should try :-

     

    SetEVExchangePermissions.ps1 -User "domain\EVault Admin"

     

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    14 years ago

    Having said that I tried both ways .. and it worked.

     

    So...  double check the username and also confirm your VAULT SERVICE ACCOUNT is on the Exchange 2010 server, with a mailbox.

  • BigAnvil's avatar
    BigAnvil
    Level 5
    14 years ago

    Tony hit it on the head.  Although the manual doesn't specify it, the command needs to use the display name and not the account name... there have been other inconsistencies in the "Installing and Configuring" EV 9.0 guide as well.

    I ran it again without the space in the username and it ran successfully.

    With the way Exchange 2010 hanles mailbox moves it's pretty much impossible to not know if the mailbox didn't actually get moved to 2010.  Mailbox moves go into a move queue where you can watch the progress and they do not get automatically removed from the queue when the move completes.  You need to remove completed jobs from the queue, which I think is nice because you can track the status of your moves and have an easy to reference list of what was moved... nice touch.