DHCP Migration 2k to 2003

  • Thread starter Thread starter Convexity
  • Start date Start date
C

Convexity

"dhcpexim" will not function on old 2000 box to export dhcp.
Please advise on alternate tool; tried manual "copy" migration method
(export / import registry keys & copy of %systemroot%/system32/dhcp
directory to 2003 box) nothing I've tried will allow me to successfully
export old dhcp database. ??
 
One way it can be done is to upgrade the o/s on the server that had the dhcp
db and then used the import/export tool. I'm not sure if there are other
options available to do this other than that.
 
Have you seen:
MS-KBQ325473_How to move a DHCP database from a computer that is running
Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer
that is running Windows Server 2003

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto #
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
 
Is it possible to rollback such an upgrade if required?



-Many thanks for the response
 
Jorge de Almeida Pinto,

Indeed I have - as a matter of fact I believe I've read and followed
virtually every KB ever posted on this subject :)

No success yet...
 
Bring up a virtual server on 2000 copy the dhcp across to the virtual server
and upgrade the virtual server to 2003 and export it.

nothing in production will be impacted.
 
I have had plenty of troubles in tha past as well. I should restate, we
have migrated but that was after later versions of import/export tool came
along. it used to be real buggy.

So check out your tool and make sure it is at least later than 1/2004.
 
Paul,

1. Virtual server live on existing 2k box? (apologies: lack of
experience with VS)
2. Copy across to VS how? As I mentioned attempted copies earlier?


-C
 
Paul:

OK: version of dhcpexim must be the problem: my version is aparrantly
2001;
Downloaded it from MS in only location I could find it though - where
else if anywhere do you know of I can find it? Cannot find latest
version on any ResKit; nor on MS TN?


-C
 
I'm not sure, you want me to e-mail you what I have? I believe Microsoft
sent it to.
 
It is in the mail, but like I said in the e-mail. This is "AS IS." I
believe there shouldn't be any issues but Microsoft provided to me. I have
zero control over any of it. Use at your own risk.
 
Paul,

I completely understand; I assume all risk from this point forward;
already read the "Microsoft does not support any resource kit tools"
etc...


-C
 
Paul,

I have not yet received your email, can you verify send, or perhaps
send with a server receipt?


-C
 
I would suggest try find another machine to see if you get the same message.
Possibly when Microsoft provided it, it was to be run on a 2003 machine
(Which does you no good).



When you had problems before were you able to load the software and import
the db on 2003? The only issue was it wouldn't had out addresses on
sub-nets? If that is the case I can tell you how to get around that. That
was a known issue of the older dhcpexim tool.
 
Paul,

Problem is the machine I am trying to export FROM is a 2000 server; I
have tried the tool I have a copy of on other machines (2000 boxes)
with the same result. Currently I am unable to import anything with
the 2003 box; understanding nothing I try to import is a result of a
dhcpexim export.

The tool I have simply does not work regardless which machine I've run
it on (all 2000 boxes for the export). Specifically, I can install the
tool fine, launch it fine, but when it is supposed to pop the "save
file as" dialog it crashes out. (the utility - not the machine)

The new copy I have simply reports "program too big to fit in memory"
although I've only tried this on my primary DHCP box. I will be
trying it on other machines shortly....

-Matthew
 
Also, an other FYI, (separate DHCP issue) I have attempted to "rebuild"
DHCP on the 2003 box manually creating the scopes and their options.
All configuration is identical, however when the old DHCP is taken
offline, and a client on the net is restarted - it never receives an
address from the new DHCP. I also tried using separate ip ranges;
still keeping the old DHCP offline, still no addresses handed to the
restarted / refreshed clients.

I am happy however to ignore this until I can migrate the database.
Configuration is no big concern at this time....


-M
 
I'm uncertain of your environment but have you authorized the new dhcp
server and have you redirected any dhcp relay agents to point to the new
dhcp server?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DHCP Import-Export 2
AD2K - 2K3/2K8 Migration question 4
DHCP Exim Tool 1
Windows 2000 to Windows 2003 DHCP migration 1
DNS migration 1
Moving DHCP Server from Windows 2000 Domain to Windows 2003 Domain Controller 2
Moving dhcp to a different server 2
DHCP & Wins Migrations 1

Back
Top