(imported topic written by menke123491)
I’m trying to deploy a fixlet to run netsh to re-configure WINS addresses. I’m running into, what I’m guessing is, a permission problem.
I’ve tried creating a batch file where each netsh command is run separately, e.g. “netsh int ip set wins…”, “netsh int ip add wins…”, etc. I’ve tried creating a netsh script and invoking it via “netsh -f scriptname.txt”. I’ve ran both scripts under the System account (via both “at” and using psexec) - and they work fine.
However, when deployed through the fixlet, they don’t work completely. For example, before running the script, I have WINS servers 1.1.1.1 and 2.2.2.2. The batch file invoked through the fixlet changes the WINS servers to 3.3.3.3 and 4.4.4.4-
netsh int ip set wins name=“Local Area Connection” source=static addr=3.3.3.3
netsh int ip add wins name=“Local Area Connection” addr=4.4.4.4
After running the fixlet, “ipconfig /all” continues to report 1.1.1.1 and 2.2.2.2 and I continue to see WINS traffic to those two addresses. Interestingly, “netsh int ip show wins”, the registry, and the gui interface properties show the new addresses - 3.3.3.3 and 4.4.4.4. It’s like the command makes the changes, but can’t quite commit them.
I’d think it was a netsh issue, but again, it works fine - run under the System account - outside of Bigfix. Are there any other restrictions on running commands through the BES client?