SCCM 2007 - Collections

Guy's
I was created all systems collection but suddenly it's showing very less number of system but AD for that OU showing correct count only
For example : India OU - 1200 systems - In SCCM Server India-All-System Collection showing 450 only
why this devation ?
Please help me anyone
Best Regard's Krishna

Hi,
Did all OU clients show up in the default All Systems collection now?
And colleval.log on the site server records details about when collections are created, changed, and deleted by the Collection Evaluator. You could have a look.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

MOF file migration from SCCM 2007 to SCCM 2012

Hi,
I have an issue while migrating SCCM 2007 MOF (Configuration.mof) to SCCM 2012,Problem is...
In our infrastructure, We have integrated our custom inventory classes with the logon script.Now we are migrating to SCCM 2012.When i migrate the same Custom inventory classes to SCCM 2012,I can able to compile/migrate, However SCCM 2012 views are not in
sync with SCCM 2007.
Example: If i use SCCM 2007 collection/Query in SCCM 2012 that uses these custom inventory classes, its thrown an error saying that objects in this query are not valid, because of this none of the collections/Queries that uses old inventory classes are not
working.
I dont want to change anything in the logon script...
Can someone please help me on this.Thanks in advance..
srkr

Hi Garth,
Thanks for the reply.
As per my understand,there's nothing to do with SMS_DEF.mof and only Configuration.mof can be editable.
When you say Importing sms_def.mof in SCCM 2012,I guess there's is something i missed out.
Below is the both SMS_DEF.mof and Configuration.mof from SCCM 2007, Also please let me know how to import SMS_DEF.mof in SCCM 2012
************SMS_DEF.MOF*********************
//-- SCCM Report: XXX_AD_Info
[SMS_Report(TRUE),
SMS_Group_Name("XXX AD Info"),
ResID(6200),
ResDLL("SMS_RXPL.dll"),
SMS_Class_ID("XXX|EDADInfo|5.0")]
class XXX_AD_Info
[SMS_Report(TRUE), key]
string KeyName;
[SMS_Report(TRUE)]
string Distinguished_Name;
[SMS_Report(TRUE)]
string AD_Site;
[SMS_Report(TRUE)]
string DCName;
[SMS_Report(TRUE)]
string MachineDomain;
*********Configuration.mof*******************
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
class XXX_AD_Info
[key]
string KeyName;
string Distinguished_Name;
string AD_Site;
string DCName;
string MachineDomain;
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
instance of XXX_AD_Info
KeyName = "XXX AD Info";
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Distinguished-Name"), Dynamic, Provider("RegPropProv")]
Distinguished_Name;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Site-Name"), Dynamic, Provider("RegPropProv")]
AD_Site;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|DCName"), Dynamic, Provider("RegPropProv")]
DCName;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|MachineDomain"), Dynamic, Provider("RegPropProv")]
MachineDomain;
srkr

Collection in SCCM 2012 of SCCM 2007 clients?

Hi,
I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
Can that be done?
I guess queries can only be run on what sccm 2012 client return on info (I tried a simple query: configuraiton manager client state - version but it only return versions 5.x).
Pls advise.
J
Jan Hoedt

I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
Can that be done?
Can't you just add the column '(client) version' in the console? Are they displayed then? (Also keep in mind that it's theoretically not possible that CM07 clients can be assigned to a CM12 site)
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2007 R2 - configuration item compliance for a collection.

Hi All,
Can some one share the information of reports for configuration item compliance of for a collection in SCCM 2007 R2 using desired configuration management feature.
Rgs,

Yes, but no data shows up.
What does this mean? What troubleshooting have you done? When do you create the DCM?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 - All clients from primary site have vanished from central site collections

Hi all,
we have a SCCM 2007 R2 setup with one central site, one Primary Site (A) with a secondary site hanging off it and another Primary Site (B). Suddenly all the clients from the Primary Site A (and also it's Secondary Site) have vanished from the central
site. All the clients are still present when we check Collections from the admin console on Primary Site A site server - they have simply disappeared when we check Collections from the Central Site admin console.
Can anyone provide any info on a good starting point for troubleshooting this issue? As a sidenote, we can still push packages out to the Primary Site A distribution point and both the Primary and Central site can communicate/ping each other.
Any help/info would be much appreciated!
Thanks

Check the
site replication on central site, is that SQL is working fine, and also see the
inbox folder in central site, might be there is backlog and those DDR files are
not processing, and after maintenance they got deleted.<o:p></o:p>
please run
the heartbeat discovery by hour or day, and once the clients will sent all the
DDR files then they will appears again.<o:p></o:p>
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

How to perform a query to read an xml file in SCCM 2007

Good,
I need read knows how to read an csv file for a specific column after collecting the results, then put the PC's in a collection in particular.
A greeting and thanks

Good,
What I want to do is create a query that examine a csv that is on a server. And after consideration and select the column that I am interested
in(Name pc) be able to engage these data to a collection, clear is if it can be done in SCCM 2007
A greeting and thanks

Can I use SCCM 2007 to deploy SCCM 2012 Agent

I was reading the scenarios for deploying the SCCM 2012 agent here
http://technet.microsoft.com/en-us/library/gg682132.aspx
I have been planning to deploy the 2012 agent using an SCCM 2007 deployment package. I am not migrating any data/packages/collections/anything from SCCM 2007.
I am looking for a sane way to deploy 2000ish clients a day for 2 weeks and be done.
I figure they are all SCCM 2007 clients so lets deploy 2012 agent using SCCM 2007.
I read the following in the link above and it sounds like the way I want to go – use SCCM 2007 software distribution…
Upgrade installation by using application management
Upgrades clients to a newer version by using Configuration Manager application management. You can also use Configuration Manager 2007 software
distribution to upgrade clients to System Center 2012 Configuration Manager.
Then later in the same document there is this…
How to Upgrade Configuration Manager Clients by Using a Package and Program
You can use Configuration Manager to create and deploy a package and program that upgrades the client software for selected computers in your hierarchy. A package definition file
is supplied with Configuration Manager that populates the package properties with typically used values. You can customize the behavior of the client installation by specifying additional command line properties.
You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client.
What???!?? There is no Automatic client upgrade feature in 2007 – so how does that even make sense? In one section, it says I can deploy the 2012 Agent using SCCM 2007 software distribution, and then later in the same document, it
says I can't. I am probably misunderstanding somthing.
Is it possible to make a package/program in SCCM 2007 that will make targeted clients upgrade to Agent 2012 and join the new SCCM 2012 Site?

I tested this (deploying 2012 agent using existing 2007 SCCM infrastructure) with a few test systems at my desk and it seems to work pretty smoothly. I made a package to deploy SCCM 2012 SP1 and added it to my SCCM 2007 Site. Then I deployed
the 2012 agent from 2007 and it worked great. If it works this well in production, I will be able to migrate all of my clients in less than a weeks time.
I have not published the 2012 site information in AD - and I don't plan to. We would have some overlapping site boundaries - and in 2012 it seems its unnecessary in a single site hierarchy. I AM planning to use boundaries to assign
DPs, but thankfully site and DP boundaries have been separated. It works great to just specify the site in everything and not worry about auto discovery. My clients don't move among sites since I only have one large site.
Sorry that I somehow posted this same question twice, and thanks for cleaning that up.
In my installation, I just called ccmsetup.exe with the following command line...
/mp:myMP.mydomain.com CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=1000000 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=myMP.mydomain.com SMSSITECODE=CCM
I am not sure that I need to specify the MP twice, but it is working to do so. I'm also not sure whether the log and cache flags will be honored since there are existing settings from SCCM2007 agent. I think that the 2012 install will not change
these settings upon installation, but it does not appear to hurt the process to include them just in case it does work.

Software Distribution & Patching Design Issues - Migration of Packages SCCM 2007 to Application or Conventional Packages in SCCM 2012

Hi All
I am starting in discussion to deep root on Software Distribution & Patching model in large environments from SCCM 2007 migrating to SCCM 2012.
Below are certain assertions i am putting forward for your expert views or you may in a similar situation
1- I have migrated the packages from SCCM 2007 to SCCM 2012 as conventional methods, now i am deploying them [ not migrated the advertisements and collections ], so while deploying i am facing a peculiar situation that the deployment when created is of the
name "<<Package name>>(program)". I am not able to rename the deployment for the conventional packages. is there a way out to that??
2- Will the collection queries work the same in SCCM 2012 as was in SCCM 2007??
3- In SCCM 2012 Primary site there is default role called Site System role in that there is tab for proxy settings. I have observed that if do not check the proxy tab there and punch in proxy IP and port then after some time in the WSUS server the update
source and proxy server tab the proxy option gets unchecked and hence the sync in software update point status appears failed. Is that anyone else also has observed !!!!!
Regards Sushain KApoor

This is a duplicate of
https://social.technet.microsoft.com/Forums/en-US/2ddb8170-529b-4652-830e-fd0ade384b98/software-distribution-patching?forum=configmanagermigration
Please do not double post.
Jason | http://blog.configmgrftw.com | @jasonsandys

OSD: SCCM 2012 collection which should exclude Windows 7 clients (query not working fine)

Hi,
We have an SCCM 2012 collection to which we deploy Windows 7.
Vista clients get a SCCM 2012 client in SCCM 2007 and once they have it, they get a Windows 7 deployment.
The group is populated by an AD query and that works fine. However, when we try to exclude Windows 7 machines (query = not Windows NT ... 6.1) the query does not return any result.
Please advise.
J.
Jan Hoedt

Please check your query. It should be like the following.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version != "6.1.7601"
Juke Chou
TechNet Community Support

After Upgraded to SQL 2012 Iam getting several Errors in SCCM 2007

After I upgrade my sql 2008 to sql 2012, I am getting several errors in SCCM 2007.Please find the below screen short
Configmgr reporting service point - Critical
SMS-Collection-Evaluator -critical
SmS-dstribution Manager -Critical
SMS-SRS reporting point -critical
SMS-Discovery Data manager -critical
SMS-Status Manager -critical
SMS policy Manager -critical
How can I resolve this issue.

I updated the path still I have the same problem...several error message found in SCCM server.please find the below one error message
On 7/21/2013 10:51:16 AM, component SMS_DISCOVERY_DATA_MANAGER on computer DCD-SCCM reported: SMS Discovery Data Manager failed to process the discovery data record (DDR) "", because it cannot update the data source.
Possible cause: On a Primary site, it is probably a SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not full.
6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server.
Solution: Make more space available on the site server.
how can I resolve the issue??

SCCM 2007 and Active Directory - On-boarding and Off-Boarding Process

Currently, when a user resigns from our company, we rebuild their computer immediately and provide to another user.
From a best practice perspective, should we delete the computername from AD and then rebuild and join to the Domain? We also have SCCM 2007 in place. Are there other best practices for SCCM 2007 and AD that we should be following for on-boarding
and off-boarding users? Any suggestions would be greatly appreciated. :-)

With respect to AD, it will be better to reset the account rather than deleting it. This way the SID is retained and all permissions (for DNS records etc) and AD group memberships will be retained. AD group memberships will be more significant, depending
on whether it is used for SCCM collection definition rules
In SCCM, if the record is not deleted, it will be identified as a known computer and OSD advertisement can be pushed on the client. Ideally task sequence should use same name as the SCCM resource record for naming the newly built computer. In case AD/SCCM
objects are deleted, duplicate records may get created depending on the timing of client registration and AD system discovery cycle. If SCCM client gets installed and registered before next AD system discovery cycle, there shouldn't be any issues.
But if AD discovery cycle runs before client registration, two records will show up in SCCM console and one will be obselete, which has to be deleted manually. This issue can be resolved by adjusting the frequency and schedule of AD system discovery cycle.
My suggestion will be to reset the computer account in AD and retain the SCCM resource in case of machine rebuild scenarios. In case of task sequence not retaining the computer name, custom steps can be added in TS to set variables as required.

Right Click tools for SCCM 2007 issue

We have SCCM 2007 R2 with Right click tools installed (I know this is not a direct SCCM query but linked to it and thought I might try my luck here)
I use the "ConfigMgr Collection Tools - Add Systems to a collection" option within Right click tools a lot
However in the last few days it keeps failing a lot with the following error message
Line:68
Char: 5
Error: Object required: 'objDialogWindow.document.body'
The Addcoll.hta looks like the following
Line 68: LineobjDialogWindow.document.body.style.fontFamily = "Helvetica"
Line 69: objDialogWindow.document.body.style.fontSize = "11pt"
Line 70: objDialogWindow.document.writeln "<html><body>Adding PCs to " & collName.Value & " </body></html>"
Line 71: objDialogWindow.document.title = "Please wait."
Line 72: objDialogWindow.document.body.style.backgroundColor = "dodgerblue"
Line 73: objDialogWindow.document.body.style.borderStyle = "none"
Line 74: objDialogWindow.document.body.style.marginTop = 15
Line 75: AddToCollection ComputerList.value, CollID.value, ss.Value, objDialogWindow
Line 76: objDialogWindow.Close()
Line 77: self.ResizeTo 400,550
Has anyone had this issue and if so how have you resolved it?

You need to contact the author of the tool and get them to help out. This is not a CM07 issue.
However having said that it look like you are having a problem with the font.
http://www.enhansoft.com/

Bulk loader for SCCM 2012 collections

I am looking for a tool which will add users / computer names as direct membership to collections, Bulk loader was there in SCCM 2007 but it is not working in SCCM 2012. Please suggest..

Hi,
Here is a PowerShell script with GUI for your reference.
Configuration Manager 2012 Direct Membership Collection Manager
http://blogs.msdn.com/b/rslaten/archive/2014/03/10/configuration-manager-direct-membership-collection-manager.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

After migration from sccm 2007, there are many systems with no client installed

Hi Everyone,
We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
There may be some stale systems in AD.
Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

You could also remove the objects without a client and adjust the settings in the
Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 - Collections

Similar Messages

Maybe you are looking for