In Enterprise Vault 11.0, there are many PowerShell commands introduced.
This is an introduction to how to get started.
Symantec.EnterpriseVault.PowerShell.AdminAPI.dll Symantec.EnterpriseVault.PowerShell.Core.dll Symantec.EnterpriseVault.PowerShell.IMAP.dll Symantec.EnterpriseVault.PowerShell.Monitoring.dllThis is an easy to import them and confirm they are loaded by Get-module command.
PS> Get-ChildItem -Filter *PowerShell*dll | %{ Import-Module $_.FullName} PS> (Get-Module).Name
PS> get-command -Module Symantec.EnterpriseVault.PowerShell* |Sort-Object ModuleName |ft -AutoSize
PS> Get-EVTask |%{ [pscustomobject]@{State=(Get-EVTaskState $_.EntryID);Name=$_.name;}}|ft -auto
To automate the Import you can create "Microsoft.PowerShell_profile.ps1" file in "C:\Users\vaultadmin\Documents\WindowsPowerShell\" folder and write the Import-Module commands.
C:\Users\vaultadmin\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.AdminAPI.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.Core.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.IMAP.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.Monitoring.dll"
To run the Micorosft.PowerShell_profile.ps1 script, Excecution Policy has to be changed.
PS> Set-ExecutionPolicy RemoteSigned
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.