Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Adam Cook

Pages: 1 2 3 [4] 5
That sounds like the problem. At this time, you need to download and use the 32-bit installer.

It sounds like you have auto-publishing enabled and this is causing the Publisher to try and automatically publish TeamViewer because it has detected it as installed in your environment. You can right click on TeamViewer and choose 'Exclude from auto-publishing rules'.

Some products in our catalogue depend on a local folder, referred to as the 'local content repository'. Read more here:

Are you downloading the 32bit MSI for TeamViewer? Their 64bit installer is relatively new that we're yet to add to our catalogue, at this time it needs to be the 32bit installer.

We do supersede updates. Versions 15, 17, 20 and 21 are major versions which are still in support by Adobe.

If you no longer want these updates, deselect them from the Publisher and decline them in WSUS. Note: deselecting products in the publish does not remove existing updates from your environment, you still need to decline them.

Hey FabinaR

You can decline updates in WSUS using the Run Wizard tool in the Publisher:

Declining updates in WSUS and syncing your SUP will show those updates as expired in the ConfigMgr console.

Hi David

As far as we know, no. If you encounter any which need to be added to the list, let us know and we can review / update the page.

It looks like there's a new version available, too.

I've contacted the vendor seeking support on the issue, once we get a reply we should be able to fix:


We have similar concerns over the auto update of the apps which we want to test before rolling it out to production. Is there any article or guide that we can refer to for cases like this?

Appreciate any help provided. We are now running the trial version of PMPC - 1 week old :)

What information do you need specifically? This section here on this article details the right click option:

Hi, you can read more about the software on the vendor's website here:


For 0x80070643 / 1603, you can refer to this article:

For the others, please collect these log files from each example failing client and share them:



Could you share WCM.log, wsyncmgr.log and WSUSCtrl.log please? You might prefer emailing these to [email protected] as they will contain hostnames or IP addresses.


No problem, reach out if there's more we can do.

The new version (15.0.18384.0) was released yesterday by Microsoft so it should be in our next catalogue release.

That error code resolves to 1603 which is unfortunately generic and usually a client-side issue. Generally there's more detail in the vendor install log files or if you launch the installer GUI on the problem device. We have an article which discusses that here some more:

I looked at the KB for this issue as well as followed the video but I'm confused.  I've never stood up a separate software update point as the video suggests as a possible cause.

The registry entry cites J:\WSUS, which is the SQLTempDB volume.  I've absolutely no idea how it got there.  It's also got nothing in it beyond two folders WsusContent and UpdateServicesPackages.   
The SQL query cites G:\WSUS, which I think is where it's supposed to be.  That's the Content Source volume, and it's definitely got lots of contents, clocking in at three quarters of a terabyte.
The IIS Basic Settings cite C:\Program Files\Update Services\WebServices\Root as the physical path.

When I run the wsusutil.exe to specify G:\WSUS, it tells me:

Content location is being moved. Please do not stop this program.
Content move failed. Please refer to the log file for more details.
Fatal Error: The new content file location is the same as the old location: G:\WSUS
Parameter name: newContentPath

Should I move it somewhere else?

It sounds like you've got a bit of a mismatch as to where the registry, IIS (specifically the path for the virtual directory "Content") and the database thinks your content path actually is. I can help you get this fixed up but it might just be simpler over the phone.

The registry value, shared folder paths and IIS Content virtual directory path described here are the things we will all want to match with what SQL is referencing. Use this link to book a 60 minute call with me so we can take a look at this.

Pages: 1 2 3 [4] 5