Admin-Access Recovery: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
(→‎Basics: Third)
(→‎Locked User Profile: Better wording)
 
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
The Admin-User's Login is ''QSECOFR'', the default password likewise.<ref>On OS Releases after V4, the case is important: QSECOFR ≠ qsecofr.</ref>
The Admin-User's Login is ''QSECOFR'', the default password likewise.<ref>On OS Releases after V4, the case is important: QSECOFR ≠ qsecofr.</ref>


This admin user profile exists '''twice''' on the system: Within the OS, and in the Dedicated Service Tools, or sort ''DST''.<ref>Almost but not exactly like a PC's BIOS.</ref> From experience, the DST password is most often left to the default password value, ''QSECOFR''.<ref>Starting with OS Release V5, DST password is ''case sensitive'', so take care.</ref>  
This admin user profile exists '''twice''' on the system: Within the OS, and in the Dedicated Service Tools, or short ''DST''.<ref>Almost but not exactly like a PC's BIOS.</ref> From experience, the DST password is most often left to the default password value, ''QSECOFR''.<ref>Starting with OS Release V5, DST password is ''case sensitive'', so take care.</ref>  


Without reinstall, it's possible to
Without reinstall, it's possible to
* reset the DST password via an OS command,
* reset the DST password via an OS command,
* reset the OS password via DST,
* reset the OS password via DST,
* reset the OS password via another, known OS-User with appropriate Rights.<ref>And a known password, of course!</ref>
* reset the OS password via another, known OS-User with appropriate authority.<ref>And a known password, of course!</ref>


== Locked User Profile ==
== Locked User Profile ==
In addition to a unavailable password, there's also the possibility that the profile itself is locked.
In addition to a unavailable password, there's also the possibility that QSECOFR's user profile itself is locked. A recovery from this condition is only possible
* by using the system console, in manual mode,
* via another, known User with appropriate Rights.


== Weblinks ==
== Weblinks ==

Latest revision as of 20:48, 9 June 2022

Qsicon Fixme.png This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.

Reason: Distill information from linked IBM docs into article.

If you inherited a machine from somewhere, most likely there's no default admin password set anymore, and the password saved on the system isn't known anymore. To get back in, you need to follow Recovery Procedures.

Basics

The Admin-User's Login is QSECOFR, the default password likewise.[1]

This admin user profile exists twice on the system: Within the OS, and in the Dedicated Service Tools, or short DST.[2] From experience, the DST password is most often left to the default password value, QSECOFR.[3]

Without reinstall, it's possible to

  • reset the DST password via an OS command,
  • reset the OS password via DST,
  • reset the OS password via another, known OS-User with appropriate authority.[4]

Locked User Profile

In addition to a unavailable password, there's also the possibility that QSECOFR's user profile itself is locked. A recovery from this condition is only possible

  • by using the system console, in manual mode,
  • via another, known User with appropriate Rights.

Weblinks

References

  1. ↑ On OS Releases after V4, the case is important: QSECOFR ≠ qsecofr.
  2. ↑ Almost but not exactly like a PC's BIOS.
  3. ↑ Starting with OS Release V5, DST password is case sensitive, so take care.
  4. ↑ And a known password, of course!
Retrieved from "http://try-as400.pocnet.net/index.php?title=Admin-Access_Recovery&oldid=1111"