I've opened a case through the self-service site, but thought I'd ask for some opinions/input here. I'm currently upgrading from 8.6 to 8.7 SP4, we have 2 cores, one for corporate and one for the data center. Patches download to corporate core and the data center core gets it's patches from the corporate core. In order to get this configuration to work, the consultant who did the original set up installed LANDesk on the C:\ drive of the data center core, then, for reasons unknown to me, he put a copy of the entire LDLogon share folder on the D:\ drive and moved all the share rights to that ldlogon folder, instead of leaving the ldlogon share in place C:\ with the rest of the LANDesk folder/file structure and simply moving only the patches folder to D:\ .

I upgraded my test core and the corporate core with no problems, but this data center core configuration (described above) is producing problems with the upgrade installation. At the end of the LDMS upgrade, after the reboot, a message pops up that "the agent configuration INI file could not be created". The upgrade installation moved the share rights to the original ldlogon folder on C:\ and the share permissions are gone from the "old" ldlogon folder on the D:\ drive. I'm assuming this error message is due to the way the consultant customized the data center core's installation originally, but I'm at a loss with regard on how to fix it. I was vainly hoping that it would be something I could manually fix after applying SP4 and the mini-rollup, but SP4 hangs and eventually produces an error, "This operation returned an error because the timeout period expired. (0x000005B4) CreateClientConfiguration.exe /rebuild,6000". When I cancelled out of the SP4 install, there was again the "the agent configuration INI file could not be created" messages hiding behind the SP4 installation screen.

Soooo..., I'm assuming at this point that I cannot successfully upgrade this core without "fixing" this dorky LDLogon share configuration first (I have a backup image of the core made just prior to the upgrade attempt), but thought I'd ask if there might be anything I can do to remediate the issue in lieu of restoring my backup image, fixing the LDlogon share config and starting all over with the upgrade.

If I start completely over and move the LDlogon share back to C:\ prior to running the upgrade, do I simply copy all of the files from what had been the "working" D:\LDlogon share into the LDlogon share folder on C:\ that wasn't previously being used? Also, if I have to start over, should I have the SQL database restored to it's pre-8.7 upgrade state?

Thanks, Connie K.