Hi
After installing DOpus, the domain logon script does not run, it just opens a folder.
I believe that it is the following command that DOpus wrongly catches:
Start "IDV 2014" /MIN %LOGONSERVER%\NETLOGON\Idv\Idv2014.Cmd
DOpus is set to replace exporer.
Please ask for more information, an thanks in advance.
/Lars
And I have tested with "Replace Explorer" off
Then everything runs as it should.
/Lars
Which versions of Windows and Opus are you seeing this with?
Assuming it is safe to do so, what happens if you run the same command from a command prompt?
I've tried running a similar command via a command prompt here and it works correctly, launching the .cmd batch file. I'm not sure if the difference might be down to what %LOGONSERVER% is translated to, or if it's to do with the server or pre-logon environment (e.g. if the folder is not accessible at the time the check is done to see what is being pointed to).
Sorry, I forgot that elementary info:
Windows 8.1 x64
Dopus 11.7
If I run the script manually, it runs as it should.
What's the folder that opens?
Sorry Again 
the folder that opens is: %LOGONSERVER%\NETLOGON\Idv or translated to: \server\NETLOGON\Idv
When it opens, is Idv2014.Cmd selected?
It's strange that something different happens in the logon script compared to running exactly the same command after logon.
Adding \server\NETLOGON\Idv to the list of excluded folders under Preferences / Launching Opus / Explorer Replacement may act as a workaround. Please try that to see if it works. (Make sure to add it using the UNC path, not a mapped drive letter or similar, if there is more than one way to access the same folder.)
Hi sorry for the late response.
No, idv2014.cmd is not selected.
Yes, by adding the full path to the idv folder on netlogon, it works.
Will this be the official workaround, or will it be fixed in an update in the future?
If it will be fixed in an update, will you let mw know, so I can try it?
Again, if this will be looked at, I can also test a beta build if you would like.
Thank you for your response.
Regards Lars
If the cmd file is not selected then I wonder if it is the start command itself which is causing a folder to open, or if it is something in the cmd file.
Can you tell us what is inside the cmd file? (Blank out or change any secret/confidential details, of course.)