Windows 10: Windows Defender Latest definition blocking a vbs script used to map drives at logon

Starting with version 1051 update, Windows Defender managed via System Center Configuration Manager is blocking a vbs script we use for drive mappings during customer log on. The message being displayed is "Microsoft VBScript runtime error: This script contains malicious content and has been blocked by your antivirus software.: 'Run'". It categorizes it as a

Trojan:VBS/CoinMiner!ams.

Alert level: Severe

Status:Active

Data: 8/8/2018

Recommended action: Remove threat now.

Category: Trojan

Details: This program is dangerous and executes commands from an attacker

Affected items: amsi: VBScriptf9333915020759f0


I have verified that the vbs script being ran is not infected

Is anyone experiencing this issue?




:)

 

Mapped network drives do not connect at logon in vista with automatic logon enabled

I have vista x64 . I have some mapped network drives . They get connected when i enter the password at logon screen. Now i enabled automatic logon in vista and they do not connect anymore . I have to double click on them and enter the password manually .

Windows displays the message "Could not connect to all drives" at logon .

They used to connect automatically in xo with automatic logon enabled.

My logon password is the same as the administrator password with which i can connect to these drives .

 

Windows 10 Mapping Drives With Net Use Command

Using a domain built on Windows Server 2012 R2 I have a GPO that runs a logon powershell script like:

net use x: \\deviceNAS\folder /user:username <password>

Logging on as a regular domain user this script executes and maps the drive.

Logging on as a domain admin or domain user that is
a member of the local administrators group the script executes but the drive does not map. (Drive appears in File Explorer but with red X on drive icon. When drive is clicked credentials screen appears.)

I have ran gpresult /r and verified that the GPO was applied.

I have ran RSOP and verified that the logon script was executed.

I have enabled GPO logging and can see that the script was ran (c:\windows\debug\UserMode\gpsvc.log).

I have added log output commands in the script file (to output a log file with the results of the script execution) and can confirm that the script executes successfully.

If I run the script (that is being ran during from GPO logon process) manually the drive maps. It is only when the script is ran during logon process that the drive does not map (but only for users that are members of the local administrators group).

I have tested the same GPO (with same logon script) on a Windows 7 machine and the drive maps for every user whether or not they are a member of the local administrators group.

Is there something in Windows 10 that prevents drive mapping via script during the logon process for members of the workstations' Local Administrators group?

 

Setting Default Printer via Startup Script

This looks like a good solution, and similar to some of the VB scripts I tried.. but it is a logon script. I would need something that works as a startup script. We are not mapping printers to users as they move around too much, but rather mapping to each computer.

The Link that W1ZZARD posted is good information. Sadly however, I have tried utilizing most of the commands that are available. The /c command is indeed interesting, but we are trying to map them when a computer starts up (prior to logon screen) versus just mapping them remotely. The purpose would be if we had a lab that needed the default printer changed, sure we could just send the remote command to each machine, or even remote into them ourselves and manually do it, but I was looking for a smoother alternative.

It seems like its just something that will have to be done manually and with user education.

Thanks for all the suggestions though.