{"id":635,"date":"2013-05-20T16:15:16","date_gmt":"2013-05-20T14:15:16","guid":{"rendered":"http:\/\/sccmfaq.wordpress.com\/?p=635"},"modified":"2013-05-20T16:15:16","modified_gmt":"2013-05-20T14:15:16","slug":"sccm-2012-sp1-remove-client-from-collection-after-osd","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=635","title":{"rendered":"SCCM 2012 SP1 – Remove Client from Collection after OSD"},"content":{"rendered":"

Times are changing, so are our scripts. I can’t tell you how often I used this VB-Script http:\/\/ccmexec.com\/2012\/07\/remove-from-collection-and-clear-pxe-flag-vbscript-using-status-filter-rule\/<\/a>\u00a0, but I think now, the new cmdlets for powershell are more comfortable. So I decided to change my auto-remove to a powershell script.<\/p>\n

This is what you need, that the script will run:
\n-Trust the Module that has to be imported <\/strong>(This will be explained in the Blog)
\n-The script has to be executed in x86 mode
\n-The server that runs the rule\u00a0has to be added with permissions<\/strong><\/p>\n

So, let’s start with the prerequisites, they are Powershell 3 and the SCCM 2012 SP1 Console, and you have to trust the module of the configuration manager psd file. This can be done through starting the powershell console via the SCCM console:
\n\"Start<\/a><\/p>\n

You should decide to always trust this module, otherwise the script will always ask, and when run through Status Filter Rules, the script will fail to run.<\/p>\n

\"Trust<\/a><\/p>\n

It is also necessary that the SCCM Server has right in SCCM itself. You can achieve this, when you add the SCCM Server via Console. I decided to use the Full Administrator role, it’s upon you, how far you want to go. If you don’t add the server, the script will fail, because the psdrive of your site will not be found. Typical error message is: “Cannot find drive. A drive with the name ‘$Sitecode’ does not exist.” When you start a powershell session with “NT AuthoritySystem” and try manually to import the module, when changing on the ps-drive, it will fail. So add your server as in the print-screen beyond.\"SCCM<\/a>The Server also needs the DCOM Remote\u00a0Access Permission:
\n\"DCOM<\/a><\/p>\n

You will have to change the variable “$CollectionIDs” to apply it on your environment. You can change the variable $bEventlogEntry to “0”, then the script will not write in the Application log of the Server. And with $bClearPXE = “1” the PXE flag will be cleared after the computer is removed from the collections.<\/p>\n

Here is the script (It’s on my skydrive):
\nhttps:\/\/1drv.ms\/t\/s!Aq0GcVCqC0RlhTtNDcR9uJRgGf3X<\/a><\/p>\n

————————–
\n
\n#Call example:
\n#C:\\Windows\\SysWOW64\\WindowsPowerShell\\v1.0\\powershell.exe -ExecutionPolicy ByPass RemoveFromCollection_1.0.ps1 %msgsc %msgsys
\n#%msgsc = Site-Code
\n#%msgsys = ComputerName<\/code>
\n
\n#Set required Input Parameters
\nParam(
\n[string]$SiteCode,
\n[string]$ComputerName
\n)<\/code>
\n
\n#--------------------
\n#User defined variables here
\n<\/code>
\n$CollectionIDs = \"S0100025;S010002C;S010001E\"
\n$bEventlogEntry = \"1\"
\n$bClearPXE = \"0\"<\/code>
\n
\n#End user defined variables
\n#--------------------<\/code><\/p>\n

If($SiteCode -and $ComputerName){}
\nelse{
\nWrite-Host \"Required Input is missing! Omit SiteCode and Computername.\"
\nexit
\n}<\/code><\/p>\n

#$SiteCode = \"S01\"
\n#$ComputerName = \"rudolph\"<\/code><\/p>\n

#Check for 32-bit execution
\nIf ($env:Processor_Architecture -ne \"x86\") {
\nwrite-host \"Script has to be executed in x86 mode!\"
\nexit
\n}<\/code><\/p>\n

#Import SCCM Module
\n$ModuleName = (get-item $env:SMS_ADMIN_UI_PATH).parent.FullName + \"ConfigurationManager.psd1\"
\nImport-Module $ModuleName
\nCD $SiteCode\":\"<\/code><\/p>\n

#Remove Client from collections
\n#Get collection id array
\n$aCollections = ($CollectionIDs).Split(\";\")<\/code><\/p>\n

#check for each collection if a directmember chip exist, and remove it
\nforeach($Collection in $aCollections){
\nIf((Get-CMDeviceCollectionDirectMembershipRule -CollectionId $Collection -ResourceName $ComputerName).count -eq 1) {<\/code>
\n
\n#Write Eventlog entry
\nIf($bEventlogEntry -eq 1){
\nwrite-eventlog -logname Application -source \"SMS Client\" -eventID 3001 -entrytype Information -message \"Computer $ComputerName will be removed from Collection $Collection\" -category 1 -rawdata 10,20
\n}<\/code>
\n
\n#Remove Client from collection
\nRemove-CMDeviceCollectionDirectMembershipRule -CollectionId $Collection -ResourceName $ComputerName -Force<\/code><\/p>\n

#Clear PXE Flag
\nIf($bClearPXE -eq 1){
\nClear-CMPxeDeployment -DeviceName $ComputerName
\n}
\n}
\n}
\n<\/code>
\n————————–<\/p>\n

When you have\u00a0copied the script, then it’s time to create the Status Filter Rule:<\/p>\n

\"Create<\/a><\/p>\n

Fill up the following values in the Wizard:
\nName: Remove Client when OSD finished<\/strong>
\nComponent: Task Sequence Manager<\/strong>
\nMessage ID: 11171<\/strong><\/p>\n

\"Status<\/a><\/p>\n

In the action tab, you can choose to create a eventlog entry, if you want to see, that the status filter rule really triggers. And you will have to specify the “Run a program” option as following, make sure that you are using the full Path of the powershell executable<\/strong>:
\nC:\\Windows\\SysWOW64\\WindowsPowerShell\\v1.0\\powershell.exe -ExecutionPolicy ByPass “<path to script>RemoveFromCollection_1.0.ps1” %msgsc %msgsys<\/p>\n

As written above, Powershell x86 is needed, probably you will have to define the execution policy and don’t forget the variables “%msgsc %msgsys”. The picture:
\n\"Stauts<\/a><\/p>\n

Finish the wizard and enjoy the automatic removing of your clients from your OSD Collections.<\/p>\n

Hope this helps, Martin \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Times are changing, so are our scripts. I can’t tell you how often I used this VB-Script http:\/\/ccmexec.com\/2012\/07\/remove-from-collection-and-clear-pxe-flag-vbscript-using-status-filter-rule\/\u00a0, but I think now, the new cmdlets for powershell are more comfortable. So I decided to change my auto-remove to a powershell script.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,40],"tags":[],"class_list":["post-635","post","type-post","status-publish","format-standard","hentry","category-collection","category-tools"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=635"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/635\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}