G
Guest
Hello,
I'm trying to gather more information about a problem we've run into. We
are in the process of upgrading our DC's in our forest from Windows 2000 to
Windows 2003. However, we have experienced a problem that has caused a major
disruption in services for many of our offices.
It appears, that by running the "winnt32.exe /checkupgradeonly" on any of
the servers that are running the DHCP service, for some reason will stop the
service and not restart it. We were in the process of gathering information
to see if any of the DC's had software installed on them that was not W2K3
compatible and did not immediately notice that the service was down. It was
only after users systems lease time had expired and tried to get a new one
that our help desk started to get flooded with calls.
I was wondering if anyone had heard of this before? I have done searches on
both the MS Support site as well as Google and can find no mention of anyone
having similar problems. This problem is reproducible on all of our DC's
(which are the DHCP servers for each site). It makes no sense why we're
seeing this but sure enough the second we run the command the DHCP service
stops. Any insight would be greatly appreciated!!!
Ken
I'm trying to gather more information about a problem we've run into. We
are in the process of upgrading our DC's in our forest from Windows 2000 to
Windows 2003. However, we have experienced a problem that has caused a major
disruption in services for many of our offices.
It appears, that by running the "winnt32.exe /checkupgradeonly" on any of
the servers that are running the DHCP service, for some reason will stop the
service and not restart it. We were in the process of gathering information
to see if any of the DC's had software installed on them that was not W2K3
compatible and did not immediately notice that the service was down. It was
only after users systems lease time had expired and tried to get a new one
that our help desk started to get flooded with calls.
I was wondering if anyone had heard of this before? I have done searches on
both the MS Support site as well as Google and can find no mention of anyone
having similar problems. This problem is reproducible on all of our DC's
(which are the DHCP servers for each site). It makes no sense why we're
seeing this but sure enough the second we run the command the DHCP service
stops. Any insight would be greatly appreciated!!!
Ken