Re: How can I Disable JIT Debugger for my builds?

From: ZMan (news-replies_at_thezbuffer)
Date: 11/28/04


Date: Sat, 27 Nov 2004 21:31:09 -0800

I'm not sure how much you know about .Net permissions but they are
independant of the OS permissions. They don't override them but it should be
possible to get your code running from your share if you know the machine
admins well enough without giving you any more access to the machines.

What you need to do is convince the newtork admins to grant your file share
\\server\Starlocke Full Trust permissions in the .Net security tool (make
sure you run the 1.1 version, there is one for 1.0 and one for 1.1). This
means that any code running from that share and only that share gets
FullTrust (meaning anything that .Net can do, its the same as running on the
local machine). This FullTrust only affects the .Net security, if your
account can't write to a particlar folder then you will stillfail becuase of
operating system permissions. Now you will have to be machine admin to set
up that policy but once ts done on all the machines you should be good to
go.

I wouldn't recommend changing things like Intranet or (especially) Internet
to FullTrust, do it based on a path only. Giving FullTrust allows people to
dopy files and change registry settings etc so its something you will want
to make sure the newtork admins uderstand.

ZMan

"Starlocke" <Starlocke@discussions.microsoft.com> wrote in message
news:53EB9958-1C7A-4894-AF18-F67391C52D99@microsoft.com...
> Well, turns out that the security-zones must have been the issue. I
> copied
> everything to the local machine and the DirectX builds worked immediately!
>
> Now... If only I had admin priveledges on all the systems so I could
> update
> them to run managed directX and everything...
>
>
> Thank you!
>
>
> "ZMan" wrote:
>
>> Are you running your builds from a network share and the EXEs from the
>> SDK
>> which is installed on the local machines? Lots of these locked down
>> environment used roaming profiles which means your My Documents folder
>> will
>> be on a server and therefore subject to the Intranet Zone security
>> policy.
>>
>> ..Net security policy gives restricted access to programs running from
>> netowrk shares. Unless your windows form tries to access the local hard
>> drive (or other such insecure actions) it will happily run from a network
>> share. DirectX applications require Full Trust (I seem to remember Tom
>> Miller clarifying the exact trust but its very high) as the managed SDK
>> performs unsafe operations.
>>
>> I'm not sure what the JIT debugging error is that you are seeing - can
>> you
>> send the full text of the error?
>>
>> ZMan
>>
>> "Starlocke" <Starlocke@discussions.microsoft.com> wrote in message
>> news:24A6EEB4-931D-4F39-868B-04D0C4F17380@microsoft.com...
>> > As a poor student restricted to labs full of locked-down systems, I get
>> > the
>> > problem of the program trying to launch some JIT debugger whenever I
>> > try
>> > to
>> > run anything using DirectX.
>> >
>> > For instance, the DirectX SDK sample executable for "Player" (in the
>> > misc
>> > section) runs perfectly. Yet when I compile my own copy of that sample
>> > even
>> > as a Release build, it tries to use some JIT debugging service, and is
>> > blocked by security permissions, etc.
>> >
>> > What exactly did Microsoft do when they compiled their executable that
>> > got
>> > rid of the need for that DirectX debugger?
>> >
>> > Our empty System.Windows.Forms programs ran fine as long as they
>> > weren't
>> > using DirectX.
>>
>>
>>



Relevant Pages

  • Re: Programs and Group Policies
    ... > resides under the shared folder. ... >> If the NTFS permissions are more restrictive than the share permissions, ... and several other users with that are in the Domain Admins group on ... Indicating that Domain Admins are in the local ...
    (microsoft.public.windows.server.sbs)
  • Re: "Domain Admins", user account and privileges
    ... permissions for "domain users" are restricted? ... Restricting permission are done with DENY, ... and FC to Admins in no way restricts the admins. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Delegate Control... Reset Passwords
    ... You can force replication to make the changes immediately to all DCs. ... want that Admins keep the users password. ... that Read and Write permissions in pwdLastSet attribute. ... >>> goal is to reset passwords for users in selected OU's, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Prevent changes to Administrator password
    ... Restricted Admins group to mitigate against what you propose Deji. ... This posting is provided "AS IS" with no warranties and confers no rights! ... you need to understand that permissions on the ...
    (microsoft.public.windows.server.active_directory)
  • Re: solving the problem of spsearch
    ... the service to run if I put my service account into the local machine ... After a lot of tinkering with COM launch permissions (which didn't ... to get the search service to run without error. ...
    (microsoft.public.sharepoint.windowsservices)