<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VSC 4.2.1 broken when I upgraded to vCenter Server 5.1 (and Single Sign On) in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-4-2-1-broken-when-I-upgraded-to-vCenter-Server-5-1-and-Single-Sign-On/m-p/100067#M8031</link>
    <description>&lt;P&gt;I'm running VSC 4.2.1 and have recently upgraded to vCenter server 5.1 (which includes single sign on). &amp;nbsp;VSC now gets authentication errors and I suspect it's because of the new vCenter server single sign on. &amp;nbsp;I had to rip out VSC and reinstall it to get it working. &amp;nbsp;In that process I had to use different credentials (running as the administrator instead of using the service account I had set up) to get it to work. &amp;nbsp;That was my hint that I've got an authentication problem with the new single sign on functionality.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got several systems that use SnapDrive to snap volumes that are actually VMFS volumes. &amp;nbsp;SnapDrive is failing to authenticate it's discussion with vCenter to sort out which volumes to snap, even as the administrator. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming that you folks have survived this transition already. &amp;nbsp;If someone has pointers on getting everything happily authenticated with SSO under vCenter 5.1, I'd love to hear about it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:11:08 GMT</pubDate>
    <dc:creator>orametrix</dc:creator>
    <dc:date>2025-06-05T05:11:08Z</dc:date>
    <item>
      <title>VSC 4.2.1 broken when I upgraded to vCenter Server 5.1 (and Single Sign On)</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-4-2-1-broken-when-I-upgraded-to-vCenter-Server-5-1-and-Single-Sign-On/m-p/100067#M8031</link>
      <description>&lt;P&gt;I'm running VSC 4.2.1 and have recently upgraded to vCenter server 5.1 (which includes single sign on). &amp;nbsp;VSC now gets authentication errors and I suspect it's because of the new vCenter server single sign on. &amp;nbsp;I had to rip out VSC and reinstall it to get it working. &amp;nbsp;In that process I had to use different credentials (running as the administrator instead of using the service account I had set up) to get it to work. &amp;nbsp;That was my hint that I've got an authentication problem with the new single sign on functionality.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got several systems that use SnapDrive to snap volumes that are actually VMFS volumes. &amp;nbsp;SnapDrive is failing to authenticate it's discussion with vCenter to sort out which volumes to snap, even as the administrator. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming that you folks have survived this transition already. &amp;nbsp;If someone has pointers on getting everything happily authenticated with SSO under vCenter 5.1, I'd love to hear about it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:11:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-4-2-1-broken-when-I-upgraded-to-vCenter-Server-5-1-and-Single-Sign-On/m-p/100067#M8031</guid>
      <dc:creator>orametrix</dc:creator>
      <dc:date>2025-06-05T05:11:08Z</dc:date>
    </item>
  </channel>
</rss>

