Netlogon installation is helpful in situations where you are regularly adding new users to a Windows server, or if you are managing a Terminal Services, Citrix, or VMware environment where users do not have persistent user files.
For these situations, RemoteScan has provided a sample netlogon batch file which provides each user with the needed RemoteScan files at user logon. A sample batch file named rslogon.bat is provided with every RemoteScan installation, and it may also be downloaded from the RemoteScan web site here: http://www.remote-scan.com/downloads/rslogon.bat To get the sample rslogon.bat file to execute properly, first place the rslogon.bat file into your shared netlogon directory.
The netlogon folder is typically located at: %SystemRoot%\sysvol\sysvol\<domain DNS name>\scripts
It is advisable to run the RemoteScan installer at least once to extract some needed files. The sample rslogon.bat script is configured to look for the following three RemoteScan items in a subdirectory called “RemoteScan” under the netlogon folder: twain_32 (a windows folder) twunk_32.exe twain_32.dll These RemoteScan files can be placed anywhere that is accessible, but if it is a different location than the directory specified in rslogon.bat, you will need to make a change to the sample rslogon.bat file to specify the new location. To do that, you will want to open the rslogon.bat file to edit, and then look for the following lines of code: net use v: %LOGONSERVER%\netlogon set srcPath=v:\RemoteScan By default, RSlogon sets a mapped drive (v:) to the servers \netlogon folder and then looks within the RemoteScan sub-directory. If you need to change the location of the files, you will need to update these lines of code in the sample rslogon.bat file. Once you have these files in place and the rslogon.bat file source path has been correctly modified, then you can specify the logon script file for whichever users or groups you want to utilize RemoteScan. In an Active Directory environment, this is done by editing a user’s or group’s Active Directory Properties, clicking on the profile tab, and then placing "rslogon.bat" in the logon script edit area. One advantage to having an Active Directory setup is that you can apply a setup script to a group policy so that the script will execute for anyone who is a member of that group, which saves the hassle of having to setup the rslogon.bat for every new user. To do this, you will need to set the proper setting to allow this. The setting in Group Policy is "User Configuration", "Windows Settings", "Scripts (Logon/Logoff)", "Logon". The simplest way to do this is to copy the rslogon.bat script to the Windows clipboard, open the "Logon" setting in the Group Policy editor, press the "Show Files..." button, and paste the rslogon.bat file in the dialog. You can select the file and edit it in this dialog as well. Presto, it now works for all users who are a member of whatever group you set this up for. Once this is done, the logon script will check for the existence of the needed RemoteScan files in the user’s homedrive and homepath and then copy them over, if need be.