We have a small NT4 based network (with W2K / XP, 2x NT servers & 1x 2k server) Clients that was badly setup & poorly maintained and is therefore a mess.
Problems include but are not limited to: a public ip address range on a private network 193.30.1.xxx (it belongs to HP) instead of 192.168.xxx.xxx.
User groups & accounts that are best described as random. Shares & directories that follow no logic & permissions that are as random as the users & groups. Finaly one server that uses 150% - 200% of physical memory as it hosts more than its share of applications.
One of the NT severs has just had a terminal disk err (it's ok the man from IBM will fix it) so we have an oppotunity to leave the NT4 mess completely. This is my outline plan is is sensible? Is there a better approach?
Rebuild the broke server to W2k (We have UA/SA on the server licence (about to exipire)). Create new users / groups, DHCP Server, DDNS, AD the whole lot on the rebuilt server set as DC. Move the W2k server (make it secondary DDNS, DC), move the clients and make them participate on the new domain. Transfer the data from the remaining NT4 server, flatten it & rebuild to W2k server.
I realise that all static IP's will have to be reassigned manually (assuming we change the ip range at the same time). With moving to a new domain all the user SID will force a new user profile to be created on the clients therefore people with data in my documents locally will have difficulty getting at it. Client server applications will need reducating as to the location of their server. We also run domino & notes which may cause some problems during transfer.
What are your thoughts?
Many thanks
Pete
Problems include but are not limited to: a public ip address range on a private network 193.30.1.xxx (it belongs to HP) instead of 192.168.xxx.xxx.
User groups & accounts that are best described as random. Shares & directories that follow no logic & permissions that are as random as the users & groups. Finaly one server that uses 150% - 200% of physical memory as it hosts more than its share of applications.
One of the NT severs has just had a terminal disk err (it's ok the man from IBM will fix it) so we have an oppotunity to leave the NT4 mess completely. This is my outline plan is is sensible? Is there a better approach?
Rebuild the broke server to W2k (We have UA/SA on the server licence (about to exipire)). Create new users / groups, DHCP Server, DDNS, AD the whole lot on the rebuilt server set as DC. Move the W2k server (make it secondary DDNS, DC), move the clients and make them participate on the new domain. Transfer the data from the remaining NT4 server, flatten it & rebuild to W2k server.
I realise that all static IP's will have to be reassigned manually (assuming we change the ip range at the same time). With moving to a new domain all the user SID will force a new user profile to be created on the clients therefore people with data in my documents locally will have difficulty getting at it. Client server applications will need reducating as to the location of their server. We also run domino & notes which may cause some problems during transfer.
What are your thoughts?
Many thanks
Pete
