
Doug Kinsey
Comments
-
Thanks, Shane. Figured that one out after a few minutes of head scratching.
-
However, when the next AD sync occurred, it erased the non-domain machine from inventory.
-
Well, adding the machine name to the hosts file did the trick.
-
I am able to ping the machine, yes. I agree it must be something basic that is being overlooked, but perhaps I am just not meant to track non-domain equipment the easy way!
-
0 Tests failed when I analyzed the machine. The result of nbtstat gives me the machine name/groups and MAC address. Yes, I can access the ADMIN$ on the remote machine, but I am prompted for usern...
-
Thanks, Shane. I have allowed access, double checked DNS, checked firewall, set Standard Profile Group Policy, and still no dice. The PCs add to the list with no problem at all, but that is al...
-
Powershell came back as true, but I went ahead and disjoined and rejoined the domain anyway. All is well with the world again. Hard telling exactly what happened, but it is working normally now. ...
-
Thanks, Stephen. I will give that a shot. I should also add, this is the 4th Windows 10 PC I am pushing out, the others went oddly easy. This one is making me pay for it.
-
Thanks, Jason. I thought permissions too until it worked with the IP address. Everything is set exactly as it is on other computers that are working fine. I'm wondering if it might be a hiccup i...
-
Yes, that's actually where I pulled the IP address from to try deploying by that.