Jump to content


GarthMJ

Moderators
  • Posts

    1,939
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by GarthMJ

  1. Who found this? Where exactly are you seeing this? Why do you care about it?
  2. a quick internet search revealed lots of blogs on the subject for example this one https://blogs.technet.microsoft.com/servicemanager/2009/12/17/service-manager-connectors/
  3. Unless your lab is an EXECT clone of you production environment, the restore will not work. When I say exact clone, I mean you need to clone your DC too! It can't be a forest/domain with the same name, it has to be exactly that domain/forest.
  4. OU, is not always populated by AD discovery, it is also populated by heartbeat discovery. Similarly, Security groups are populated by Heartbeat discovery too. As such I never recommend using that query style instead, use a direct membership for the Sec group. This allow computers to install the SW (assuming that is what the collection is for) without having to wait for heartbeat discovery to run.
  5. No, CMCB is NOT a CMDB, However SCSM (Service Manager) is a CMDB and you can do that with it.
  6. No don't change it to slow, keep the site setup for fast. Once your MP, AD extension and the boundaries are right, client will automatically start reporting to the site.
  7. If it is manually entered then you should enter it directly into the CMCB. There is no point in "shoe horning" into CM.
  8. Just to be clean CM is NOT a CMDB. CM is not intended to store the data that you are looking for that is the job of a CMDB. The company that I work for does have product for some of the items you are looking for.
  9. CM is not a CMCB, as such it is not the right place to store this data. However CM is a great tool to collect data. You will need to look at 3rd party tools to collection some of this data. However not all of it can be collected for example IP Phones.
  10. Remember a lot of the console data is cached. Reports will always show you live data. Personally I would never setup an ADR for SU, only Virus defs. Also remember that depending on how to setup your ADR, it can take time before it is seen and deployed.
  11. if you are going to create a PowerShell script to collect, I would take this one step farther and Tattoo the image version in either WMI or registry. This way you can inventory it was Hardware Inventory. I would also make sure that you update your TS to do this as well.
  12. ok, so there is nothing wrong with CM12 as it is reporting exactly what the cleitn detects. There is nothing wrong between CM12 and the end client as the results on the client are exactly what is on the client. There is nothing wrong with the Client itself as the CI is executing and giving results. So this mean there is a problem with the CI itself. First off I would avoid using a "/" in anything as it is a special character in C. Instead try 247, does that work? Secondly I would change the detection time to 1 days. I personally find that anything less that 4 hours seems to have problems.
  13. Just to be clear, When you run the compliance check on the local computer, Report on the local computer show as being compliant or not?
  14. yup, I need more coffee. Normally I do everything via report.. So are you sure that you don't have two computers with the same name? I know that seems like a dumb question but look in the All system collection to be sure. Have you force the client to recheck it status? Does it update in the console?
  15. So where are you seeing within the console that it is compliant for that PC? I might need more coffee, but I'm not seeing it in mine.
  16. So why have RP remote from the Primary server? Where will SQL be installed for the SUP? Why have DP with 16GB of Ram? What have SS at all? Without your network layout there is no way anyone can tell you that 16 DP and SS is a good idea.
  17. The best advice I have give you it to not over complicate CMCB environments. Keep it simple. Why would you want two WSUS server? WSUS is only used for detecting in CMCB.
×
×
  • 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.