<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vco on The IT Hollow</title>
    <link>https://theithollow.com/tags/vco/</link>
    <description>Recent content in Vco on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Sep 2014 10:57:25 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vco/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>vRealize Automation 6 Service Designer and vCO</title>
      <link>https://theithollow.com/2014/09/08/vcac-6-service-designer-vco/</link>
      <pubDate>Mon, 08 Sep 2014 10:57:25 +0000</pubDate>
      <guid>https://theithollow.com/2014/09/08/vcac-6-service-designer-vco/</guid>
      <description>&lt;p&gt;vCAC 6 (now renamed vRealize Automation) allows us to provision more than just virtual machines.  We can also publish vCenter Orchestrator packages.  To do so, we need to configure the Service Designer.&lt;/p&gt;
&lt;p&gt;Go to the Administration Tab &amp;ndash;&amp;gt; Groups and create a group that will have access to the service designer.  I just used the Domain Admins group, mainly because it&amp;rsquo;s my lab.  Click the dropdown to edit the group properties. &lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2014/08/Advanced-services-designer1.png&#34;&gt;&lt;img alt=&#34;Advanced services designer1&#34; loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2014/08/Advanced-services-designer1.png&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
