OPEN

Google Adwords Editor 9.7.1 and 9.8.1 and 9.9.0 again has been released with major design flaws, see Developers best practice for Windows user profiles. It saves itself, including Adwords data in Windows folder structures that are getting lost on a user logout. Additional to this, there is no way to redirect the data folder to a Roaming Profile folder like it's possible with Google Chrome.

The fundamental broken Windows basics are:

• Roaming Profiles are not supported
  • As result - all data and the application itself get's lost if you log off from the computer.
  • This happens for the reason that the Application is installed to LocalAppDataFolder, what is a folder that is per definition a folder that is excluded from roaming.
• Application is not installed for All Users
  • This is at least wrong design as Adwords should be used by 98% in Enterprises and not at home. The application need to be deployable per machine to be Enterprise ready.

How to workaround some of the issues?

You may have just upgraded from Simpana 8.x to Simpana 9 SP2 or later and installed the Exchange DA Client on your Windows 7 client (x64) or Windows XP. Outlook is x86 version and Simpana 9.x Outlook Addin (MSI).

The Commvault documentation Install Using AD Group Policies just tell you in the last sentence that you need permission to Galaxy.Ex2KMBDM.CVEAAddin key. That sounds like a bad joke as it does not explain that you cannot set this value with a GPO together with the installation GPO and also not with two GPOs ordered one after the other (what Support suggested). The setup removes all it's registry keys and reinstall them later (also on updates over existing versions). To apply the permissons on the registry keys and folder you need to reboot the machine after the setup has been completed. But the setup does not reboot itself as there have been no files in use that require a reboot. Now, try to explain this reboot requirements to a few hundred users...

If you are installing a CommCell Console GUI on your Administrator PC it normally download and installs all patches from the CommCell Server to the client. You do not need to do anything manually, but with this bug these feature is more or less broken.

Symptoms:

• CommCell Console GUI before 8.x SP4 is not installing patches on Windows XP at all.
• CommCell Console GUI with 8.x SP4 installed fails to upgrade to SP5.
• CommCell Console GUI starts up and update dialog is shown. After you press Yes for installing the patches, nothing at all happens and patches are not installed.

Reason:

• Proper UAC (User Account Controll) logic implementation seems missing for Windows Vista and Windows 7 in Simpana 8.x and 9.x. By Microsoft certification rules the product is therefore not certified for Vista / Windows 7.
• Auto-Upgrade often fails to install other required patches

Workarounds:

This issue describes symptoms that occur for ages with HP Data Protector and that may become a critical issue for your if you don't see them. There will be no notification from DP at all if this happens. The main cause of these bugs seems to be very unreliable internally error handling process in Data Protector. I personally see this for many years now and nothing get's really better over time in these product if you don't stress your bugs.

Symptoms:

• Job is running and cannot killed. You can try to kill it 1000 times and you can wait days for the kill, but it never get's killed.
• Planned backup jobs with same job name are not running any longer as DP is waiting for the hanging job to finish.
• Restarting all Data Protector services will not kill a job.

How to identify: