Cant create instance of IE via IIS 7

Has anyone tried this? I know back in the day I was able to do this in IIS
5.x and greater I know the security model in both IIS 7 and vista have
changed greatly. However I cant not do some of the IE automation that we have
going on behind the scenes (which is basically for creating dynamic screen
captures and offering the ability for the client to download them) through
IIS 7. I believe that it must be security related. If I execute the same code
as a Console App it works just fine. If I execute the code against the built
in Web Server supplied with Visual Studio the code all executes just fine.
However in IIS 7 it doesnt work in most cases it will spawn a new instance of
IE then that process terminates almost immediately. I have tried
impersonation, tried changing the app pool identity. I have even used direct
Code impersontation as well. And for the life of me I can not get IE to stay
active and behave in the same manner that it does when running in a different
Application context/Security Context. Any one have any ideas? Something in
DCOM config I am possibly missing????



Thanks in Advance

-Will

Has anyone tried this? I know back in the day I was able to do this in IIS
5.x and greater I know the security model in both IIS 7 and vista have
changed greatly. However I cant not do some of the IE automation that we have
going on behind the scenes (which is basically for creating dynamic screen
captures and offering the ability for the client to download them) through
IIS 7. I believe that it must be security related. If I execute the same code
as a Console App it works just fine. If I execute the code against the built
in Web Server supplied with Visual Studio the code all executes just fine.
However in IIS 7 it doesnt work in most cases it will spawn a new instance of
IE then that process terminates almost immediately. I have tried
impersonation, tried changing the app pool identity. I have even used direct
Code impersontation as well. And for the life of me I can not get IE to stay
active and behave in the same manner that it does when running in a different
Application context/Security Context. Any one have any ideas? Something in
DCOM config I am possibly missing????



Thanks in Advance

-Will