Bug

Google Adwords Editor 9.7.1 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?

If you'd like to deploy VMware Player in your Enterprise you need to extract the MSI setup from the standard setup. You need to download the normal VMware-player-4.0.1-528992.exe file from VMware site. Than just launch these installer .exe, wait until the setup shows the "Welcome to the installation wizard for VMware Player", but don't install the Player. While the setup is launched setup creates a folder in C:\Users\%username%\AppData\Local\Temp\vmware_[random number]. Make a copy of this folder to your distribution share. Cancel the launched setup. Now you have the required MSI file vmware player.msi in the copied folder.

If you try to deploy VMware Player 4.0.0-471780 or 4.0.1-528992 to your Desktops via Active Directory you will expierence some major difficulties. At very first it's not possible to install at all. After some investigation it looks like very many others reported this bug in the VMware Community Forums, but nobody came up with a solution.

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 9.x SP3 is not installing patches at all.
• 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:

• Upgrade logs complain about some missing dependencies that are not fullfilled. Looks like the patch references table on CommCell is broken again and missing required references.

Solution:

• Upgrade your CommCell from SP3 to SP3a

History:

If you are running Simpana 9.0 SP2a and you backup Windows 2003 servers they are no longer backed up after you have installed SP2a. There is no notice or warning at all. You will not get an email if the job has failed to backup your data. Hopefully you have no data loss before you came aware of this bug...

Symtoms:

• Windows 2003 machines are not backed up. Windows 2008 or Windows R2 is not affected.
• Alert system does not notify you about the data backup failure.
• It does not matter if you use VSS or not.
• It does not matter if you have selected some files or all files for backup.
• Only the Commvault Jobs folder and SystemState is backed up.

Solution:

• Rollback to SP2 (without A).
  • Execute C:\Programme\CommVault\Simpana\Base\RemoveUpdates.exe
    • Select a Rollback date before you installed SP2a
    • Select Remove Binary Updates
• Install SP2b and critical hotfix WinX64_9.0.0B84_ScanNotPickingFilesNonEngWinOS(36229).exe listed on the download page.

History:

Commvault has an Exchange public folder archiver and you are running it to get your public folder store size reduced.

If you are running Simpana 8.0 you should be aware that all written public Commvault documentation has told by fault that Exchange 2010 is suppported, but it wasn't. This wrong documenation was public until Oktober 2010 and has been removed in a "cloak-and-dagger operation" with my support call. We banged on this migration wall while moving from Exchange 2003 to 2010 and have been made by Commvault to wait for Simpana 9.0 SP1 that came available in mid January 2011. Because of so many bugs in the product we have been made waiting until mid May 2011 (SP2). You may be working with Exchange 2010 since November 2009 and you may have just waited for Exchange 2010 SP1 that has been released in June 2010 to get a more stable Exchange 2010 and to finish migration.

You have just upgraded to Simpana 9 SP2 or earlier and installed the Exchange_DM_Client on your Windows 7 client (x64) or Windows XP. Outlook is x86 version and Simpana 9 Outlook Addin is 9.0.84.0 (MSI date is 08/05/2011).

Symtoms:

If you's like to install software via Active Directory it may fail with Error: %%1274.

Symtoms:

• You can reboot as often as you'd like and your deployed Software always fails with Error %%1274
• Eventlog entry:
  • Source: Application Management Group Policy
  • Event ID 101
  • Description: Die Zuweisung der Anwendung ShoreTel Communicator 16.23.5631.0 der Richtlinie ShoreTel Communicator ist fehlgeschlagen. Fehler: %%1274
  • Description: The assignment of application ShoreTel Communicator 16.23.5631.0 from policy ShoreTel Communicator failed. The error was : %%1274

Workaround:

• Explicitly set the policy Startup policy processing wait time: Activated Amount of time to wait (in seconds): 120s. This is normally not required if FastLogonOptimization is disabled, but Windows 7 seems to have a bug here.

History:

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:

Mid January 2011 we found a bug in Commvault's Exchange Public Folder Archiver. This bug prevented us from restoring items that have been archived in past. It was a bit random, but my feeling was it is related to mails with attachments. As always supposed, it was not an issue of the MAPI connection configuration or other issues on our side. This is a Commvault bug and nothing else.

Required:

• Commvault Simpana 8.x
• Commvault Simpana 9.x

Symtoms:

• Archived public folder items cannot restored.
• Mails with attachments have mostly failed.
• User received very unspecific error message from Commvault Archiver Add-on in Outlook.

Solution: