That is true but we are commited to SCCM 2012 for the near future. I believe this is an issue with the civil install even without SCCM in the equation.
On a repair of Civil 2012 and 2013 it uninstalls the content pack. I am fixing for both manual install and SCCM install.
They made it even harder by moving the content pack to its own MSI.
But yeah I hate 2012 and I think we might even be looking at other deployment solutions but that is a decision way higher than me.
This has been a known issue dating back to ver 2009 or earlier. See link below for help
This thread has several issues resolved related to your problem.
Hope it helps.
Hi John, it's a known issue indeed but all the fixes offered in various topic just dont'work. I hope it's fixed in the 2014 release but don't have high hopes on that.
NJDodd, I assume you still haven't fixed it either have you?
Access a broad range of knowledge to help get the most out of your products and services.