Hi there,
Currently we run SCCM 2007 r2 supporting roughly 1200 computers.
We use SCCM quite aggressively with a combination of virtual & physical apps along with the usual windows patching etc. I have been tasked with a project to setup application delivery for all apps via AD groups, this totals at over 500 apps.
Which, in itself is not a problem, but I have a big question that is holding me back from starting which I'm looking to find the answer to.
Before I plough on ahead and devote hours upon hours of my time to get this setup and working correctly, another project I am working on is the upgrade to SCCM 2012 r2.
2012 r2 is going to be BAU for us in Feb/March time which isn't far away.
Now I know that when upgrading all the packages and collections will go with it automatically as 2012 is pretty clever as will the memberships as well. However, is the same SQL string used to discover AD groups for collections? IE will it pick-up the AD groups again? Or will I have to go through and redo everything?
Basically, I don't want to end up doing the same work twice for no further gain, I'd rather do it once and be done with it (understandably)
The code being used for AD Discovery is as follows:
"select SMS_R_USERGROUP.ResourceID,SMS_R_USERGROUP.ResourceType,SMS_R_USERGROUP.Name,SMS_R_USERGROUP.UniqueUsergroupName,SMS_R_USERGROUP.WindowsNTDomain from SMS_R_UserGroup where SMS_R_UserGroup.Name = "DOMAIN\\GROUPNAME""
So it discovers the groups fine, happy with that. But when we migrate to 2012 r2 will it pull through the above correctly?and more importantly will it work? What initially raised the question in my mind is that from what I know (or believe to know) is that 2012 uses a different SQL version, so I'm thinking this may cause problems coming from the 2007 setup.
If so I'll steam into this and get it done before 2012 goes live, if not and it will need setting up again, I will hold off.
Thanks for any help in advance, sorry if the above sounds confusing, it's only 9am and I'm still pre-coffee.
Best,
Jake