Linda Poltersdorf
asked on
Unable to see all computers.
I have tried all the resolutions I could find to be able to view all computers on my domain. I have turned on network discovery file sharing and print sharing,
Started these services "Function Discovery Provider Host" and "Function Discovery Resource Publication" DNS Client - Automatic, SSDP Discovery - Automatic, UPnP Device Host
Enabled SMB 1.0/CIFS File in Programs and Features both the SMB 1.0/CIFS Client and Server.
Ran this command from admin cmd prompt netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes
I still an unable to see all computers and before win 10 I could even see my servers cannot now.
Started these services "Function Discovery Provider Host" and "Function Discovery Resource Publication" DNS Client - Automatic, SSDP Discovery - Automatic, UPnP Device Host
Enabled SMB 1.0/CIFS File in Programs and Features both the SMB 1.0/CIFS Client and Server.
Ran this command from admin cmd prompt netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes
I still an unable to see all computers and before win 10 I could even see my servers cannot now.
Rob Williams
"Function Discovery Resource Publication" usually resolves this in a Win 10 environment and almost immediately. Did you change it from manual to automatic and then start it.
Personally I am not a fan of trying to see all of the devices. It hasn't been necessary since Windows 2000. It is even more challenging if you have multiple subnets, or hundreds to thousands of devices.
Drive mappings can be done through GPO (preferably to a DFS Namespace).
Printers can be published to AD or assigned via GPO.
I don't tell users the names of servers, and there is no need for them to know. The only reason why they need to know the name of their own device is so they can tell us which device to remote into when they need remote support.
Drive mappings can be done through GPO (preferably to a DFS Namespace).
Printers can be published to AD or assigned via GPO.
I don't tell users the names of servers, and there is no need for them to know. The only reason why they need to know the name of their own device is so they can tell us which device to remote into when they need remote support.
ASKER
I did change it from manual to automatic and then start it.
On the computer I am using. The reason I am interested it I was trying to eliminate unnecessary workstations using bandwith by shutting them down remotely. I am the admin of our domain and when we shutdown for covid 19 people left their computers on.
On the computer I am using. The reason I am interested it I was trying to eliminate unnecessary workstations using bandwith by shutting them down remotely. I am the admin of our domain and when we shutdown for covid 19 people left their computers on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I use free Specops Gpupdate to remotely shut down devices, and boot back up.
https://specopssoft.com/product/specops-gpupdate/
Your firewall should be able to tell you what is active. An idle machine shouldn't consume much bandwidth. If it is, it is likely in use, getting updates, or something is wrong and needs to be investigated.
https://specopssoft.com/product/specops-gpupdate/
Your firewall should be able to tell you what is active. An idle machine shouldn't consume much bandwidth. If it is, it is likely in use, getting updates, or something is wrong and needs to be investigated.
Thanks Linda. Sounds like you have it resolved.
Cheers!
Cheers!