Jump to content

Cegertec

Members
  • Content Count

    53
  • Joined

  • Last visited

About Cegertec

  • Rank
    Candidate
  1. Hi! Thank for your reponse but i have all in french (kaspersky console , agent and KESC etc) but the preboot display startup is in english
  2. Ok for Keyboard but my question is for the display text .. The interface display
  3. Ok and for my other question for the display language for the startup agent
  4. Hello! I'm sorry for my English I have questions about encryption. We are currently using Symantec PGP which has imposed by the parent company, but following a company separation, we want to use the encryption of Kaspersky Because we continued to buy licenses for the full suite since for 8 years. We have 2 problems. The official version does not support SSD type NVME ex: Dell 5470, HP Zbook 15U g2 and G3 etc. I tried the Beta SP2 version and the encryption works. When do you think come out officially? Otherwise we will be forced to buy a server and Symantec PGP suite. Second question Is it possible to change the startup display language of the encryption to be in french? We are in Quebec and the Act obliges to have an interface in french and also avoided to have complaints of the users. We have the console Security center 10 in French, including the Agent and the antivirus. With Symantec PGP we are able to change text display and language etc. thank you very much
  5. Bonjour! J’espère que vous allez bien! J'ai des problèmes avec mon Kaspersky Security Center (9.2.69) depuis un certain temps.. version du serveur 9.2.69 version antivirus Mp4 6.0.4.1424 Version de l'agent 9.2.69 - J'ai plusieurs postes à chaque jour qui se ramasse dans Unassigned computers.. - Il arrive souvent que quand j'installe le package antivirus + l'agent , l'installation se complète a 100% , il indique bien que l'installation a communiqué avec le serveur admin kit etc mais quand l'ordinateur redémarre, il n'embarque pas dans la "policy" du serveur etc.. il faut que je réinstalle le package 2-3 fois... même si j'attends.. Pourtant j'ai revalidé le packages d’installation, les config et les Policy de l'agent et des Workstation... Merci à l'avance pour votre aide!
  6. Pour le contact du revendeur, j'aimerais pas trop.. Juste pour faire une demande de License supplémentaire, cela a pris presque 2 mois donc... Je reste au Québec (Canada)
  7. Salut Thierry Je vais essayer de vous envoyer le rapport d'ici quelques jours, pour l'instant , j'ai désinstaller Kaspersky et installer microsoft security essential.. Je vais retourner voir une des 6 personnes à problèmes pour réinstallés kaspersky Je vous tiens au courant Merci
  8. Merci Hectory mais il donne le même résultat que le log que j'ai indiqué plus haut. On Wed 2011-03-09 18:00:27 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini030911-01.dmp This was probably caused by the following module: klif.sys (klif+0xE57B) Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFFBA350D70, 0x0, 0x0) Error: UNEXPECTED_KERNEL_MODE_TRAP_M file path: C:\WINDOWS\system32\drivers\klif.sys product: Kaspersky™ Anti-Virus ® company: Kaspersky Lab description: Klif Mini-Filter [fre_wnet_AMD64] Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klif.sys (Klif Mini-Filter [fre_wnet_AMD64], Kaspersky Lab). Google query: klif.sys Kaspersky Lab UNEXPECTED_KERNEL_MODE_TRAP_M
  9. Bonjour à tous! J'ai plusieurs postes HP 6540 qui font des écrans bleus et je n'ai pas trouvé de solution... Les postes sont en windows xp SP3 avec Kaspersky Workstation 6.0.4.1424 a.d avez-vous des idées?? le bios et les drivers sont à jour... Merci à l'avance Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [R:\TRANSFERT\Donald Simard POR135\Mini030911-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Wed Mar 9 13:00:27.551 2011 (UTC - 5:00) System Uptime: 0 days 4:48:22.836 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {8, ba350d70, 0, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys *** WARNING: Unable to verify timestamp for igxpmp32.sys *** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys *** WARNING: Unable to verify timestamp for VIDEOPRT.SYS *** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys *** WARNING: Unable to verify timestamp for igxpdx32.DLL *** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : klif.sys ( klif+e57b ) Followup: MachineOwner ---------
  10. Aucune autre solution?? Si ça continue, je vais réinstaller la version anglaise partout!
  11. Bonjour Hectory , merci pour l'information. J'ai exécuté le fichier klcfginst.exe sur mon serveur d'administration, j'ai redémarrer et relancer la policy de l'agent et aucun changement pour l'instant... Avez-vous d'autres idées??? Merci David
  12. Salut Tybilly J'ai désactivé pendant 1 journée et réactivé l'option et toujours le même problème... Bizarre?
  13. Bonjour! J'ai remarqué que depuis l'installation de la nouvelle version de kaspersky admin kit que mon registre d'application ne fonctionne plus vraiment... Sur les pc : l'agent : 8.0.2134 Antivirus : 6.0.4.1424 Admin kit Serveur : 8.0.2134 J'ai pourtant bien pousser la nouvelle version de l'agent sur l'ensemble du bureau J'ai aussi créer une policy pour l'agent avec les options pour " registre d'application" Je ne comprend pas trop... Merci à l'avance!
  14. Même problème qu'ici http://forum.kaspersky.com/index.php?showtopic=185251 Il faut désinstaller le logiciel , juste le désactiver le change rien.. Version 6.4.1424 a.d
  15. Bonjour à tous.. Depuis environ 1 semaine, j'ai eu 3 postes informatiques qui par hasard , le disque dur avait un taux de transfert de 5-6 mo/sec avec HDtune et HDtach donc, les usagers se plaignaient de lenteur énorme.. Après plusieurs tests, mise a jour du bios , driver stata tralala... En désinstaller Kaspersky (juste désinstaller Kaspersky sur un Intel core I7 860 a pris plus de 20 minutes... ) et en le réinstallant , voila .. retour à la normale de la vitesse de transfert d'environs 90-120mo/sec Je vais faire le tour de d'autre poste , et je suis certain que je vais avoir le même problème ailleur... Avez-vous une idée? Merci
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.