GarthMJ

Basic solely on what you have posted, my original design stands.

Since the forest has already gotten Schema extension there is nothing more to do. You other domain has everything it needs. Why can’t you push to domain B? What error are you getting? Domain A&B already have a full trust because they are within the same forest.

You not really giving a lot of details but bases solely on what little details that you have given, a single primary site leveraging branch cache will be all you need.

It is because you are querying the wrong thing. You query will tell you the MAC address of your clients, not of all of the MAC on the system. Instead you want SMS_G_System_NETWORK_ADAPTER.MACAddress to get all of the MAC address.

So exactly what is the problem? You remove their rights to edit those collections.

This will get you started. http://smsug.ca/blogs/garth_jones/archive/2008/02/04/basic-all-in-one.aspx

SQL is used for Report, WQL is use for Collections, In either case you will find lots of example here. http://smsug.ca/tags/WQL/default.aspx

CM12 is not a real time product, you would be better off look at OpsMan for this.

When you restore you MUST restore with the EXACT same layout as before. The space can be adjust if needed. It is not supported to edit the database and there is more to it then just editing the database.

You will need two WSUS servers.

No it doesn't help.. it doesn't tell you what is failing.

First off you don't need a CAS unless you are over 100,000 computers and if you are over 100, 000 computer then you need to change SQL versions to Enterprise. I quickly looked at your log file and I don't see any errors in it. Can you post the log with the error in it.

The simple answer is WMI and how CM12 queries it. if you want more than that you will need to contact your TAM and get them to give you and official support statement. But IMO why do you care if you need to replace a DP and it has a new name? Client will get the new name form the MP and therefore will know about the new DP within an hour so....

I hate to say this but there is nowhere enough details for anyone to give you a recommendation. I would start by hiring a senior consultant who has experience with this type of thing, there are not many worldwide. In the meantime, start documenting your network, network speed, # of user, what existing at the site now, what problem exist at the site, expected growth, etc. Keep you primary sites to a minimum. Each primary site that you add, serious increase the complexity

This is not going to be supported. So why are you trying to do this?

Yes, sure it is not the answer MadMacs77 was hoping for but IMO there is a much bigger issue here that just ADSS. <After re-reading this and still on my first cup of coffee, this seems preachy, but it not meant to be. > If you are you are going to “clean up” AD then you really need to do a full health check for that you need to look at: Network Network speeds Network latency Network reliability. AD itself Replication Workload Etc. ADSS DNS Is DNS working correctly IS DNS savaging turn on? DHCP IP Addresses IP Subnets Masks What is your DHCP lease time Each DC All the OUs All the GPO All logon scripts Get a list of all known issues, etc. </end peachy stuff> Now getting back to the ADSS and should you create a site for a network without a DC. It will depend on a lot of things. I have created ADSS for force GPO setting at a particular site (BITS setting for example) but rarely will I do it for anything else if there are no DCs at the site. As an aside, I personally don’t recommend using AD sites for CM07 or CM12. The reasons are supernet and outdated subnet details in AD. The bigger your environment the more likely they will not be up-to-date. I recommend IP ranges and if you have a single site the 0.0.0.0 – 255.255.255.255, works great! ;-)

ok, so what??? Can computers and users logon, I'm willing to bet yes. So exactly what problem are you trying to solve? Without this answer, there is no point in moving forward.

The SU reports don't use QFE for their result, they use WSUS data only. If you are not seeing results, it is because those computer are NOT reporting to CM12 for SU.

It will depend on what you are trying to do and why. Why exactly are you trying to clean it up? What problem are you trying to solve?

ok, I have already told you what the process is, there is nothing more to it than that.

Let me put it another way. It is complete not supported to do that.

Again, not all columns in CM12 will show the Full Version #, some will only show the SP version#. If you are saying that within one column you are seeing some with the updated versions and other without then yes there might be a problem. Generally HB will fix this but I just review the inventoryagent.log and the CM12 client version is NOT listed as one of the fields queried, therefore I'm not sure what actually updated this.

This is normal, not every place list the FULL version number. it will only list the last service pack version number.

No the assumption is that an administrator knows exactly when the best time is to install and application. However you can get fancy and use the app model to no install on servers or no allow the app to install on server OS but IMO why care... If an administrator install the application and reboot the server, why should you care?

yes that is right.