Posts tagged Windows 7

Avaya VPN Client Release 10.05.150 for Windows 7

18

Avaya has released version 10.05.150 of their VPN client (formerly Contivity client) that supports both 32-bit and 64-bit versions of Windows 7. This single client supports the following operating systems (in both 32-bit and 64-bit versions);

  • Windows XP
  • Windows Vista
  • Windows 7

The release notes mention the following compatibility issues;

User may experience Blue Screen of Death (BSOD) during VPN tunneling if McAfee VirusScan v8.8 is installed on the machine. It’s due to an issue with McAfee driver mfewfpk.sys. McAfee provided a hot fix in October, 2011 and also embedded it into McAfee VirusScan v8.8 Repost 1. Please either apply the patch or use the v8.8 Repost 1.

The Avaya VPN Client (AVC) must not be installed on the same client machine in which either the Avaya VPN Gateway (AVG) NetDirect Installable Client (NDIC) or NetDirect portable client (ActiveX or Java-based) is installed, or vice-versa. Doing so may result in unexpected client behaviors. The AVC client may report “Failed to Activate the VPN Adapter”. Ensure that conflicting clients are uninstalled prior to installation of either AVC or NDIC/NetDirect.

The following issues have been resolved;

  • wi00938485 Splittun Disabled/Enable_Inverse Failure on Windows7
  • wi00924999 If users connect AVC to AVG from behind a non-IPsec-aware NAT box, they might experience intermittent banner retrieval failure or disconnection.
  • wi00947500 Sometimes the upload speed is low.
  • wi00887226 In rare occasions network applications might be impacted because of dropped packets.
  • wi00924795 Custom taskbar icons have wrong file names.

You should refer to the release notes for all the details.

I will continue to host the client files on my website.

AVC32-10.05.150.exe (32-bit Windows XP, Windows Vista, Windows 7)
AVC64-10.05.150.exe (64-bit Windows XP, Windows Vista, Windows 7)

Cheers

Avaya VPN Client Release 10.05.100 for Windows 7

48

Avaya has released version 10.05.100 of their VPN client (formerly Contivity client) that supports both 32-bit and 64-bit versions of Windows 7. This single client supports the following operating systems (in both 32-bit and 64-bit versions);

  • Windows XP
  • Windows Vista
  • Windows 7

The following feature has been added;

Integrated smart card PIN prompt (wi00565664)

When users use smart cards, normally the smart card reader applications and the operating system handle the context setup, i.e. they pop up PIN prompt and PIN verification. However, with the introduction of Windows 7/Vista’s “Session 0 isolation”, this mechanism does work for some smart cards any longer. Their PIN prompts get blocked by “Session 0 isolation” when the calling applications run as services.

In this release, we take care of the smart card context setup within our client in a way that is compatible with the OS that users can continue using smart card based authentication smoothly as before.

The following issues were resolved;

  • wi00889552 – On Windows 7, when AVC establishes a SSL VPN tunnel, it identifies its local OS to Avaya VPN Gateway (AVG) as Vista.
  • wi00888226 – Certificates not available for selection if there are certificates installed on the PC that do not have a Subject field
  • wi00896822 – Occasionally the upgrade install on Windows XP 64-bit doesn’t install the driver properly.

You should refer to the release notes for all the details.

I will continue to host both the 32bit and 64bit installation files here on my blog for download until such time as I run out of bandwidth or someone from Avaya objects (whichever occurs first).

If you feel so inclined why not leave a comment, even if it’s just to say “Hi!”.

AVC32-10.05.100.exe (MD5SUM HASH – 08f1a124ec969333680f883580327009)
AVC64-10.05.100.exe (MD5SUM HASH – 4174ea5afba84ad496356744a7ac579e)

Cheers!

Windows 7 x64 Service Pack 1 Installation Failed

2

This weekend I decided to install Service Pack 1 on my home Windows 7 x64 personal computer. As luck would have it the installation failed. The installation reported error 0x800f0a12 when I clicked on the details link. When I check the System Log I found the following event;

Installation Failure: Windows failed to install the following update with error 0×80070643: Windows 7 Service Pack 1 for x64-based Systems (KB976932).

I examined the Component Based Servicing log (C:\Windows\Logs\CBS.log) and found the following two entries;

2011-06-25 09:27:36, Error                 CBS    SPI: (CSPInstall::AutoMountDisableCheck:1026)Bcdedit failed with error code 0×1 hr=0x800f0a12
2011-06-25 09:27:36, Error                 CBS    SPI: (CSPInstall::CompatibilityApplicabilityScan:1471)AutoMountDisable check failed hr=0x800f0a12

With that information I turned to the great and powerful Google in search of enlightenment and found a reference to the following blog post on TechNet, Windows 7/2008 R2 Service Pack 1 fails with 0x800f0a12. That article provided a link to another Microsoft article entitled, Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) installation error: 0x800F0A12.

Apparently the error code 0x800f0a12 means the installer cannot access the system partition of the personal computer to update the files. This error can be caused by a few different issues including, the system partition isn’t automatically mounted, Windows is running on a storage area network (SAN), or a disk management tool from another software manufacturer was used to copy (or clone) the disk or partition on which you’re trying to install SP1.

The TechNet article advises users to run Diskpart which is the disk partitioning tool in Windows. However, the Microsoft article provides a command line solution by running the command mountvol /E as an administrator and then rebooting the computer.

Cheers!

Go to Top