Ideas for new discussion groups

So - something didn't or doesn't work as expected. You think you have to remediate the problem immediately - no time looking for the cause. You do it on your own or you call support and they suggest a course of action. It might or might not work. Only then you realise that you've not only wiped out (almost) all forensic evidence but also can't recreate the situation. Embarrassing?

Let me give you two examples:

1) When migrating to SEC 4.0 I started a remote console after the installation on the server had finished (I had logged off from the server as is always required but did not immediately login again). The library migration had (not unexpectedly) failed and the console presented me a pop-up which I clicked away expecting I could call it up again any time later. When I logged in to the server, opened the Console and did not find the "Retry migration" option it began to dawn on me that I'd dismissed the pop-up for good. Well - see above for the rest.

2) While beta testing SEC 4 I managed to cripple autoupdate on a server . Neither me nor support gave any consideration to the fact that AU reported looking in vain for the CID for SAVNT. After quite some un-, de-, reinstall, installer cleanup activity and registry hacking the problem was eventually resolved. Last weekend I forced an unmanaged notebook to update from the webCID, it installed SAV9 but then - the red x! Guess you already reckon what I found in the update log. It didn't occur to me that I had already seen this and so I concentrated on resolving the problem instead of collecting the logs.

I assume that one or the other has had similar "experiences" and therefore I suggest a place for "occurrences, encounters and chimaeras".

Christian

So - something didn't or doesn't work as expected. You think you have to remediate the problem immediately - no time looking for the cause. You do it on your own or you call support and they suggest a course of action. It might or might not work. Only then you realise that you've not only wiped out (almost) all forensic evidence but also can't recreate the situation. Embarrassing?

Let me give you two examples:

1) When migrating to SEC 4.0 I started a remote console after the installation on the server had finished (I had logged off from the server as is always required but did not immediately login again). The library migration had (not unexpectedly) failed and the console presented me a pop-up which I clicked away expecting I could call it up again any time later. When I logged in to the server, opened the Console and did not find the "Retry migration" option it began to dawn on me that I'd dismissed the pop-up for good. Well - see above for the rest.

2) While beta testing SEC 4 I managed to cripple autoupdate on a server . Neither me nor support gave any consideration to the fact that AU reported looking in vain for the CID for SAVNT. After quite some un-, de-, reinstall, installer cleanup activity and registry hacking the problem was eventually resolved. Last weekend I forced an unmanaged notebook to update from the webCID, it installed SAV9 but then - the red x! Guess you already reckon what I found in the update log. It didn't occur to me that I had already seen this and so I concentrated on resolving the problem instead of collecting the logs.

I assume that one or the other has had similar "experiences" and therefore I suggest a place for "occurrences, encounters and chimaeras".

Christian