Jump to content


juice13610

Established Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About juice13610

  • Rank
    Member
  1. The problem with solutions mentioned in this blog post on technet is that it seems MS thinks anyone who is an SCCM admin has only SCCM as a responsibility. Also, it mentions creating huge compliance-only update groups (not deployed) that you can check to make sure your machines are patched, but it never mentions how to patch just the ones that need it. Do I have to check this compliance and then create collections with potentially hundreds of machines that missed an update 6 months ago? Doesn't really do a great job explaining, IMHO.
  2. Interested in the responses you receive as I, too, am still awaiting seeing a compelling reason to move from patching with WSUS to patching with SCCM.
  3. Thanks - I have checked these logs and this is what I've found. Does this tell you anything? From UpdatesDeployment.log in no specific order [No actionable updates for install task. No attempt required.] [updates could not be installed at this time. Waiting for the next maintenance window.] [Attempting to install 0 updates] [Auto install during non-business hours is disabled or never set, selecting only scheduled updates] [A user-defined service window (non-business hours) is avbailable. We will attempt to install any scheduled updates.] From UpdatesStore.log There were some errors, but now for the past few days it has said "Successfully refreshed Resync state message" and "Refresh status completed successfully".
  4. I know this question is old, but if it were to be answered, it would be of great help to me. I am in a lab environment, so I installed WSUS on a server, then added it to my primary site as the SUP. I created a SUG and deployed them to a device collection to no avail. In fact, it is just showing "Unknown" for the collection as though it doesn't even know if any of the PCs (1) in the collection needs the updates. I only have a WSUS server and SCCM. No GPOs, no changes to the desktop (it was added to the domain and left alone). When I created a device collection containing said desktop and deployed the package, nothing.
  5. In other words, what do I have to do to the actual PC? As of right now, all I have done is install windows and join the domain, and let SCCM do the rest. It is doing nothing when attempting to deploy patches to it. When I go to the Monitoring -> Deployments -> Windows 7 Updates to STL Computers OU area, it shows that the 1 pc in the collection is "unknown." I don't know what I'm supposed to do to make the computer take the deployment and "comply".
  6. How is the client supposed to be setup? Do you have to setup a gpo to enable windows updates or anything at all?? I approved some patches a few days ago for a single computer (a collection that contained one computer) but when looking at the update group, it says 0 compliant, 0 required, 0 not required, 4 unknown. What do I have to do to make them report???
  7. I have been setting up SCCM 2012 in a lab environment and to be completely honest, I have no idea what I'm doing regarding the patching aspect. I took a beta 4 day in-class class and have my book, so I'm not totally running blind, but I'm still lost. I setup a site server named LAB-WSUS that had WSUS 3.0 SP2 installed and downloaded updates. Why does it appear my SCCM CAS is going directly out to Microsoft.com for updates? Shouldn't it be going to the WSUS server? Isn't that the point of the SUP site server? When I downloaded the patches, it asked me where to put the "package.". It just downloaded all of the patches onto the SCCM CAS server (per my direction). I setup a deployment package and chose to deploy to one of the device collections I have setup. I have no GPOs set to point those servers to the appropriate WSUS server, but why do they have to? It appears that my SCCM server is doing all the work. Thanks in advance!!!! Juice
  8. Ok, got it after I completely uninstalled SQL and started over from scratch!
  9. I have installed SQL Server 2008 R2, Service Pack 1, and Cumulative Update 4. I am still having issues that I have no idea where to begin because the error message is useless. When I get to the "Database Information" page, I enter the name of the server (LAB-SCCM.COntoso.com) where SQL is installed, database name of "CM_CAS" which I assume is created on installation, and SSB port is 4022 (default). I get this error; "Configuration Manager sites require a support SQL Server version with required hotfixes for site database operation to succeed. Before Setup can continue, you must install a support version of SQL server on the specified site database server. For more information, see " Thanks in advance Joey NOTE: Due to my issues, I have now removed everything related to SQL Server on the server. This is a lab environment by the way, so I Have no problem installing SQL on the actual server that SCCM resides on.
×
×
  • Create New...