I'm not aware of any that would do that.
In I have found a couple, like Paragon Partition magic or acronis, but I was looking for a working plugin or people who experienced that on the Wintech bootable CD.
And in the other way, how it is possible to achiev that task ? How McAfee is supporting this ?
But at least, does anybody know if this is a process that McAfee is supporting, I mwan the possibility to resize an encrypted aprtition, even under Windows itself ?
Can anyone confirm ?
No, it's not something we "officially support" - which means, if it messes things up, you can't call our support number and ask for help - it would be like calling McAfee and asking how to do cascaded table numbering in Word 10. It's not our product, how would we know?
BUT, within certain boundaries it should work fine. Just make sure whatever you use to adjust the partitions does not move any safeboot.* files in the root of the boot drive. Other than that, you're in the hands of the partition changing tool - it's up to it to follow all the rules and put things back in the right places.
Thank you very much. That was exactly what I was supposing, but just wanted a confirmation.
We have tried a couple of different tools, but before choosing one, I needed to know if it may cause any particular issue.
In our internal guidelines, we will note that thing related to the SBFS in the C: drive.
Many thank again for your very helpfull and clear answer.
I'm not sure and not tried this but..
You can repartition it but would it change the SBR info especially the CRYPT List?
even if we're not moving safeboot .* file, are we sure that Partition tools would not change the SBR info esp on SBFS infomation?
the crypt list is a list of what is, and what's not encrypted - moving the partitions around does not change that, the sectors will still be encrypted and decrypted the same.
the repartitioning tool works within windows, so its writes go through the crypt as well.
the interesting part is the routine which interprets the policy - it wants to encrypt C and not D for example, so the hard work is translating "C" to a sector range - that's the part unique to EEPC. If the system thinks C is 1-1000 and the drive says C: is 1-900, then EEPC should go and decrypt 901-1000 on the next sync.