About this tag
Discussions tagged with server interference on WindowsForum.com focus on login script failures in Windows Server 2012 R2 environments. A common issue involves net use commands returning System error 67 (network name not found) when executed via batch scripts at login, while manual execution in Command Prompt succeeds. The discrepancy arises because scripts run under the SYSTEM account rather than the user account, leading to permission or network path resolution problems. Troubleshooting steps include verifying network share accessibility, checking service account permissions, and ensuring the server name resolves correctly under the SYSTEM context. These threads provide practical solutions for administrators facing similar script execution errors.
  1. mardique

    Windows 7 Login script not working

    I know this should probably go in the networking subforum but it's kinda deserted and I need an answer fast. I have a 2012 R2 server (alone) and a Win 7 station. My login script is very simple, it's only a few net use commands (net use :G /delete - net use :G \\Server\Folder). But right now...
    • mardique
    • Thread
    • 2012 r2 access issues batch file cmd file sharing net network network drive permissions script execution scripting server interference system error troubleshooting windows 7 windows server
    • Replies: 1
    • Forum: Windows Help and Support