1 / 13

Windows 2000

Windows 2000. Common Problems / Unique Solutions?. We all face common problems. Windows 2000 may be used to help resolve some of these problems Windows 2000 introduces many problems into our environment. Communication.

jade-nunez
Download Presentation

Windows 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Windows 2000 Common Problems / Unique Solutions?

  2. We all face common problems • Windows 2000 may be used to help resolve some of these problems • Windows 2000 introduces many problems into our environment

  3. Communication • Microsoft spends the time and money to communicate how Windows 2000 can be used as a solution • Who takes on the task of communicating the problems that Windows 2000 introduces?

  4. Risk of highlighting the problems • Central Information Technologies perceived as Microsoft bashers or luddites • Concerns about political fallout from “disparaging” Microsoft • Resources may be the same that are needed to get a working deployment

  5. Examples of unique solutions • We will all probably have different directory designs • Dictated by local politics, legacy systems, 3rd party software • Single Domain vs. Forest vs. Multiple Forests

  6. Examples of common problems • Misconfigured Win2k Domain may appear as a Denial of Service Attack on the network • DHCP responses, inconsistent DNS information, … • Impact of Exchange on existing email infrastructure • AD yet another data repository

  7. What have we done so far? • workshops • online project notebooks • mailing lists

  8. workshops • Joint CSG/Microsoft workshop, June 1998 http://www.stonesoup.org/ms98/ • May, 2000 CSG meeting http://www.stonesoup.org/Meetings.past/0005/mtg.pres • June, 2000 University of Colorado workshop http://www.colorado.edu/its/windows2000/conf.html • July, 2000 MSR sponsored workshop <url coming soon!>

  9. Online project notebooks • CMU http://asg.web.cmu.edu/orpheus/ • MIT http://mit.edu/pismere/ • Stanford http://www-nt.stanford.edu/Win2000/ • Colorado http://www.colorado.edu/its/windows2000/ • UMich http://www.umich.edu/~lannos/win2000/

  10. Mailing lists • Stanford’s win2000-dev and win2000-hied lists • MIT’s pismere list • University of Colorado MSN web community http://communities.msn.com/Windows2000inHigherEducation

  11. What haven’t we done? (in common) • Developed white papers to explain to departments why Windows 2000 takes lots of planning and highlight the potential problems • Communicate to local departments what other schools are doing • Develop a set of common best practices

  12. Starting points • http://web.mit.edu/is/help/win2000/nodc.html • http://www-project.slac.stanford.edu/windows2000/windows2000_project.html

  13. Call for resources • Develop white papers that highlight potential problems and best practices • Author(s) • Scheduled conference calls

More Related