I am currently testing, whether we could disable the netlogon-scripts and instead use a user-configuration which gets deployed at every logon.

During my tests I have had some strange issues:

1. I have had a couple of batch scripts uploaded into the script repository and I had several user configurations to deploy these batches during login.

Some of them did not work very good so I moved the configurations to "trash".

But at the next login they were still deployed!

I can even see the entry in the dcconfigaccess.log.

How is this possible?

Does DesktopCentral not send something like a "STOP" signal if a configuration is moved to trash?

Same happened with "suspended" configurations!

Only when the configs are completely deleted (deleted from trash) the action stops.

Is this an error or is it not implemented that way?

--

2. Sometimes when I login the script does not execute at all or only very very late. This is a rare happening but it still occurs.

When using netlogon the batch script is executed instantly.

Is this a problem of the client agent needing more time for starting up?

Am I logging in "too fast" so that the configuration cannot be processed or something like that?

I believe I am going to stick with the netlogon source because it seems more reliable, still I would like to understand the configuration and batch handling.

Kind Regards

Stefan