Marshall,
Anything is possible. However, brining in a system component in a post FBA image is typically a laborous process and usually taken
when no other choice left.
For the component you mentioned you will have to :
- Make sure all the component dependencies are in your image and registered properly:
These includes:
Dependency on "Primitive: Ntdll" caused by "NTDLL.DLL"
Dependency on "Windows API - Advanced" caused by "ADVAPI32.DLL"
Dependency on "Windows API - Kernel" caused by "KERNEL32.DLL"
Dependency on "RPC Local Support" caused by "RPCRT4.DLL"
Dependency on "Primitive: Setupapi" caused by "SETUPAPI.DLL"
Dependency on "Windows API - User" caused by "USER32.DLL"
Dependency on "Primitive: Netapi32" caused by "NETAPI32.DLL"
Dependency on "Primitive: Userenv" caused by "USERENV.DLL"
Dependency on "Primitive: Oleaut32" caused by "OLEAUT32.DLL"
Dependency on "Primitive: Ole32" caused by "OLE32.DLL"
Dependency on "Primitive: AuthZ" caused by "AUTHZ.DLL"
Dependency on "Primitive: Wldap32" caused by "WLDAP32.DLL"
Dependency on "Security Accounts Manager Client" caused by "SAMLIB.DLL"
Dependency on "Primitive: Esent" caused by "ESENT.DLL"
Dependency on "Windows NT MARTA Provider" caused by "NTMARTA.DLL"
Security Configuration Engine for Professional depends on FBA: SCE
Dependency on "Microsoft Visual C++ Run Time" caused by "MSVCRT.DLL"
- Copy the following files to your runtime:
defltwk.inf - \windows\inf
dwup.inf - \windows\inf
syscomp.inf - \windows\inf
scecli.dll - \windows\system32
scersop.mof - \windows\system32\wbem
- Register scecli.dll with regsvr32.
