The bug is easy: the sg_logo.gif file is missing from the installer (which means you get an ugly 'image placeholder' at the head of your http://<servername>/Vaultservice/ page). Its also easy to fix: just copy the sg_logo.gif from the prior installation.
The annoying 'gotcha' is a bit more subtle. We use AD-authentication for our VAULT so we have the web user impersonating an AD user so that the AD-lookups can be peformed by the webservices to authenticate our users. This works great (and thanks again for even offerting this capability -- I can't tell you how many toolsets out there run 'on windows' but fail to take advantage of just about any windows infrastructure other than IIS as the webserver!).
In past installs, after you selected to use 'custom impersonation', the installer would provide a UI within which you had to provide the username and password of the domain user to impersonate. This always seemed annoying to me to have to provide during each upgrade, since of course the needed creds were already in the existing web.config file of the vault instance being upgraded.
In the 4.1 installer, I was pleasantly surprised to see that this had (apparently) been rectified. After selecting 'custom impersonation', the subsequent dialog box did offer me the option of providing username/password creds, but this time instead of these textboxes being empty they were instead already populated with the proper values from my existing web.config. Hallelujah, I thought -- I don't have to keep entering this when I upgrade.
Sadly, this feature seems only partially-implemented in the 4.1 installer.
The value in the textbox for username correctly displayed <domain>\<username> as parsed back out of my web.config. But the textbox for the password displayed ******** as all good password textboxes have been trained since birth to do
When I saw the proper <domain>\<username> value in the username textbox and I saw that the password textbox was already showing ******, I just clicked NEXT > to the next page of the installer.
The results I got in my newly-installed web.config were not as expected...the relevant line did properly list the correct value for the <domain>\<username> user, but the password value was set to "" (empty string).
Obvioulsy it was trivial for me to correct the problem by entering the right password into the node in the web.config and I'm off to the races, but I wanted to point this out and recommend that you correct it. I am guessing (but haven't tested) that if I were to have followed the [...] button to actually select a user and enter an actual password (as was always the case in prior upgrades) that this would have worked correctly, but I think there is definitely a bug in the path thru the installer that pre-populates this dialog with existing values from the web.config. They are being properly populated but whatever variable is supposed to be set after the user enters something into that text field isn't being set if the installer pre-populates it and the user never actually changes the pre-populated value.
Again, problem easy to correct on my end, but maybe you want to look into it for any subsequent releases.
Otherwise I love the VAULT product (and have for a number of years)...keep up the great work~!
-Steve B.