GarthMJ

If you add the Class "B" as boundaries to the CM12 server then they will be considered Intranet and everything will work fine.

CM07 does support Windows 7 and Windows 8. You need to review the logs files to determine what the problem is. This blog post will help you. http://be.enhansoft.com/post/2013/07/25/Troubleshooting-Inventory-Flow.aspx

Because it take 2 second to run and it give you last logon user details. Hardware Inv should also be daily. Software Inv should be turn off or set to every 14 days as it is useless.

Based on your other post within the Technet forums. This info come from Heartbeat discovery. I always recommend that this be set to Daily.

BTW, Rob is in the UK too. ;-) He is (or was) the user group leader for the SCCM user group in London. He is a good guy to know, if you live in the UK.

All I do is increase the log file sizes until you get 3-5 days worth of logs. I don't understand your first comment. Retries of what? if you inboxes are overload it sounds like you either have aggressively settings or underpowered server with not enough IOPS. You second comment doesn't make sense when you take about Primary in CM12. Primary site are NOT security boundaries like they are in CM07. Remember that alot of stuff is global data and therefore share between primary site and therefore one group CAN affect the second group even if their are two primary site. Also remember that it is STRONGLY recommend that all administration be done at the CAS not at the Primary sites. ONLY RBA can use to resolve this problem (I have used to several places for this exact reason) OR Two completely different primary sites that don't talk to each other at all, again would be far similar that adding a CAS into the mix.

It is not possible. Why would you want to discovery disabled users?

A CAS will NOT protect you in this situation, there are no, if, and, or, but about it. With 5000 devices you need to stay with a simple primary server and use RBA to preform role separation.

Yes.. :-) You need to 2 datasets if you want to create a drop down menu. You need only 1 dataset if you want freeform text box. or if you want to hardcode the Collection. Personally I would go with two, it make the report much clearer looking.

You can do this using dbo.v_FullCollectionMembership the SQL view and preforming a inner join on ResourceID between both SQL views.

Don't worry about it. Best of luck getting this fixed up.

Ok, Now I see where you are trying to go and what the issue is. No one will be able to answer this question without first looking at the query you are trying to run to grab the data for your CMDB. Assuming that you are populating your CMDB every 24 hours, it could take ~48 hours for data from CM12 to get into your CMDB. There are a number of variables that will increase or decrease this time. IMO this is starting to become something that can't be easily answered within a forum and as such you should look at hiring a CM expert that can help grab the data from CM12 and get it into your CMDB.

I'm completely confused. At the beginning of this post you talk about discovery taking days for a PC to show up but later in the post you say a PC shows up within 10 minutes. Go back to the beginning, exactly what problem are you trying to solve? aka why do you think that there is a problem at all?

Again, where are you looking for these details? Resource Explorer, Reports, Collection, ????

If you have you HW inventory set to daily then it will happen every day, once the CM12 client is installed. BUT... That does NOT mean that it will show up within all collations within 24 hours. Hence the reason why I asked where are you looking for this details. Are you looking for it within the All Systems Collection? On top of that it could take a while for the PC to get the CM12 client installed. So why do you think that it take 4 days for the client to show up? Exactly what troubleshooting steps have you taken? Have you confirmed that the PC is listed in AD? Have you confirmed that the PC name is resolvable by DNS? Have you confirmed that the CM12 client has been installed? How is the CM12 client getting installed? Exactly where are you looking for the client in CM12?

Hardware Inv. should be call System Discovery as it will find everything about the system, (Registry, Add/Remove program/ AI, BIOS, HD, RAM, etc.) Software Inv. should be call file inventory. It will ONLY find file header detail and ONLY find it for those files you tell it to. I recommend even using it, particularly if you have AI inventory classes enabled. Heartbeat discovery is a special discovery method, think of it as a really, really lite version of HW inv. (Name, IP, MAC, User Name, and a few other details). This one is so quick and so small that running it every hour will have little impact on either your CM12 server or end PCs. if it does then you have much bigger problems.

I'm a bit confused why do you say that you have discovery enabled at 11am ever day? you AD discovery is setup to run every 7 day at midnight and it look like you have delta discovery enable and the default is every 5 minutes. When a new PC is created does it not show up within the All systems collection within ~10 minutes? You don't want network discovery.

I hate to say it but this is not a 5 minute task that can be easily explained within a forum. My first recommendation to you is to learn how to edit/write SQL queries, without that there is nor poihnt at looking at Report builder.

Which discovery are you talking about? AD or Network? How do you have you discoveries configured?

Assume that you have 10000 PCs. If you schedule that to occur at the predefined time say 9PM, you are then forcing every one of your PC to talk to your MP at 9pm. Then you are forcing all 10000PC to send their HW Inventory all at the same time. This will cause a backlog on the site server that will take time to clean up. It get worse if you also tell the PCs to do all of the other task at the same time. SW, Heartbeat, SU Scan, etc... It is not best practice to schedule these tasks, it always best practice to use a simple schedule as this will allow all of the inventory/scans to occur over several hours generally from 6am - 10 am. Thereby not overloading any particular part of your network or CM environment. On top of that if any PC is turn off at 9pm, they will perform these same tasks when the PC is turned on next and therefore you are not protecting them at all from the "risk". IMO there is no risk to any of the clients using the setting that I have suggested. I know that most of the other MVPs will also recommend similar settings. Particularly with respect to SW Inv. SW Inv is the only Inventory task that client will "feel" and most of the MVP will recommend that you turn it off or have very strict guideline about using it.

Actually I don't recommend scheduling a time for the inventories to occur as this will affect your site server performance. I always recommend that you use a simple schedule and depending on what inventory task it is, they have different values. IMO only SW inv. will have performance issues on end clients. HW tends to be ~80 seconds and Heartbeat is ~1 second, I have yet to see any client notice either of them. HW Inv. every 1 day SW Inv. Disabled or every 14 days Heartbeat: every 1 day or once hour; depending on needs of the client.

Do you have a simple schedule or a custom schedule? As Peter says the cached HW inv will be upload when the PCs connects to the network.

Have you edited a report before? if yes then adjust the query to add the new view and column, then add the column to the table. if not then this is a much bigger task.

Sure you can edit the report and add it. You will find the Processor name under the v_GS_PROCESSOR in the Name column.

In CM12R2 the SSRS folder is called Upgrade Assessment.