<?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 RE: BAT file in System Administration</title>
    <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125554#M14234</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;yes, i agree 100%, that would be better, but security here is rediculous, and IT would need to do that and getting IT to do anything is a huge mess...&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Mar 2010 11:36:17 GMT</pubDate>
    <dc:creator>cdiaz-2</dc:creator>
    <dc:date>2010-03-05T11:36:17Z</dc:date>
    <item>
      <title>config.sup question</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125548#M14228</link>
      <description>what i want to do is to setup a config.sup on the network so i can have all users seeing the same config.sup file and if a change is made, it only needs to be made to the .sup file on the network and after the new pro launch the user will have the latest and greatest. my question</description>
      <pubDate>Sun, 13 Dec 2020 22:36:37 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125548#M14228</guid>
      <dc:creator>cdiaz-2</dc:creator>
      <dc:date>2020-12-13T22:36:37Z</dc:date>
    </item>
    <item>
      <title>config.sup location</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125549#M14229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Maybe someone else in your position has figured out a clever answer to this, but I don't think there's an easy way. The standard look-for location is the loadpoint text directory, and, as far as I know, there's no config option to change that. Maybe a better approach is some kind of script file for automatically copying updated config.sup files to each of the machine, IF you have easy access to the loadpoint directories. Good luck!&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Mar 2010 22:59:19 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125549#M14229</guid>
      <dc:creator>DavidButz</dc:creator>
      <dc:date>2010-03-03T22:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: config.sup question</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125550#M14230</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="jive-quote"&gt;&lt;P&gt;"Carlos Diaz" wrote:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&lt;/P&gt;&lt;P&gt;what i want to do is to setup a config.sup on the network so i can have all users seeing the same config.sup file and if a change is made, it only needs to be made to the .sup file on the network and after the new pro launch the user will have the latest and greatest. my question is where do i set the search path for pro to look for the config.sup file on the network? side note: we have pro installed local on all our machines, so putting a config.sup file on a local hard drive in the loadpoint/text directory does nothing for the other users, unless i copy n paste the same config.sup file into all the machines but that makes it a pain when we make changes to the .sup file since we will have to copy and paste the changes into all the machines so they all see the latest and greatest config.sup file. thanks guys Carlos Diaz&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Mar 2010 06:12:38 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125550#M14230</guid>
      <dc:creator>MartinHanak</dc:creator>
      <dc:date>2010-03-04T06:12:38Z</dc:date>
    </item>
    <item>
      <title>BAT file</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125551#M14231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Martin, Clever, simple solution! David&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Mar 2010 13:59:41 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125551#M14231</guid>
      <dc:creator>DavidButz</dc:creator>
      <dc:date>2010-03-04T13:59:41Z</dc:date>
    </item>
    <item>
      <title>RE: BAT file</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125552#M14232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;great, thank you! that should get me going in the right dierection for now, incase u haven't noticed already, im not a pro/e admin guy, im just a user, but where i'm at now pro/e is like a redheaded step child thrown in a corner, and solidworks is the evil step child that gets all the attention... lol it's a hot mess here, i'm trying to slowly but surely turn the tide, solidworks is pretty cool, but pro/e will always be king. until i got here, all the pro/e machines had different builds, no libraries, no standards, not formats, someone basically installed pro/e and said have at it any way u can. yes, its horrible, but management has seen the light and how getting everything in order will make the few of us on pro alot more productive. thanks again guys Carlos Diaz&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Mar 2010 15:09:14 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125552#M14232</guid>
      <dc:creator>cdiaz-2</dc:creator>
      <dc:date>2010-03-04T15:09:14Z</dc:date>
    </item>
    <item>
      <title>RE: BAT file</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125553#M14233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;You should consider to have ProE installes on a server share and remove from local disk. This way you only have one locatiopn to update.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Mar 2010 06:56:14 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125553#M14233</guid>
      <dc:creator>ptc-291018</dc:creator>
      <dc:date>2010-03-05T06:56:14Z</dc:date>
    </item>
    <item>
      <title>RE: BAT file</title>
      <link>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125554#M14234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;yes, i agree 100%, that would be better, but security here is rediculous, and IT would need to do that and getting IT to do anything is a huge mess...&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Mar 2010 11:36:17 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/System-Administration/config-sup-question/m-p/125554#M14234</guid>
      <dc:creator>cdiaz-2</dc:creator>
      <dc:date>2010-03-05T11:36:17Z</dc:date>
    </item>
  </channel>
</rss>

