NickDK

I opened another support ticket for my question about UNC paths and file names being invalid in the "ignore list."

Gonzo, thanks, I have opened a ticket for my immediate problem with launching executables from a UNC path. I'm still interested in an answer to my original question about allowing "ignore" list entries for UNC paths and file names. Nick

Additional information since I cannot edit my post above: When I try to open \\appserver\App\App.exe I receive a Windows dialog with this error message: Network Error Windows cannot access \\appserver\App\App.exe Error code: 0x80070002 The system cannot find the file specified. If I disable MEE Filesystem Protection in the system tray, I can run this application from the network location with no problems. It is definitely being blocked by MEE for some reason. Here's where it gets interesting.... I can take the App.exe and move it to a different server (\\appserver2\App\App.exe) and it works fine with MEE Filesystem Protection enabled. So, what doesn't MEE like about my \\appserver? Both servers are running Windows Server 2008 R2 Datacenter Service Pack 1. Any ideas?

An application (App.exe) we use is blocked by MEE. Users access this executable via a desktop shortcut to the UNC path (\\appserver\App\App.exe). I tried to ad it to the "Ignore List" but MEE tells me that UNC paths (\\appserver\App\App.exe) and file names (App.exe) are both "invalid." I tried mapping a drive to the \App\ folder and adding that to the ignore list (T:\App.exe). This did not work either, the file is still blocked. Even if this did work, it is not a great solution; I can't map a drive for every executable stored on a server that may need to be ignored. The only solution I can find is copying the executable to the local system and running it from there. This is also not a viable solution since the executable depends on other files found on the network drive which are changed by multiple users. I need to be able to "ignore" an executable via its UNC path and/or by filename alone. Help! Nick

Yes, exactly, terminology is the problem. But since every SCCM admin I know calls it "imaging" when it is not actually a scripted "Task Sequence," I want you to be aware of that, and not tell them that they can't install MBAM as part of their "imaging" process.

AdvancedSetup and Lazz, You are hurting your product by saying that "imaging is not supported," especially imaging with SCCM. Please STOP saying that. When your customers say "imaging," they don't always mean copying an existing installed partition to new hardware. That's not how SCCM works. SCCM uses a Task Sequence process, which installs a base Windows image, then installs software from .exe or .msi or scripts or whatever you want it to do. The "Malwarebytes Managed Client" is installed from an .exe or .msi, just like it would be if done manually. There is no reason this should be "unsupported" especially when your biggest potential customers are all using this process. We install "Malwarebytes Managed Client" as part of the SCCM Task Sequence on all new computers and it works perfectly. We also push it out as a package to existing PCs. I love your product, so please stop posting things that hurt it which will be read by potential customers looking at these forums. Nick