Save user time zone preferences

My requirement here is pretty standard; I need to allow users to select their current TimeZone and save it against their account. Then I use this value to convert the stored values DateTimeto localized time.

My current thinking is that I will allow users to select .NET TimeZoneInfo.Idfrom the list (stored in the database for a more convenient description, but built with TimeZoneInfo.GetSystemTimeZones()). Then I use this value to return the appropriate TimeZoneInfoinstance using TimeZoneInfo.FindSystemTimeZoneById()and perform the conversion. The main problem that I see here is that it TimeZoneInfo.Idis a value stored in the registry and is not a "standard" identifier (compared to Olson, for example). Thus, it is possible that server updates / migrations can completely invalidate stored identifiers and break down conversions.

In short - is this approach valid / safe? If not, is there a better way to store user time zone preferences, as well as daylight saving time processing, etc. Without a ton of additional logic?