GPO: ADMX Global Connected Script
Posted: Sat Sep 04, 2021 8:38 pm
Hello,
We are using the ADMX for Viscosity.
It looks like my batch file is being ignored by Viscosity. I did set it at "Global Connected Script" and did add "\\lan.domainname.ext\SysVol\lan.domainname.ext\scripts\User_SetEnv__Drive_Mappings.cmd". The extension is ".cmd".
I did poke around in the Viscosity client and I did notice I can use ".bat" and ".vbs" under "Advanced" > "Connected Script".
I can (probably) workaround this issue by renaming the file (rename {filename}.cmd {filename}.bat) or something like that. But it would be great to see if we can keep using .cmd files. I would like to suggest to add it to the "Advanced" > "Connected Script" options.
Thank you.
We are using the ADMX for Viscosity.
It looks like my batch file is being ignored by Viscosity. I did set it at "Global Connected Script" and did add "\\lan.domainname.ext\SysVol\lan.domainname.ext\scripts\User_SetEnv__Drive_Mappings.cmd". The extension is ".cmd".
I did poke around in the Viscosity client and I did notice I can use ".bat" and ".vbs" under "Advanced" > "Connected Script".
I can (probably) workaround this issue by renaming the file (rename {filename}.cmd {filename}.bat) or something like that. But it would be great to see if we can keep using .cmd files. I would like to suggest to add it to the "Advanced" > "Connected Script" options.
Thank you.