Updated: Remove a computer from a Collection when OSD Task Sequence is completed

This looks like a great workaround and automation piece for OSD with SCCM 2007. However I am finding that i do not have the Task Sequence Manager in my component drop down. Anyone know why this would be?

Thanks,

Eric

I have used your tool…its really very helpful.

I’m using this script on some software deployment collections and it works great. I’m having some issues getting it to work for OSD collections though. If a computer is renamed during the OSD task sequence it doesn’t seem to work. If it keeps the name it works fine. The comments above suggest this should work based on how it does the look up, at least that is how I interpreted it, but doesn’t seem to be the case for me. Pretty much we pull a computer from the box, it gets imported with a simple name and then the task sequence is run which renames the computer. Anyone have any idea what the problem might be? I know the obvious answer is to import with the final name but the goal is to automate as much as possible and remove as many chances for human error as we can.

Nice script and it does work.
However i do have one issue – if i import a system, it than boots through PXE, TS walks throug etc. untill it is finished. I do see the correct event in TS log, but don’t see this script fired up, and there is no event beeing created in system log.. A few minutes later SCCM client on the freshly installed system pick’s up the advertisment and runs the TS again. After the second run the system is removed from collection and the corresponding event entry is created in system log.
I’m kind of curious if it is my SCCM or something else?

Thanks for the script, it’s just what I needed to easily create “permanent” OSD collections where computers can be rejoined if needed to reinstall.

Just one thing.. The script seems to work only randomly. Most of the time it works, but sometimes it just leaves the computer in the collection. Status filter rule creates an event log event like this:

“On 16.9.2011 14:44:26, component Task Sequence Manager on computer reported: The task sequence manager successfully completed execution of the task sequence.”

So, the status filter seems to work like supposed, but the next event logged by the script only appears randomly, even for the same computer in the same collection. Either it just doesn’t run the script at all (unlikely) or the script does not complete successfully.

That seems to occur at least if you just add the computer into the OSD collection by MAC address using “Import computer, single computer” task, do not refresh any collection memberships in the console or the console views and just PXE boot the computer up.

Any ideas why?

Thanks for such a useful script.
It works for me but for the collection that I added the PC to it for Deploy OS. After Installation script remove the pc so far it sounds good, but now I have 2 pc’s with same name in original collection (i.e “All Windows 7 Systems”).

I added the “All Windows 7 Systems” collection ID to the script to delete the old name, but the script still remove the pc just from the deployment collection not original collection!

Has anyone any idea ?

Thanks,
Bab

Hi,

must I add this status filter to every primary site or can I just do it on the CAS?

For now it seems to work in our environment. I also checked the box to Report to the event log. But there’s a thing; my devices are being removed from the specified collection but when I log onto a client, I don’t see the action of remove.vbs in the event log (Windows Logs > Application). So I don’t know if my devices are remove from the collection by the Status Filter Rule or there is another reason that they are remove from the collection. Can you show me in which (event)log I should see the message?

Your commenthis vbscript not working for me

Let me tell me my scenario first.I am using sccm 2007 R3

I have hundreds of machine records with SCCM client agent as “NO Status” (AD discover Object)
My manger told me dont show up that machine in SCCM only client =yes machine should me there in SCCM.

So I have created a collection to pull all inactive AD discovered object and decided to delete those machine from sccm databe using your script

I have kept the script in F drive in sccmtool folder and changed the collection ID like below

sEventlog = “1”
sCollectionIDs = “WGP0031F”

The I called the script in command prompt with the command

“cscript.exe e:\sccmtools\remove.vbs %msgsys”

But cscript is just running and nothing is happening

Event viwer shows “%msgsys will be removed from the following collection ID’s WGP0031F”

Please help me.it is very urgent for me

Jörgen, I’m trying to get this to work on a SCCM 2012 R2 SP1. the computer does not get removed from any collection but it is logged on the application log. Do you need to add permission for the SCCM primary server to be able to run the script because it is being run under system context?