User manual SOPHOS SAFEGUARD EASY 4.50.3

[. . . ] xp~ÑÉdì~êÇ=b~ëóz ñÅ xa~í~=éêçíÉÅíáçå=Äó=ÉåÅêóéíáçåz táåÇçïë=pÉêîÉê=OMMP táåÇçïë=um táåÇçïë=OMMM sÉêëáçå=QKRMKP All rights reserved. No part of this documentation may be reproduced or processed, copied, distributed by a retrieval system in any form (print, photocopies or any other means) except for personal use without prior written consent of Utimaco Safeware AG. Utimaco Safeware AG reserves the right to modify or supplement the documentation at any time without previous announcement. Utimaco Safeware AG is not liable for misprints and damage resulting from this. [. . . ] Enter the correct logon information in the input fields and click [OK]. ñÅ ORN 6. You then see the SAL dialog. [Yes]: Activates the relationship between the SafeGuard Easy and the Windows user. The status of the check box labeled "Don't ask this question again for the current SafeGuard Easy user" specifies whether the dialog is to be displayed again on every logon or not. Next time the PC is restarted, and the user enters their SafeGuard Easy user data during PBA, they are automatically logged on to Windows. ORO NT `Ü~åÖáåÖ=íÜÉ=táåÇçïë=é~ëëïçêÇ Windows passwords have to be changed regularly for security reasons. However, the way in which a newly-defined password is integrated into the Secure Auto Logon process depends on the method used to change the user password. Forced Password Change Users can be forced to change their operating system passwords by the "User must change password after next logon" option in their user profile. If the user has to change their password when logging on, they are prompted to do so by a system message. As soon as the user confirms the new password, the system updates the SAL file. At next logon, the user can log on without having to re-enter their Windows access data, and Secure Auto Logon is run without notification. User Changes Password If the user change the password in the Windows logon dialog (e. g. by pressing [CTRL]+[ALT]+[DEL] on their desktop), they can change their password by selecting "Change password". If they change their password in this way, the system automatically accepts the new Windows password, and stores it in the Sgsal. dat file. When logging on after a password change, the user does not have to re-enter their Windows access data, and Secure Auto Logon is run without notification. If the password is changed via Windows user administration, the system does not automatically accept the new Windows password and it is not stored it in the Sgsal. dat file. Instead a warning message appears on the screen saying that the Windows password is not valid and the user must enter the correct new one in the logon screen. After the password has been changed, the user can log on without having to re-enter their Windows access data, and SAL is run without notification. ñÅ - ORP NTKNKO= pÉÅìêÉ=^ìíçã~íáÅ=içÖçå=ïáíÜ=ëã~êíÅ~êÇ= Epã~êíÅ~êÇ=p^iF The Smartcard SAL function stores the PIN on the card in such a way that the smartcard is automatically released when the user enters their SafeGuard Easy data during PBA. The smartcard then reads the Windows logon data (provided that it is saved on the card) and the data is then used to log on to the operating system. How to implement Smartcard SAL: 1. If no Windows information is saved on the smartcard, the system displays a dialog that prompts you to confirm whether the data should be written to the smartcard. If you click "Yes", you see the "Windows Access Data" dialog. In it you can enter your User Name, Password and Domain, which will be written to the smartcard. NOTE: The Windows user written to the smartcard must already have been created on the operating system, otherwise the logon will not be successful. ORQ NT 6. The system displays a dialog, prompting you to confirm whether Smartcard SAL is to be enabled. [. . . ] Internal error accessing system partition 1254 1255 1256 1257 SERVICE errors 1261 1262 1263 1264 1265 1266 1267 ñÅ Info about a memory object for a system service \ncould not be released. The service information block couldn't be found. \nThere is probably not enough memory available. \n\nErrorcode: %1. REGISTRY errors 1271 1272 1273 1274 Entry in the registry could not be opened. Entry in the registry could not be created. RNR 1275 1276 1277 1278 1279 1280 1281 1282 Entry in the registry could not be removed. Invalid entry in the registry detected. Driver database file errors 1291 1292 1293 1294 1295 CRAREA errors 1301 1302 1303 1304 1305 1306 Installation drive cannot be accessed. [. . . ]