DRRAM
asked on
number of PCs in each site
Please
I Have a server Windows 2008 Domain Controler (active directory) and i have several site in the AD
Please how can I know the number of PCs in each site
(via ??? or other solution : link between DHCP and Active directory )
Thx
I Have a server Windows 2008 Domain Controler (active directory) and i have several site in the AD
Please how can I know the number of PCs in each site
(via ??? or other solution : link between DHCP and Active directory )
Thx
ASKER
Can you give me another idea please ???
If you are wanting to know the computer names on each site......
assuming each site has a different IP Range
GO to Start>Programs>Administrat ive Tools
Open DNS
Expand DC Name
Expand Domain Name
IN the list on the right you will see all the current PCs which have obtained an IP Adress listed according to Computer Name.
Now Arrange the List by IP Address.
Ideally you should know what IP Range is associated to what site.
Once known and arranged, you can quickly and accuratley gadge what PCs are at what Site, Their Computer Names, their IP Addresses, even Pritners.
assuming each site has a different IP Range
GO to Start>Programs>Administrat
Open DNS
Expand DC Name
Expand Domain Name
IN the list on the right you will see all the current PCs which have obtained an IP Adress listed according to Computer Name.
Now Arrange the List by IP Address.
Ideally you should know what IP Range is associated to what site.
Once known and arranged, you can quickly and accuratley gadge what PCs are at what Site, Their Computer Names, their IP Addresses, even Pritners.
Well, AD Sites are merely logical containers of subnets, so to find out how many workstations you have under each site, you need to count the workstations under the subnets associated to the site.
Now, to count the workstations, you need some sort of an IP scanner. You could just look at the address leases on DHCP, but that won't give you any workstation that has a static IP address, so it won't be accurate. Besides, you'll have to figure out which leases are for computers and which ones are for printers/phones/etc.
I think the quickest way to do this is through ZenMap (http://nmap.org/zenmap/). Just download it, put the IP range of each subnet (ex. 192.168.0.1-254), and run a quick scan. There might be other ways that I don't know about, so let's see what others say.
Now, to count the workstations, you need some sort of an IP scanner. You could just look at the address leases on DHCP, but that won't give you any workstation that has a static IP address, so it won't be accurate. Besides, you'll have to figure out which leases are for computers and which ones are for printers/phones/etc.
I think the quickest way to do this is through ZenMap (http://nmap.org/zenmap/). Just download it, put the IP range of each subnet (ex. 192.168.0.1-254), and run a quick scan. There might be other ways that I don't know about, so let's see what others say.
@apache09, yes but DNS still won't give him an accurate picture of all the workstations. Non-Windows workstations (Mac, Linux) won't auto-register their A records on DNS through DHCP. The same thing applies to phones and printers. The A records for these need to be added manually.
The only real, sure-fire way to find every single device in the subnet(s) is to ping/scan every IP, while watching the ARP table. Most modern boxes have firewalls and don't respond to pings or unsolicited requests anyway. The MAC addresses from the ARP table can then be referenced in a manufacturer look up table, to determine device type. Nmap is also pretty good at guessing OS type. This could all be automated with a little script-fu, of course.
Digus is right, but that's a very time consuming process.
NMap (ZenMap) still detects the hosts if you run an intense scan, since it doesn't rely on ICMP (ping) responses only. It looks for hosts by scanning for open ports on the entire IP range, and a few other methods which I don't remember, but it can still miss a few.
NMap (ZenMap) still detects the hosts if you run an intense scan, since it doesn't rely on ICMP (ping) responses only. It looks for hosts by scanning for open ports on the entire IP range, and a few other methods which I don't remember, but it can still miss a few.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm still testing it now
This also somewhat depends on what you want to count as PC.
Nmap and other scanning tools will of course only detect PCs that are switched *on* during the scan.
The existence of computer accounts in AD may be a better idea to catch PCs not running, but may contain stale entries ...
Nmap and other scanning tools will of course only detect PCs that are switched *on* during the scan.
The existence of computer accounts in AD may be a better idea to catch PCs not running, but may contain stale entries ...
LOL, thehagman is right. I guess if you really need to know the actual number, you should grab a pen and a piece of paper and walk through the site. If there are way to many computers, or you don't have access to the site, then a combination of all of the above should at least give you an idea. Again, I highly recommend Spiceworks for network auditing/monitoring, I just can't imagine how I could live without it.
ASKER
THX
Even better, you can install SpiceWorks (free) on any workstation, add all the subnets to its configuration, and scan the entire network. Be aware that SpiceWorks is resource-intensive on the workstation that it's running on, but it gives you a very detailed image of all your devices, down to the installed software, hardware utilization, event logs, and so on.