• Category Archives ToolBox posts
  • Importing and Exporting Mail and User Accounts in Outlook 2007

     

    Credits: Jephens Technology

    Outlook 2007 did away with the export account information that was present in earlier editions. So, if a user with one account moves machines, it’s often faster to just recreate the account on the new machine. However, if a user has 8 accounts (like one did today) it’s time to find a better way.

    That better way is hidden the registry.

    On The Old Machine

    Outlook 2007 is nice enough to put all of its account info for each profile under one key.

    HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\

    So, first off, close Outlook if it’s running.

    To export your Outlook account information, we just need to export that magic key.

    1. Open Registry Editor.
    2. Select the key that you want to save as a file.
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, in Save in, click the drive, folder, or network computer and folder where you want to save the hive.
    5. In File name, enter a name for the key. (outlook_profile.reg would work great.)
    6. In Save as type, make sure it’s set as Registration Files (*.reg)
    7. Click Save.

    Caveats: Every profile on your system under your logon will be exported.

    To move your old mail, you’ll need to copy your PST file to the new machine.

    1. Click StartRun
    2. Type %userprofile%\local settings\application data\microsoft\outlook
    3. Click OK
    4. In that folder there will be some *.pst files. Copy (don’t move!) them to a removable drive or a network share. The one you’re most likely concerned with is outlook.pst

    On The New Machine

    First, we need to import the profile information.

    1. Double-click the file (outlook_profiles.reg) you exported on the old machine. That will import the new information into the registry. (Simple!)

    Next, we need to get your data file back over.

    1. Click StartRun
    2. Type %userprofile%\local settings\application data\microsoft\outlook
    3. Click OK
    4. Copy (don’t move!) the *.pst files you found on the old machine. The one you’re most likely concerned with is outlook.pst

    Lastly, we need to set Outlook to use the profile from the old machine.

    1. Open Control Panel.
    2. Open the Mail applet.
    3. Click on the Show Profiles button.
    4. Choose the profile name that matches the one you used to use from the “Always use this profile” dropdown.
    5. Click OK.

    Now, when you open Outlook, you should have your old mail and the mail accounts all set up and ready to go.

    Passwords

    Outlook on the new machine mightwill ask you for passwords the first time it does a send/receive on all non-Exchange accounts.

    If you know the passwords, awesome. If not, you’ll need to find them out, and we go back to the old machine to do so.

    What we need to do is peer behind the dots that Microsoft uses in their password boxes. To do so, we need a piece of freeware that will do that for us.

    Passware offers a utility, Asterisk Key, which will do the job.

    1. Download, install and run the tool on the old machine using this link.
    2. Open Notepad.
    3. Open Outlook 2007.
    4. Click Tools, Account Settings.
    5. Double-click the account you don’t know the password to.
    6. Go into Asterisk Key and click the RECOVER icon on the toolbar.
    7. The tool will reveal your password for that account. Click the COPY LINK next to the revealed password.
    8. PASTE the password into your notepad document.
    9. Repeat Steps 5-8 as necessary.
    10. Save the Notepad document so you can move it to the new machine.
    11. At the new machine, paste the passwords from the Notepad document into Outlook.

  • Installing ESXi 5.x on a supported USB flash drive or SD flash card (2004784)

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004784

    Purpose

    This article provides instructions for installing ESXi on a USB drive or SD flash card. However, certain considerations must be made before proceeding with an installation. Ensure that the USB flash drive or SD flash card you are using is supported for installation of ESXi 5.x, consult your server vendor for the appropriate choice of a USB or SD flash storage device.

    Note: In the event that your original SD flash card or USB drive fails, these steps can be used in a disaster recovery capacity to get a fully functional ESXi host running as quickly as possible on a replacement USB drive or SD flash card.

    Resolution

    Installing ESXi 5.x on to a USB flash drive or SD flash card

    Note: Installing ESXi 5.x on a USB flash drive or SD flash card has the same minimum requirements as installing to typical SCSI or SATA hard disk. For more information, see the minimum requirements in our vSphere 5.x Documentation Center and ESXi Hardware Requirements.

    1. Acquire and create an installation CD/DVD by downloading ESXi 5.x from the VMware Download Center and burn the ISO file onto CD/DVD media.
    2. Insert the ESXi 5.0 Installable CD into the CD/DVD-ROM drive.
    3. Press the key required to activate your machine’s BIOS setup. This key is often a function key or the Delete key. For more information, consult your hardware vendor documentation.
    4. Ensure that you have set the BIOS to boot from a CD/DVD-ROM device. This varies based on manufacturer.
    5. Boot off the ESXi 5.0 Installation CD/DVD media.
    6. Let the Automatic boot countdown and boot as normal.The ESXi 5.x installation process begins and you see that the kernel modules and drivers are loaded.The installation continues to load at a yellow screen.
    7. Wait for the installation to load completely.
    8. After you see the Welcome screen, click Enter to continue with the installation.
    9. Read the End-User License Agreement (EULA) and press F11 if you accept.The installer detects the disks available for installation. If it sees the flash drive, it is presented as USB under type, and the model as flash reader.
    10. Select this device to install ESXi 5.x and press Enter. If the device is not listed, ensure that your machine sees the device and that the device is compatible. For more information, see the vSphere Compatibility Matrix.
    11. Select the keyboard layout. This is usually Default.
    12. Enter the root password you want. VMware recommends that you do not leave this blank.The installation begins and may take up to 15 minutes.
    13. When the installation completes, remove the installation CD/DVD-ROM.
    14. Click Enter to reboot the host.
    15. Set the first boot device to be the drive on which you installed ESXi on to the USB flash drive or SD flash card.

    Limitation when installing on USB flash drive or SD flash card:

    When installing ESXi onto a USB flash drive or SD flash card, if the drive is less that 8GB is space, this prevents the allocation of a scratch partition onto the flash device. VMware recommends using a retail purchased USB flash drive of 16GB or larger so that the “extra” flash cells can prolong the life of the boot media but high quality parts of 4GB or larger are sufficient to hold the extended coredump partition.To workaround this limitation:

    1. Connect to the ESXi host via SSH. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
    2. Backup the existing boot.cfg file (located in /bootbank/) with the following command:cp /bootbank/boot.cfg /bootbank/boot.bkp
    3. Open the boot.cfg file using VI editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
    4. Modify the following line:kernelopt=no-auto-partition to kernelopt=autoPartition=TRUE skipPartitioningSsds=TRUE autoPartitionCreateUSBCoreDumpPartition=TRUE
    5. Save and close the boot.cfg file.
    6. Restart the ESXi host.

    Impact/Risks

    Disaster Recovery Scenario

    If you have a local datastore containing production information and have completed the installation on a replacement USB flash drive or SD flash card in a disaster recovery scenario, you may be required perform these additional steps:

    1. Connect to the ESXi host using the vSphere Client or add the ESXi host to an existing vCenter Server implementation.
    2. Click the host.
    3. Click the Configuration tab.
    4. Click Storage.
    5. Click Rescan to ensure you can see all datastores.
    6. Browse the datastore and register any virtual machines that are located on the datastores. For more information, see Registering or adding a virtual machine to the inventory (1006160).

  • How to implement SSL in IIS

    http://support.microsoft.com/kb/299875/en-us

    This article was previously published under Q299875

    SUMMARY

    The Internet has opened up new ways for organizations to communicate, both internally and externally. Better communication between employees, vendors, and customers enables an organization to cut costs, bring products to market faster, and build stronger customer relationships. This improved communication requires–at times–transmitting sensitive information over the Internet and intranets. It thus becomes imperative to be able to conduct private, tamper-proof communication with known parties. To bring this about, organizations can build a secure infrastructure based on public-key cryptography by using digital certificates with technologies such as Secure Sockets Layer (SSL). This step-by-step guide discusses how to set up SSL on an Information Services (IIS) computer.

    Requirements

    The following items describe the recommended hardware, software, network infrastructure, skills and knowledge, and service packs that you will need:

    • Windows 2000 Server, Advanced Server, or Professional, with Internet Information Services (IIS) version 5.0 and Microsoft Certificate Server version 2.0 installed and configured.
    • Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise Edition, Windows Server 2003 Datacenter Edition, or Windows Server 2003 Web Edition-based computer with Internet Information Services (IIS) 6.0 and Certificate Services installed and configured.

    If the computer that is hosting Certificate Server is not the same computer that has IIS, you need a valid network or Internet connection to the server that is hosting Certificate Server.

    Create a certificate request

    First, the Web server must make a certificate request. To do this, follow these steps:

    1. Start the Internet Service Manager (ISM), which loads the Internet Information Server snap-in for the Microsoft Management Console (MMC). To do this, click Start, point to Programs, point to Administrative Tools, and then clickInternet Service Manager or Internet Information Services (IIS) Manager.
    2. Double-click the server name so that you see all of the Web sites. In IIS 6.0, expand Web Sites.
    3. Right-click the Web site on which you want to install the certificate, and then click Properties.
    4. Click the Directory Security tab, and then click Server Certificate under Secure Communications to start the Web Server Certificate Wizard.
    5. In IIS 6.0, click Next. If you are running IIS 5.0, go to step 6.
    6. Select Create a new certificate and click Next.
    7. Select Prepare the request now, but send it later and click Next.
    8. Type a name for the certificate. You may want to match the certificate name to the name of the Web site. Now, select a bit length; the higher the bit length, the stronger the certificate encryption. Select Server Gated Cryptography if your users may be coming from countries with encryption restrictions.
    9. Type your organization name and the organizational unit (for example, MyWeb and Development Dept). Click Next.
    10. Type either the fully qualified domain name (FQDN) or the server name as the common name. If you are creating a certificate that will be used over the Internet, it is preferable to use a FQDN (for example, www.MyWeb.com). Click Next.
    11. Enter your location information, and then click Next.
    12. Type the path and file name to save the certificate information to, and click Next to continue.

      Note If you type anything other than the default location and file name, be sure to note the name and location you choose, because you will have to access this file in later steps.

    13. Verify the information that you have typed, and then click Next to complete the process and create the certificate request.

    Submit a certificate request

    The certificate request that you just created needs to be submitted to a Certificate Authority (CA). This may be your own server with Certificate Server 2.0 installed on it or an online CA such as VeriSign. Contact the certificate provider of your choice and determine the best level of certificate for your needs. There are different methods of submitting your request. Contact the Certificate Authority of your choice to request and receive your certificate. You can create your own certificate with Certificate Server 2.0, but your clients must implicitly trust you as the Certificate Authority. The steps below assume that you are using Certificate Server 2.0 as the certificate provider.

    Note The IIS Certificate Wizard will only recognize the Default Web Server template. When you select an Online Enterprise CA, the Authority will not be listed unless the CA is using the Default Web Server template.

    1. Open a browser and browse to http://YourWebServerName/CertSrv/.
    2. In IIS 5.0, select Request a Certificate and click Next. In IIS 6.0, click Request a certificate.
    3. In IIS 5.0, select Advanced Request and click Next. In IIS 6.0, click advanced certificate request.
    4. In IIS 5.0, select Submit a Certificate Request using a Base64 and click Next. In IIS 6.0, click Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
    5. In Microsoft Notepad, open the request document that you created in the “Create a certificate request” section. In IIS 6.0, you can also click Browse for a file to insert.
    6. Copy the contents of the document. The contents should resemble the following:
      -----BEGIN NEW CERTIFICATE REQUEST-----
      MIICcjCCAhwCAQAwYjETMBEGA1UEAxMKcm9ic3NlcnZlcjELMAkGA1UECxMCTVMx
      CzAJBgNVBAoTAk1TMREwDwYDVQQHEwhCZWxsZXZ1ZTERMA8GA1UECBMIV2FzaGl0
      b24xCzAJBgNVBAYTAlVTMFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALYK4sYDNQ7h
      LmSfL0qpIvUfY7Ddw7fNCvDp3rM7z4QqoLhA2c8TkyamqWTBsV0WRHIidf/J6mU4
      wN4wrUzJTLUCAwEAAaCCAVMwGgYKKwYBBAGCNw0CAzEMFgo1LjAuMjE5NS4yMDUG
      CisGAQQBgjcCAQ4xJzAlMA4GA1UdDwEB/wQEAwIE8DATBgNVHSUEDDAKBggrBgEF
      BQcDATCB/QYKKwYBBAGCNw0CAjGB7jCB6wIBAR5aAE0AaQBjAHIAbwBzAG8AZgB0
      ACAAUgBTAEEAIABTAEMAaABhAG4AbgBlAGwAIABDAHIAeQBwAHQAbwBnAHIAYQBw
      AGgAaQBjACAAUAByAG8AdgBpAGQAZQByA4GJAGKa0jzBn8fkxScrWsdnU2eUJOMU
      K5Ms87Q+fjP1/pWN3PJnH7x8MBc5isFCjww6YnIjD8c3OfYfjkmWc048ZuGoH7Zo
      D6YNfv/SfAvQmr90eGmKOFFiTD+hl1hM08gu2oxFU7mCvfTQ/2IbXP7KYFGEqaJ6
      wn0Z5yLOByPqblQZAAAAAAAAAAAwDQYJKoZIhvcNAQEFBQADQQCgRCWkaXlY2nVa
      tbn6p5miPwWfrbViYo0B62wkuH0f7J0nSGcxMnn/6Q/iLEIsgHqFhox5PWCzIV0J
      tXKPWrBL
      -----END NEW CERTIFICATE REQUEST-------

      Note If you save the document with the default name and location, it is located at C:\Certreq.txt.

      Note Be sure to copy all of the content just as shown.

    7. Paste the contents of the document into the Web form’s Base64 Encoded Certificate Request text box.
    8. Under Certificate Template, select Web Server or User, and then click Submit.
    9. If Certificate Server is set to Always Issue the Certificate, you can access the certificate immediately. To do this, follow these steps:
      1. Click Download CA Certificate (do not click Download CA Certificate path or Download certificate chain).
      2. When you are prompted, select Save this file to disk and save the certificate to your desktop or another location that you will remember. You may now go directly to the “Install the certificate and set up an SSL Web site” section.

    Issue and download a certificate

    To issue a certificate in Certificate Server, follow these steps:

    1. Open the CA MMC snap-in. To do this, click Start, point to Programs, point to Administrative Tools, and then clickCertificate Authority.
    2. In IIS 5.0, expand Certificate Authority and click the Pending Requests folder. Your pending certificate requests appear in the right pane. In IIS 6.0, expand the server name.
    3. Right-click the pending certificate request that you just submitted, select All Tasks, and then click Issue.

      Note After you select Issue, the certificate is no longer displayed in this window and folder. It now resides in the Issued Certificate folder.

    4. After you have issued (and authorized) the certificate, you can return to the Certificate Servers Web interface to select and download the certificate. To do this, follow these steps:
      1. Browse to http://YourWebServerName/CertSrv/.
      2. On the default page, select Check on a pending certificate and click Next. In IIS 6.0, click View the status of a pending certificate request.
      3. Select your pending certificate, then click Next to go to the download page.
      4. On the download page, click Download CA Certificate (do not click Download CA Certificate path orDownload certificate chain).
      5. When you are prompted, select Save this file to disk and save the certificate to your desktop or another location that you will remember.

    Install the certificate and set up an SSL Web site

    To install the certificate, follow these steps:

    1. Open the Internet Services Manager and expand the server name so that you can view the Web sites.
    2. Right-click the Web site for which you created the certificate request and click Properties.
    3. Click the Directory Security tab. Under Secure Communications, click Server Certificate. This starts the Certificate Installation Wizard. Click Next to continue.
    4. Select Process the pending request and install the certificate and click Next.
    5. Type the location of the certificate that you downloaded in the “Issue and download a certificate” section, then clickNext. The Wizard displays the Certificate Summary. Verify that the information is correct, then click Next to continue.
    6. Click Finish to complete the process.

    Configure and test the certificate

    To configure and test the certificate, follow these steps:

    1. On the Directory Security tab, under Secure Communications, note that there are now three available options. To set the Web site to require secure connections, click Edit. The Secure Communications dialog box appears.
    2. Select Require Secure Channel (SSL) and click OK.
    3. Click Apply and then OK to close the property sheet.
    4. Browse to the site and verify that it works. To do this, follow these steps:
      1. Access the site through HTTP by typing http://localhost/Postinfo.html in the browser. You receive an error message that resembles the following:

        HTTP 403.4 – Forbidden: SSL required.

      2. Try to browse to the same Web page using a secured connection (HTTPS) by typinghttps://localhost/postinfo.html in the browser. You may receive a security alert that states that the certificate is not from a trusted root CA. Click Yes to continue to the Web page. If the page appears, you have successfully installed your certificate.

    Troubleshooting

    • The use of SSL slows performance between HTTP servers and browsers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

      150031 Use of SSL creates performance overhead for browsers

    • When you use Microsoft Visual InterDev version 6.0 to author Web sites with SSL, there are several issues and limitations to consider. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

      238662 Using Visual InterDev and Secure Sockets Layer

    • This article discusses server certificates only. A server certificate enables users to authenticate your server, check the validity of Web content, and establish a secure connection. If you also intend to authenticate users who browse to your Web site, you may consider using client certificates. A typical client certificate contains several items of information: the identity of the user, the identity of the certification authority, a public key that is used for establishing secure communications, and validation information, such as an expiration date and serial number.

  • Windows Fast Logon Optimization feature

    Start gpedit.msc
    Go to:
    Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon

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

    By default in Windows 8, Windows 7, Windows Vista, and Windows XP, the Fast Logon Optimization feature is set for domain and workgroup members. Policy settings apply asynchronously when the computer starts and when the user signs in. As a result, Windows 8, Windows 7, Windows Vista, and Windows XP do not wait for the network to be fully initialized at startup and sign-in. Existing users are logged on by using cached credentials. This results in shorter logon times. Group Policy is applied in the background after the network becomes available. Be aware that, because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. Additionally, changes that are made to the user object, such as adding a roaming profile path, root directory, or user object logon script, may take two logons to be detected.

    If you turn off this feature, Windows waits for the network to be fully initialized before users are logged on. This results in the synchronous application of policies when the computer starts and when the user logs on. This application of policies resembles a background refresh process and can reduce the time that is required for the Logon dialog box to display and the time that is required for the shell to be available to the user. An administrator can change the default by using the Group Policy MMC snap-in.

    Fast Logon Optimization is always off during logon when a user first logs on to a computer.

    You should be aware that, under the previous conditions, computer startup can still be asynchronous. However, because logon is synchronous under these conditions, logon does not exhibit optimization.

    When your folder redirection policy is not completely applied at first logon, you can find the following warning in the event log:

    Event Type: Warning
    Event Source: Folder Redirection
    Event Category: None
    Event ID: 301
    Description: Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.

    Folder redirection and software installation policies

    Be aware that when logon optimization is turned on, a user may have to log on to a computer two times before folder redirection policies and software installation policies are applied. This is because applying these kinds of policies requires the synchronous policy application. During a policy refresh (which is asynchronous), the system sets a flag that indicates that applying folder redirection or a software installation policy is required. The flag forces synchronous application of the policy at the user’s next logon.

    BE aware that Windows clients support Fast Logon Optimization in any domain environment. To turn off Fast Logon Optimization, you can use the following policy setting:

    Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon

    When this policy is enabled, a Windows XP client behaves in the same manner as a Windows 2000 client at both system startup and at user logon.

    Note This also applies to systems that are running Windows 7 or Windows 8. However, in those systems, the event ID changes to 510:

    Event Log: Application Log
    Event Type: Error
    Event Source: Microsoft-Windows-Folder Redirection
    Event ID: 510
    Description: Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.


  • Determine Which .NET Framework Versions Are Installed

    How to: Determine Which .NET Framework Versions Are Installed

    .NET Framework 4.5
    The .NET Framework consists of two main components: a set of assemblies, which are collections of types and resources that provide the functionality for your apps, and the common language runtime (CLR), which manages and executes your app’s code. These two components are versioned separately. The .NET Framework and assemblies share the same version number, and the CLR is identified by its own version number (see .NET Framework Versions and Dependencies). You can install and run multiple versions of the .NET Framework on your computer. To see which versions of the .NET Framework are installed on your computer, you should view the entries in the Windows registry. To determine which version of the CLR is currently executing code, you can use the System.Environment class.

    This article provides instructions for detecting .NET Framework versions on a computer both manually and programmatically, and detecting the runtime version using a tool and programmatically. For information about detecting the installed updates for each version of the .NET Framework, see How to: Determine Which .NET Framework Updates Are Installed. For information about installing the .NET Framework, see the installation guide.

    To find the installed .NET Framework versions manually (versions 1-4)

    1. On the Start menu, choose Run.
    2. In the Open box, enter regedit.exe.

      You must have administrative credentials to run regedit.exe.

    3. In the Registry Editor, open the following subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP

      The installed versions are listed under the NDP subkey. The version number is stored in the Version entry. For the .NET Framework 4 the Version entry is under the Client or Full subkey (under NDP), or under both subkeys.

      Note Note
      The “NET Framework Setup” folder in the registry does not begin with a period.

    To find the installed .NET Framework versions manually (versions 4.5 and later)

    1. On the Start menu, choose Run.
    2. In the Open box, enter regedit.exe.

      You must have administrative credentials to run regedit.exe.

    3. In the Registry Editor, open the following subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

      Check for a DWORD value named Release. The existence of the Release DWORD indicates that the .NET Framework 4.5 or newer has been installed on that computer.

      The registry entry for the .NET Framework 4.5. 

      The value of the Release DWORD indicates which version of the .NET Framework is installed.

      Version Value of the Release DWORD
      .NET Framework 4.5 378389
      .NET Framework 4.5.1 RC 378681

    To find the current runtime version by using a tool

    • Use the CLR Version Tool (Clrver.exe) to determine what versions of the common language runtime is installed on a computer.

      From a Visual Studio Command Prompt enter clrver. This command produces output similar to the following.

      Copy

      Versions installed on the machine:
      v2.0.50727
      v4.0.30319

      For more information about using this tool, see Clrver.exe (CLR Version Tool)


  • Microsoft Windows Server 2003 – Event ID: 5603 Event Source: WinMgmt occurs when Microsoft Health Monitor is used.

    www.reboot.ro/troubleshooting/software/microsoft-windows-server-2003-event-id-5603-event-source-winmgmt

    Event Type: Warning
    Event Source: WinMgmt
    Event Category: None
    Event ID: 5603
    Description:
    A provider, PerfProv, has been registered in the WMI namespace, ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

    Resolution:
    open WMI (Windows Management Infrastructure): Start > run > wmimgmt.msc
    Windows Management Infrastructure (WMI) > WMI Control (local) > Properties
    Properties > Security (tab) > Root (tree) > CIMV2 > MicrosoftHealthMonitor > PerfMon > Security (button)
    Security for ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon > Security > Add (button) > Advanced > Find now > Performance Log Users (select) > OK
    Performance Log Users (select) > Execute Methods (tick) > Enable Account (tick) > Remote Enable (tick)


  • Turn off Caching of Windows 7 Thumbnails in Hidden thumbs.db Files

    Start gpedit.msc
    Go to:
    User Configuration->Administrative Templates->Windows Components->Windows Explorer
    enable “Turn off the caching of thumbnails in hidden thumbs.db files”

    Disable Thumbnail Previews in Windows 7 or Vista Explorer

    If you want to speed up browsing around in explorer, you might think about disabling thumbnail previews in folders.

    Note that this works in Windows 7 or Vista

    To make this change, click the Organize button on any folder, and choose Folder and Search Options from the menu.

    Click the View tab, and then check the Always show icons, never thumbnails checkbox.


  • Use Outlook Anywhere to connect to your Exchange server without VPN

    Enable Outlook Anywhere in Outlook

    Your Exchange administrator can automatically configure all copies of Outlook in your organization or provide a special executable script file that enables Outlook Anywhere. You can also manually configure Outlook Anywhere if the system requirements are met and you have the correct URL and security information from your Exchange administrator.

    1. On the Tools menu, click Account Settings, select the Exchange account, and then click Change.
    2. Click More Settings, and then click the Connection tab.
    3. Under Outlook Anywhere, select the Connect to Microsoft Exchange using HTTP check box.

    Connection tab

    NOTE   If the Outlook Anywhere section is not available, your computer is probably not running Windows XP Service Pack 2 or a later service pack.

    1. To specify a proxy server, click Exchange Proxy Settings.

    Connection settings

    Callout 1 Type the URL provided by your Exchange administrator.

    Callout 2 If your Exchange administrator tells you to use a Secure Sockets Layer (SSL) connection, select the Connect using SSL only check box.

    Callout 3 If your Exchange administrator instructs you to do so, select the Only connect to proxy servers that have this principal name in their certificate check box, and then type msstd: followed by the URL provided by the administrator.


    1. Under Proxy authentication settings, click Basic Authentication or NTLM Authentication as instructed by your Exchange administrator.

    Proxy authentication settings

    NOTE   If you click Basic Authentication or NTLM Authentication and an LM Compatibility Level of less than 2, you will be prompted for a password each time a connection is made to Exchange. With Basic Authentication, the password is sent in clear text. For increased security, we recommend that you select theNTLM Authentication and Connect using SSL only options.