Well, RasEapOptions is actually used by the RasDialer during the dialing process to set flags that the dialer uses and doesn't relate directly to the entry. Depending on whether you're trying to use certificates or a pre-shared key determines what you need
to call. There hasn't been much interest in EAP within the project thus far, which explains the lack of threads on the subject.

In order to actually update the pre-shared key used by the client you'd need to use the WINXP build type (Windows 2000 doesn't support pre-shared keys) and add the entry to the phone book before trying to update the credentials. This is just a Windows restriction,
the project doesn't store credentials in memory, and Windows requires the entry to be in a phone book before writing credentials to it.

If you want to use certificates there are some known problems with some client/server configurations. Occasionally certificates can't be found, not really sure why. As for actually setting the certificate data you can use the SetEapUserData method on the
class to set the certificate data. However, you have to know the inner workings of the EAP DLL you're using, which there is no documentation for the structure of the data in memory. There are flags you can set that choose your certificate needed by the connection
automatically, however with security configurations you're best following the advice I give most everyone when building entries:

The best way I've found over the years to build a connection when you don't know which flags to set is to build the connection using the Windows interface, verify the connection works correctly, and open it in a RasPhoneBook and inspect the settings that
Windows has chosen.

I ended up creating the connection with as many settings that I could generate using RasEntry, then backing up the generated pbk file, then making the changes in windows, then running a compare to see what changes.

It turns out that there were a couple of changes, but in the end I was able to just write a good old batch script to xcopy the new pbk file to all the clients (with some checks to see if the pbk is already there etc)

I'll find that part of the pbk file that was changed and post it when I get back to my computer and see of there is an option in DotRas after all.

Also since this is an IKEv2 VPN, there are no preshared keys. The domain computers already have the root certificate from the server and we just use EAP-MSCHAPv2 to pass through the user's current credentials.

Well, RasEapOptions is actually used by the RasDialer during the dialing process to set flags that the dialer uses and doesn't relate directly to the entry. Depending on whether you're trying to use certificates or a pre-shared key determines what you need
to call. There hasn't been much interest in EAP within the project thus far, which explains the lack of threads on the subject.

In order to actually update the pre-shared key used by the client you'd need to use the WINXP build type (Windows 2000 doesn't support pre-shared keys) and add the entry to the phone book before trying to update the credentials. This is just a Windows restriction,
the project doesn't store credentials in memory, and Windows requires the entry to be in a phone book before writing credentials to it.

If you want to use certificates there are some known problems with some client/server configurations. Occasionally certificates can't be found, not really sure why. As for actually setting the certificate data you can use the SetEapUserData method on the
class to set the certificate data. However, you have to know the inner workings of the EAP DLL you're using, which there is no documentation for the structure of the data in memory. There are flags you can set that choose your certificate needed by the connection
automatically, however with security configurations you're best following the advice I give most everyone when building entries:

The best way I've found over the years to build a connection when you don't know which flags to set is to build the connection using the Windows interface, verify the connection works correctly, and open it in a RasPhoneBook and inspect the settings that
Windows has chosen.