Donnerstag, 24. Januar 2013

Outlook Symbbolleisten/Toolbars bleiben nicht wo sie sollen

Wenn das Problem im Zusammenhang mit einer Toolbar eines Zusatzprogrammes auftritt, hilft eventuell das Umbennen der outcmd.dat. Diese befindet sich unter %appdata%\Microsoft\Outlook.

Quellen:
http://www.msoutlook.info/question/152
http://www.slipstick.com/problems/outlooks-toolbars-dont-stay-where-you-put-them

Mittwoch, 23. Januar 2013

Montag, 21. Januar 2013

Trendmicro Probleme beim Installieren / Deinstallieren von Clients

Unter http://community.trendmicro.com/t5/Business-Security-Forum/Officescan-10-Clients-Can-t-Install-via-Client-Installer-Link/td-p/1309 folgendes gefunden:

Option I: Using other osce client installation method
Option II: Troubleshooting Web Install

Option I: If you prefer to use other osce client installation method such as Remote Installation, Autopcc, and Client Packager

Remote Install
===============================================
1. Open the OfficeScan Web console then click Networked Computers > Client Installation > Remote.
2. The Domains and Computers list displays all the Windows domains on your network. To display computers under a domain, double-click the domain name. Select the target computer, then click Add. You may also use the "Search" option to locate the target computers.
3. Type the user name and password of an administrator account then click Log in. The target computer appears in the Selected Computers list.
4. Repeat steps 2 to 3 to add more computers.
5. Click Install when you have finished selecting the target computers.
6. Click Yes when the confirmation message appears. A window appears showing the installation progress.
When OfficeScan completes the installation to a target computer, its status appears in the Result column, and its icon appears with a green checkmark.
===============================================

Client Packager
===============================================
1. On the OfficeScan server, open the \PCCSRV\Admin\Utility\ClientPackager folder then double-click ClnPack.exe. This opens the Client Packager console:

2. For Package type, select the type of package you want to create:

• Setup – creates an executable file that installs the OfficeScan client program.
• Update – creates an executable file that only updates the OfficeScan client components.
• MSI – creates a setup package that conforms to the Microsoft Installer Package format.

3. If you are creating an executable file, select the operating system for which you want to create the package. It is either 32 or 64 bit computers. If you selected the MSI package type, you will only be able to install the OfficeScan client in Silent Mode. Also, you no longer need to choose the platform because the MSI package can be used for both 32 and 64-bit OS. Under Scan Method, kindly select either Conventional or Smart Scan.

4. Under Options, select any of the following installation options:

• Silent mode – creates a package that installs the client program in the background, without displaying any windows. MSI packages can only be installed in silent mode when using Active Directory or Microsoft SMS.
• Update Agent – sets the client to act as an update agent (applicable only to packages for Windows 2000/XP/Vista/Server 2003)
Note: If you enable this option, any OfficeScan server that manages the client will be unable to synchronize or modify the following settings:

Update Agent privilege
Client scheduled update
Update from the Trend Micro ActiveUpdate server
Update from other update sources

• Force overwrite with latest version – overwrites old component versions with the latest version; applicable only when you select Update as the package type.
• Disable prescan (only for fresh install) – disables the file scanning that OfficeScan performs before installation.

5. Under Client utilities, select the utilities to include in the package:

• Outlook Mail Scan – scans the client's Microsoft Outlook mailbox for security risks.
• Check Point SecureClient Support – installs the module to support Check Point SecureClient for Windows 2000/XP/Server 2003

6. Under Components, select the program components to include in the installation package (applicable only when you select Update as the package type).

7. On the Source file field, make sure that the location of the ofcscan.ini file is correct. To change the path, click then select the ofcscan.ini file (by default, this is located in the PCCSRV folder of the OfficeScan server).

8. In the Output file field, click to select the location where you want to create the package, then specify its file name (e.g. ClientSetup.exe).

9. Click Create. When the Client Packager finishes creating the package, the message "Package created successfully" appears. Check the output directory you specified to verify if it has been created successfully.

10. Send the setup package to users via email, or copy it into a CD or similar media for distribution. Ask the users to run the package by double-clicking the .exe or .msi file. Windows Vista users should right-click the file then select Run as administrator.

Note: Send the package only to users whose OfficeScan client will report to the server where the package was created.
===============================================

Autopcc
===============================================
1. On the target computer, go to Start > Run then type the following:
\\<Officescan server IP>\ofcscan\autopcc.exe
===============================================

Option II: Troubleshoot Web Install

1. What OS is the client using? What's the IE version, the web install only supports IE version 5 or later
2. Are there any ActiveX security alert pop-ups while Web Install is in use?
3. Will it be possible to capture the screen where the installation stopped (NTSetup1.htm)?
4. Kindly also try to rebuild Officescan 10 web site by opening a command prompt on the OfficeScan server and go to the location below:

C:\Program Files\Trend Micro\Officescan\PCCSRV

Please run the following command one by one:

svrsvcsetup.exe -uninstall
svrsvcsetup.exe -install
svrsvcsetup.exe -setvirdir
svrsvcsetup.exe -setprivilege

<If you are using SSL to access console, please run the following line as well>

svrsvcsetup.exe -enablessl

5. Kindly try to perform web install again.
6. If the issue still persists, please enable ofcdebug on one affected client.

- Open a notepad and type the following:

[Debug]
DebugLog=C:\ofcdebug.log
DebugLevel=9

- Save the file as ofcdebug.ini on drive C:\ of the target client computer.
- On the Officescan server run CDT tool with All EVENTS enabled. You may download the tool from the link below:

http://www.trendmicro.com/download/product.asp?pro​ductid=25

Filename: cdt_25_win_en_1106.zip

-While the CDT is running on Debug mode, replicate the issue by using Web Install again.
- Once the issue occured, wait for about 5 minutes then on the server, stop CDT debugging and proceed to the succeeding steps in CDT console

8. Kindly send to us the following info if the problem still persists:

a. CDT Log (generated ZIP file using CDT) from the server
b. ofcdebug.log from the client
c. Screenshot mentioned on point # 4
d. Answers to the questions asked (if available)
e. %WINDIR%\temp\ofcxxxx.tmp (from the client if there’s any)
f. ...\Trend Micro\OfficeScan\PCCSRV\Web_OSCE\Web_console\HTML\​ClientInstall folder from the Officescan server

You may upload the files on the link below: [ftp addresss and info provided to nmgadmin]

Kaspersky TDSSKiller

Bei Verdacht auf Rootkits soll der Kaspersky TDSSKiller helfen.

Donwload via: http://support.kaspersky.com/downloads/utils/tdsskiller.exe

Kurz-Anleitung in einem Thread unter http://forums.malwarebytes.org/index.php?showtopic=105917