Events broken in RR

For everybody who checks this topic. We found a procedure to alleviate the issue. Please note that Stephen is located in the UK, thus his Core Servers are set for the English UK locale. When installing/upgrading Rapid Recovery, if the user selects the English language, the Core locale may default to English US. (I was not able to reproduce the issue but it surely happen on Stephen's cores; I suspect that it is related to the UK Windows installation media -- but this is an issue for another discussion). In a nutshell, the following steps seem to get the DELL log back in action:

1. Find a suitable maintenance interval for each core, starting with the target cores.
2. Install Chrome and make it the default browser. (Internet Explorer is IMPREDICTABLE with Notifications)
3. Change the locale to English (UK) both on the server and the Core Software (Settings->General->Locale)
4. Disable the core service
5. Stop the core service and the SRM service if you are upgrading a DL appliance
6. Run the script#2 from Dev to remove the unnecessary registry subkeys (shown below -- use with caution, no responsibility taken ...)
7. Remove the HKLM\Software\AppRecovery\Core\Events Registry key (it will be recreated with the default values)
8. Install P-1859 (keep the core service stopped)
9. Restart the eventlog service (& dependencies)
10. Start the core service and the SRM service if you are upgrading a DL appliance
11. Enjoy the fruits of your labor (if any)… 

Powershell Script mentioned above. It removes the EventsService registry key if present (it should be present only for the agents set with individual notifications).

Set-Location -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents
$allAgents = dir | select Name

foreach ($agent in $allAgents)
{
$eventsService = "Registry::" + $agent.Name + "\EventsService"
if (!(Test-Path $eventsService)) {continue}
try {
Remove-Item -Recurse -Path $eventsService
Write ("Removed " + $eventsService)
}
catch {}
}

try {
Remove-Item -Recurse -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Events
}
catch {}

I hope that Stephen will keep us posted how it works for him -- he has quite a few cores to set up...

For everybody who checks this topic. We found a procedure to alleviate the issue. Please note that Stephen is located in the UK, thus his Core Servers are set for the English UK locale. When installing/upgrading Rapid Recovery, if the user selects the English language, the Core locale may default to English US. (I was not able to reproduce the issue but it surely happen on Stephen's cores; I suspect that it is related to the UK Windows installation media -- but this is an issue for another discussion). In a nutshell, the following steps seem to get the DELL log back in action:

1. Find a suitable maintenance interval for each core, starting with the target cores.
2. Install Chrome and make it the default browser. (Internet Explorer is IMPREDICTABLE with Notifications)
3. Change the locale to English (UK) both on the server and the Core Software (Settings->General->Locale)
4. Disable the core service
5. Stop the core service and the SRM service if you are upgrading a DL appliance
6. Run the script#2 from Dev to remove the unnecessary registry subkeys (shown below -- use with caution, no responsibility taken ...)
7. Remove the HKLM\Software\AppRecovery\Core\Events Registry key (it will be recreated with the default values)
8. Install P-1859 (keep the core service stopped)
9. Restart the eventlog service (& dependencies)
10. Start the core service and the SRM service if you are upgrading a DL appliance
11. Enjoy the fruits of your labor (if any)… 

Powershell Script mentioned above. It removes the EventsService registry key if present (it should be present only for the agents set with individual notifications).

Set-Location -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents
$allAgents = dir | select Name

foreach ($agent in $allAgents)
{
$eventsService = "Registry::" + $agent.Name + "\EventsService"
if (!(Test-Path $eventsService)) {continue}
try {
Remove-Item -Recurse -Path $eventsService
Write ("Removed " + $eventsService)
}
catch {}
}

try {
Remove-Item -Recurse -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Events
}
catch {}

I hope that Stephen will keep us posted how it works for him -- he has quite a few cores to set up...