Re: user rights and group memberships of students using Visual Studio in a college classroom
From: Thomas H (T_at_H)
Date: 08/02/04
- Next message: Vycka: "Sorting TreeView"
- Previous message: Steve: "COM Interop Registration Failed"
- In reply to: Joel Morgan: "user rights and group memberships of students using Visual Studio in a college classroom"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 2 Aug 2004 14:02:19 -0400
"Joel Morgan" <jpmorgan@nospam.bigfoot.com> wrote in message
news:qPbPc.2101$oA5.1688@okepread05...
> I'm configuring Visual Studio .Net for a large scale college classroom
> deployment. The professor insists that students must be members of the
> "admin" group. I think in some cases that may be true, but in general
lower
> level classes can get by using only "user" rights. I expect to have to
make
> exceptions for upper level courses.
>
> I found a document from Microsoft University relations titled "Visual
Studio
> .NET User Groups Use, Permissions, Security"
> http://www.msdnaa.net/solutions/dotnetdevvsgroups.pdf. Is anyone in this
> group using this configuration?
>
> I found another interesting document on development using Visual Studio
.Net
> on Terminal Server at
>
http://msdn.microsoft.com/academic/techdown/techprod/netframework/devsys/devsysws03/default.aspx.
> Is anyone in this group using this configuration?
>
> Can anyone comment on user rights and group memberships of students using
> Visual Studio in a college classroom setting?
Joel, I'm glad to see someone else reading those docs! You (and the
professor) might also want to look at this document, "Developing Software in
Visual Studio .NET with Non-Administrative Privileges". The link is long,
you might have to cut & paste:
If the professor also wants to teach "Best Practices", he/she should not
have them program as Administrators. First, it's a security risk. Secondly
(and most important as far as teaching a class!), if a programmer works as
an Administrator user, and their clients work as Power Users, this might
cause a permission conflict when the programmer deploys their product! I do
all my development as a Power User, and I have no problems planning or
developing my applications.
End users should never be Administrators- any IT department (of which I'm
in) will emphasize that fact. In fact, you might be able to get support for
this from your school's departmental (or central) IT department. Last year,
we had to review an application- when we found out that it required
Administrative privileges to work, we rejected the product! It was too much
of a security risk- and even if the program itself wasn't a risk, it still
exposed an un-necessary system vulnerability. And campus networks are
notorious for being the least-secure networks. Even though this might be an
isolated lab on a private subnet with no outside connectivity, I'd still
hesitate to run as an Administrator. Besides, that could mean that UserA
can look at- and copy- UserB's code!
I read the first doc you listed (VS.NET User Groups Security) when I was
setting up my development environment at work. I wanted to use the
semi-isolated team development model with ASP.NET and remote server
debugging, and wound up falling on my face. Turns out that with ASP.NET,
you still need to be an Admin to debug- unless you change the user that
ASP.NET runs under. Since I like all my machines (development PC, test
server, production server) to have similar environments, I didn't change the
ASP.NET user. My solution was to log out as my normal Power User account,
and log back in as Administrator for debugging. Most of the time I don't
need ASP.NET debugging (I can tell enough from the error message itself), so
it's not that much trouble for me- and I feel it's the most secure method.
Keep us posted on the outcome!
-Thomas
- Next message: Vycka: "Sorting TreeView"
- Previous message: Steve: "COM Interop Registration Failed"
- In reply to: Joel Morgan: "user rights and group memberships of students using Visual Studio in a college classroom"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
