Forum Discussion
Difference between ".com" and the ".com/sites/" site collections
Your first line of (1.) is what i'm hoping.
Something in the back of my head tells me that once the Pub.Inf is switched on, there are residual bit's left behind even if turned off.
Thanks for your contribution.
Removing/recreating the rootsitecollection will cause problems as a few things are done for the whole environment. I would prefer to disable the features that are activated. by comparing a new sitecollection to the root sitecollection. After that i would suggest to look at the libraries so you can remove the libraries that are overhead. Hope this helps
Hi Deleted
I agree.
I do not intend on removing the .com site, but i'm trying to find out the things it does for the whole environment. Once I know the relationship between .com and .com/sites/xyz i will be in a better position to assess the risks of the actions so far.
The second part of this is that even once I've deactivated the features, are there any bit's and pieces remain? I know this sounds odd, but i have a vague recollection that some functionality at the .com level, once activated, will have an effect even if deactivated.
I'm hoping that i can find a conclusive answer....... even though MS changes things so often.
Regards.
Deleted wrote:
Removing/recreating the rootsitecollection will cause problems as a few things are done for the whole environment. I would prefer to disable the features that are activated. by comparing a new sitecollection to the root sitecollection. After that i would suggest to look at the libraries so you can remove the libraries that are overhead. Hope this helps
There are definitely hidden lists in the root site collection that are needed and if damage/deleted will require intervention by MS Support to get fixed. One example is the list for the Feature Links on the home page of the root site. Last time I had a problem with this, i determined that they were undocumented.
Bottom line, there is lots going on under the covers in the root collection that the tenant depends on.
Yeah, that's what i thought, and this is my concern.... what has my predecessor done in the .com?
I'll need come up with a strategy!
Thanks.
Some features only generate a library disabling will only disable the feature but will not remove te library
a sites/site or Com should have the same libraries etc. Only in the hidden part has the com site more options.
