Solved: Passwords in LMS3.1

marshajr · ‎07-23-2009

We've just upgraded from LMS2.6 to LMS3.1, not everything working properly at the moment. I am a bit confused by the relationship between all of the different passwords e.g. casuser, Userguest, db password etc.

Is ther anywhere that explains how these relate to other modules, ACS, and end devices, so that I make sure everything is properly in-sync?

Joe Clarke · ‎07-23-2009

Casuser's password is an internal password that is shared between LMS and the Windows SAM database. This password need not be known to the user. It just needs to satisfy any system policies, and be the same in LMS and the SAM.

The guest password is used by the guest user. This user only has help desk access. This account need not be used at all.

The database passwords are random by default, and should never need to be used except internally by LMS. However, under some circumstances, TAC may require them for database troubleshooting.

The two passwords that play a key role in getting started with LMS are the admin password and the System Identity User password. These two SHOULD be unique. The System Identity User is used for interprocess and inter-server communication. This account must exist in ACS with full access to all LMS-managed devices and LMS tasks if you plan on doing LMS/ACS integration.

View solution in original post

Joe Clarke · ‎07-23-2009

Casuser's password is an internal password that is shared between LMS and the Windows SAM database. This password need not be known to the user. It just needs to satisfy any system policies, and be the same in LMS and the SAM.

The guest password is used by the guest user. This user only has help desk access. This account need not be used at all.

The database passwords are random by default, and should never need to be used except internally by LMS. However, under some circumstances, TAC may require them for database troubleshooting.

The two passwords that play a key role in getting started with LMS are the admin password and the System Identity User password. These two SHOULD be unique. The System Identity User is used for interprocess and inter-server communication. This account must exist in ACS with full access to all LMS-managed devices and LMS tasks if you plan on doing LMS/ACS integration.