My company is thinking about embarking on a project to migrate from Windows NT 4.0 to Windows 2000 server (standard and advanced) on numerous servers across the enterprise. We are not planning on implementing Active Directory initially, or installing Professional on the client desktops. We are planning to run in "mixed" mode until enough thought, training and analysis can be completed regarding Active Directory.
We are currently compiling an updated server inventory, which includes the metrics we THINK are necessary to know about each server for a Win2K server deployment. But, we are concerned that we may be overlooking something significant that is applicable/significant to Win2K server .
Does anyone have a list/template of the kinds of information (the "metrics") one needs to know regarding their servers to assist in developing a Win2K server deployment strategy? (other than the obvious questions like: -server size/type/role -no. of processors/size -disk space used/free -applications running and their compatibility with win2k -production schedule -interdependencies to other servers -no. of users supported/using the server
What other information is required/questions need to be asked and why?
Any help would be greatly appreciated. I have searched the web and found nothing of practical value in compiling a comprehensive summary of facts one needs to know to assist in developing a Win2K server deployment plan that makes sense to the features/modules of Win2K (especially those that are new). Saving Changes...
Anonymous
I shall appreciate if someone can share a checklist of activities to be completed in (a) developing a deployment strategy and (b) building a deployment plan. Saving Changes...
