Jump to content


lark2056

Established Members
  • Posts

    13
  • Joined

  • Last visited

lark2056's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I am having some weird behaiour in my SCCM environment. You know how in the folders on the clients where the updtaes are supposed to go. C:\Windwos\system32\CCM\Cache\44444dkjdd-87dfsdf-sjsuejcu-.......... the last folder being the long name and inside it is the update. I am experiencing an issue where the folder gets created when the client goes for the update, but the folder remains empty! I cannot get the update to show up. How does the folder get created yet the folder remain empty? Very weird. Has anyone ever seen this? Thanks! Ken
  2. that was it. Thank you Sir!!
  3. Can someone tell me why my updates are failing to reach this host from the message in the WUAhandler.log below? http://DN1DRWSUS01 and Policy ENABLED]LOG]!><time="10:06:55.304+360" date="10-15-2009" component="WUAHandler" context="" type="3" thread="2208" file="sourcemanager.cpp:1107"> <![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({B7E9F409-10EC-4604-847A-67777AEEE793}). Error = 0x80040692.]LOG]!><time="10:06:55.304+360" date="10-15-2009" component="WUAHandler" context="" type="3" thread="2208" file="cwuahandler.cpp:2358"> Any and all responses are greatly appreciated!! Ken
  4. when I am in a collection and I right click on a computer to go to start > resource explorer. Then expand hardware, the windows update agent is not showing up? Is there a setting somewhere in my domain where it can potentially be blocked and I am not allowing it to check in to SCCM? I know the latest windows update agent is on my client, I just cannot get it to show up in the resource explorer under hardware. Any ideas out there? Thanks!
  5. We have an environment where someone put out Windows 2003 SMS along time ago. This was unbeknownst to us. I had put out system center configuration manager, and when it went to do it's discovery, it came back with all of these machines with the old SMS 2003 client on there. There were over 300 of these virtual machines with the old client on there. So what I did, I went to every machine and ran the CCmclean.exe /all on every box just for good measure, as opposed to the upgrade to the new client. So now all of the virtual machines do not have the client on there, but almost all of them still show assigned as a client with an agent. I have right clicked on All Systems and executed the Update collection membership several times adn they still show up the same. I am trying to think of my options. 1. Do I just be patient and it will eventually show up right? 2. Should I delete everything form the collections and then do another discovery? I am just curious as to what you all might do so I can have everything show up correctly. This is a stand alone site in Mixed Mode. Thanks!! Ken
  6. OK, here is a good one. I have 4 sites. I will list them and then give their domain and site code central primary DOMAIN1 ST1 child Primary DOMAIN2 ST2 child Primary DOMAIN3 ST3 child Primary DOMAIN4 ST4 We like to manage everything from the central primary site DOMAIN1 ST1 I started to update some old SMS2003 agents in the DOMAIN4 ST4 area with the new 4.0.xxx configuration manager agent before the errors started showing up. On the central primary site, we have some collections that were created for the DOMAIN2 ST2 area. The collection for all the servers in that domain. They usually show up just fine. name, domain, and site code. There are 300 servers in that collection. Just yesterday, I noticed that 40 of the servers in that collection started to show everything normal, except they had their site code listed as ST4!!! This is all at the central primary site. Everything at the child Primary DOMAIN2 ST2 looks fine. Its just at the central primary site when I look at that collection that was made at the primary site for that domain, that 40 of the servers are showing the correct domain, just the wrong site code, ST4 How can this happen? Is there an action I could have done to cause this behaviour. I have updated the collection membership I don't know how many times. Hopefully, someone has some insight to this. Thanks. Ken
  7. Is there a wait time unitl a client shows up under client as "yes" in the collections windows? I have installed a client for one of my windows 2003 boxes. the Icon shows up in the control panel and it is looking at the right site. It even has my SMS Agent Host as started in services. Just wondering if I am being impatient or if it should show up right away. Thanks.
  8. I was able to figure it out. I removed the distributio point role and then it went away under the site system status area. Thanks for all of the help. I am the one who installed this guy. I can't explain how that role got there, but I am glad it is not there anymmore.
  9. No, the parent site does not have the PXE Service point role on it. I did a search in the registry and I did find under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Components\SMS_WINNT_SERVR_DISCOVERY_AGENT that their is a key for Discovered Site Systems and this one does show up below in that KEY. <SMS Distribution Point><["Display=\\DN1DRSCOM01\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=DN1"]\\DN1DRSCOM01\SMSPXEIMAGES$\> I wonder what would happen if I just deleted that line in that key. If that would cause damage to SCCM.
  10. Nope, not listed there. That is what is so strange. I never installed that role, yet it looks like it was there at one time. I am not sure if their is a clean way to get rid of that without messing anything up.
  11. It doesn't show under Site Systems. It only shows under the site system status. Thats the thing. I know I didn't choose PXE Service point. And now it looks like I did install it, and then uninstalled it, and it shows up as an error. I have attached a screen shot. Document.rtf
  12. I have installed a child (primary) site in our disaster recovery site for my company. The issue I am having is that under Site Systems, on of the roles I have is SRVDRSCOM01\SMSPXEIMAGES$ as a config manager distribution point. (SRVDRSCOM01 is the name of my server.) Plus that share does not exist on this server. It is showing critical. But I have never installed the PXE service point roll on this box, which is what I beleive this role is for. I need to know how to cleanly get rid of it. How do I get rid of a role, for a role I never installed? Any help would be greatly appreciated. Ken
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.