No problem. You could leave 4 out but then check for bad mifs being generated. In my experience of numerous ConfigMgr instances it always occurred. This action will cause the devices to run full inventory after they boot back up after a log off.
On Fri, Oct 16, 2015 at 1:36 PM, Mawdsley R. <[email protected]> wrote: > Thanks very much Paul. > > > > Will look into getting this done in our VDI. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* 16 October 2015 13:32 > *To:* [email protected] > *Subject:* Re: [mssms] VDI Machine Duplicates - Deleting > > > > Rich, > > > > Take a look at my Technet article here > http://social.technet.microsoft.com/wiki/contents/articles/23923.implementing-sccm-in-a-xendesktop-vdi-environment.aspx. > You will need to perform 4 actions when creating your master image. The 4th > action is to stop bad mifs being created by the VDI's (more on that here > https://sccmentor.wordpress.com/2014/04/08/dealing-with-bad-mif-files-in-a-vdi-environment/ > ). > > > > 1. Stop the SMS Host Service – to do this run the command net stop > ccmexec as an administrator > > 2. Delete the SMSCFG.ini file from the Windows folder – to do this run > the command del %WINDIR%\smscfg.ini > > 3. Delete the SMS certificates – to do this run the following line in > PowerShell – Remove-Item -Path > HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force or > from DOS using powershell -command "Remove-Item -Path > HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force" > > 4. 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 > > > > > > On Fri, Oct 16, 2015 at 11:39 AM, Mawdsley R. <[email protected]> > wrote: > > No. I assume it should be? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* 16 October 2015 11:15 > *To:* [email protected] > *Subject:* Re: [mssms] VDI Machine Duplicates - Deleting > > > > Did you delete the smscfg.ini also? > > > > On Fri, Oct 16, 2015 at 11:11 AM, Mawdsley R. <[email protected]> > wrote: > > Correct, non-persistent. > > > > Installed in the master image fully working. Pki cert deleted before > capture. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* 16 October 2015 10:59 > *To:* [email protected] > *Subject:* Re: [mssms] VDI Machine Duplicates - Deleting > > > > Rich, > > > > That shouldn't be happening. Are they non-persistent? How's the client > configured in the master image? > > > > On Fri, Oct 16, 2015 at 10:49 AM, Mawdsley R. <[email protected]> > wrote: > > Morning All, > > > > Our VDI machines have the SCCM agent installed, but they have quite a high > turnover rate in terms of a user logging in, logging out and the machine > being blown away and recreated.. and thus a new Device created in SCCM. > > > > It’s no big issue, but it throws reports out in terms of inactive > machines. We delete inactive machines every 60 days using they built in > methods. > > > > Is there any way to set a separate rule up that says if these machines > have been inactive for more than a day, to delete them? > > > > I currently manually delete them every couple weeks. > > > > > > > > Thankyou > > Rich > > --------------------------------- > > Rich Mawdsley > > SoftwareServices - iSolutions > > University of Southampton > > --------------------------------- > > > > > > > > > > > > > > > > > > > > > >
