W2k
and xp update their own dns records but only when they renew their leases or get
a different lease. Here is a different way of doing it.
Shorten your leases to a couple of hours. The clients will update at the
50% time mark and register their new name. Tell me if it
works
-----Original Message-----
From: Wright, T. MR NSSB [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 11:08 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] AD DNS/DHCP issue/questionI'm pretty sure that will work... that was one of the aforementioned 'work arounds'. I was just curious why it wasn't updating itself as it does when I sit on the same network. Thanks for the ideas...-Tim
From: Carr, Jonathan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 10:08 AM
To: [EMAIL PROTECTED]You might want to run a post setup job to run ipconfig /registerdns-----Original Message-----
From: Wright, T. MR NSSB [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 8:46 AM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] AD DNS/DHCP issue/questionGonna try and keep this short and sweetI have 1200 clients that I am adding to the network. They get their new machine with our ghost image called 'image' they plug it into the network, when they bring it up they are asked a few questions (name, username etc.) this info is passed into the answer file for sysprep. The machine reboots, sysprep runs, it changes the name to meet our naming convention, adds it to the domain etc. then the user logs in for the first time and the logon scripts take care of the rest.My issue is when they first plug the machine in, the lease in DHCP server shows up as 'image' and once the machine is renamed and added to the domain, for some reason it doesn't update itself in DHCP which in turn doesn't update the DNS PTR record. I'm concerned that having 1200 machines called 'image' on the network is not going to be a good thing. This is all happening in another building on campus (through a few routers/switches)When I do the same test on the SAME network as the DHCP/DNS servers it works like a charm, the name is updated before the user logon box even appears. It seems as if there is some sort of broadcast traffic that is not getting to where it needs to get, although I was under the belief that once the client knows it's DHCP server it will automagically try to go back to the same machine first. I have asked the network guys to take a look, and as usualy they say theres nothing wrong with their network;-)I am using the default settings for the DHCP scope, and all the clients are WinXP pro SP1. I have a few ideas for a workaround but I would like to see it work as intended. Any ideas?Thanks,-Tim
