Forum Discussion

Tifosa's avatar
Tifosa
Level 4
13 years ago

Symantec's SetEVExchangePermissions.ps1 not working

Hi All,

We are trying to only assign permissions on a single Exchange 2007 CCR cluster, however when we run SetEVExchangePermissions.ps1 with the below information it applies to the entire enterprise

SetEVExchangePermissions.ps1 -User domain\serviceaccount -Server servername

We get the following error

 

Ignoring -Server parameter as the script is being run from within Exchange Management Shell
 
We are running this script from the EMS which is ran as Administrator. All out permissions are fine
 
Can someone please assist?
 
Cheers
Configuring
Documentation
Enterprise Vault
Information Governance
Installing
Troubleshooting
Upgrade

3 Replies

Sort By
  • LCT's avatar
    LCT
    Level 6
    13 years ago

    That's not an error...it's just a warning telling you that it will ignore - server parameter as it is running using the Exchange Management Powershell which is what you should be using.

    To ensure that the permissions have applied correctly check the user's mailboxes permissions and ensure that VSA has full permissions. You may need to wait for replication to take affect or you can restart the information store service to speed it up (if you can do it during working hours).

    Hope that helps.

  • Tifosa's avatar
    Tifosa
    Level 4
    13 years ago

    Hi CTEV,

    Sorry i wasn't clear on what we are after. We only want to apply the permissions on one server, which is why we want to use the -server parameter

    It does indeed set the permissions, but across the entire organisation while we only want to limit to one server. This particular server is in another region and we want to lock it down so other admins won't be able to have higher permissions than they require

  • LCT's avatar
    LCT
    Level 6
    13 years ago

    Ah I see....OK.

    http://www.symantec.com/business/support/index?page=content&id=TECH51293

    http://www.symantec.com/business/support/index?page=content&id=TECH138606

    You probably have seen these already. But try and run the script remotely using Windows powershell v2 and 'I think' you can specify the exchange server.

    Otherwise you'll probably have to check the script itself and change appropriately. I have had a few people changing the script itself to apply the permissions to their own needs. Unfortunately I am not a script person so I can't help you with this part. May have to log a case with Tech Support to see if they can assist you if no one here can.

    Hope this helps.