04-06-2010 12:28 AM
Solved! Go to Solution.
04-06-2010 05:37 AM
To set up IIS to use HTTPS you can use the following:
http://support.microsoft.com/kb/324069
Do not forget to create the SSL certificates needed to stop any IE warnings regarding security
http://support.microsoft.com/kb/299875
Once this has been set up, you will need to enable the https option in the site properties, synchronize all the users and then use RestoreShortcutBody registry key to change the URLs from http to https.... note though that this will take some time depending on how many users and shortcuts there are to process as well as retrieving the DVS files from storage
http://seer.entsupport.symantec.com/docs/282855.htm
Note that because it is updating and changing every shortcut message, it can cause the Exchange transaction logs to grow exponentially, and if it gets interrupted (say for backup mode) when it restarts it will start from the beginning and update shortcuts , regardless if they've previously been updated.
What i would suggest is doing a Run Now using Shortcut Processing against a select number of users in batches, then removing the key during regular archive runs
because if you have the restoreshortcutbody your archiving throughput will be minimal
04-06-2010 03:46 AM
04-06-2010 05:24 AM
04-06-2010 05:37 AM
To set up IIS to use HTTPS you can use the following:
http://support.microsoft.com/kb/324069
Do not forget to create the SSL certificates needed to stop any IE warnings regarding security
http://support.microsoft.com/kb/299875
Once this has been set up, you will need to enable the https option in the site properties, synchronize all the users and then use RestoreShortcutBody registry key to change the URLs from http to https.... note though that this will take some time depending on how many users and shortcuts there are to process as well as retrieving the DVS files from storage
http://seer.entsupport.symantec.com/docs/282855.htm
Note that because it is updating and changing every shortcut message, it can cause the Exchange transaction logs to grow exponentially, and if it gets interrupted (say for backup mode) when it restarts it will start from the beginning and update shortcuts , regardless if they've previously been updated.
What i would suggest is doing a Run Now using Shortcut Processing against a select number of users in batches, then removing the key during regular archive runs
because if you have the restoreshortcutbody your archiving throughput will be minimal
04-08-2010 04:43 AM
Firstly, thanks a lot for your attention .... your suggestions was so helpful.
Change HTTP to HTTPS passed successfully
Thanks again,
04-08-2010 05:14 AM