GarthMJ

#1. If you have a CAS then it mean that you have 150,000 computers. right?? If not you really need to re-look at your CMCB infrastructure. #2. IMO there is no need to completely duplicated you environment, it only need to represent it. Since you have 150,000 computers, 8 DP will not be enough unless you are us ACP. 8*4k = 24,000 computers. #3, Software updates along will take up a ton of space....

#1, Get rid of the CAS, unless you will have 150,000 computers, you are begging for trouble. #2, 3TB of space will get used up quickly if you have 8 DPs. Why so many? #3, 64 GB of RAM is not enough for this setup. you need 12 GB for each CAS/Pri that is 60 GB alone for those servers.

The computer that is causing the problems is listed within first screenshot.

By default Domain Admin are NOT SQL admins and therefore this make perfect sense.

So Here are a few questions: What version of SSRS are you using? Have you applied all the SP and CU to the SSRS server? Have you checked the Firewall between the two servers? I assume that SSRS is remote from CM Are you trying to install the RP on the SSRS server?

yes that is correct.. No enough coffee. :-)

First off, can you access the SSRS websites?

No, you have use Reg2mof to collect HKCU. You only method to collect this data is to script it and store it someplace that CM can inventory it.

A lot of time these hash errors are caused by WAN accelerators. So check withy your networking team.

Since you are posting in two different places and you are NOT posting the exact same details to both forums AND you are doing different things between each forums. You must pick one forum to work on your problem and abandon the other forum post.

Did you review the msi log as suggested in this log snitit? You can't just run the msi manually. it must by run by CM site server. Are you post this same question in two different forums?

Have you review the RP setup logs? What about the srsrp.log?

There isn't a lot you can do. However I would keep your package a small as possible. Work with the Network team to get those links increased in speed. Adjust your SLA to match what is realists. Without throwing the network team under the bus too much, make sure that management know there is an issue. Work with the Network team to setup QOS between your site server and your DPs, this will ensure that you get the BEST possible throughput.

Are you sure that BITS is not configured. Your problems sound very much like a BITS being configured with very small BITS setting. BTW BITS should not be disabled, it is used by CM to download content from DPs.

Have you checked your BITS settings? What about AV setting?

Client will never move between sites. You will need to either update the site assignment or reinstall the client.

IMO, only in RARE cases will you fine that the SW will install 100% of the time without any interaction from a user. For example look at MS office, you need to customize it first before you can deploy. That customization maybe as little as adding the license key details. In most companies, If the user is prompted for anything during the install it will mean a call to the helpdesk or worse yet they install it wrong and now a tech has to visit the PC. Automating the install also meaning testing it, defining who the owner of the SW is, therefore is responsible for upgrades and defining EOL for the SW. There is a lot more to it than just adding SW to CM. Do you need WinZip, 7zip, etc? or will one do? Who says yes to one SW and no to the other? Should you?? When something goes wrong who will troubleshoot this issue? This last one is a HUGE issue for custom SW that always exists, in companies.

Personally, I would define that SLA time for the private company to automate the install. I would ensure that their count of 10 is for an automated install and not just a imported program. Define who will control licensing Define who will control reporting Define HOW application are deployed, to user, computer both. Are they deploy to a security group (either user or computer), direct membership, WQL query, etc. Define how SW upgrade process works. Define how SU deployment process works etc...

Sure if you don't automate the install. And that is one of my points too. You can fairly easily do everything if there is no automation. There is even added bonuses in doing so but there are also draw backs too. Pros: You know what content is used to install the SW Your Techy's don't have to keep a "install" SW share User's can do the install if setup correctly. Cons: You have to have all SW on all DPs You will have SW with unknown owners. aka who is responsible for upgrading it to the next version? Who controls the licenses for it? The install will be different for each computers There is no wrong answer here as to what could be done. But I love the options. :-)

Start with this blog. http://www.enhansoft.com/blog/updated-troubleshoot-configmgr-hardware-inventory-issues Does the first step even happen?

This is loaded question. Personally, I looked after 20k of PC and we started with 50 computers was the cut off. But after about 2 years it drop to 20 then to 10. Why because we couldn't handle doing every tiny little app. But as we got better and has time. We kept knocking off the biggest time wasters for the helpdesk. As a consultant I have worked at places where no SW can be installed without CM. IMO This is not truly workable as are you going to play a senior CM guy to package SW in an automated fashion? OR is it ok for helpdesk to install the ones and twos? What about does the SW need to be automated, aka install promptlessly? Or is it ok to install it with prompt is the HD tech does the install. So is your question about having it promptlessly for applications?

It say to reinstall the CU on the server, so what is the problem?

Correct you will need to script it. using UDI will create the interface but that is all.

You can't, you would have to write a custom script/ interface for this.

No there is not and that is by design too. It is useful to the user to know what is not vs what has been there for a while. Plus it is easy for the user to change the sort option.