When creating a connection profile for VPN, we use a PIN for installation. When a user launches the connection profile, it will ask for the PIN, when the correct PINis typed in the user receives the error "The Installation cannot proceed. Either the PIN you provided is incorrect, or cryptography is improperly onfigured on your machine. Check your CAPS LOCK key. If the problems persist, contact your System Administrator. I know this profile works on Windows XP SP3 without a problem. We tried running the profile using the administrators account but that doesn't fix the problem. Not sure why crypto changes need to be made to allow the users to imput the PIN to install the program. While we could create a profile without a PIN would prefer not to. Any suggestions?

I have the Same issue with L2TP VPN client. Could you please any suggestions?

If the connection profile is created with windows server 2003 CMAK the profile dose NOT work in windows 7 and you need to create it with windows server 2008 R2 CMAK to work with windows 7Microsoft Certified System Engineer 2003

The Windows Server 2008 CMAK also doesn't workon Windows Vista and Windows 7 32 bit machines. Works fine on 64 bit machinesincluding the use of aPIN. So with 32 bit client machines were sorta stuck. The bulk of the Windows Vista and 7 machine are 32 bit. Can't use the W2003 CMAK with an encrypted PIN to install on Vista and 7 and can't use W2008 CMAK because for some reason those profiles dont' workon 32 bit clients. Try it an see. create a CMAK profile on W2003 server with a PIN to install and run it on Vista 32 bit. Then create a profile on a W2008 64 bit machine using CMAK and install it on a 32 bit Vista /7 client. Just my experience.

Thank you for help. It was working properly on Windows7 RC ver. Why it does not working on windows7 Enterprise, Ultimate and professional?

I can confirm this. I have exactly the same problem!RegardJoern

I found the solution. The CMAK for Windows 7 32bit is included in the Client. http://technet.microsoft.com/en-us/library/cc771679.aspxRegardsJoern

Installation of CMAK isn't the problem, it's creating the profile for clients using CMAK which resides on a 64 bit server. Creating the profile for clients using the 64 bit version of CMAK installed on a 64 bit server doesn't work on 32 bit machines. Rightfully so, it's 64 bit. Buthaving to use a 32 bit machine to create 32 bit profiles is double the work and it's one 2 different machines. I have to keep track of them, document them, and it's a lot of extra work. I don't mind creating 2 different versions of the profile, 32 bit and 64 bit, but I would rather do it on the same machine.