Pages

Wednesday 31 March 2010

Add Permissions for Client Users to Access Public Folder Content

http://technet.microsoft.com/en-us/library/aa998834.aspx

When adding client permissions, you can either use predefined permission roles (which consist of specific access rights) or you can customize permissions by manually applying the available access rights. To specify the permissions for the client user, you can use the Add-PublicFolderClientPermission cmdlet or the AddUsersToPFRecursive.ps1 user management script.

Looking for other management tasks related to public folder permissions? Check out Managing Public Folder Permissions.

Aa998834.note(en-us,EXCHG.140).gifNote:
If a client user already has a specific access right to a public folder, you can't add the same access right again. Therefore, if you use the AddUsersToPFRecursive.ps1 script, and the user already has one of the access rights that you're trying to grant, a warning will appear stating that the current access rights will be removed before new access rights are granted.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Public folder client permissions" entry in the Mailbox Permissions topic.

Aa998834.note(en-us,EXCHG.140).gifNote:
You can't use the EMC to add public folder permissions for a client user.

This example adds Publishing Editor permissions for the user Kim to access the public folder West Coast.

Add-PublicFolderClientPermission -Identity "\Marketing\West Coast" -AccessRights PublishingEditor -User Kim

For detailed syntax and parameter information, see Add-PublicFolderClientPermission.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Public folder client permissions" entry in the Mailbox Permissions topic.

This example adds Reviewer permissions for the user David to access the top-level public folder Sales and all of the public folders under it.

AddUsersToPFRecursive.ps1 -TopPublicFolder "\Sales" -User "David" -Permission Reviewer

For more information about how to use public folder management scripts, see Scripts for Managing Public Folders in the Exchange Management Shell.

Thursday 25 March 2010

Powershell Commands With Exchange 2003

Get-WMIObject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -comput
er ExchServer | sort-object MailboxDisplayName | format-table MailboxDisplayName,Servername,StorageGroupName,StoreName,Siz
e,SentItems,TotalItems, DeletedMessageSizeExtended

Monday 15 March 2010

vpxd.cfg Advanced Configuration

The vpxd.cfg is an XML formatted file which can be modified to alter the behaviour of the VMware vCenter Server.



The vpxd.cfg file is located by default at %ALLUSERPROFILE%\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
  • On Windows Server 2008, this would generally be C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg
  • On Windows Server 2003, this would generally be C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
Remember to restart the VMware VirtualCenter Server service in the Server Manager for changes to vpxd.cfg to take effect.

Tag:  blockingTimeoutSeconds
Nested In:  vmomi, soapStubAdapter
What It Does:  Defines the timeout value in seconds for SOAP layer blocking.  Use cases for increasing: slow connections, low bandwidth, or high latency between virtual infrastructure components.  Read more here and here.
Example:
< vmomi> 
< soapStubAdapter> 
< blockingTimeoutSeconds> 10800< /blockingTimeoutSeconds> 
< /soapStubAdapter> 
< /vmomi> 

Tag:  calls
Nested In:  trace, vmomi
What It Does:  Unknown.  Read more here.
Example:
< trace> 
< vmomi> 
< calls> true< /calls> 
< /vmomi> 
< /trace> 

Tag:  cipherList
Nested In:  vmacore, ssl
What It Does:  Reverts to cipher suites used in previous versions of vCenter Server (2.5u3 and earlier) for browser/SSL compatibility issues.  Read more here.
Example:
< vmacore> 
< ssl> 
< cipherList> DEFAULT< /cipherList> 
< /ssl> 
< /vmacore> 

Tag:  compressOnRoll
Nested In:  log
What It Does:  Defines whether or not vCenter Server vpxd log files are rolled up and compressed into .gz files.  Read more here.
Example:
< log> 
< compressOnRoll> false< /compressOnRoll> 
< /log> 

Tag:  cpuFeatureMask
Nested In:  guestOSDescriptor, esx-2-x-x, all-versions, all-guests
What It Does:  Masks CPU features to force VMotion compatibility between hosts. VMware neither supports nor recommends modifying the VMotion constraints for CPU features.  Read more here.
Example:

< guestOSDescriptor> 
< esx-2-x-x> 
< all-versions> 
< all-guests> 
< cpuFeatureMask> Elements and mask definition go in here< /cpuFeatureMask> 
< /all-guests> 
< /all-versions> 
< /esx-2-x-x> 
< /guestOSDescriptor> 

Tag:  directory
Nested In:  log
What It Does:  Defines the location for the vCenter logs.  Read more here.
Example:
< log> 
< directory> D:\VC_Logs< /directory> 
< /log> 

Tag:  dontstartconsolidation
Nested In:  vcp2v
What It Does:  May resolve an issue where the Consolidation button is missing in the Virtual Infrastructure Client.  Read more here.
Example:
< vcp2v> 
< dontstartconsolidation> true< /dontstartconsolidation> 
< /vcp2v> 

Tag:  filterOverheadLimitIssues
Nested In:  vpxd
What It Does:  Unknown.
Example:
< vpxd> 
< filterOverheadLimitIssues> true< /filterOverheadLimitIssues> 
< /vpxd> 

Tag:  hostRescanFilter
Nested In:  unknown
What It Does:  Defines the behavior of mass ESX(i) host rescans of vmHBAs.  Read more here.
Example:
< hostRescanFilter> true< /hostRescanFilter> 

Tag:  IoMax
Nested In:  vmacore, threadpool
What It Does:  Unknown but my guess is it defines the maximum I/O for the vpxd.exe process (vCenter Server service). Influenced by TaskMax.
Example:
< vmacore> 
< threadpool> 
< IoMax> 200< /IoMax> 
< /threadpool> 
< /vmacore> 

Tag:  level
Nested In:  log
What It Does:  Defines the logging level for vCenter logs.  Read more here.
Example:
 < log> 
< level> trivia< /level> 
< /log> 

Tag:  logLevel
Nested In:  trace, vmomi
What It Does:  Enables debug logging level for vmomi?  Read more here.
Example:
< trace> 
< vmomi> 
< logLevel> verbose< /logLevel> 
< /vmomi> 
< /trace> 

Tag:  loglevel
Nested In:  nfc
What It Does:  Enables debug logging level for the NFC process.  Read more here.
Example:
< nfc> 
< loglevel> debug< /loglevel> 
< /nfc> 

Tag:  managedIP
Nested In:  unknown
What It Does:  Defines the managed IP address used in vCenter Server Heartbeat.  Read more here.
Example:
< managedIP> 10.10.0.1< /managedIP> 

Tag:  maxCostPerHost
Nested In:  ResourceManager
What It Does:  Defines the number of simultaneous VM migrations (both hot and cold) per ESX(i) host.  Read more here.
Example:
< ResourceManager> 
< maxCostPerHost> 8< /maxCostPerHost> 
< /ResourceManager> 

Tag:  maxFileNum
Nested In:  log
What It Does:  Defines the maximum number of log files for vCenter logs.  Read more here.
Example:
< log> 
< maxFileNum> 50< /maxFileNum> 
< /log> 

Tag:  maxFileSize
Nested In:  log
What It Does:  Defines the maximum log file size in Bytes and thus rollover interval for vCenter logs.  Read more here.
Example:
< log> 
< maxFileSize> 10485760< /maxFileSize> 
< /log> 

Tag:  name
Nested In:  log
What It Does:  Defines the log file prefix name for vCenter logs.  Read more here.
Example:
< log> 
< name> vpxd< /name> 
< /log> 

Tag:  notRespondingTimeout
Nested In:  heartbeat
What It Does:  Defines the heartbeat timeout value in seconds between ESX(i) hosts and vCenter Server.  Use case would be to increase the value if remote ESX(i) hosts frequently go into a not responding state in vCenter Server due to WAN bandwidth or latency issues.  Read more here.
Example:
< heartbeat> 
< notRespondingTimeout> 60< /notRespondingTimeout> 
< /heartbeat> 

Tag:  portReserveTimeout
Nested In:  dvs
What It Does:  Defines the timeout value in minutes for unused dvPort reservations.  Lowering the value temporarily is helpful for unlocking dvPorts to remove a vDS or dvPort group.  Read more here.
Example:
< dvs> 
< portReserveTimeout> 10< /portReserveTimeout> 
< /dvs> 

Tag:  serializeadds
Nested In:  vpxd, das
What It Does:  Unknown but if I had to guess I’d say it defines the behavior of how the HA agent is installed on cluster hosts.
Example:
< vpxd> 
< das> 
< serializeadds> true< /serializeadds> 
< /das> 
< /vpxd> 

Tag:  slotCpuMinMHz
Nested In:  vpxd, das
What It Does:  Defines the minimum CPU calculation of a HA cluster slot size when there are no CPU reservations. Read more here.
Example:
< vpxd> 
< das> 
< slotCpuMinMHz> 256< /slotCpuMinMHz> 
< /das> 
< /vpxd> 

Tag:  slotMemMinMB
Nested In:  vpxd, das
What It Does:  Defines the minimum memory calculation of a HA cluster slot size when there are no memory reservations. Read more here.
Example:
< vpxd> 
< das> 
< slotMemMinMB> 0< /slotMemMinMB> 
< /das> 
< /vpxd> 

Tag:  sspiProtocol
Nested In:  unknown
What It Does:  Defines the authentication mechanism used with passthrough authentication between the Virtual Infrastructure Client and vCenter Server.  Read more here.
Example:
< sspiProtocol> Kerberos< /sspiProtocol> 

Tag:  TaskMax
Nested In:  vmacore, threadpool
What It Does:  Defines the number of worker threads for the vpxd.exe process (vCenter Server service). Influences IoMax.
Example:
< vmacore> 
< threadpool> 
< TaskMax> 30< /TaskMax> 
< /threadpool> 
< /vmacore> 

Tag:  timeout
Nested In:  task
What It Does:  Defines the timeout value in seconds for long tasks.  Read more here.
Example:
< task> 
< timeout> 10800< /timeout> 
< /task> 

Tag:  verbose
Nested In:  trace, db
What It Does:  Enables database tracing.  Enables database logging in the vpxd log.  Read more here and here.
Example:
< trace> 
< db> 
< verbose> true< /verbose> 
< /db> 
< /trace> 

Tag:  verbosity
Nested In:  trace, vmomi
What It Does:  Unknown.  Read more here.
Example:
< trace> 
< vmomi> 
< verbosity> verbose< /verbosity> 
< /vmomi> 
< /trace> 

Tag:  verboseObjectSize
Nested In:  trace, vmomi
What It Does:  Unknown.  Read more here.
Example:
< trace> 
< vmomi> 
< verboseObjectSize> 40< /verboseObjectSize> 
< /vmomi> 
< /trace> 

Tag:  VMOnVirtualIntranet
Nested In:  migrate, test, CompatibleNetworks
What It Does:  Setting to false enables VMotion for VMs connected to an internal vSwitch. Setting to false will turn off the internal vSwitch restriction on VMotion events. Useful for servers behind a firewall virtual appliance deployed in bridged networking mode.  Read more here.
Example:
< migrate> 
< test> 
< CompatibleNetworks> 
< VMOnVirtualIntranet> false< /VMOnVirtualIntranet> 
< /CompatibleNetworks> 
< /test> 
< /migrate> 

Tag:  VMOverheadGrowthLimit
Nested In:  cluster
What It Does:  Defines the growth rate cap in terms of MB per minute for VM memory overhead at the cluster level. Can be adjusted to resolve high CPU utilization in guest VMs introduced in ESX(i) 3.5 and vCenter 2.5.  Read more here.
Example:
< cluster> 
< VMOverheadGrowthLimit> 5< /VMOverheadGrowthLimit> 
< /cluster> 
 
Slightly related, the vCenter Server process (vpxd.exe) can be launched at a command prompt on the vCenter Server (instead of starting as a service) for troubleshooting purposes.  The executable is located at:

< Install Directory> \VMware\Infrastructure\VirtualCenter Server> vpxd.exe

Usage: vpxd.exe [FLAGS]
Flags:
-r Register VMware VirtualCenter Server
-u Unregister VMware VirtualCenter Server
-s Run as a standalone server rather than a Service
-c Print vmdb schema to stdout
-b Recreate database repository
-f cfg Use the specified file instead of the default vpxd.cfg
-l licenseKey Store license key in ldap and assign it to VirtualCenter
-e feature Set the feature to be in use for VirtualCenter. This option takes only one feature at a time.
-p Reset the database password
-v Print the version number to stdout