[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework

enterprise policy configuration

A.

6/18/2008 11:54:00 AM

Hi

We are soon going to deploy some applications that are build on the dotnet
framework. Inthat regard we're looking at how we can configure the framwork
on our client computerts centrally. On each client computer you have the "
Microsoft Dotnet framework configuration".

How can we do this configuration centrally and how can we do this for
multiple versions of hte framework at the same time?

/A.
5 Answers

Alvin Bruney [ASP.NET MVP]

6/18/2008 11:07:00 PM

0

That's not possible. These are individual, client computers not connected to
your deployment server. The best you can do is configure the policy on your
deployment server and push it to client servers. Your push can be in the
form of SMS or GPO or some homegrown derivative that does the same thing
under the covers.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------


"A." <andy.i@spamblcoker.org> wrote in message
news:e9ThBoT0IHA.4400@TK2MSFTNGP06.phx.gbl...
> Hi
>
> We are soon going to deploy some applications that are build on the dotnet
> framework. Inthat regard we're looking at how we can configure the
> framwork on our client computerts centrally. On each client computer you
> have the " Microsoft Dotnet framework configuration".
>
> How can we do this configuration centrally and how can we do this for
> multiple versions of hte framework at the same time?
>
> /A.
>
>

A.

6/19/2008 9:23:00 AM

0

One thing we're thinking about is using the "Microsoft dotnet framework 2.0
Configuration" tool and create a deployment package for one of the "Runtime
Security policies", and then distribute that MSI package with gpo's.
In that deployment package we could either give the localintranet Zone
FullTrust permission set, so we can execute exe files directly from all our
network shares, or give a more detailed execute rights on only certain
shares. Either way, we don't have to install every single application
locally on all clients. We only need a shortcut to the application on all
clients.
The way I see it this would solve our problem, wouldn't it?

/A

"Alvin Bruney [ASP.NET MVP]" <vapor dan using hot male spam filter> wrote in
message news:A1DB2EE5-20AE-455C-B179-1E085C8E9040@microsoft.com...
> That's not possible. These are individual, client computers not connected
> to your deployment server. The best you can do is configure the policy on
> your deployment server and push it to client servers. Your push can be in
> the form of SMS or GPO or some homegrown derivative that does the same
> thing under the covers.
>
> --
>
> Regards,
> Alvin Bruney [MVP ASP.NET]
>
> [Shameless Author plug]
> The O.W.C. Black Book, 2nd Edition
> Exclusively on www.lulu.com/owc $19.99
> -------------------------------------------------------
>
>
> "A." <andy.i@spamblcoker.org> wrote in message
> news:e9ThBoT0IHA.4400@TK2MSFTNGP06.phx.gbl...
>> Hi
>>
>> We are soon going to deploy some applications that are build on the
>> dotnet framework. Inthat regard we're looking at how we can configure the
>> framwork on our client computerts centrally. On each client computer you
>> have the " Microsoft Dotnet framework configuration".
>>
>> How can we do this configuration centrally and how can we do this for
>> multiple versions of hte framework at the same time?
>>
>> /A.
>>
>>

Marc Gravell

6/19/2008 10:17:00 AM

0

Yes, that will work, but it isn't very graceful. If going down this
route, I'd at least limit full-trust to a named server/share, or a known
signature.

A better option might be ClickOnce; this again works just via shortcut
(to the .application), but has a lot of features built in to make
deployment easier - and it doesn't need any caspol changes - just a
trusted certificate.

Marc

Marc Gravell

6/19/2008 10:17:00 AM

0

Yes, that will work, but it isn't very graceful. If going down this
route, I'd at least limit full-trust to a named server/share, or a known
signature.

A better option might be ClickOnce; this again works just via shortcut
(to the .application), but has a lot of features built in to make
deployment easier - and it doesn't need any caspol changes - just a
trusted certificate.

Marc

Alvin Bruney [ASP.NET MVP]

6/20/2008 10:00:00 PM

0

To add to that, once you start bending over backwards to get an application
to work, you really ought to step back and review the design. This
application would work better as either click once or a web application.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------


"Marc Gravell" <marc.gravell@gmail.com> wrote in message
news:485A320D.4030504@gmail.com...
> Yes, that will work, but it isn't very graceful. If going down this route,
> I'd at least limit full-trust to a named server/share, or a known
> signature.
>
> A better option might be ClickOnce; this again works just via shortcut (to
> the .application), but has a lot of features built in to make deployment
> easier - and it doesn't need any caspol changes - just a trusted
> certificate.
>
> Marc