ggordon
Programmer
- Sep 15, 2003
- 45
Hi,
I am a web guy, not a network guy (haha) and have been asked to find out the following. I would sincerely appreciate any advise anyone can provide with regard to the installation and set up of IIS and .NET, etc. on a Windows 2003 server.
Questions:
1) Is it good or bad to install MS Office Professional 2003 on a Windows 2003 SERVER? They are telling me it is not good to do. I sometimes, while working on the server, could benefit by the ability to open .mdb files, .xls files, .doc files, etc. to look at them and manipulate them while working directly on the server. But if Office isn't installed, I won't be able to do this. I also wouldn't be able to run macros, etc. within an .mdb file since there wouldn't be any MS Access to open the file and execute them.
So, I need (if possible) a list of benefits and potential draw backs from installing MS Office Professional on the actual server. The more detail the better.
2) Are there a list of "settings" that I should be aware of to make after loading IIS, etc. onto the server? I just want to make sure that the server is set up (in general) with all the "good stuff" it should be set up with. For example, I will be running .asp and .aspx pages. The server will be connected to the Internet so users can access the websites that will be running on it.
Any idea of a good and comprehensive list of things I should set, should install, should NOT install or set, etc.???
3) Any other advise?
Thanks,
Gary
Gary M. Gordon
ggordon@garymgordon.com
I am a web guy, not a network guy (haha) and have been asked to find out the following. I would sincerely appreciate any advise anyone can provide with regard to the installation and set up of IIS and .NET, etc. on a Windows 2003 server.
Questions:
1) Is it good or bad to install MS Office Professional 2003 on a Windows 2003 SERVER? They are telling me it is not good to do. I sometimes, while working on the server, could benefit by the ability to open .mdb files, .xls files, .doc files, etc. to look at them and manipulate them while working directly on the server. But if Office isn't installed, I won't be able to do this. I also wouldn't be able to run macros, etc. within an .mdb file since there wouldn't be any MS Access to open the file and execute them.
So, I need (if possible) a list of benefits and potential draw backs from installing MS Office Professional on the actual server. The more detail the better.
2) Are there a list of "settings" that I should be aware of to make after loading IIS, etc. onto the server? I just want to make sure that the server is set up (in general) with all the "good stuff" it should be set up with. For example, I will be running .asp and .aspx pages. The server will be connected to the Internet so users can access the websites that will be running on it.
Any idea of a good and comprehensive list of things I should set, should install, should NOT install or set, etc.???
3) Any other advise?
Thanks,
Gary
Gary M. Gordon
ggordon@garymgordon.com
