Day: April 1, 2011

There is one log collecting tool that is built into the Endpoint Protection software that can be used instead of the Symbatch Diagnostic Utility. It doesn’t collect as much information as the Symbatch Diagnostic but it will provide some information that will be useful for SEPM support engineers. Go to C:Program FilesSymantecSymantec Endpoint Protection ManagerTools In this folder, you will see a cmd file that is titled CollectLog.cmd. Click on that icon and it will run the tool. When it is completed, it will create a zip file in the same directory. The zip file will be titled SEPM_logs.zip. You […]

If the reporting database is a MSDE database, you can use the osql command. If the database is Microsoft SQL Server, use the SQL Server Enterprise Manager. Before you begin: You must know the sa user password. In the examples below, the password is: password, and the Reporting user password is reset to: resetme123 If the user account is locked, see KB document 2006021009444048 Resetting locked passwords for Reporting Server This method is not supported by Symantec. Reset the password with the osql command If the reporting database is a MSDE database, you can use the osql command To reset […]

There is no provision in the user interface to unlock accounts. To unlock accounts, one must do so manually in the database. Unlock SEP console user accounts: Log on as an administrator on the database server. Execute the following command from a command window:         osql -E On the osql prompt enter the following lines (the first two lines end with a semicolon):         use Reporting;         update adminuser set Locked=” where user_name=’USERNAME’;         go         exit          Replace USERNAME with the name of the user to be unlocked. For MSSQL 2000/2005 with multiple instances, you will also need to […]