View Full Version : AD Logon Script
sky-knight
10-01-2008, 03:46 PM
I have just deployed the vbs script into group policy. I can see wscript.exe running on the clients now. Is there a way to test this software any further other than wait for a report?
The live event logs in the rack are still showing raw IP's.
tbelote
10-01-2008, 04:14 PM
Yes goto https://untangle_ip_address/adpb/debug
or something like that.
It should show a list of all the usernames and associated ip addreses.
sky-knight
10-01-2008, 04:24 PM
Very nice thanks, that link shows IP, Username, and Machine Name.
sky-knight
10-01-2008, 04:28 PM
WHOAOHAHAHAHA HOLD THE PHONE!!
This page you pointed me at doesn't require any authentication!! We've just exposed internal network configuration data and usernames to the FREAKING INTERNET!
sky-knight
10-01-2008, 04:29 PM
Never mind... it just cached my credentials.
tbelote
10-01-2008, 04:56 PM
Yes, it should require you login as admin at least once, somewhere. Let me know though if you find a way it doesn't :)
sky-knight
10-01-2008, 06:53 PM
So now I guess we get to find out if this thing can keep up with machines connected to the network twice. ;)
Yes, I have id10t users that insist on being on the wire and wireless segments at the same time.
JGrubbs
10-20-2008, 01:07 PM
What is the best way to get the users who are not showing up on this list to be included? Simply reboot their workstations?
They may be excluded for other reasons. To be on the list, the user must satisfy the following criteria:
1. Normal account
2. Not expired
3. Not locked out
4. Password is required
5. They must be able to change their own password
JGrubbs
10-20-2008, 03:43 PM
I fixed it!! For some reason the script was missing from the Group Policy Management where I had it setup before. I'm not sure how it got removed, but that is why the rest of our users were not showing up in the list. I just set it back up and rebooted my system and now I am in the list.
YeOldeStonecat
10-23-2008, 07:42 AM
They may be excluded for other reasons. To be on the list, the user must satisfy the following criteria:
1. Normal account
2. Not expired
3. Not locked out
4. Password is required
5. They must be able to change their own password
Criteria # 5 is strange.....you're talking about their domain account?
I'm having issues troubleshooting the AD connector..and users showing up in the user list under /debug.
The first day I deployed the GPO and the ad logon script...a few computers showed up in the reports..including a test workstation I used. But since then....on a network of 60+, I only had several show up that first day..and the list has dwindled down to nothing since then. Been 2 weeks now....people have certainly rebooted since then.
sky-knight
10-23-2008, 01:20 PM
I'm seeing the same thing... but I can't put my finger on a reason. We have a 60 seat network and 23 people show? I haven't had time to work through the missing users to see if it is a wscript issue, or heck.. given how crazy this place is it MAY be accurate! And the 60 seat number is over inflated.
sky-knight
10-23-2008, 01:22 PM
Oh, and I forgot to mention that I have 2 accounts the user cannot change their own password on showing in the debug list. So I don't think that is a real limitation.
YeOldeStonecat
10-29-2008, 05:36 AM
Sky-Night...you found anything yet? As to why user list disappears, or de-populates?