Jump to content


TimN_FL

Established Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TimN_FL

  • Rank
    Newbie
  1. I am currently working on a number of projects that will have me building a number of SCCM sites, some for differing environments ( dev, test, prod ) and some for other clients. To make this process as easy as possible I have most of the installation already scripted with as little user intervention as possible. The only items that I have left are the site related configuration items. Right now the item that I can't see to find any info in the site control file is the Client push installation properties. Is there any programmatic method to access this information?
  2. With this project, shortly is a relative term. Best case scenario, we wouldn't be ready to install CM12 until after the first of the year but "patching" the existing clients are things that could be done now. The drivers for getting CM07 R3 installed now is for the image pre-staging and power management features.
  3. I was hoping for a little assistance. I am at a client site that is currently running SCCM 2007 R2. We have begun the planning stages for implementing SCCM 2012 R2, but during this transition period I wanted to go ahead and upgrade the site to SCCM 2007 R3 so they can make use of the enhancements and new features. We have testing the migration several times in our test lab, so I don't expect many surprises as far as that is concerned. But I did have a question as far as the recommended hotfixes that should be installed. to have everything working properly. The guides listed here on the site seem to have slightly dated lists I have seen the list here: http://social.technet.microsoft.com/wiki/contents/articles/4505.list-of-public-kb-articles-and-hotfixes-for-configuration-manager-2007-sp2.aspx but that list seems a bit daunting and I was hoping there was a more manageable list or is the recommendation that I request and download each of these updates to make sure that everything is working as it should. I have been reading the various articles and I have also noticed that a number of these updates were superseded by other updates. Ideally the list that I am looking for would be the hotfixes that I would need to install for all of the existing clients and the new ones created via an OSD task sequence. Thanks again for any assistance.
  4. I am current trying to build and capture a WIndows 2008 R2 image. I am currently running SCCM 2007 R2. My first version of the TS was just a vanilla TS with minimal steps to minimize complications. It installed the OS from an OS install package and captured the image without issue. I then added a step after the "Setup Windows and ConfigMgr" step to install updates. The updates install as expected and the computer reboots to a black screen where it applies the updates. Then the machine reboots again, I get a flash ( I am assuming that this is where the error is occuring ), the machine reboots and I get the initial configuration screen for Windows 2008. I have checked the logs and don't see any errors with the updates or the TS so i am not sure what is going on or where to start with troubleshooting this issue. Any ideas? Thanks in Advance, TimN_FL
  5. We have just started to use SCCM 2007 r2 ( working on the upgrade to r3) to build and deploy a Windows XP SP3 image to a number of lab environments that we have setup. The deployment process works completely as expected. Its the build process that we are having a problem with. We would like to keep our Images fairly up-to-date by "rebuilding" the images monthly after new updates have been incorporated after patch tuesday. The problem that we are having is that the build process takes so long. Our last build took about 12-13 hours to complete which seems excessive to me. We are building from scratch each and everytime using installation media and not the previous wim. We figured that this would be a cleaner image as it would not include patches that are no longer applicable because they have been superceded, expired, etc... And we assumed that this would help our imaging process since bad items would not be carried over from the previous image as we continue to update\tweak our process. I am assuming that I am not the only one that has encountered this. Does anyone have any suggestions to speed up the process? Thanks in advance for any advice\suggestions, TimN_FL
  6. I was wondering if anyone could give feedback or suggestions about the way that I have my updates setup currently incase there are any pitfalls that I haven't caught. I am running SCCM 2007 R2 on windows 2003 r2 ( I am working on upgrading it to Win 2008 r2 and SCCM 2007 r3).Before I get to far into a description of my environment I want to add that this entire process is scripted via powershell and run via a scheduled tasks and only requires intervention where specified as maintaining this manually would have been a nightmare. Collections: I have a collection for each environment (Dev, Test, Prod) and sub collections for each Type of Machine ( Servers, Workstations, Laptops) Search Folders: I have a Search Folder for each Product that I update via SCCM ( Windows XP, Windows 7, SQL 2005, etc...). The search folders are created to exclude all Superceded, Expired and excluded updates. I exclude updates from being added to the listby setting the custom severity to something other than nothing. Update Lists: Each Product has an update list for each environment and type for each month within a given window everything older than the window is placed in a baseline Update List. For instance, I have Production-Workstation-Windows XP-201203 Update List that contains all of the updates for that month for Windows XP that will be targeted to the Production Workstations. For Production, I have a 6 month Update window so anything older than 6 months gets put into a baseline Update List ( i.e.- Production-Workstation-Windows XP-Baseline). I initially started doing this because I read that this helps for compliance reporting and because there is a best practice of no more that 500 updates in a given list. I can confirm that even with Windows XP. The update lists are created by parsing the applicable Search Folder and grouping them by Release Date. Deployment Templates: For Each type of Environment and machine Type there is a deployment template created with all of the applicable rules and requirements (i.e. - Production-Workstation, Test-Server, etc....) Update Assignments: For each Update list that is created, there is a corresponding Update Assignment assigned to the appropriate Collection based off of the appropriate Deployment Template Update Packages: There is an update package for each month for each product (i.e. - Windows XP-201203, SQL 2005-201112, etc...) Each time the script runs it cleans up anything that might have changed (downloads new updates, remove superceded, expired or excluded updates). And it sends out a notification of new updates to allow myself and the other admins to decide whether to exclude the update or not. I can confirm that all of the items created and maintained by this script works as described and I do not have any issues with corrupt or malformed objects of any kind. Does having so many Update assignments create any issues? In the scenario described above, for production I would have 7 Assignments per product. So for a Production Windows XP machine with Office 2007, silverlight that would theoritically be 21 assigments ( I say theoretically because things like silverlight don't have updates all that often and empty Assignments, List, and packages are removed automatically). So far this setup has not presented any issues and we have been using it in production for a couple of months and all of the automatic features have been working (cleaning up updates, deploying new updates, etc... ). I am just looking for opinions from the group to see if any of this will cause any issues. Thanks in advance for any suggestions, TimN_FL
×
×
  • Create New...