Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 11489 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update Manager removal

KevNorris

So, We have a working Sophos server running Management Console & Update Manager. This is working fine.

We have recently protected new clients who appear to have had an older version of Sophos installed, this includes the Update Manager Software (version 1.2.1.161) , but we are not able to remove the Update Manager software as it gives us the error :

Setup can not continue. OLD-DOMAIN is not a valid domain name.
To be valid the part domain user name must be either a domain or a physical server ora workstation. Véifiez the name and try again.

The OLD-DOMAIN has been completely retired now, but the uninstall wont allow it to continue.

Is there any way around this?

Please assist.

Thanks,



This thread was automatically locked due to age.
  • +1

    Hello KevNorris,

    new clients
    must be pretty old when SUM is 1.2.1, but more important - a SUM is normally installed on a server (and furthermore should update itself as long as it's alive). I wonder about their history and how and why you seem to try to "reuse" them this way. Can't say why the .msi does this check upon uninstall and whether it checks the credentials as well (likely not).

    Don't think you can change the UpdateMgr user by re-running setup (if it's available at all). Look like the value UserData of the key HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{2C7A82DB-69BC-4198-AC26-BB862F1BE4D0} is the place that's checked. Its format is Server;Domain;User,create;created where Server is the machine, Domain either the domain or machine for a local account, User the account name, create and created are flags. Check this value if what I say makes sense. Then - warning: this is not only unofficial but pure guesswork, save you data and use at your own risk - I'd set the UserData value to Machine;Machine;SUMUser;0; (make sure SUMUser exists as local user, no value for created) and give uninstall another try.

    Apart from the uninstall issue - you've managed to protect them or not? But anyway, given the IMO (as far as I understand it) untrustworthy state of the machine(s) I'd think twice to continue to use them.    

    Christian

  • 0 in reply to QC

    Worked for me!! In my case, the server changed hostname and becomes member server from Domain Controller.

    Thank You!!

  • 0 in reply to QC

    Thanks for this.

    The issue for me was that the PC name had been changed. I swapped the old name for the new name and the uninstall ran fine.

Unfiltered HTML