Hi All,
I am currently deploying a Cisco Anyconnect upgrade using the toolkit via SCCM 2007. It works well for the majority of installations but around 10% are failing returning error code 255 to SCCM.
The toolkit calls a .cmd supplied by Cisco that references findstr and returns the following error to the toolkit log file:
"'findstr' is not recognized as an internal or external command,
operable program or batch file.
1==0 was unexpected at this time."
First of all I checked that C:\windows\system32 is in the Env Variables path on the laptop, and it is already.
I then ran the toolkit from the laptop running as my admin user, without using SCCM . The toolkit runs fine and upgrade succeeds. So its only when I use the toolkit via SCCM that the failures occur.
I am using version 3.2.0.
Any suggestions please ?
Thanks.
I am currently deploying a Cisco Anyconnect upgrade using the toolkit via SCCM 2007. It works well for the majority of installations but around 10% are failing returning error code 255 to SCCM.
The toolkit calls a .cmd supplied by Cisco that references findstr and returns the following error to the toolkit log file:
"'findstr' is not recognized as an internal or external command,
operable program or batch file.
1==0 was unexpected at this time."
First of all I checked that C:\windows\system32 is in the Env Variables path on the laptop, and it is already.
I then ran the toolkit from the laptop running as my admin user, without using SCCM . The toolkit runs fine and upgrade succeeds. So its only when I use the toolkit via SCCM that the failures occur.
I am using version 3.2.0.
Any suggestions please ?
Thanks.