yep, go for it

side note:- but how do you update DNS with the workstation details -- the beauty of using Windows DHCP is that it automatically updates DNS using the DHCP registrations

 

i,ll answer my own question you must update them manually

 

ipconfig / registerdns is always a good way

 

quite right kieran

had a blonde moment --

and if you have the Register this connection's addresses in DNS check box ticked -- in the network properties it will do it for you automatically

the DHCP will do it for older clients that cant register automatically

aplologies for any confusion

 

yep, just update DNS manually

if I did use windows DHCP, and made a change in the DNS, how long would it take for this change to register on the workstations ? Would that interval be dictated by the DHCP lease time ?

Ok, I'm going to go for it! Feel much better knowing the AD will be fresh as a daisy and not carrying anything over from Win2k or NT4 before that!

Must say everyone on here has been brilliant , particularly Hanley and Hodgy who have the patience of a saint to deal with an idiot like me!

Wish me luck!

 

ooh, that's one to file away in my memory! cheers!

 

got the new domain / domain controller up and running along with a fully functioning DNS server onboard. In fact AD wizard did all the work and even set my TCP > primary DNS up as localhost!

Only single problem was in the event 12 - which is to do with the ntp client. Can't believe I have to go into the registry and hack it to point to an external time source. Isn't there an application that can do this for me ?

 

Wow - I've had a couple of days off putting my new garage floor in and you've created a new AD environment!!

Once all your desktops are members of the new domain I would try and get rid of the dodgy object...you'll have nothing to lose and it will give you good experience.

Well done, I bet you feel you've learnt a lot over the last couple of weeks, once it's all done you can relax and have a few

 

if you want to reregister an IP address through DHCP immediately then use:

ipconfig /release
ipconfig /renew

in that order, you'll get a new DHCP allocated address then.

Oh, and if you want to reset the DNS cache on the p.c. when you do this:

ipconfig /flushdns

 

external ntp time source on the Forest root is done by:

net time /setsntp:[external_time_source]

speak to your ISP for the name/ip address of their NTP Server

 

although not actually needed for a functioning AD, so I wouldn't worry too much about it

 

lovely - thanks all!

 

All sorted?

 

Just migrating the applications installed on the current server. It's taken a little bit longer than nornal.

eg. the coldfusion application I wrote has now been relocated onto a web server at our website hosts. They were running a much newer version which threw up a couple of incompatibilities that I fixed yestersay. Also, because there's a restriction on space on the web hosts server, I had to optimise all the photography used in the database, which I've just finished.

I've moved the accounts package over.

Then I've got to transfer the time recorder / clock-in/out application that talks to the punch machines in both factories.

I'm currently recreating all the user accounts on the new server.

I've been checking the event logs and everything looks rosey!

 

That's good - 'cos if you have any more problems we're not going to help you, cheeky beggar

 

I've learned a LOT about Windows Server and AD in the last 2 weeks. I'm extemely lucky to have had such a great bunch to help me.

With the experience I've gained, looking back on it, I'm in a better position to evaluate a problem like that in future. Sometimes the simplest solution is the correct one! Ockham's Razor was correct!

 

KISS!!