Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

After factory reset, the VersionHistory.txt is not retaining the latest installed dmupgrade

Solved801 views24th March 2022SLReset
1
Ciprian Moga [SLC] [DevOps Member]318 24th March 2022 0 Comments

Hi,

Upon performing a factory reset with the help of the SLReset tool, I’ve noticed that the VersionHistory.txt file gets trimmed down to a single row. This row does not reflect the version of the latest hotfix package (.dmupgrade) that was installed on the machine, which was running prior to running the tool.

Is the SLReset performing any form of downgrade action in the background or is the tool not taking the hotfix packages into consideration and only lists, for example, the version of the last known full upgrade package?

Thanks in advance,

Ciprian Moga [SLC] [DevOps Member] Selected answer as best 24th March 2022

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
3
Brent [SLC]1.57K Posted 24th March 2022 0 Comments

Hey Ciprian,

Rest assured, the SLReset tool does not change anything regarding the installed version, no downgrade, or upgradeactions are performed.

SLReset only removes the VersionHistory.txt which is then recreated during dataminer startup. SLNet will get the current version from the buildinfo.bin (which only contains the latest base-version. It will then scan the upgrades/Hotfixes-path to see if there are any hotfixes applied.Since SLReset clears the content of that folder the hotfixes will not be shown in the versionhistory. Something we can improve upon.

However you can still verify the files and their version using the “About” window in cube. Where the files changed by the hotfix will be marked with “Different from upgrade”.

Ciprian Moga [SLC] [DevOps Member] Selected answer as best 24th March 2022
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs