Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM/Smarts IP: Can I rename my current Smarts installation directory and install a new version to the previous (old) directory name? (374809)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3111Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Can I rename my current Smarts Smarts IP Manager (Smarts IP) or Smarts Service Assurance Manager (Smarts SAM) installation directory and install a new version to the previous (old) directory name?
How can I change the Smarts IP or Smarts SAM vpd.script to allow me to rename my current installation directory so I can install a new version to the previous (old) directory name?

Can I change the vpd.script to allow me to rename my current installation directory of Smarts IP or Smarts SAM software and install a new version to the previous (old) directory name?

Receive the following error message when trying to upgrade Smarts IP or Smarts SAM installation:

The installer found a matching suite, but you cannot update the matching suite with this or lower version.

Cause

The above installer error is generated because the vpd.script is accounting for both the currently installed version and new version as being installed in the same directory. Consider the following example scenario:

Currently you have Smarts SAM 8.1.2.3 installed in the following directory

/opt/InCharge812

You want to upgrade to SAM 8.1.3.2 (8.1.3 with Patch 2), but would rather rename your current directory and install the software from fresh.

You rename above directory to the following:

/opt/InCharge/812-Old

You then install Smarts SAM 8.1.3 to the old directory:

/opt/InCharge812

When you attempt to apply Smarts SAM 8.1.3 Patch 2 (HF2), it can produce the above installer error because the vpd.script will account for both Smarts SAM 8.1.3 and SAM 8.1.2.3 as being installed in the same directory.

Resolution

Renaming of a current Smarts software installation directory and installing a newer Smarts software version to the same previously named directory is not recommended as a general principle. However, if required for your environment, this can be done as follows:

Navigate to the following directory on the Smarts installation environment:

/root/InstallShield/Universal/common/Gen1/_vpddb

Copy the vpd.script file found in the above directory and make a back up of this file in a separate location.

Open the vpd.script file in an appropriate editor, and search for evidence of the old installation.

In the example scenario above with Smarts SAM 8.1.2.3 installed, the vpd.script file would contain evidence of the Smarts SAM 8.1.2.3 installation in /opt/InCharge812. This is the directory that was renamed /opt/InCharge812-Old and would now have Smarts SAM 8.1.3 installed in this same directory.

Remove the evidence of the old installation from the vpd.script file. Using the same example, the lines would be similar to the following"INSERT INTO" lines. The entire lines should be removed from the vpd.script file (they have been shortened for the following example):

INSERT INTO INSTALLED_SOFTWARE_OBJECT VALUES(43,'071eac5635fc916637bcb98fcf737541tt','/opt/InCharge812/SAM',1,'8.1.2.3'
INSERT INTO INSTALLED_SOFTWARE_OBJECT VALUES(44,'bcd198edb579ff954de43a437ca1eb31','/opt/InCharge812/SAM/_rpuninst',1,'8.1.2.3'
INSERT INTO INSTALLED_SOFTWARE_OBJECT VALUES(45,'0c87d6fd4b213e0d91160af9ae0038ac','/opt/InCharge812/SAM/smarts',1,'8.1.2.3'

Save and close the vpd.script file. It should be saved in the directory where it is by default as noted above.

Apply the Smarts SAM 8.1.3 HF2 to the /opt/InCharge812 directory.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant