Lab Geek

(Originally posted 11/6/2014. Reposting for reference)   This series of articles will provide a method of tracking end-to-end OSD revisioning using a few simple Task Sequence tasks and an optional PowerShell script.  In this first article, looked at why the out-of-box forensic information is useful but insufficient, and we implement a method for version control in the core image.  Now that we have a method of tagging our core image, how do we capture changes around the deployment of that…

Read More Read More

(Originally posted 11/6/2014. Reposting for reference) This topic has come up several times on the myITforum email lists, so this seems like a good opportunity to provide an example of how to do image version control in ConfigMgr.  There are numerous different ways this can be done, so this is just an outline that should be modified or improved upon to fit the particular implementation.  Ultimately, do what works best for your situation. This two-part series of articles will provide…

Read More Read More

(Originally posted 11/27/2013. Reposting for reference) With disk space being relatively inexpensive these days, limiting the local ConfigMgr cache to 5GB by default seems almost stingy. However, since very few circumstances require one to set content to persist in the local cache, the assumption is that ConfigMgr will do its usual good work in purging out older content to make room for new should the cache bump up against that limit.  As it turns out though, the client behavior can…

Read More Read More