I would confirm by reproducing the behavior with psexec –s to emulate the SYSTEM account.
Otherwise, doing a runas is either a task sequence or some PowerShell, but trying to store credentials in the script is highly not recommended. You may want to also look into a compliance script, as that would ensure it is always set properly. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Richard Poole Sent: Friday, December 11, 2015 11:26 AM To: [email protected] Subject: [mssms] Netsh running as LocalSystem account Hi everyone, I’m encountering something odd and hoped someone else out here has seen the issue and know of a workaround. We’re upgrading systems to Windows 8.1 at remote sites that only have a Windows 2003 file server they’re connected to. Apparently there’s a known issue doing this that causes everything on the workstation to just slow to a crawl, with the fix being to disable the autotuning level. I’ve created a blank package in SCCM 2012 R2 with just the program command “netsh int tcp global autotuninglevel=disable” in it. After it runs the settings are good and performance noticeably better, but after a reboot the settings go away and user is back to a crawl. Run the same command from an admin account on the system and the settings stick after reboot. I could just create a task sequence with the command line to run as another user, bypassing the LocalSystem account, but was hoping someone out there knew of a better option. Thanks, Richard Poole The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
