Scott, Well.. there is "clean" and there is "clean"....
If you mean that the host is a entierly new host that does not have an existing ARS server license key/file then when you install the new v7.1 server it has no file to "read" so it would be unlicensed. (And operating in a demo mode) You would likely need to do a purge to move an existing key or buy a new key for the new server. Or... If you mean that you uninstalled/deleted/turned off an existing ARS server on an existing host and installed the v7.1 server into a new directory on the existing server then there might be an existing license key/file for the install to read and it would auto "convert" the key into the DB where the v7.1 server keeps those things now. And as far as the ITSM app license go.... you can configure the server to think you have purchased the products already and the installers will run against that server. No application keys from BMC are technically required for the installers to run or the application to function. However, you are still obligated by the license agreement to BUY the products. So you should not add more licenses than you have purchased. But you could tell the server that you have Migrator when you have not purchased it... then later go pay BMC for it too. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/6/07, HARTWICK, SCOTT G CTR DISA JSSC <[EMAIL PROTECTED]> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > > We are building a 7.1 server from scratch. I know we will have to install a > Server license. > > Will we have to install the other ITSM licenses prior to installing each > product? > > You say below that it will upload the license file to the form. So how would > a clean install work? > > Thanks, > Scott. > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Easter, David > Sent: Tuesday, September 04, 2007 7:07 PM > To: arslist@ARSLIST.ORG > Subject: Re: 7.1 available today? (some more questions regarding licenses) > > ** > Vincent, > > As Doug suggested, it is best just to leave that directory alone. > > > 1) KEEP the directory because the arsystem.tag file is still needed > > and deleting it removes functionality > > 2) Delete the multilicense.lic file if you want because it is no > > longer used > > 3) Leave the arsystem.lic file as documentation/backup even though it > > is no longer used and once the 7.1 or later system is installed, all > > licenses in this file are uploaded into the new license form > > Best course of action is to just leave everything alone. AR System will > just ignore the .lic files after the upgrade. If you really need a couple of > bytes back on your file system, you can delete the multilicense.lic file. > > Thanks, > > -David J. Easter > Sr. Product Manager, Service Management Business Unit BMC Software, Inc. > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > > ________________________________ > > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Vincent RIEDWEG > Sent: Tuesday, September 04, 2007 4:06 PM > To: arslist@ARSLIST.ORG > Subject: Re: 7.1 available today? (some more questions regarding licenses) > > > ** > > Doug, > > > > The armonitor.conf is in /etc/arsystem/<server_name>... If we delete the > /et/arsystem, did the AR System server start ? > > > > Did the 7.1 use the armonitor.conf or this file is obsolete or in another > location? > > > > Regards, > > > > Vincent. > > > > ________________________________ > > De : Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] > De la part de Mueller, Doug Envoyé : mardi 4 septembre 2007 22:18 À : > arslist@ARSLIST.ORG Objet : Re: 7.1 available today? (some more questions > regarding licenses) > > > > Joe, > > > > Just to help David out a bit with a couple of answers: > > > > ... delete the folder /etc/arsystem/ .... > > > > Maybe... how is that for a crisp, clear, consise and definitive answer! > > > > We will no longer be using the arsystem.lic file or the multlicense.lic file. > Those files are obsolete as of the > > 7.1 release. > > > > However, there is one more file that you might have (you definitely have if > you are an ITSM customer). It is > > called arsystem.tag. That file is still important. > > > > This is a file with some licensing information for the approval server. > > > > There is a form in the system that can hold the data that is in this file, > and in the future, applications will put > > the data in that internal form. For now, the system will check both the > internal form AND this file for the tag > > information and will use it appropriately. HOWEVER, the upgrade does not > copy the content of this file into > > the form (because there are versions of the applications that still will > install in this file rather than the form). > > > > There is no need for you to do anything, the system will still reference the > file if it is present. Over time, all > > apps will be updated to use the internal table that is now present and this > file will not be needed. BUT, for > > the interum, you need this file. > > > > So, don't delete the directory if there is a .tag file in it. You can get > rid of the two .lic files (although it is > > suggested that you keep a backup copy of arsystem.lic just in case and why > not leave it there). > > > > In summary, > > > > 1) KEEP the directory because the arsystem.tag file is still needed and > deleting it removes functionality > > 2) Delete the multilicense.lic file if you want because it is no longer used > > 3) Leave the arsystem.lic file as documentation/backup even though it is no > longer used and once the 7.1 or > > later system is installed, all licenses in this file are uploaded into > the new license form > > > > > > ".. shared systems..." > > > > As David noted, since all the servers in a server group are pointing to the > same DB and since the license data > > is now a table in the DB, there is no need to generate parallel licenses for > applications, options, services, > > users on each server in the server group. They all share the same definitions. > > > > HOWEVER, you will still need a server license for each server in the group. > You can enter multiple AR > > System server licenses. Each will be tied to the Host ID of the respective > server. You cannot enter multiple > > of other licenses, you just specify total counts for things like users (much > easier than having to add them up). > > > > Each server will have its host ID in one of the licenses and that is how it > validates itself. Other licenses are on > > the server in a table and by validating the server license, the rest of the > contents of the license are > > accepted/validated > > > > In a server group, ALL licenses apply to ALL servers (other than the AR > System server license which is per > > server). There is no need to identify which are mine and which are not. It > is a single logical server environment > > so all the app/user/option licenses are identical across the logical group. > > > > > > Hopefully, this answers the "tech detail" aspects of your questions, > > > > Doug Mueller > > __20060125_______________________This posting was submitted with HTML in > it___ __20060125_______________________This posting was submitted with HTML > in it___ __20060125_______________________This posting was submitted with > HTML in it___ > Classification: UNCLASSIFIED > Caveats: NONE > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
