Jump to content


bmkiss67

Established Members
  • Content Count

    19
  • Joined

  • Last visited

  • Days Won

    1

bmkiss67 last won the day on November 2 2018

bmkiss67 had the most liked content!

Community Reputation

1 Neutral

About bmkiss67

  • Rank
    Member

Recent Profile Visitors

541 profile views
  1. My thing with the SCCM interface is that customers like pretty things so when they want to see patch data they want to see it in the SCCM interface.
  2. Thanks, good to know. Is there a way to force a refresh on the console?
  3. When you look at the SCCM interface it will show some machines needing certain patches. When you go to IE and run a report it does not show the same data. Any ideas on what can be causing this or how to fix this? Thanks
  4. I've linked a screen capture that deals with my question. As I was setup one of the SCCM updates I ran into a screen that had to do with Client Update Settings. The bottom selection had a senetence in it that said, "Later, you can overwrite the production package using Client Update Options in the Updates node of the Configuration Manager console." Great, except I have no idea where "Updates" node is. Where is that at?
  5. Anyweb, I wanted to thank you for you help. I used this site to learn everything I know about SCCM, so I'm glad you do this. It's helped alot.
  6. Let me also ask this, is that 43G just SCCM updates or are they are updates in there like Win 10 updates for pushing?
  7. Hi. I just followed steps 1, 2, and 3. I checked my UpdatePacks directory and it is 43.8G in size. That doesn't seem right to me. Why would it be so large?
  8. So I see these errors in my wsyncmgr.log Can these errors be the cause of my issues? Failed to sync update 09dc7113-fa44-4ca8-9d70-ec254d4d2f04. Error: The Microsoft Software License Terms have not been completely downloaded and~~cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCM-B.project.local SITE=CM1 PID=2464 TID=5188 GMTDATE=Wed Jun 07 16:30:47.735 2017 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
  9. Here's a quick question, can a network have 2 primary stand alone SCCM servers in it?
  10. I installed Client Center for Configuration Manager and connected to 1 of my machines and it says that the client health passed.
  11. ServerA is setup to handle 99% of the machine, everyone that he can see. ServerB is setup to only see 5 machines that ServerA can not see. The clients on the machines that server sees do see him as the correct management site.
  12. Sorry, our system is truly air-gapped. We have no outside connection to it at all. What is the best way to know if your clients are healthy?
  13. Alright, did a little testing on a client and discovered this. With Windows Explorer open to monitor the CCM->logs I opened Configuration Manager Properties and ran the action Software Update Deployment Evaluation Cycle and noticed that there were no log files being updated.
  14. So let me give you our situation. We have an isolated network with a server (server A) running MS Server 2012 R2 and SCCM 2012 R2. We are replacing all of our machines, so with that we now have a server (server B) running MS Server 2012 R2 with SCCM current branch (v1606) installed in the same network. In an attempt to transition from SCCM on Server A to SCCM on Server B we altered a few things on server A. Discovery Methods Active Directory Forest Discovery has been turned off Active Directory Group has been turned off Active Directory System has been turned off Heartbeat Discovery is the only thing left on Because we do not want Server B to take everything over till we can get Server B to work correctly we have only set Discovery Methods Active Directory System is on Heartbeat Discovery is on By not having Active Directory Forest Discovery on the boundary was not made automatically. So we manually built the boundary with these settings Boundary Type – Active Directory Site Active Directory Site name: Default-First-Site-Name There is only one group Boundary Group and it has our 1 boundary in it. The component status was good for a few days and then I was getting errors on Site Status SUP and 2 (I don’t remember which 2) from Component Status. I had read something that made me look at the IIS Server (which is on Server B) and found that Application Pools -> WSUSpools was stopped. I don’t know why, but I restarted it and it has been fine for 4 days now. That also cleared up the Site/Component Status issues. SCCM (server B) would not install its own client; I had to manually do that. I current have 3 WIN 10 boxes; spilt into 2 collections and 2 Server 2012 R2 boxes in 2 collections. SCCM (server B) does see all the machines and sees what patches are needed for each client. I made a deployment for server B and for 1 of the Win 10 collections. And none of the machines have received any of the patches. When I look at the Software Update->A Compliance->Compliance 1 report it shows that the machines are not compliant. I’m not sure where to go from here. I hope I’ve included enough information this time. Any help would be greatly appreciated. Thank you
×
×
  • Create New...