I ended up configuring the ASA device to use two different scripts for Windows clients when they log in. I searched for a different way and finally came up with the fix which as it turns out so much less complicated than the way I was originally trying to do this. Some clients have differing AV clients which might block files from being downloaded. We recently replaced the NAS device this share was hosted on which for whatever reason resulted in certain clients being unable to access the share and thus download the PowerShell script for execution. This worked fine initially and got the desired result. The batch would then execute the PowerShell script that was downloaded. This batch script would connect to a Windows share on our internal network, copy down a PowerShell script along with the related support files to the users local machine. Originally what I did was create a batch script that was executed when a user logged into the VPN. I know this is somewhat old now, but I wanted to add how I ended up finally fixing this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |