Tuesday, August 11, 2009

Active Desktop Recovery

I found these fixes on the web.

image

FIX #1

  1. Open an explorer window (open My Computer for example)
  2. Tools
  3. Folder Options
  4. View
  5. Uncheck Hide protected operating system files
  6. Now do a search for desktop.htt…it should be on your C: normally
  7. Delete any desktop.htt files you find (there could be more than one depending on how many user profiles are on the machine)  They should be located in Documents and Settings\User\Application Data\Microsoft\Internet Explorer
  8. Close all windows you have open
  9. Now reboot your PC..Windows will recreate desktop.htt for you and it should work.
  10. Change back the file settings to Hide protected operating system files

FIX #2

  1. Go to Run, type regedit and hit enter
  2. Go here HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Desktop\SafeMode\Components
  3. Select the value DeskHtmlVersion
  4. Select the Decimal radial button
  5. Change the value of 272 to 0
  6. Press F5 while on the desktop
  7. Most of the time it might take a few seconds for your background to appear and other times…you might need to restart your computer.

Monday, July 6, 2009

Several dialog boxes are blank in IE, Search, System Restore, etc

I had this issue on a couple of PC’s.  On one PC McAfee had deleted some files and apparently corrupted the jscript.dll file.  On another we are guessing a program called CCare which is for CareCredit.  It uses Java and it possibly caused the corruption.

Other symptoms you may get are blank pages in IE when you try to log into Hotmail/Live mail, etc.

Here is an article from Microsoft that helped me.  I was able to get things working by simply re-registering jscript.dll.

http://support.microsoft.com/kb/831430 

You may experience one of the following symptoms:

  • When you try to view any one of the following dialog boxes, the dialog box may appear to be empty or partly empty:
    • Search Companion
    • User Accounts
    • Windows Update
    • Help and Support
    • System Restore
  • When you try to start Microsoft Windows Media Player, you may receive an "An internal application error has occurred" (or a similar) error message.
  • Internet Explorer may not be able to print. When you click File, and then click Print, the Print dialog box does not appear. The print preview is blank.

This issue may occur if one or more of the Jscript registry key settings are incorrect. This issue may also occur if the Jscript.dll file is missing or damaged.

Method 1: Reregister Jscript.dll
  1. Click Start, and then click Run.
  2. In the Open box, type regsvr32 jscript.dll, and then click OK.
  3. Click OK.
If the file does not register as expected, or if you receive an error message, the system file may be missing or damaged. To extract the missing file in Windows XP, follow these steps:
  1. Click Start, and then click Run.
  2. In the Open box, type msconfig, and then click OK.
  3. Click Expand File.
  4. In the File to restore box, type the name of the file that you want to restore.
  5. In the Restore from box, type the path of the Windows XP .cab file where you want to restore the file, or click Browse From to locate the Windows XP .cab file.
    Note The Windows XP .cab files are stored in the I386 folder on the Windows XP CD.
  6. In the Save file in box, type the path where you want to extract the new file, or click Browse To to locate the folder that you want.
  7. Click Expand.
  8. In the System Configuration Utility dialog box, click OK. If you are prompted to restart the computer, click Restart.

Open a dialog box that previously experienced the issue that is described in the "Symptoms" section of this article. If the issue recurs, go to the next method.

Method 2: Edit the registry
To do this, follow these steps.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32

    The (Default) value data should contain the following value:

    C:\WINDOWS\SYSTEM32\JSCRIPT.DLL

    If it does not, double-click Default, type C:\WINDOWS\SYSTEM32\JSCRIPT.DLL in the Value data box, and then click OK.

  4. The ThreadingModel value data should contain the following value:

    Both

    If it does not, double-click ThreadingModel, and then type Both in the Value data box.

  5. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\CLSID\{f414c261-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32

  6. Repeat steps 3 and 4 to edit this key, and then go to step 7.
  7. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\CLSID\{f414c262-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32

  8. Repeat steps 3 and 4 to edit this key, and then go to step 9.
  9. Exit Registry Editor.

Friday, May 15, 2009

Excellent location for Open Source software

http://www.osalt.com

Great way to find alternatives to paid software.  I like it because they give descriptions of the software.

 

 

Thursday, April 23, 2009

LogMeIn Extra Security

Get email notifications of failed logon attempts.

Go to Account then Extra Security.  Select Email notification.  Put in as many email addresses as you wish then check whichever notification you prefer.  I chose both so I am notified when successful and failed logon attempts into my account occur.

clip_image001

I tested it by logging in with a bad password and immediately received an email including the IP address of the PC that attempted to log in (I put “X”’s in place of the email and IP):

There was an unsuccessful login attempt to your LogMeIn account.

From IP address:  XX.XX.XX.XX

Time:             04/23/2009 11:21:19

Account email:    XXXX@XXX.com

Attempt number:   1

Source:           Website

You chose to receive these alert emails on your Account / Extra Security page. Uncheck the relevant box to stop receiving such emails.

I would suggest anybody with a LogMeIn account should at least set up email notification as well.

Tuesday, April 14, 2009

Client install packager for Trend Micro Offic eScan

Client Packager

  • Tools > Client Tools > Client Packager

Client Packager can compress setup and update files into a self-extracting file, which you can then send to users using conventional media such as CD-ROM. When users receive the package, all they have to do is run the setup program in the client computer.

Client Packager is especially useful when deploying the client setup or update files to clients in low-bandwidth remote offices. OfficeScan clients you install using Client Packager report to the server where Client Packager created the setup package.

Self-extracting files created by Client Packager
  • Executable: This common file type has an .exe extension.

  • Microsoft Installer Package Format (MSI): This file type conforms to Microsoft's Windows Installer package specifications. You can send the MSI package through conventional media or use Active Directory™ and Microsoft SMS. See the Installation and Deployment Guide for information on deploying an MSI package using Active Directory and Microsoft SMS. For more information on MSI, see the Microsoft Web site.

Client computer requirements
  • Minimum of 160MB free disk space

  • Windows Installer 2.0 (to run an MSI package)

To create a package using the Client Packager user interface:
  1. On the OfficeScan server computer, browse to \PCCSRV\Admin\Utility\ClientPackager.

  2. Double-click ClnPack.exe to run the tool. The Client Packager console opens.

  3. Note: You must run the program only from the OfficeScan server computer.

  1. Select the type of package you want to create:

  2. Setup: Select if installing the OfficeScan client program. This will create an executable file.

  3. Update: Select if updating OfficeScan client components only. This will also create an executable file.

  4. MSI Package: Select if creating a package that conforms to the Microsoft Installer Package format

  1. If creating an executable file, select the operating system for which you want to create the package.

  2. Select from among the following installation options:

  • Silent Mode: Creates a package that installs on the client computer in the background, unnoticeable to the client and without showing an installation status window

  • Update Agent: Gives the client the ability to act as an Update Agent (Update Agents are alternative servers that help the OfficeScan server deploy components to clients.). If you install the OfficeScan client program using Client Packager and you enable the Update Agent option, you must use the Scheduled Update Configuration Tool to enable and configure scheduled updates.

  • Tip: If you install the OfficeScan client program using Client Packager and you enable the Update Agent option, any OfficeScan server that registers with the client will not be able to synchronize or modify the following settings: the Update Agent privilege, client scheduled update, update from Trend Micro ActiveUpdate server, and updates from other update sources.
    Trend Micro recommends installing only on client computers not registered with any OfficeScan server and configuring the Update Agent to get its updates from an update source other than an OfficeScan server. If you want to modify the Update Agent settings mentioned above, use a client program installation method other than Client Packager.

  • Force overwrite with latest version: Overwrites old 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

  1. Select the OfficeScan client utilities to include in the package.

  2. Outlook Mail Scan: Scans Microsoft Outlook mailboxes for security risks

  3. Check Point SecureClient Support: Support for Check Point SecureClient for Windows 2000/XP/Vista/Server 2003

  1. Select the components to include in the installation package.

  2. Next to Source file, ensure that the location of the ofcscan.ini file is correct. To modify the path, click to browse for the ofcscan.ini file. By default, this file is in the \PCCSRV folder of the OfficeScan server.

  3. In Output file, specify the location where you want to create the client package and the file name (for example, ClientSetup.exe).

  4. Click Create. When Client Packager finishes creating the package, the message "Package created successfully" appears. To verify successful package creation, check the output directory you specified.

  5. Send the package to your users.

  • Warning: You can only send the package to the OfficeScan clients that report to the server where you created the package. Do not send the package to OfficeScan clients that report to other OfficeScan servers.

Using the Scheduled Update Configuration Tool

Use the Scheduled Update Configuration Tool to enable and configure scheduled updates on OfficeScan clients acting as Update Agents that you installed using Client Packager. This tool is available only on Update Agents that Client Packager installs.

To use the Scheduled Update Configuration Tool:
  1. On the Update Agent that Client Packager installed, open Windows Explorer.

  2. Go to the OfficeScan client folder.

  3. Double-click SUCTool.exe to run the tool. The Schedule Update Configuration Tool console opens.

  4. Select Enable Scheduled Update.

  5. Specify the update frequency and time.

  6. Click Apply.

Copyright © 1998-2007 Trend Micro Incorporated. All rights reserved.

Imaging PC’s with Trend Micro OfficeScan

Image Setup Utility

  • Tools > Client Tools > Image Setup Utility

Disk imaging technology allows you to create an image of an OfficeScan client and make clones of it to other computers on your network.

Each client installation needs a Globally Unique Identifier (GUID) so that the server can identify your clients individually. Use an OfficeScan program called ImgSetup.exe to create a different GUID for each of the clones.

Image Setup Utility helps you use hard drive imaging technology to deploy the OfficeScan client software.

  • Note: Image Setup supports Windows 2000, XP and Server 2003, but not Windows Vista, 2008, and x64 platforms.

Before you install clients:

  • Check the client system requirements.

  • Identify which computers on your network do not currently have protection against security risks. You can do this by running the Trend Micro Vulnerability Scanner. This tool analyzes computers on your network for installed antivirus software based on an IP address range you specify.

To create a disk image of an OfficeScan client:
  1. Obtain a disk imaging software.

  2. Install the OfficeScan client to a computer. You will use this client as the source of the disk image.

  3. Copy ImgSetup.exe to this computer from the OfficeScan server's \PCCSRV\Admin\Utility\ImgSetup folder.

  4. Run ImgSetup.exe on this computer. OfficeScan creates A RUN registry key under HKEY_LOCAL_MACHINE.

  5. Create a disk image of the OfficeScan client using your disk imaging software.

  6. Restart the clone. ImgSetup.exe will automatically start and create one new GUID value. The client will report this new GUID to the server and the server will create a new record for the new client.

  7. Warning: To avoid having two computers with the same name in the OfficeScan database, remember to manually change the computer name or domain name of the cloned OfficeScan client.

Copyright © 1998-2007 Trend Micro Incorporated. All rights reserved.