Clever thinking Jason. I like it. :-)
> On 14 Aug 2015, at 20:28, Jason Wallace <[email protected]> wrote: > > Or just not enable HINV on your VDIs > > > >> On 14 Aug 2015, at 21:11, Paul Winstanley <[email protected]> wrote: >> >> Nothing really but if you don't run full inventory then you'll have to clean >> out the mifs regularly. That's the option >> >> >> >>> On 14 Aug 2015, at 19:51, Jason Wallace <[email protected]> wrote: >>> >>> Paul's guide is the one that I always point people to but then, as I would >>> do with a customer I'd challenge you what, in a non-persistent VDI is >>> hardware inventory going to provide that you do not already know about that >>> device? >>> >>> >>> >>>> On 14 Aug 2015, at 19:23, Paul Winstanley <[email protected]> wrote: >>>> >>>> Here's an article I wrote about 18 months ago for a non-persistent >>>> environment. Note I had to add in an extra step to force a full hardware >>>> inventory on startup otherwise the system was flooded with bad mifs. >>>> >>>> https://sccmentor.wordpress.com/2014/03/05/implementing-sccm-in-a-xendesktop-mcs-vdi-environment/ >>>> >>>> >>>> >>>>> On 14 Aug 2015, at 18:04, Juelich, Adam <[email protected]> >>>>> wrote: >>>>> >>>>> And you have the ConfigMgr client on all of those? If so, are you doing >>>>> that on non-persistent images just for inventory purposes? >>>>> >>>>> ----------------------------------------------- >>>>> >>>>> Adam Juelich >>>>> >>>>> Pulaski Community School District >>>>> >>>>> Client Management Specialist >>>>> >>>>> 920-822-6075 >>>>> >>>>> >>>>>> On Fri, Aug 14, 2015 at 11:57 AM, Daniel Ratliff <[email protected]> >>>>>> wrote: >>>>>> Both. I think we are about a 4/5 persistent, 1/5 non-persistent split. >>>>>> >>>>>> >>>>>> >>>>>> Daniel Ratliff >>>>>> >>>>>> >>>>>> >>>>>> From: [email protected] >>>>>> [mailto:[email protected]] On Behalf Of Juelich, Adam >>>>>> Sent: Friday, August 14, 2015 12:46 PM >>>>>> To: [email protected] >>>>>> Subject: Re: [mssms] prepping CM client in VDI master image >>>>>> >>>>>> >>>>>> >>>>>> Are you guys using Linked Clones and Refreshing them on a regular basis? >>>>>> Or are you using dedicated assignment and managing them just as your >>>>>> would a physical machine? >>>>>> >>>>>> >>>>>> >>>>>> ----------------------------------------------- >>>>>> >>>>>> Adam Juelich >>>>>> >>>>>> Pulaski Community School District >>>>>> >>>>>> Client Management Specialist >>>>>> >>>>>> 920-822-6075 >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Aug 14, 2015 at 11:38 AM, Daniel Ratliff <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Here is our short list: >>>>>> >>>>>> >>>>>> >>>>>> 1. Install the client >>>>>> >>>>>> 2. Stop ccmexec service >>>>>> >>>>>> 3. Delete the certs using ccmdelcert.exe >>>>>> >>>>>> 4. Delete %windowsroot%\smscfg.ini >>>>>> >>>>>> 5. Capture image >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Daniel Ratliff >>>>>> >>>>>> >>>>>> >>>>>> From: [email protected] >>>>>> [mailto:[email protected]] On Behalf Of Art Flores >>>>>> Sent: Friday, August 14, 2015 12:31 PM >>>>>> To: [email protected] >>>>>> Subject: [mssms] prepping CM client in VDI master image >>>>>> >>>>>> >>>>>> >>>>>> Does anyone know if the information in this article is still valid on >>>>>> preparing a Windows 7 master image with the ConfigMgr client already >>>>>> installed? >>>>>> >>>>>> >>>>>> >>>>>> The last time we did this, I was following a different link, which I >>>>>> can’t find now, and figured someone may have a more up to date link. I >>>>>> also remember using the following command to remove the trusted root key >>>>>> and other certificates before capturing the image. >>>>>> >>>>>> >>>>>> >>>>>> CCMSetup resetkeyinformation=true >>>>>> >>>>>> >>>>>> >>>>>> http://henkhoogendoorn.blogspot.com/2013/07/prepare-configmgr-client-for-sysprep-or.html >>>>>> >>>>>> >>>>>> >>>>>> Thanks. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 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. >
