The reason that it stops mapping after F: is that you have only three resource records defined - IBB Kondor, BEBOUW, & Van Agtmaal. The first valid CLASS is "Disk", and the TARGET is F: for each. Thus it sees that there is only one drive (F:) to map.
The logic that does the resource mapping can be exposed by creating a LOGINDEBUG.LOG file in the users %USERPROFILE% folder. Create that file, run the login script, and post the contents of the debug logfile. we will be able to see how the script is (mis)interpreting your config entries.
Also - you will need to distinguish how the script should process the F: drive for different groups of users. I didn't see any OUS= or GROUPS= entries.
Glenn
_________________________
Actually I
am a Rocket Scientist!
