<?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: SAS 9.3 License Renewal with SCCM 2012 in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119312#M1212</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;
&lt;P&gt;Doc@Duke wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;In the past (through 9.3), the SAS renewal process just changed one file in the $SASHOME directory tree.&amp;nbsp; You could manually renew SAS on a test machine, find and grab that file, and then use SCCM to push it to your users (Our IT team does that with another desktop management tool.).&amp;nbsp; The only caveat is that the file contents may be different for different versions and "bit-ness" of SAS and you risk trashing a working PC (SASRENEW does that checking for you.).&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the answer. Do you happen to know which file gets changed?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Oct 2013 12:13:44 GMT</pubDate>
    <dc:creator>js2a</dc:creator>
    <dc:date>2013-10-23T12:13:44Z</dc:date>
    <item>
      <title>SAS 9.3 License Renewal with SCCM 2012</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119309#M1209</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello. I work at a Help Desk at a fairly large college. We have recently started using SCCM 2012 to push applications to our users, and have started looking into SAS renewal as well. I have some experience pushing out applications using Microsofts new "Application Model", as well as having pushed out one manual package (i.e. how SCCM 2007 deployed applications). I'm wondering how I would go about using SCCM to perform the SAS license renewal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've found plenty of knowledge base articles on the silent mode usage for sasrenew.exe, like this one &lt;A href="http://support.sas.com/kb/31/021.html"&gt;http://support.sas.com/kb/31/021.html&lt;/A&gt; However, after scouring forums, I'm unable to find the exact method for using SCCM to renew the SAS license. For instance, I could create a package that contains the license txt file, but what would the command line syntax be since it references the absolute path for the txt file using the -s switch? Would I actually include sasrenew.exe in the package? Or, do I need to use a script when using SCCM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically, I'd love to hear some feedback from anyone using SCCM (especially 2012) on doing a SAS renewal. Thanks. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Oct 2013 20:53:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119309#M1209</guid>
      <dc:creator>js2a</dc:creator>
      <dc:date>2013-10-21T20:53:25Z</dc:date>
    </item>
    <item>
      <title>Re: SAS 9.3 License Renewal with SCCM 2012</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119310#M1210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't use SCCM but SASRENEW.EXE is already part of installed SAS so you wouldn't need to include it in SCCM. I would have thought that the SCCM package would have to be copied to a PC drive folder and then you could reference the licence file from there. You may find it easier to ask SAS Tech Support about this. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2013 19:20:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119310#M1210</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2013-10-22T19:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: SAS 9.3 License Renewal with SCCM 2012</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119311#M1211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the past (through 9.3), the SAS renewal process just changed one file in the $SASHOME directory tree.&amp;nbsp; You could manually renew SAS on a test machine, find and grab that file, and then use SCCM to push it to your users (Our IT team does that with another desktop management tool.).&amp;nbsp; The only caveat is that the file contents may be different for different versions and "bit-ness" of SAS and you risk trashing a working PC (SASRENEW does that checking for you.).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Oct 2013 03:11:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119311#M1211</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2013-10-23T03:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: SAS 9.3 License Renewal with SCCM 2012</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119312#M1212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;
&lt;P&gt;Doc@Duke wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;In the past (through 9.3), the SAS renewal process just changed one file in the $SASHOME directory tree.&amp;nbsp; You could manually renew SAS on a test machine, find and grab that file, and then use SCCM to push it to your users (Our IT team does that with another desktop management tool.).&amp;nbsp; The only caveat is that the file contents may be different for different versions and "bit-ness" of SAS and you risk trashing a working PC (SASRENEW does that checking for you.).&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the answer. Do you happen to know which file gets changed?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Oct 2013 12:13:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119312#M1212</guid>
      <dc:creator>js2a</dc:creator>
      <dc:date>2013-10-23T12:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: SAS 9.3 License Renewal with SCCM 2012</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119313#M1213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The license is updating the file core.sas7bcat in the sashelp directory (with this word you can google/verify)&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/kb/34/306.html" title="http://support.sas.com/kb/34/306.html"&gt;34306 - An authorization error&lt;BR /&gt;occurs when you attempt to update a SAS® 9.2 license&lt;/A&gt; (9.2 notes) . You could put an updated version over that. &lt;/P&gt;&lt;P&gt;&amp;nbsp; Or you could&amp;nbsp; use a mklink to an other loction with a own correct version of that file&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Oct 2013 19:47:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-9-3-License-Renewal-with-SCCM-2012/m-p/119313#M1213</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2013-10-24T19:47:58Z</dc:date>
    </item>
  </channel>
</rss>

