Amen to that ... you all just know we is anti-CAS right? :-) CAS where not needed += €€€€££££$$$
Robert Jason Sandys <[email protected]> wrote: >Dead horse: Reason #316 not to use a CAS. > >J > >From: [email protected] >[mailto:[email protected]] On Behalf Of Daniel Ratliff >Sent: Tuesday, September 3, 2013 9:56 AM >To: [email protected] >Subject: RE: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >If you have a CAS, it takes approximately 5-15 minutes because it has >to replicate down and back up from your primaries. A huge pain for any >immediate updates needed for collections. > >Daniel Ratliff > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) >Sent: Tuesday, September 03, 2013 10:45 AM >To: [email protected]<mailto:[email protected]> >Subject: AW: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >Works well for me. What problems have you encountered? > >Von: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] Im Auftrag von Marcum, John >Gesendet: Dienstag, 3. September 2013 16:40 >An: '[email protected]' >Betreff: RE: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >Adding machines on the fly to collections for OSD in 2012 doesn't work >well. > >________________________________ >John Marcum >Sr. Desktop Architect >Bradley Arant Boult Cummings LLP >________________________________ > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) >Sent: Tuesday, September 03, 2013 9:33 AM >To: [email protected]<mailto:[email protected]> >Subject: AW: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >You could use a pre-execution staging hook, build a script into the >hook that queries the mac address and the computer manufacturer/model. >Then use the hook to pull the machine into a collection. Then it will >receive an advertisement. You can use a similar step at the end of the >ts to remove the machine from the collection. > >Von: >[email protected]<mailto:[email protected]> >[mailto:[email protected]]<mailto:[mailto:[email protected]]> >Im Auftrag von Koster, Maik >Gesendet: Dienstag, 3. September 2013 16:26 >An: [email protected]<mailto:[email protected]> >Betreff: RE: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >It has to be executed with the dongle/Docking station detached. So you >would need to remember what dongle/docking station was used, check if >it's still connected and if so re-schedule. > >Regards >Maik Koster >Cameron Flow Control Technology GmbH - Sitz der Gesellschaft: Celle - >Handelsregister: Amtsgericht Lüneburg HRB 204184 - Geschäftsführung: >Cheryl Roberts, Grace Holmes > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]]<mailto:[mailto:[email protected]]> >On Behalf Of Hedges, Dustin >Sent: Dienstag, 3. September 2013 16:07 >To: [email protected]<mailto:[email protected]> >Subject: RE: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >What about leveraging the _SMSTSPostAction Variable (ConfigMgr 2012 >SP1)? Or even setting a RunOnce Registry setting to execute a script >with those commands? > > >Dustin Hedges >Sr. Systems Engineer > >eBay Inc. >[email protected]<mailto:[email protected]> ebayinc.com > >[cid:[email protected]] > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Ryan >Sent: Tuesday, September 3, 2013 7:38 AM >To: [email protected]<mailto:[email protected]> >Subject: Re: [mssms] ConfigMgr 2012 meets tablets - The case of the >"Unknown" > >Three options come to mind... First off, you could delete any records >that show up in the collection with those MAC addresses. You'd lose the >imaging information on the computer though, so it probably isn't the >best idea. > >Another option is changing the MAC address in WinPE... Change it before >the TS runs and have it automatically generated based on the wifi MAC. >I'm not sure if that will fool ConfigMgr into thinking it is a >different device. > >Another thought is to add 802.11x support and just use the dongle to >boot into WinPE... >http://blogs.technet.com/b/deploymentguys/archive/2010/01/15/added-support-for-802-1x-in-windows-pe.aspx > You'll need a very stable WiFi network for this. > >On Tue, Sep 3, 2013 at 6:49 AM, Mattias Benninge ><[email protected]<mailto:[email protected]>> wrote: >Would it be possible to use "devcon" to eject the USB-dongle and then >force a full HW-Inventory as the last steps of an TS? I do not know >what happens to the TS if the connections drops from the dongle and >moves over to Wifi. If that makes the TS fail it wont work. > >This was just an wild idea, not sure it will work in real life since i >have no tablets or usb-networdcards to test with. One problem I can see >is that you must know the hardware ID of the dongle so you make sure >the right device is being ejected. > >Regards >Mattias Benninge > > >On Tue, Sep 3, 2013 at 12:34 PM, Koster, Maik ><[email protected]<mailto:[email protected]>> wrote: >I'd like to start a small discussion on an issue I ran into recently. > >The full story can be found here: >http://myitforum.com/cs2/blogs/maikkoster/archive/2013/09/03/configmgr-2012-sp1-meets-tablets-the-case-of-the-unknown.aspx > >To give a short abstract. > >We had to deploy Windows 8 to some tablets using ConfigMgr 2012 SP1 and >used a Task Sequence deployed to the "Unknown Computers" collection. >The tablets we had for testing didn't have any built-in NIC, so we used >a USB-To-Ethernet dongle and a docking station. First deployment(s) ran >fine, but on the second device (using the same dongle, as the first >device doesn't need it because it's being used wireless) it didn't >start the Task Sequence as it was no longer unknown. The first device >had the Mac Address assigned, so if ConfigMgr queries for devices based >on MAC and UUID, it will find a resource based on the Mac (of the >dongle) and not handle it as an unknown computer. > >We forwarded this information to Microsoft and the response was, to buy >a dongle/docking station per device. Which is not only a cost-intensive >solution, it will most likely also not work on the long run, as I would >guess most support staff doesn't really unpack and connect a >dongle/docking station per deployment, rather having a few "stations" >prepared to do the deployments and then just hand out the still boxed >dongle/docking station to the user. At least that's how most of our >deployments are done internally. > >So we tried to get it working with a few dongles/docking stations only. >But we didn't wanted to deploy this to a large collection like all >systems and we also didn't wanted to pre-stage each single tablet. So >we created a collection based on the Mac Addresses of the Dongles and >docking stations we used for this initial deployment and restricted the >deployment of the TS to media and PXE only. This prevented the >deployment to be shown in the Software center of already deployed >devices. However, all the "old" tablets were still shown in this >collection and would stay in there, until this entry ages out. > >After some testing on how to get rid of this information as soon as >possible, we figured out, that we had to update the DDR and then force >a full hardware inventory, to get this done. So we advertised a package >with a batch that executes two WMIC commands (show in the blog post). >This has to run on a regular schedule on the computers in the >collection, as the dongle has to be disconnected during execution to >get rid of its Mac address. When the dongle was disconnected and the >two commands have been executed, they would drop out of the collection >and no longer execute the commands. > >While this is a usable solution, it still is a bit complex and doesn't >feel "smooth". So I thought I reach out to the combined knowledge and >experience of this group to get some additional input and hear about >solutions others have found. As I assume, I'm not the first one who >tackled this issue. And with an increasing amount of tablets even in >enterprises, this will also become more common over time. > > >Regards >Maik Koster > > > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >This email message is for the sole use of the intended recipient(s) and >may contain confidential and privileged information of Cameron and its >Operating Divisions. Any unauthorized use or disclosure is prohibited. >If you are not the intended recipient, please contact the sender by >reply email and delete and destroy all copies of the original message >inclusive of any attachments. >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >This email message is for the sole use of the intended recipient(s) and >may contain confidential and privileged information of Cameron and its >Operating Divisions. Any unauthorized use or disclosure is prohibited. >If you are not the intended recipient, please contact the sender by >reply email and delete and destroy all copies of the original message >inclusive of any attachments. >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > >________________________________ > >Confidentiality Notice: This e-mail is from a law firm and may be >protected by the attorney-client or work product privileges. If you >have received this message in error, please notify the sender by >replying to this e-mail and then delete it from your computer. > >________________________________ > >Confidentiality Notice: This e-mail is from a law firm and may be >protected by the attorney-client or work product privileges. If you >have received this message in error, please notify the sender by >replying to this e-mail and then delete it from your computer. > > > >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.
