I did a few things for Deep Freeze computers...
1. Created a package with batch file using those commands, This get deployed to the computer exactly at the beginning of their maintenance window. 2. We avoided SW inventory like the plague on these computers as it can take up all of the MW time for just SW inv. 3. We had more than one MW a week. This was due to both SU, App deployment and Inventory happening. 4. On a few select computer, we used the Task Scheduler too This will not stop the re-sync but it will mean that the inventory is no more than a few data old. From: [email protected] [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Monday, May 9, 2016 1:42 AM To: [email protected] Subject: [mssms] RE: Hinv not running as scheduled Hi Garth, I haven't reviewed the dataldr.log on the clients because I'm not seeing adequate data in the inventoryagent.log. Essentially it's about a half and half situation - half the clients did not run a hinv on Sunday, according to the inventoryagent.log. On these clients I opened and merged all the CM logs to confirm there was other client activity on Sunday, just no hinv. The other half did run a hinv on Sunday but it was at 9am instead of 10am. I can see the hinv occurring in the inventoryagent.log at 9am and then nothing for the rest of the day (except a DDR). I'm expecting the hinvs to be deltas because when I installed the CM client the machine was thawed so my expectation is the client will know a full inventory has been performed and every Sunday during the thaw period it will perform a delta and know about it. I've read your article, am I best to implement your method? Daniel. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Garth Jones Sent: Monday, 9 May 2016 1:16 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Hinv not running as scheduled Hi Daniel, there is lots is things to look at: 1. Did you look at the client's log file to confirm that HW invent has taken place. 2. Are you forcing a full HW inv each time? 3. Did you review the dataldr.log to see if the HW inv is getting reject and a re-sync notice occurs. 4. This blog post is more or less what I have used for deep freeze computers http://www.enhansoft.com/blog/how-to-avoid-receiving-inventory-re-sync-requests-for-snapshot-vms From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Sunday, May 8, 2016 9:30 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Hinv not running as scheduled I applied a custom client settings to a small collection of systems late last week that schedules a hinv for every Sunday at 10:01am. Checking this morning (Monday) and I can report that none were successful. It's a combination of the hinv wasn't run at all on the Sunday (despite confirming the machine was on) and the hinv running on Sunday but not at the scheduled time (~1 hour before the scheduled time). These machines are using Deep Freeze with a thaw period specified for every Sunday 9am - 5pm for maintenance and are configured to power on at 8am daily and shutdown at 6pm. When I installed the CM client on these machines last week I ensured they were thawed and had received policies so I'm not sure what's going on here. Any thoughts? ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law.
