continuity
asked on
Web-based User Administration for Windows Server 2003
Hi,
My company is running a website for a third party which makes use of NT authentication to manage user access. We'd like the client to be responsible for administering the users of the site but they're not able to connect using Remote Desktop Connection through their firewall. Can aonyone recommend a good tool for providing web-based administration of a Windows 2003 server? Obviously it'd need to be secure and allow for the creation/management of users.
Thanks in advance for your help.
Continuity.
My company is running a website for a third party which makes use of NT authentication to manage user access. We'd like the client to be responsible for administering the users of the site but they're not able to connect using Remote Desktop Connection through their firewall. Can aonyone recommend a good tool for providing web-based administration of a Windows 2003 server? Obviously it'd need to be secure and allow for the creation/management of users.
Thanks in advance for your help.
Continuity.
have you looked at frontpage server extensions? this lets you do user management using either local server or domain accounts.
ASKER
No, I've not looked at frontpage extensions. Do you know where I could get more information about using them, and specifically the user management aspects?
Thanks.
Thanks.
This is just an introduction to get you started, http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsa01.mspx
it's a bit vague on the detail part though so I'll see if I can find you something better tomorrow.
Can you just quickly answer these for me too?
Is your website IIS?
Are you wanting user management specifically for the website?
Do the users need to be domain users / local users / sql users / doesn't matter as long as they can get in?
it's a bit vague on the detail part though so I'll see if I can find you something better tomorrow.
Can you just quickly answer these for me too?
Is your website IIS?
Are you wanting user management specifically for the website?
Do the users need to be domain users / local users / sql users / doesn't matter as long as they can get in?
ASKER
1. Yes, the website is IIS.
2. Yes, we want user management specifically for the website. Basically we've got a whole load of documents on the site and we want to make sure we control access to those files. The easiest way of doing that seems to be using NT authentication for users, provided we can resolve the user management issue.
3. Ideally local users, but it doesn't matter so long as we meet the criteria above. i.e. we can control access to the files stored on the site.
Thanks for your help.
2. Yes, we want user management specifically for the website. Basically we've got a whole load of documents on the site and we want to make sure we control access to those files. The easiest way of doing that seems to be using NT authentication for users, provided we can resolve the user management issue.
3. Ideally local users, but it doesn't matter so long as we meet the criteria above. i.e. we can control access to the files stored on the site.
Thanks for your help.
How much usage (users / traffic) does this site get?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's exactly what I needed, thanks very much.
No problem.
recommendations:
- do a security audit / penetration test if you can when you're done and make sure you're organisations data is protected as much as possible. https may be a small improvement if it's viable.
- make sure you've got really good backups of the system (when we started out with this, one of our web admins used to kill extensions on a regular basis by, um, "seeing what it could do" - thankfully we had backups and i'd done my share of playing before I let the developers at the system so I knew our config back to front).
- schedule the server extensions to run health checks. This'll keep all your ntfs permissions clean and fix up any extensions files that go walkabout.
AJ.
recommendations:
- do a security audit / penetration test if you can when you're done and make sure you're organisations data is protected as much as possible. https may be a small improvement if it's viable.
- make sure you've got really good backups of the system (when we started out with this, one of our web admins used to kill extensions on a regular basis by, um, "seeing what it could do" - thankfully we had backups and i'd done my share of playing before I let the developers at the system so I knew our config back to front).
- schedule the server extensions to run health checks. This'll keep all your ntfs permissions clean and fix up any extensions files that go walkabout.
AJ.