GarthMJ

Anything is possible. How would you do this programmatically? Once you can answer that questions, it fair easy to update this for CM12.

Can you access the RP using IE? Do reports work in IE? The simplest solution is to Remove you RP and Re-add it. this will tell you within the Logs what the error is.. But my guess is a permissions or SQL CU issue.

What report are you running? Is the AI sync point enabled?

Are you sure that they are coming form WOL and not PowerManagement?

No you can't manually add the user to CM12. It would be the ad Discovery logs. AD*.log

It is very common to have issue with quote marks within blog post, But other than that all SQL query should work. Again without any details as to what errors or issues you are having, there is very little anyone can do to help you.

Install the SCOM client. All of these items are nativity collected by SCOM. Keep in mind that you will need to purchase a license for each computer.

I hate to say it but you are barely giving anyone anything to go on. Have you imported/edit the MOFs yet? Have you confirmed that SQL is being inventoried? Which query did you try in each post?

1. yes, if you query is written right they will automatically fall into the correct collection at the next collection refresh cycle. 2. Your query will only ever find computers that have the CM12 client installed. If they don't have the CM12 Client install, then they will never show up within the collection but they might show up within the All Workstation collection. It will depend on how you have written your All Workstation collection. 3. That not exactly what Sherry is suggesting. In the console if you type HT to find all HTxxx computers within the All Workstations collection. Then you would get any get all computer with HTxxx for the computer name AND you would also get all computers with a user that has HT in their user name too. Therefore make sure that you counts are correct. 4. I hate to say this but, if this is a bug, it is going to be in the way you written your collection queries, but it will not be a bug in CM12 itself.

Without your queries for each collection, there is very little anyone can do to help you. When you delete a computer for CM12 it will removed it from all collections not just one collection.

You don't. This is not a task that can/should be done with CM12. This is a task that should be done with SCOM.

Have you review the log file to see why the user is not being detected?

Nope, you will need to rebuild everything. You can't move anything to the new CAS. But why have a CAS in the first place. If everything is going to be at one DC then there is no point in have a CAS and to primary sites until you are over 200,000 computers.

This is not a question that can easily be answer in the forums. Your best bet is to contact your MS licensing specialist and talk to them. But as a general rule you will not have to pay anything for VMs.

There not much to tell. Client content to the DP, download to their cache fold and run the install. If the content doesn't exist nothing will install. Don't touch the share/file permissions for the DPs, CM12 will set them correctly.

What source folder are you taking about? the DP itself or the source files that get copied to the DP.

Go over their heads, to their manager. This site is clearly not working and therefore it is their problem to solve.

If this is just after you had you site restored then I would go back to CSS and tell them it still not right. Making sure that you get inventory and deploying both SU and App/packages is a fundamental task of CM12. If this was nto tested after the restore then IMO the job is not done yet.

Nope, there is no license need for DPs.

Anything can be done if you write the script to do it.

What wrong with the built-in query for that? It can be use to create a collection.

The answer is always going to be it depends.. for a CM Lab you will need. 1 VM for your DC 1 VM for your CM12 server 1 VM for your test client This means, you really need ~13 GB of RAM just for your VMs. if you can give 1 core to each VM that should be enough. As with any lab the bigger the better.

First off, Why does it matter? Secondly, none of my Hyper-v VMs has a floppy drive. Not unless I enable it.

Simply create DP at each location, when setup correctly this is exactly what they are for. Don't forget to "protect" them.

You need lots of RAM and SSD are really nice to for this type of thing. But honestly why not use VPN or Direct access to access a real lab?