K1000 inventory with Deepfreeze
It looks like Im having an K1000 inventory problem with Deepfreeze. When I go to any computer record in the K1000 under inventory, it is taking longer and longer to open the record. If I show changes for software/patches I see the same patches going back and forth between being detected and no longer detected. The machines have Deepfreeze installed and they are frozen and Im sure the software is there the entire time. For example I see something like.
Security Update for Microsoft Windows (KB2305420) 2013-10-04 12:02:21 - Detected
Security Update for Microsoft Windows (KB2305420) 2013-10-03 20:27:13 - No longer detected
Security Update for Microsoft Windows (KB2305420) 2013-09-30 10:20:01 - Detected
Security Update for Microsoft Windows (KB2305420) 2013-09-30 08:22:24 - No longer detected
Security Update for Microsoft Windows (KB2305420) 2013-09-27 13:37:01 - Detected
Security Update for Microsoft Windows (KB2305420) 2013-09-27 11:39:10 - No longer detected
Security Update for Microsoft Windows (KB2305420) 2013-09-26 15:54:58 - Detected
Security Update for Microsoft Windows (KB2305420) 2013-09-26 13:56:58 - No longer detected
Security Update for Microsoft Windows (KB2305420) 2013-09-23 10:21:23 - Detected
This is just an example, this particular computer 1200 entires for patches alone. Any idea how to prevent this happening? If I cant fix it, its going to become unuseable fast.
Answers (2)
Are you scheduling your patches to coincide with the machines being thawed?
Comments:
-
We are not patching on these computers at all, they have udpates disabled and we are not pushing software/patches via kace to them yet. What is installed is not changing but the inventory is reporting that it is. Im guessing it has something to do with the inventory xml file prior to being frozen but we never had any guidance that this needed to be deleted when using deepfreeze. - nimexx 10 years ago
We created 2 different orgs on our kbox for this reason, all of the acad desktops are frozen so they are in a different org then the admin desktops. This way we do no automatic patching/updates or deployments to the frozen machines.
Comments:
-
Does that have any advantages over setting up two labels instead to separate machines? - nheyne 10 years ago
-
The other advantage is this works with the way are duties are assigned in the dept. There are 3 tier techs who have root access, admin and acad access, We normally create or help create all the MI's, Scripts, Etc and do the kbox upgrades. We then have 2 other techs that do mid level admin tasks. Then one tech who oversees the acad section. This allows us to set who can get to what org, also the admin machines get 3-4 MI's pushed to them when they join the domain. This also helps to separate software licenses and inventory. Admin has provisioning turned on Acad does not. The acad stations are bought with tech fees and admin thru budget so they need to be tracked differently. The biggest part of this the techs cannot screw-up the other sections machines by mistake since they are not in their org. - SMal.tmcc 10 years ago
