AD Schema

[Chris]

Is there a way to add a custome property to a computer object in AD.
Specificly the current IP address of a computer. Maybe even the default
gatway and name server entries ?

 

[Joe Richards [MVP]]

Yes you can easily add those to the schema, but it doesn't mean that the
computers will update it. You will have to have some script or tool that runs on
the clients and updates the info. You also have to consider if there are any
concerns with additional replication load in the event that the info changes
daily say if you have a DHCP environment with a very short lease period.

 

[Kevin D. Goodknecht Sr. [MVP]]

Is there a way to add a custome property to a computer object in AD.
Specificly the current IP address of a computer. Maybe even the
default gatway and name server entries ?

The IP address would be impossible in a group policy, you'd need a different
policy for every computer. DHCP can assign these, but there is a group
policy for the DNS servers that works on XP and 2k3 clients.
Look here:
Computer Configuration
-Administrative templates
-Network
-DNS Client
OR you could let DHCP assign all these then disable users access to TCP/IP
properties in this policy:
User Configuration
-Administrative templates
-Network
-Network Connections

Of course if users don't have local administrative rights on their computers
they won't have access to TCP/IP either.

 

[Guest]

If you're running dynamic dns, try just pinging the computer name.

Simple and it works.

 

[Kevin D. Goodknecht Sr. [MVP]]

If you're running dynamic dns, try just pinging the computer name.

I think I mis-read the OP's question, I was getting out of it to be able to
assign an IP address.
So far as it goes, if the client is using DHCP and the DHCP server is on
Windows servers, you can view the leased IP addresses in the DHCP console
regardless of if they use DDNS.