G
Guest
I've been running a Server 2003 box for lil more than a year now and ages
back completed a migration of users/data from our steam powered Netware 3.12
box (don't laugh, too much!!). Upon trying to remove the netware client
from our windows box as it is now totally superfluous to needs, when 2003
reboots, it completely forgets what domain it's the DC of, and many other
crucial settings appear to go adrift with it. Putting the client back on
corrects this situation.
The sole reason behind wanting to remove the client is to significantly
improve server reboot times. With the NW client installed, the 2003 box
can't take roughly TEN minutes sitting there while it closes down network
connections (I'm assuming the nw client is waiting on non existant to time
out), which in my view is rediculous. Without the client installed, the
2003 box closes down in less than a minute (or there abouts).
Any ideas how I can rid my 2003 box of the netware client safely?
(rebuilding the 2003 box from scratch isn't an option!)
Cheers
Jason Aspinall
back completed a migration of users/data from our steam powered Netware 3.12
box (don't laugh, too much!!). Upon trying to remove the netware client
from our windows box as it is now totally superfluous to needs, when 2003
reboots, it completely forgets what domain it's the DC of, and many other
crucial settings appear to go adrift with it. Putting the client back on
corrects this situation.
The sole reason behind wanting to remove the client is to significantly
improve server reboot times. With the NW client installed, the 2003 box
can't take roughly TEN minutes sitting there while it closes down network
connections (I'm assuming the nw client is waiting on non existant to time
out), which in my view is rediculous. Without the client installed, the
2003 box closes down in less than a minute (or there abouts).
Any ideas how I can rid my 2003 box of the netware client safely?
(rebuilding the 2003 box from scratch isn't an option!)
Cheers
Jason Aspinall