When we upgraded to Windows 7 we found that our laptops would not connect to our VPN over 3G Datacards using the Cisco VPN Client.
This is due to the Cisco VPN Client software not supporting WWAN devices. Initially we were stunned to learn that the latest VPN Client wasn’ compatible with Windows 7! Subsequently they did release a version – we currently use version: 5.0.07.0440. But at the same time they announced that the VPN Client was end of life and that you should be using the AnyConnect client instead (that’s a whole different story see: http://www.islandearth.com/articles/2013/5/2/cisco-asa-anyconnect-vpn-per-device-ipsecv2-tunnels-using-ce.html)
This meant that WWAN was never going to be supported in the Cisco VPN Client and we could not upgrade to AnyConnect VPN due to our reliance on IPSECv1 VPN Tunnels (see article above).
After much searching we managed to find a solution:
The problem is apparently to do with a limit on Citrix DNE instrumentation measuring! Quite how this makes the VPN Client work with WWAN cards is beyond me but it does!
Getting 100% cpu but idle process is 99%?
Just take the battery pack out and re-insert and all is OK!
You should be able to move disks between HP Proliant servers without any problems by following this guide (note: applies to single or mirrored disks only RAID 0+1).
This operation is useful when a server has died (just pull the disks and follow instructions for new server below) or a server is no longer connected to a storage expander where disks are allocated to it. In both cases you can then pull the data off the drive onto a production disk array.
If the server is still operating, logon to the server you are moving the disk from and start the HP Disk Array Configuration Utility – usually under Start, Programs, HP System Tools
Find the correct logical disk/partition that you are moving – select logical disk and choose more information (this should tell you which server is connected to which drives on a storage expander – look for host controller connecting and you should see the server name in brackets).
You can also select the physical view to guide you as to which bays disks are located.
Once you have identified the physical drive(s) unslot the drive (just single drive if part of raid array) from its bay and slot it into a spare bay on the new server or storage expander.
Open the HP Disk Array Configuration utility on the new server – you should see the new drive listed as unallocated.
Select create partition on new server and tick the new drive listed – keep defaults.
Select create logical drive for partition just created.
Select save changes.
Drive should now have mounted and been assigned a drive letter – try browsing to the drive on the new server.
Exit the array configuration utility on new server.
On old server delete the partition for the drive you just pulled out, save changes and exit the ACU.
Your done – you can now pull data off and restore to a production array etc.