Topic: Question - server installer details

[hawk]

i have just been given an old sme server that is running sme 7 and they want me to recover all the emails and put a new server in. Now this server hasn't been worked on for years, (celeron with 80gb hdd) no one knows who set it up or the admin password. I should be able to recover the emails with the thunderbird that has been connected for each user. But my question is this.
would it be possible in future versions where there is a place when the server is setup for the installer to put his or her details in so years later they can be contacted. Or an encripted file accessable only to registered SME admin people to access this type of info with the servers admin password? I am aware of the possible security risk but just an idea.

your thoughts

[Stefano]

No needed
Just search wiki for root password reset

[hawk]

hi Stefano

i have used the root password many times before, it was just an idea about gathering installer info

thanks

[idp_qbn]

This is really a user issue, applicable to many systems. Anyone who sets up an IT system should record the details somewhere outside the computer.
The best way is to create a paper file with relevant details and store it somewhere safe and recoverable.

Second best (if you can login) is to store it securely on the system - but remember, it may not be recoverable if something gets corrupted.

Now, that's enough of me trying to teach granny to suck eggs ------ sorry about that.

Cheers and good luck   
Ian

[hawk]

Ian very true, external is always better.

what about something like this:

installer puts in their details, then the OS reads the serial number / make - model of motherboard / HDD etc. (some physical identifing mark of the hardware)
This info is then auto uploaded to a web site and stored.

Only registered users have access to this web site's info. Only by putting these serial numbers in can you get access to the rest of the info.

Or

At the point of installation a text file with the relivant server / installer information is generated and either emailed or saved to flash drive, this info can then be given to the owner of the server for future reference.

[janet]

hawk

All your ideas are good, but they need an expert coder/developer to implement them.
As SME Koozali server is very short of expert developers then I doubt such a feature will be implemented, as there is no strong compelling reason to do so.

If you want to pay a developer then maybe your request could be implemented.

As it stands now, it is easy enough to reset the root & admin password & obtain all that information you want by looking in server manager and/or issuing a few commands at the CLI.
Given that it is relatively easy & quick to do this, I doubt anyone will want to spend time creating code that provides an alternative method of retrieving such details & probably has a very limited use or appeal.

[Jáder]

...
would it be possible in future versions where there is a place when the server is setup for the installer to put his or her details in so years later they can be contacted. Or an encripted file accessable only to registered SME admin people to access this type of info with the servers admin password? I am aware of the possible security risk but just an idea.

your thoughts

That's called documentation. Do you document your servers ?

Most of technicians do no like to do it, but always complain about others do not did it!


I register all updates I do on my SME servers using /etc/motd.jm (that file is similar to a existing file, but I put my initial on it).
I never put root password on it, but that can be easily changed.
Other updates are recorded there.

[Daniel B.]

installer puts in their details, then the OS reads the serial number / make - model of motherboard / HDD etc. (some physical identifing mark of the hardware)
This info is then auto uploaded to a web site and stored.

Only registered users have access to this web site's info. Only by putting these serial numbers in can you get access to the rest of the info.

This would cause serious security and privacy concerns, I wouldn't want such a "feature" for the servers I install, and I guess I'm not alone. The benefits seem far too low for the potential risk of data leak