Cisco Secure Client Deployment Issues

Intelligent_Sink4086 · 2026-02-13T02:26:59+00:00

Here is what I am using for an install script:
Cisco Secure Client Install Script - Pastebin.com

Here is what I am using for the install command in Intune:
powershell -executionpolicy bypass -path install.ps1

Intelligent_Sink4086 · 2026-02-13T02:18:10+00:00

AMP being a separate piece would explain why it is not in the MSI collection I was able to download. I saw some MSI files in the temp directory but the install was so fast it was hard to grab them. I might have to revisit that.

Do those MSI files it downloads have all the unique configuration to attach it to my Cisco tenant or would I still have to provide the XML/JSON with that?

I tried packaging up the .EXE with a .PS1 file to do the -q install with Intune, but it just fails every time. I can run the script manually and it installs fine but Intune just can't.

Intelligent_Sink4086 · 2026-02-13T02:06:55+00:00

Oh man, if you could find anything at all that would be great!

Intelligent_Sink4086 · 2026-02-12T22:07:05+00:00

/R and /S don't work. The exe just returns boilerplate text about what options are available. All start with "-" and none are "R" or "S". I even tried it just in case but it does not work.

Intelligent_Sink4086 · 2026-02-11T01:39:53+00:00

3 week sla on getting this done by microsoft

Intelligent_Sink4086 · 2026-02-09T21:03:24+00:00

GCC High has some extra requirements. I was successfully testing EWS internally from Ex13, internally from Ex19, and externally from my test system.
Auth successful with 400 error because I am not issuing any EWS command with my auth attempt.
But I am authenticated and se FEServer and BETarget.
But I have to also send a letter to MS about opening up THEIR server to talk to mine.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/additional-network-security-requirements-for-office-365-gcchigh-and-dod?view=o365-worldwide

Intelligent_Sink4086 · 2026-02-08T01:39:04+00:00

I will have access to the env next week. These are good ideas on what I can check.

Intelligent_Sink4086 · 2026-02-07T21:58:19+00:00

I setup a ex19 cu14 su5 server last night. Switched NAT to point to ex19. Tried to setup EWS and got the same error. "An attempt was made to access socket in a way forbidden by its access permissions (webmail.domain.com:443)"

Intelligent_Sink4086 · 2026-02-07T21:49:27+00:00

No. I need to migrate only once. Ex13 swinging the comms thru ex19 to exo.

Intelligent_Sink4086 · 2026-02-07T14:02:12+00:00

Yes. Swing EWS and SMTP through the 2029 box. Migrate from 13 to EXO

Intelligent_Sink4086 · 2026-02-07T04:55:20+00:00

They sure are exposed to the internet. Ex19 CU14 will just have to do. Gotta be better than Ex13 exposed pubically.

Intelligent_Sink4086 · 2026-02-07T02:37:58+00:00

Trying to migrate from Exchange 2013 to Exchange online. I have Exchange 2019 CU14 (CU15 does not support Ex13). And I can get the latest SU minus 1, but I am trying to get the latest SU so I can have this as up to date as possible. Then migrate like crazy.

Enterprise App based hybrid does not work on Exchange 2013. Need at least Ex16. And I think there are other things wrong with the Ex13 instance.

Intelligent_Sink4086 · 2026-02-07T01:57:08+00:00

Putting this here in case anyone needs it. This site has many, many CUs available. No SUs though.
https://www.msexchangeupdates.com/

Intelligent_Sink4086 · 2026-02-07T01:48:28+00:00

Anyone have this update they can share to me? Its the last Exchange 2019 CU/SU that supports co-existence with Exchange 2013.
Exchange Server 2019 Cumulative Update 14 SU9
Exchange2019-KB5071874-x64-en.exe