Check of the machine is approved, if not than approve the machine [cid:[email protected]]
Maarten van Willigen Informatie & Communicatie Technologie Cofely Nederland NV From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: donderdag 3 juli 2014 1:46 To: <[email protected]> Cc: [email protected] Subject: Re: [MDT-OSD] ConfigMgr 2012 OSD - "There are no task sequences available for this computer" It sounds like it got far enough through the build to get a record created in SCCM. At that point it's a matter of what collection you have the build targeted and what criteria is used to populate it. Although these machines may have blown up after getting the client but before they had a chance to submit an inventory. So SCCM knows that they are out there lost somewhere. At least that's the gut feeling I'm getting about them. Sent from my iPhone On Jul 2, 2014, at 7:35 PM, "Murray, Mike" <[email protected]<mailto:[email protected]>> wrote: And after further pestering, the tech admits he did get the image process started, but it blew up at some point for some reason. :/ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, July 2, 2014 4:08 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] ConfigMgr 2012 OSD - "There are no task sequences available for this computer" Tried that, no luck. However, after running a report on the MAC address for one of these, it already had an entry in the console (although the tech swears he was getting failures on the first try and it never imaged). Removed it, now I have the TS screen available. So this raises a question... why did these fail, but other machines that exist in ConfigMgr and get reimaged do not fail? Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Wednesday, July 2, 2014 4:02 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] ConfigMgr 2012 OSD - "There are no task sequences available for this computer" in assets and compliance, devices, find any UNKNOWN objects (except the Unknown computer collections) and delete them, then try again *(assuming you've deployed the ts to known and unknown computers) On Thu, Jul 3, 2014 at 12:56 AM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: I've read through a bunch of articles online for possible solutions on this, but nothing fits my situation, as we are able to image many of the same model without issue. This is a Dell 9020 small form factor. One of our area techs has 4 of these that get this error. We have imaged ~60-80 of this model without issue, but these 4 aren't playing nice. No error code, just the error in the subject of this message, and the error you see below. In fact, we took a hard drive from an imaged one and put it in one of the problem children, and it worked fine. All the drivers, etc. matched the other system, so it's not a driver issue. I've verified that it's getting a good IP address, too. I can access other resources on the network from a command prompt. I'm attaching the smsts.log file. Ideas? Suggestions? <image001.png> Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ================================================================================================ De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. ================================================================================================ The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail. ================================================================================================
