G
Guest
I've been struggling for days of research figuring out how to clean up my
critical device database in the registry after bringing down a sysprep image.
There are hidden devices in my registry and services running as well that
shouldn't be, as a result of including the massstoragesection in my
sysprep.inf. I do not want to change my image or sysprep.inf because i have
it working successfully on all platforms. so my question.
why is the sysprep -clean section not properly cleaning out the critical
device database in the registry as it is designed to do? my method of
creating the image:
1. prepare image
2. run sysprep -bmsd to populate sysprepmassstoragesection
4. run sysprep -clean
5. run sysprep -reseal
6. image machine
7. bring down image to new machine
8. upon reboot minisetup runs sysprep -clean again via the cmdlines.txt
still have a fully populated critical device database.
what am i doing wrong?
thank you,
Scott
critical device database in the registry after bringing down a sysprep image.
There are hidden devices in my registry and services running as well that
shouldn't be, as a result of including the massstoragesection in my
sysprep.inf. I do not want to change my image or sysprep.inf because i have
it working successfully on all platforms. so my question.
why is the sysprep -clean section not properly cleaning out the critical
device database in the registry as it is designed to do? my method of
creating the image:
1. prepare image
2. run sysprep -bmsd to populate sysprepmassstoragesection
4. run sysprep -clean
5. run sysprep -reseal
6. image machine
7. bring down image to new machine
8. upon reboot minisetup runs sysprep -clean again via the cmdlines.txt
still have a fully populated critical device database.
what am i doing wrong?
thank you,
Scott