There are new builds of PQIdeploy and PQdisk released with GSS 2.5
These two components (in all their flavors) are at build 1515 now with GSS 2.5. There was a lot of improvements made specifically to the resizing functionality so I would suggest you upgrade. It might be good time to move over to using the Ghost tools instead as the DCL components are slowly being phased out.
Worth a mention of GSS2.5 is the capability of ghost to restore PQI images (primary partitions only) so you need not even create new images in most cases when moving form the DCL tools. Ghost also has the resizing on restore functionality you are using in you pqideploy script.
Anyway, on to your problem:
I've done some brief testing on win2k of your scenario and I am getting similar results. PQideploy seems to be running into problems when trying to resize the destination partitions although not explicitly apparent by the error messages, the debug file has a bit more info. To get your debug file try giving a location and name as arguments to the dbg option ie /dbg=test.dbg (this is working for me).
I tried the same scenario from winXP which worked.
I then found the culprit to be the /nsu switch, as once I removed this option your scenario was working on win2k also. PQIdeploy comunicates with the OS at certain stages in its operations even when you are using the /nsu (no system update) option, it seems that this option in win2k is not behaving well. The newest build 1515 with GSS 2.5 has improvents made in this OS/PQIdeploy communication which fix this problem.
So, please try the workaround of removing the /nsu switch and let me know how you get on.
Regards,
Morgan