Transfer of a thick bank client of the BSS incl. on windows 7 x64

Good afternoon, today I spent a lot of time on transferring the bank to a client of one of the banks, “going on the cutting edge of progress” - I will not call it. This bank uses a very common “thick” BSS bank client. It was written in Delphi in ancient times. A tech support employee having heard the words “Windows 7 x64” from me said that the transfer is impossible. However, I got it, and I am ready to share a brief instruction on the transfer. Sorry without screenshots.

So, the first thing is to escape. We will need:

• The folder in which the KB is installed, well, and most likely to remember the path - because in the target system, it would be desirable to deploy the KB along the same path.
• User keys. Do not forget to save not only certificates, but also private keys. If the keys in the registry - in this article, I described how to transfer them
• Database KB. It usually lies in %Programm Files%/Microsoft SQL Server/%%/Data The name can be SQL.1 or BSS *** or something else, in KB of different banks in different ways, we are also interested in BSS files *** ******************* and BSS ********************* _ log from the Data folder - we backup them

Next, go to the target system.

• We install the KB, as for the first time, as I said before, preferably along the same path that the KB was in the old system, we create an alias of the database, at the stage of issuing access rights to the keys (plates with DBA SYSDBA OPERATOR, etc.) The setup will be cursing. the technological key has been rotten for a long time - this is normal, click on cancellation (or “No” - I don’t already remember exactly how he cursed). All we were told that the KB is installed.
• Import the keys to the new system, install the certificates in the Personal store
• Go along the path %Programm Files%/Microsoft SQL Server/%%/Data , remember the name of the newly created database (BSS **********************), and rename the files BSS ********************* and BSS ********************* _ log, in their place we put the corresponding files from backup, renaming them with a fresh name (for example, if on the source system the alias was called BSSGPB201112345, and the new alias on the target system is BSS *** 30136201859> _BSS *** 30136201859 BSSGPB201112345> * 30136201859)
• We go to the transport settings, and re-register client certificates there, different transports are used in different banks, basically there are two types - either a small window hangs in the lower right part of the screen - there you have to click “Settings”, and then on the last tab choose the path to the open key (certificate in% bssroot% / subsys / keys / open / 00000000 / *. cer), and in the lower part of the window click “Browse” and select the correct key, in another case (when there is no small window in the lower right part of the screen) go to the% bssroot% / subsys / icl / icltransportsystem / folder and launch “Settings .bat »continue as previously described.

That's all, KB should work, with old keys, with an old history of extracts and without going to the bank.