Search the Community

Running 1610, I stumbled across something yesterday, and I'm wondering if anyone else has seen this: changing just the name of a query used to populate a collection breaks the collection. Steps to replicate: Change the name of the query being used as a membership rule for a collection. Collection's icon gets an hourglass, even though nothing about its membership actually changed. Hourglass doesn't go away, and collection membership no longer updates. The first time I saw this was with a query-based collection looking for %server% in operatingSystemNameAndVersion. Even after adding new devices to the environment and waiting overnight, those devices didn't get pulled into the collection this morning, even though delta was enabled so they should've been picked up within minutes. "Fixed" it by deleting and re-creating the collection. I have another, separate 1610 environment I work with regularly, so I jumped over to that one and created a new query-based collection to test with, looking for %string% in the system's name. Changed the name of the query, and sure enough, the collection's hourglass refused to go away (only left this one for 15 minutes, not overnight). Changing the actual query to %string2% seems to have gotten the collection working again, though obviously isn't really a fix, since string and string2 are different; just need to change back to the original string. Back to the initial environment, with a collection looking for system name ending with a number and a specific service existing and being set to auto-start: change the name of the query, and the hourglass has been stuck for 30 minutes. Changing the query in some non-meaningful way (adding a second space character after an "and") doesn't help. Changing the query in a meaningful way (look for a different service name) gets the collection working again. So it doesn't seem to matter what the query is looking for - three queries looking for three different things (though second and third are similar) and all of them break the collection if just the query name is change without changing the query itself.

i have a simple name query (System.Name is like "clma06v%) i'm running it agains all systems and the query returns 9 clients, but if i go to all systems and search for clma06v it returns all 24. this seems to be happening on my other queries also. i'm running sccm 2012 r2

Anyone know of an easy way to name a computer to its serial number during OSD? I have a vbs script that I used under Altiris but how/where would I inject this script during OSD?

I have two TS, one for known computers with allready installed the agent (migrate compname is on) and another for unknown computers, on this one you need to fill in the computer name during WinPE. This method works fine for Win 7 and Vista. On XP there is a problem: We work with a full operating installer in combination with an unattend.txt For allready known and unknown computers the compputername is forgotten and a dynamic name is given. How do i fix this? Please advise.

Hey guys, I work for a school district with 13 campuses. We have a naming scheme that we use which is as follows: CAMPUS-SERIALNUM-T or -S The T designating a teacher machine and the -S designating a student machine. I have scripts that will name them correctly. What would be the easiest way to accomplish getting these named correctly during a mass imaging? Separate TS's for each campus? Separate Packages on the back end? Looking for your ideas. Thanks, Todd

Hi everyone, Well, I've been a member of this forum for a short period of time, and I've asked way too many questions and gotten some good feedback from here and around the SCCM community. So, it's time for me to give back to the SCCM community. I modified a script that prompts for computer name as an OSD task is being performed. I've tested this script on a SCCM 2012 Beta 2 lab, and it's been working properly so far. Here's the link that explains how the script works as well as it shows the original owner and my modifications.