OCS 2007 R2 moving global settings to Configuration container

I have read all the documentation on whether this is necessary or not to move the global settings when you move to OCS 2007 R2.  My organization is small, and I'm not too worried about it, but I was thinking I should do it just because it seems to be best practice.  However, my question is if I don't do it then will it affect future releases of OCS?  Or in the next release of OCS will it put the global settings where they should be and not require me to manually do it?  I'd just like to upgrade right now from OCS 2007 to 2007 R2, not bother with the moving global settings, and when the next release comes out it won't matter anyway.  
Who is Participating?
Jeff_SchertzConnect With a Mentor Commented:
In CS14 the majority of the global settings are actually stored in the SQL configuration database used by the new Management Server role, so it does not matter which AD location you select for previous versions.

In your case I would recommend leaving the configuration settings where they are and simply deploying R2.  Especially if you have a single AD site, or have a root domain controller available in every AD site, then it really doesn't matter.
jpletcher1Author Commented:
Thanks, that is what I was hoping to hear.  I guess it's not a horrible process to move the global settings in OCS 2007, but I just didn't want to chance something going wrong if I really didn't need to.  I'm guessing the majority of smaller installs don't need to bother with this then.  My main and only concern was if it would affect future releases or not, so with that said, thanks for the info.  That was exactly what I was looking for.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.