GarthMJ

So you drop your database and reinstalled SSRS? Or is your database remote to SSRS?

This is not possible without an ADR. Which IMO is a bad idea for anything but Virus defs. You know that you can't share WSUS with CM, CM will control any WSUS setup and it will cause problems if WSUS is used with CM.

The error message is clear... There is nothing more that I can do to help, I would suggest that you contact CSS directly for support, they will work with you to help you solve your problem.

The error message is clear.. Reinstall SSRS.

It means that all of these computers still exist within AD, I would check AD. It is also easy to see which Discovery method, is adding the record to CMCB. Look at the properties for the computer to see what is adding it to CMCB.

https://msdn.microsoft.com/en-us/library/ms832071.aspx?f=255&MSPPError=-2147217396

ok, I will bite, why do you care?

You error means, 0x0000098 = DosMuxSemWait did not execute; too many semaphores are already set.

This means that you are having SQL issues and need to fix your SSRS / SQL install. This has nothing to do with CM12.

As far as I know that unless you have an office add-on that required x86, you are better off with x64 version as it handles memory better. As for not moving to x64 OS, I completely understand that need to stay on x86 OS as 16-bit applications will only run on a 32bit OS.

No one can answer this question, only you can, as it will completely depend on your package.

So did you review the possible solutions listed above? Possible cause: Site server does not have sufficient rights to the source directory. Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory. Possible cause: There is not enough disk space available on the distribution point. Solution: Verify that there is enough free disk space available on the distribution point.

I love the first book. :-) https://www.amazon.ca/System-Configuration-Manager-Reporting-Unleashed-ebook/dp/B01EJXNJXS/ https://www.amazon.ca/System-Center-2012-Configuration-Manager/dp/9187445174/

BTW, what is wrong with the build in report for this? Don't get me wrong I'm not saying that you shouldn't create a report.. (I love reporting but... why do the extra work??)

First off, it is NOT supported to query the tables directly, you will need to fix your query. Secondly, it is not recommend to access the reports from the console, instead access them from the web interface, plus it is faster from the web interface. Thirdly, I don't see where in the query you tried to add the collection bit? Did you try to add it to your query? ; ay I see in the screenshot.. Move it up above the where section. Don't forget to fix your join statement. Tip: Write your query in SQL Server Management Studio, first before using RB. Tip: Stop using report build, instead use SQL Server data tools Tip: There are at least two books on how to write report for CMCB, They both give you tips on SQL and on writing reports for CMCB.

Why would you convert x64 to x86? IMO this make no sense, why do you care if there is a mix of x86 and x64? IMO you should only have x64 unless the PC is x86 (any way would you have x86 PCS these days?)

Only someone that works for Microsoft could possible answer this question as you should contact you TAM and ask them.

What have you tried? What error are you getting? Honestly, this should be exactly the same as what you are already doing already to put a short cut on the desktop.

If I remember right the last mod date is the last time that use logon to the computer.

What is wrong with the built-in reports for this?

No, plus there is not such things as a child primary in CM12 or CMCB.

This link will help you find the right log files. https://technet.microsoft.com/en-us/library/hh427342.aspx?f=255&MSPPError=-2147217396

What error are you getting in the log files? How long have you waited?

It would be more than the impact to the servers as to why you should never user SW Scan. SW scan has a 4 hour (runtime) timeout, once the timeout occur, the task is rejected and no results are returned to CM. So particularly for servers, you would never know if the server has no results or if the SW Scan failed to complete. Since SW scanning is runtime not realtime, your SW scans can take days… Yes I said days before it finally timeout. To top this off, while the SW scanning occurs, no other inventory task can happen. This mean you Heartbeat and Hardware inventory will never happen until SW scans are done. So… CM’s SW scans are useless. You would be far better off using a script or a CM CI script for this. As an aside scripts are usually executed as “Normal” process, therefore it will share all the “normal” CPU cycles but anything higher will get whatever it needs. You could run the script as “below Normal” task, this would take longer with less impact on the computer. This would still be far better than what CM SW scanning does.

Sure this can be done by CM12, but you will need to talk to Symantec and ask them how to uninstall their product, it is not something that CM12 will know how to do without you telling it how to do it.