because we do not know which drive mappings are still in use - the users access a variable number of directories on each volume, it is only when all the data which they have rights to is migrated that the drive fails - we would need to check the access rights for each user across all volumes and cross reference that to what data has been migrated.

better just to let the drive mapping fail - then when all the migration is complete remove the user.kix script

we have written a drive mapping tool run from the main login script which maps drives based on AD group membership - a unc path is entered in the notes field of the group and the next available drive letter is used for that mapping - there is a button on the tool which allows the users to re-map this drive letter if necessary.