ClickOnce and Expiring Keys

[=?Utf-8?B?cmFuZHkxMjAw?=]

I'm using VS2005 and .NET 2.0.

I have a simple WinForm app that uses ClickOnce deployment, and it works
great. The strong name key file (pfx), which was generated by simply going to
Properties -Signing tab, and checking "Sign the assembly" is approaching
the expiration date. Unfortunately, I don't have the password for this pfx
file.

If I just add a new pfx file, the program compiles and runs locally. If I
deploy to my clients, the new version will not run (no surprise). If I go to
the client and Remove the previous version, the new version suddenly runs
just fine.

I'd really like to avoid having to go to each client and uninstall the
original version manually. Does anyone have a pointer on how to get ClickOnce
to Remove the previous version?

Is there any way to "Renew" a strong name key file (pfx)? Again, my original
pfx file is expiring.

Thanks,
--
Randy