Hi Folks,

We've had a major problem with our rollout of ZCM. It was running fine on one Primary server (an OES2 box running ZCM 10.1.1) and roughly 500 workstations (all XP, with SP2 and 3). We decided to roll it out to our remote sites (35 sties adding 1500 more pc's) each site runs a OES2 box with a xp vm on it running as a satalite. We have also added 2 oes2 VM's acting as Primary servers in headoffice to lighten the load on the first Primary.

6 Days Ago we noticed that no-one could install bundles that were based in the content repro, this included major apps like office and our ress system, all of them had been working before but were now getting "Bundle MSOffice is still being packaged on the server. Please try running later" with a message ID of "BUNDLE.ContentBeingPackaged" All other types of Bundle are unnaffected (like ones using a unc path or a url).

Trawling through the apps, one had the error error Failed to process action: There is an error in cached information for id c7fca8ed44df1000ba19284cbd765282 that is preventing content retrieval Doing a "zman ogp" on that GUID brought nothing back and doing a "zman ogg" on the problem bundle only showed that bundles GUID (a different GUID to the error). We deleted that Bundle first, hoping it was the root of the problem, but that didn't help. Also incrementing Bundle versions doesn't help either.

We have deleted all Bundles that are having trouble installing and recreated them, but now it is really hit and miss if bundles will install or not. Every Workstation has errors on about "Bundle Knowledge Base Files [3.6.A.2.16] is still being packaged on the server. Please try running later." and every new PC that gets imported get additional errors "Bundle Discover Applicable Updates Windows-x86-en-XPsp3 is still being packaged on the server. Please try running later."

Anyone got any bright ideas what I can try next, I've gone grey enough this year, ZCM could be the package that make whats left fall out.

Thaks Guys
Dave