GarthMJ

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.

You absolutely should be using full blow SQL and NOT WID. You also need to make sure that WSUS clean is done. In a lot of case it make more sense to remove the SUP, uninstall WSUS, drop the DB, reboot, install wsus, install SUP. I would also install SQL on the WSUS server.

Is the client healthy? Has the client download the policy with the new SU deployment? Does WUA see that the update is required? Did you trigger the SU deployment scan cycle? Did you wait 30 minutes for it to finish?

lol, that last post wasn't meant for you.. please ignore it.. Give me a few minutes to re-read the whole post.

The IIS logs are on your site server. This blog will show you how to find the MP logs but the same steps can be used for WSUS logs too. http://www.enhansoft.com/blog/where-are-my-iis-logs

First off, it is recommend that you access the report from the web interface and not via the console. Secondly, What do you mean by "go on" , all those computer listed don't have the SU install so, deploy it to them.. if any computer had an error it would be listed within comp 6 report as an error.

if this is a VHD, why set the disk to such a small size? why not use a thin vhd with a size of 128?

So what does the IIS log say is going on?

yes that is the right one.. so every 7 days.. Now how often are you syncing the WSUS database with MS? Have you turned the client policy settings back to every 60 minutes?

Wow 10 minutes.. that is WAY too often! it should 60 minutes... As for SU scanning that is also a client setting, you will find it in the same place as the client policy settings.

How many clients? Is it a MP, SUP or DP? What exactly is your policy cycle? 60 minutes? How often are you scanning for SU?

You can set to ASAP and they will not install until the first available MW they below too occurs and the MW type applies.

Why not? what exact do the log say? why exactly does the next VNP setup say?