During a recent upgrade of an ActiveRoles environment from version 6.1 to 6.5 I encountered an issue that I thought would be worth sharing. The environment had the OCS/LCS support pack version 1.1.1 installed from the 6.1 Source Media which was being used to manage LCS2005 users through the web interface. An assumption was made that the OCS support pack v2.0 included on the 6.5 media would continue to support LCS2005 – after all, v1.1.1 was called Support Pack for LCS/OCS so why not right? Wrong. OCS Support Pack 2.0 removes LCS2005 support. A broad assumption seemed to have been made by Quest that anyone deploying ARS 6.5 had already moved to OCS.
It’s important to point out that while I say this was an ‘upgrade’, it was not performed in place on an existing database. We created a side by side installation of 6.1 and 6.5. The reason for this was to start with some clean Databases to hopefully clear out some performance issues. Had we upgraded the existing ARS Database, perhaps compatibility may have been there, but I suspect not or not in a supported fashion at least.
We did of course log an incident with Quest Support, who confirmed that LCS 2005 was no longer supported, but to their credit are working on producing a public fix, which should be available in the coming weeks.
Removing this support did cause us some momentary issues as we were trying to come up with a workaround to continue allowing our IT teams to manage LCS users through the web interface. This led to a fair amount of time being lost, but it’s great for Quest to realise the impact to the customer and move to resolve this quickly and in a publicly available fix. So credit to them.
I will post details of the fix when available as it may benefit others who are either looking to make the same move from 6.1 to 6.5 or who have a 6.5 environment currently without LCS Management functionality. Of course, 6.7 is the latest and current version but not everyone has their environment there quite yet!