A
Andrea Valori
Hi everyone, I'm experiencing an issue with XPE FP2007. The components
database is updated to the November 2007 QFE.
I have an image with windows logon and explorer shell where I need to lauch
an application based on .NET 2.0 framework. The issue is: if I add the .NET
2.0 component, when I try to call for example the windows command processor
from my application I obtain a Win32Exception "Access denied"; the same if I
call for example the desk.cpl from the CMD (the command shell interface
context is added to the image and I retrieve access denied) or if I try to
open the services snap-in from the MMC. It seems to be a security issue
related to the .NET2.0 component; in fact if I remove that component and
leave all the same, all is ok (I can call the desk.cpl from the cmd, open the
services snap-in and so on). I've tried other configurations (custom .NET
shell with windows logon or minlogon, command shell, explorer shell) but all
shows the same problem. Please note I add the administrator account, the
automatic logon and configure the windows logon correctly for that account.
Thanks in advance, Andrea.
database is updated to the November 2007 QFE.
I have an image with windows logon and explorer shell where I need to lauch
an application based on .NET 2.0 framework. The issue is: if I add the .NET
2.0 component, when I try to call for example the windows command processor
from my application I obtain a Win32Exception "Access denied"; the same if I
call for example the desk.cpl from the CMD (the command shell interface
context is added to the image and I retrieve access denied) or if I try to
open the services snap-in from the MMC. It seems to be a security issue
related to the .NET2.0 component; in fact if I remove that component and
leave all the same, all is ok (I can call the desk.cpl from the cmd, open the
services snap-in and so on). I've tried other configurations (custom .NET
shell with windows logon or minlogon, command shell, explorer shell) but all
shows the same problem. Please note I add the administrator account, the
automatic logon and configure the windows logon correctly for that account.
Thanks in advance, Andrea.