<?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 Rename CMS in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/rename-cms/m-p/4778009#M3242</link>
    <description>I have a need to rename by CMS to accomodate the naming convention for the WSMAN protocol that is needed for monitoring of the Superdome 2. My current name is RN_SIMM. What are the repercussions of changing the name? Are there steps I should follow to do this? Has anyone done this and not experienced major issues?</description>
    <pubDate>Fri, 15 Apr 2011 12:21:10 GMT</pubDate>
    <dc:creator>Alice Seeley</dc:creator>
    <dc:date>2011-04-15T12:21:10Z</dc:date>
    <item>
      <title>Rename CMS</title>
      <link>https://community.hpe.com/t5/insight-remote-support/rename-cms/m-p/4778009#M3242</link>
      <description>I have a need to rename by CMS to accomodate the naming convention for the WSMAN protocol that is needed for monitoring of the Superdome 2. My current name is RN_SIMM. What are the repercussions of changing the name? Are there steps I should follow to do this? Has anyone done this and not experienced major issues?</description>
      <pubDate>Fri, 15 Apr 2011 12:21:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/rename-cms/m-p/4778009#M3242</guid>
      <dc:creator>Alice Seeley</dc:creator>
      <dc:date>2011-04-15T12:21:10Z</dc:date>
    </item>
  </channel>
</rss>

