Follow this one at your own risk, it hasn’t been thoroughly tested other than testing the fact the storefront site has actually been ‘removed’ so the end user is prompted to install / log in again.
Scenario: Client upgrading from 1.2 storefront, wanted to change names or url, store and cert. Wanted 2.1 storefront. Didnt want to upgrade or migrate.
Solution: We installed a separate 2.1 storefront server, configured it accordingly. Published the site, tested the site, then change the _citrixreceiver SRV record so the end users could enter their EMAIL address in the receiver login page. The existing store would still exist and duplicate icons would show and various other pain occurred unless the end users removed the original storefront store.
This could be manually done from the receiver or alternatively we ran a GPO on a per user basis (run once) to delete the following keys (we only had one site – so it didnt matter if we wiped the whole key/store)
This cleared the remembered store entries on the local W7 host and the users were prompted to type in their email details to connect to the storefront again – only this time because the _srv record was updated they connected to the new site.
Clunky, but so far it has worked, everytime.
Im sure there are plenty of other better ways of doing this, please do let me know if you have any advice / ideas ! We also tried the receiver clean up utility, which completely removes the receiver but somehow managed to leave some of the start menu shortcuts behind and didnt run for every user correctly..