M
Mark K Vallevand
If you have the MSDTC re-installation problem during the first boot of you
cloned image, I have the answer. I worked with Microsoft and finally pieced
together enough information to explain and work-around the problem.
During the first boot of a cloned image, some of the cloning activities are
done in parallel with service start up. Among other things, the cloning
activities include SID change and application in the file system and
security information; reinstalling MSDTC, and reconfiguring IIS. This is not
all well-documented. User installed services can interfere with the cloning
activities if not implemented correctly. The correct way to synchronize with
cloning activities is not documented. However, if a service depends on the
MSDTC service, then it doesn't start until after MSDTC is reinstalled and
the problem doesn't occur.
If you look in the application event log you can see the MSDTC service get
removed then get re-installed. If you have a service that starts before
MSDTC reinstallation, it might interfere with reinstallation.
The post-clone FBA runs as the shell application. The precursor to the
shell, LSASS, launches in parallel with services.exe. As part of cloning
FBA reads the file C:\Windows\inf\minioc.inf to direct its some actions pre-
and post-clone. The section [SysprepInitExecute] shows that MSDTC, COM+,
SCE, IIS, and Terminal Server have actions to perform post-clone.
cloned image, I have the answer. I worked with Microsoft and finally pieced
together enough information to explain and work-around the problem.
During the first boot of a cloned image, some of the cloning activities are
done in parallel with service start up. Among other things, the cloning
activities include SID change and application in the file system and
security information; reinstalling MSDTC, and reconfiguring IIS. This is not
all well-documented. User installed services can interfere with the cloning
activities if not implemented correctly. The correct way to synchronize with
cloning activities is not documented. However, if a service depends on the
MSDTC service, then it doesn't start until after MSDTC is reinstalled and
the problem doesn't occur.
If you look in the application event log you can see the MSDTC service get
removed then get re-installed. If you have a service that starts before
MSDTC reinstallation, it might interfere with reinstallation.
The post-clone FBA runs as the shell application. The precursor to the
shell, LSASS, launches in parallel with services.exe. As part of cloning
FBA reads the file C:\Windows\inf\minioc.inf to direct its some actions pre-
and post-clone. The section [SysprepInitExecute] shows that MSDTC, COM+,
SCE, IIS, and Terminal Server have actions to perform post-clone.