The whole problem with the DDTS you had mentioned was that the problem occured at the creation of the second PDL based on the first. The problem was that the existing subscribers on the first PDL were not actually in the AD group that corresponded with the secod PDL; they were only in Unity's SQL DL table.
If the system was patched, it would help for any future PDL creates (based off of an existing PDL); it wouldn't remedy any previously created PDLs in that matter.
If the user(s) that is causing trouble with the delete is really on the AD group that corresponds to the Unity PDL, there shouldn't be a problem removing that subscriber. If the subscriber is not in the AD group, then it's going to cause problems for the Unity delete from the PDL.
The best thing to do at this point is to determine for sure if the subscriber is really in the AD group that corresponds to the Unity PDL we're trying to delete the subscriber from. If the subscriber is not in there, try adding the subscriber via AD Users and Computers. Then try removing the sub from the PDL in Unity. Odd, huh?
