Yuuuup sure do have a boatload of MIFs in that folder. Thanks again. I never would have noticed this. SCCM is only one-tenth of my duties and if ain't "broke", little things like this often go unnoticed.
On Wed, Apr 8, 2015 at 10:56 AM, Paul Winstanley <[email protected]> wrote: > If you haven't implemented it yet check your inboxes I implemented against > 3 separate site servers each managing XenDesktop non-persistent VDI's at > different customers and each one experienced the problem. > > > https://sccmentor.wordpress.com/2014/04/08/dealing-with-bad-mif-files-in-a-vdi-environment/ > > On Wed, Apr 8, 2015 at 3:50 PM, ccollins9 <[email protected]> wrote: > >> Thanks for the article! And I noted the WMI thing as well, will be >> adding that into our script for sure. >> >> On Wed, Apr 8, 2015 at 10:43 AM, Paul Winstanley <[email protected]> >> wrote: >> >>> *'Our base image has the client on it, so it's always "good" with SCCM. >>> Before we shut it down and snapshot it, we clean the SCCM client with a >>> script that stops the SMS service, deletes smscfg.ini and removed the >>> machine's computer certificate.'* >>> >>> Worth noting that I had to add Point 4 to the article >>> >>> (Remove the Inventory Action ID 1 in WMI - to do this run the command >>> wmic /namespace:\\root\ccm\invagt path inventoryActionStatus where >>> InventoryActionID="{00000000-0000-0000-0000-000000000001}" DELETE >>> /NOINTERACTIVE) >>> >>> to stop bad mifs being created by each non-persistent VDI. >>> >>> >>> >>> On Wed, Apr 8, 2015 at 3:36 PM, ccollins9 <[email protected]> wrote: >>> >>>> Our base image has the client on it, so it's always "good" with SCCM. >>>> Before we shut it down and snapshot it, we clean the SCCM client with a >>>> script that stops the SMS service, deletes smscfg.ini and removed the >>>> machine's computer certificate. >>>> >>>> >>>> >>>> http://social.technet.microsoft.com/wiki/contents/articles/23923.implementing-sccm-in-a-xendesktop-vdi-environment.aspx >>>> >>>> On Mon, Apr 6, 2015 at 3:06 PM, Trice, Aaron <[email protected]> >>>> wrote: >>>> >>>>> That's how we have it as well. >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> >>>>> *Aaron Trice* >>>>> >>>>> >>>>> >>>>> *From:* [email protected] [mailto: >>>>> [email protected]] *On Behalf Of *Daniel Ratliff >>>>> *Sent:* Monday, April 06, 2015 11:59 AM >>>>> >>>>> *To:* [email protected] >>>>> *Subject:* [mssms] RE: Cm12 and VMWare VDI - patch image >>>>> >>>>> >>>>> >>>>> No, ours are persistent VMs built from a template. Our linked clones >>>>> to not have the ConfigMgr client either. >>>>> >>>>> >>>>> >>>>> *Daniel Ratliff* >>>>> >>>>> >>>>> >>>>> *From:* [email protected] [ >>>>> mailto:[email protected] <[email protected]>] >>>>> *On Behalf Of *Trice, Aaron >>>>> *Sent:* Monday, April 06, 2015 2:55 PM >>>>> *To:* '[email protected]' >>>>> *Subject:* [mssms] RE: Cm12 and VMWare VDI - patch image >>>>> >>>>> >>>>> >>>>> Are you referring to Linked Clones? We refresh after 4 hours of >>>>> inactivity and started seeing duplicate machines in SCCM so we kept the >>>>> client off the virtual machines. >>>>> >>>>> >>>>> >>>>> *Aaron Trice* >>>>> >>>>> >>>>> >>>>> *From:* [email protected] [ >>>>> mailto:[email protected] <[email protected]>] >>>>> *On Behalf Of *Daniel Ratliff >>>>> *Sent:* Monday, April 06, 2015 11:00 AM >>>>> *To:* [email protected] >>>>> *Subject:* [mssms] RE: Cm12 and VMWare VDI - patch image >>>>> >>>>> >>>>> >>>>> Manual process for now. >>>>> >>>>> >>>>> >>>>> 1. Power on template >>>>> >>>>> 2. Configure CM client >>>>> >>>>> 3. Deploy patches >>>>> >>>>> 4. Clean CM client >>>>> >>>>> 5. Capture template >>>>> >>>>> >>>>> >>>>> *Daniel Ratliff* >>>>> >>>>> >>>>> >>>>> *From:* [email protected] [ >>>>> mailto:[email protected] <[email protected]>] >>>>> *On Behalf Of *DeGuire Greg (FCA) >>>>> *Sent:* Monday, April 06, 2015 1:57 PM >>>>> *To:* [email protected] >>>>> *Subject:* [mssms] Cm12 and VMWare VDI - patch image >>>>> >>>>> >>>>> >>>>> Anyone using SCCM 2012 to patch/update the 'gold' image from which all >>>>> virtual desktops are launched in a VMWare VDI infrastructure? >>>>> >>>>> >>>>> >>>>> From what I have read, there is a way to do this with Hyper-V/VMM but >>>>> have not found a way to do this with a VMWare environment. >>>>> >>>>> >>>>> >>>>> Thanks for any info you folks can provide. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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. >>>>> >>>>> >>>>> >>>>> Confidentiality Notice: This is a transmission from Community Hospital >>>>> of the Monterey Peninsula. This message and any attached documents may be >>>>> confidential and contain information protected by state and federal >>>>> medical >>>>> privacy statutes. They are intended only for the use of the addressee. If >>>>> you are not the intended recipient, any disclosure, copying, or >>>>> distribution of this information is strictly prohibited. If you received >>>>> this transmission in error, please accept our apologies and notify the >>>>> sender. Thank you. >>>>> >>>>> >>>>> >>>>> >>>>> 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. >>>>> >>>>> >>>>> Confidentiality Notice: This is a transmission from Community >>>>> Hospital of the Monterey Peninsula. This message and any attached >>>>> documents >>>>> may be confidential and contain information protected by state and federal >>>>> medical privacy statutes. They are intended only for the use of the >>>>> addressee. If you are not the intended recipient, any disclosure, copying, >>>>> or distribution of this information is strictly prohibited. If you >>>>> received >>>>> this transmission in error, please accept our apologies and notify the >>>>> sender. Thank you. >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
