Page 1 of 1

GPO: ADMX Global Connected Script

Posted: Sat Sep 04, 2021 8:38 pm
by bouke

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.

Re: GPO: ADMX Global Connected Script

Posted: Mon Sep 06, 2021 9:57 am
by Eric
Hi bouke,

Thanks for the feedback, we'll look into supporting the .cmd extension in a future update. In the meantime I'd suggest creating another .bat file on your network share that simply calls your .cmd script.