Messages

Hello nithin,

Thank you for that information, however I am fully aware where to download the files from and the same article you mention, I also posted it above.

Let me clarify my questions.

In that article it says to place only the "Secure Mobility Client" in the local content repository, however that is a file found in the older version 4.x which as you know, is EOL March 2027.

I am trying to ask what file from version 5.x goes into the local content repository as the primary file before all the other modules as there is none named "Secure Mobility Client"  (note, in the article there is an item in the Publisher which says 'Full Client' but this is no longer there)

and secondly, in the Publisher, which option do I select for that specific file I placed in the repository?

Hello all,

Going thru the step by step on this page
https://patchmypc.com/how-to-bundle-cisco-anyconnect-modules-to-install-in-a-specific-order

However when looking for the file to store in the local repository, there isn't a 'Secure Mobility Client' for the latest version.

Trying to run the Umbrella Module tells me that it is looking for Cisco Secure Client, which I believe is the 'Setup' in the Zip file we download from Cisco.

What option in the publisher should we be selecting now since most of the information and steps are for the previous AnyConnect version 4.x.x.x?


Thanks in advance for the help

Thanks for this Nithin.

I was rattling my brain looking over the scriptrunner log and one thing that kept standing out to me was the amount of time it said it took for Team Viewer to install, it just didn't sound right to me

"finished with Elapsed Time: 00 minutes 09 seconds 292 milliseconds"

I just kept thinking that the installation takes much longer than 9 seconds to complete

The content of the PS1 scripts is as follows


$assignmentID = 'Our API key'
start-sleep -seconds 10
start-process -filepath "C:\Program Files\teamviewer\teamviewer.exe" -argumentlist "assignment --id $assignmentID"

We can manually run this Powershell script and devices would join so we know the script works outside of Patch My PC


Two days ago after posting this thread, I decided to up the amount of seconds from 10 to 120
All of a sudden the next 10 test machines are installing and assigning successfully. Seems Patch My PC was trying to run the script too soon, making it run 2 minutes after installation gives TeamViewer enough time to complete properly then can be assigned

Hello all,

Silly question, but when deploying TeamViewer updates/install via Publisher, we have in the past had a simple Powershell script to call up the application, then assign it to our account.

As of a few updates ago, the same script appears to fail to run. Tested on a few different machines and looking at the ScriptRunner log it would say the PS1 script ran, but the app is not set for Easy Access as intended.


Yesterday I noticed the Cloud version can deploy TeamViewer 15 and I also added the Powershell script to the Post Install section, tested on another machine and same thing, it doesn't assign to our account.

Is anybody else experiencing this or have a solution?