With the announcement that currently shipping PCs (Skylake) have an accelerated EOL for Windows 7 as soon as July 2017, my plan of waiting for the bugs and issues to get worked out of Windows 10 deployments is becoming less practical.
From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Wednesday, February 17, 2016 9:24 AM To: ms...@lists.myitforum.com Subject: [mssms] RE: Getting Deployments per machine Neat, will put it to a test! Thx! Sidenote: Anyone know when MS will release an ADK that works well with CM + MDT as well as the latest Win10? In a year? From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: den 17 februari 2016 16:20 To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] RE: Getting Deployments per machine The meat of it is pretty easy. Also note this only shows task sequences. $resid = $global:computercas.resourceid $collmem = Get-WMIObject -ComputerName $global:siteservercas -Namespace "root\sms\site_$global:sitecodecas" -class sms_fullcollectionmembership -Filter "resourceid = '$resid'" -Credential $global:sccmcred foreach ($coll in $collmem) { $collid = $coll.collectionid $adverts = Get-WMIObject -ComputerName $global:siteservercas -Namespace "root\sms\site_$global:sitecodecas" -class sms_advertisement -filter "collectionid = '$collid'" -Credential $global:sccmcred foreach ($advert in $adverts) { $pkgid = $advert.packageid $ts = Get-WMIObject -ComputerName $global:siteservercas -Namespace "root\sms\site_$global:sitecodecas" -class sms_tasksequencepackage -filter "PackageID = '$pkgid' and PackageType = '4'" -Credential $global:sccmcred if ($ts -ne $null) { $tslist = $tslist + $ts.Name } } } Daniel Ratliff From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Wednesday, February 17, 2016 10:14 AM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] RE: Getting Deployments per machine Cook, new there was some scripts out there but didnt know it was doable from PowerShell. How do you do it? (Or do I have to parse all that PS? ;-) From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: den 17 februari 2016 16:11 To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] RE: Getting Deployments per machine Yeah I have that functionality in my OSD FrontEnd. It's all PowerShell called from WinPE. http://www.potentengineer.com/powershell-osd-frontend-2-0/ Daniel Ratliff From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Wednesday, February 17, 2016 10:05 AM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] Getting Deployments per machine Hey peeps, Ok, so the same old crap; Adding a new machine with PowerShell to a collection with a deployment and then wanting to know when the deployment has been created so that we can PXE boot. How do I do this? Can I even do this from PowerShell? Or do I have to dig into SQL land? //Andreas The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________