$aad Start Menu Lock

Previous

Next

 

$aad Start Menu Lock

With this directive, the Administrator can assign Applications and Sets to the Start Menu of the User that are initial not visible. The User (or when the Administrator is behind the keyboard of the User...) has to enter a Password, and then those Applications and Sets become visible.

The Administrator sets the Password for Locked Menus using AADS Maintenance and Control:

It is also possible for the Administrator to use his/her own PC, and "unlock" the Start Menu of the Users and make those extra Apps and Sets visible using AADS Maintenance and Control:

The Administrator selects "Unlock Start Menu", followed by a "Refresh" of the Start Menu of the selected Users.

 

How to use the directive $aad Start Menu Lock


Use $aad Start Menu Lock in Sets

When the User "luser001" does a Login, the Desktop is as follows:

 

Right-Click Mouse / Long Press on the Start Menu Icon

 

The Administrator can also AADS Maintenance & Control for Locking / Unlocking the Start Menu of this User:

After clicking on the Refresh button, the Start Menu of the selected Users will show either the Locked Sets or not, depending on Select or De-Select the checkbox "Unlock Start Menu".


Use $aad Start Menu Lock in Start Menu (variant 1)

In this example the User gets 2 visible Applications:

The directive "$aad Start Menu Lock" is placed in the main part of the Start Menu for the User.

Possible there are also "$aad Start Menu Lock" in the Sets "User Desktop Maintenance", "Control Panel" or "Accessories", but that has become irrelevant, because now that the directive "$aad Start Menu Lock" is placed in the main part of the Start Menu for the User, the whole Start Menu of the User is invisible.

The 2 visible Apps

For demonstration purposes the User gets 2 visible Applications.
These Applications must have "Auto Start"  because the User does not have a visible Start Menu, so the User has also not the ability to start Applications.

When the User does a logon, the desktop looks as follows:

The User is able to close Notepad. However, if the User closes Firefox, after a few seconds it will be started again because of the "Auto-Restart" .

When the User presses the Win-key, the result is not showing the Start Menu of the User, but showing the Password-dialog for "unlocking the Start Menu":

After entering the Password correctly, the Start Menu becomes visible:

 

How to do a Logoff when the Start Menu is not Visible

Because of Firefox, which will run forever in this example , the Session of this User will never stop, will never logoff.
A logoff of this User / Session needs to be done by the Administrator.

Option 1

Make the Start Menu visible, by entering the Password as shown here above, and make sure that there is a "Session" menu-item in the Start Menu, such that the User can do a Logoff.

Option 2

The Administrator does logoff this User / Session, using AADS Maintenance & Control:

 

Use $aad Start Menu Lock in Start Menu (variant 2)

Again, in the example the User gets 2 visible applications:

The directive "$aad Start Menu Lock" is placed in the main part of the Start Menu for the User.

Possible there are also "$aad Start Menu Lock" in the Sets "User Desktop Maintenance", "Control Panel" or "Accessories", but that has become irrelevant, because now that the directive "$aad Start Menu Lock" is placed in the main part of the Start Menu for the User, the whole Start Menu of the User is invisible.

The 2 visible Apps

For demonstration purposes the User gets 2 visible Applications.
These Applications must have "Auto Start"  because the User does not have a visible Start Menu, so the User has also not the ability to start Applications.

The difference with the previous example is that now none of the Applications have the option for "Auto-Restart" .

When the User does a logon, the desktop looks as follows:

 


© 2012-2023 AADS WorldWide. Terminal Server | Application Server | Remote Desktop solutions | Firewall

Previous

Next