<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Permissions to cancel vCenter tasks</title>
	<atom:link href="http://www.vReference.com/2009/06/24/permissions-to-cancel-vcenter-tasks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vReference.com/2009/06/24/permissions-to-cancel-vcenter-tasks/</link>
	<description>guides, links and news for VMware and virtualization technologies</description>
	<lastBuildDate>Mon, 19 Jul 2010 21:24:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Steve Flanders</title>
		<link>http://www.vReference.com/2009/06/24/permissions-to-cancel-vcenter-tasks/comment-page-1/#comment-69</link>
		<dc:creator>Steve Flanders</dc:creator>
		<pubDate>Wed, 08 Jul 2009 22:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.vReference.com/?p=198#comment-69</guid>
		<description>I have experienced many such problems when using permissions on vCenter 2.5. The one that always bothers me is when I want to make a person an administrator of a cluster (not a datacenter), but then they are not allowed to create new VMs because they do not have access to the datastores. You can add them to the datacenter level and adjust permissions accordingly, but they can still see other datastore that are not theirs. I have resorted to creating my own custom role to address these issues.</description>
		<content:encoded><![CDATA[<p>I have experienced many such problems when using permissions on vCenter 2.5. The one that always bothers me is when I want to make a person an administrator of a cluster (not a datacenter), but then they are not allowed to create new VMs because they do not have access to the datastores. You can add them to the datacenter level and adjust permissions accordingly, but they can still see other datastore that are not theirs. I have resorted to creating my own custom role to address these issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
