Before upgrading our NW servers to 6.5sp3 and performing a VCU, the tree looked like

O
|OU
|Server
|Server_SYS_Volume
|Server_DATA_Volume1
|...(other objects)...
||OU
|||Server_DATA_Volume2
|||...(other objects)...


After the upgrade and VCU (and subsequent DSREPAIR, check volumes / trustees) we have

O
|OU
||Server
||Server_SYS_Volume
||Server_DATA_Volume1
||Server_DATA_Volume2
||...(other objects)...
||OU
|||Server_DATA_Volume2
|||...(other objects)...


In 2 of the 6 places this has occured, the SERVER_DATA_Volume2 is "linked" to the _OLD volume that the VCU process creates. In the other 4 of the 6, it is linked to the proper SERVER_DATA_Volume2. The issue, however, is that when I use "MassUser" (www.hbware.com) to repair the users home directory attribute, the utility can't see that the folders exist. (the test run through says "Would Create directory (CN)"
If I point the same utility to the Server_DATA_Volume2 located one level higher in the tree, all functions normally and as we would expect.

How can we resolve this issue? Ideally my supervisor would like to maintain the previous object structure since it is what some of our users are accustomed to.

Thanks,

Preston