rjarrett
Posts: 593
Score: 17 Joined: 5/26/2004 Status: offline
|
We have a "Backup and Restore" utility that captures a Ghost image of the machine and stores it on the network. When the backup is restored, it does not send an inventory because from its perspective nothing has changed since its last inventory. We traditionally use this feature when we are doing software deployment testing. If you install anything onto the computer in the interim between its last inventory and the Ghost image, it is "orphaned" in the central database. For example, assume my machine inventories at 9:00 AM and I commence the backup at 9:30 AM. Later, I deploy my test application at 10:00 AM. Once the inventory for that new software goes forward, it is in the central database. Then "restore" the machine. At this point, it is sitting there thinking it has the exact same configuration as it did at the 9:00 AM inventory. So, when the next inventory rolls around, it computes no change. As a result, it does not update the inventory. As a result, the test application is still in the server inventory. Thus, the computer is set back in time to a point where it is happy with itself, despite the intervening test installation.
_____________________________
Let me know if this helped... Rob Jarrett SMS\VB Development
|