Inconsistent AD login application

itcinc · 07-07-2009, 08:44 PM

I have 6.2 running well after a reinstallation from scratch. I have deployed the AD script as a group policy per the wiki. The AD setup page tests fine and users are pulled properly from the AD.

However, the results from the domain login seem to be inconsistent. If I look at the users logged in via the AD connect screen it only shows SOME of the users. Other users I know have restarted and logged back in but do not show.

The server is Windows 2003 Std R2 Sp2. The event log shows event 1085:
"The Group Policy client side extension scripts failed to execute. Please look for any errors reported earlier by that extension." I have not yet correlated the user login with the time shown in the event log but I bet they match with a user login that does not show on the AD logged in users.

The articles that I have seen regarding this error refer to earlier versions of Windows 2003. I have not yet had a chance to view the event log on the client workstations running Windows XP Sp3 but would expect a similar error to be reported.

All users have the same kixstart login script on the Profile tab. I have also added Domain Users to the Untangle Login group policy. All users are members of Domain Users. All client computers are identical Dell Optiplex 330 with Windows XP Pro Sp3.

Do you think the Group Policy is the best way to deploy the AD login script? I would prefer to use a login script - probably in vb - but have not tried too hard to make that work.

Any thoughts on troubleshooting steps or ideas?

Ron

sky-knight · 07-07-2009, 10:38 PM

I believe the issue is kixstart.

There was another user here in the past that had to make a batch script call the VBS via kixstart to get around it. Something to do with the way that scripting environment.

itcinc · 07-13-2009, 09:31 PM

I have determined that kixtart is NOT the problem. The AD script works fine with the kixstart script WHEN the users reboot following the installation. For some users following instructions is not their forte.

Also had one user with a profile that seemed to be a problem. An application of chkdsk /f and removing temporary files fixed him up and now he shows on the list of active directory users. Oh yea, he is now limited to only a handful of specific work related sites too!

Untangle is good stuff! Now if only it has AD group support we would really be rockin'.

Ron

WebFooL · 07-14-2009, 01:56 AM

Quote:

Untangle is good stuff! Now if only it has AD group support we would really be rockin'.

Vote for it :P
http://bugzilla.untangle.com/show_bug.cgi?id=2660

itcinc · 07-14-2009, 08:03 AM

Quote:

Originally Posted by WebFooL

Vote for it :P
http://bugzilla.untangle.com/show_bug.cgi?id=2660

I already have. Can I stuff the ballot box and vote again?

Ron

07-07-2009, 08:44 PM	#1 (permalink)
itcinc Master Untangler Join Date: Dec 2008 Location: Dallas, TX Posts: 256	Inconsistent AD login application I have 6.2 running well after a reinstallation from scratch. I have deployed the AD script as a group policy per the wiki. The AD setup page tests fine and users are pulled properly from the AD. However, the results from the domain login seem to be inconsistent. If I look at the users logged in via the AD connect screen it only shows SOME of the users. Other users I know have restarted and logged back in but do not show. The server is Windows 2003 Std R2 Sp2. The event log shows event 1085: "The Group Policy client side extension scripts failed to execute. Please look for any errors reported earlier by that extension." I have not yet correlated the user login with the time shown in the event log but I bet they match with a user login that does not show on the AD logged in users. The articles that I have seen regarding this error refer to earlier versions of Windows 2003. I have not yet had a chance to view the event log on the client workstations running Windows XP Sp3 but would expect a similar error to be reported. All users have the same kixstart login script on the Profile tab. I have also added Domain Users to the Untangle Login group policy. All users are members of Domain Users. All client computers are identical Dell Optiplex 330 with Windows XP Pro Sp3. Do you think the Group Policy is the best way to deploy the AD login script? I would prefer to use a login script - probably in vb - but have not tried too hard to make that work. Any thoughts on troubleshooting steps or ideas? Ron

07-07-2009, 10:38 PM	#2 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 7 Posts: 9,951	I believe the issue is kixstart. There was another user here in the past that had to make a batch script call the VBS via kixstart to get around it. Something to do with the way that scripting environment. __________________ Intouch Technology Rob Sandling, BS:SWE, MCP Office: 480-272-9889 rob@intouchtechllc.com

07-13-2009, 09:31 PM	#3 (permalink)
itcinc Master Untangler Join Date: Dec 2008 Location: Dallas, TX Posts: 256	I have determined that kixtart is NOT the problem. The AD script works fine with the kixstart script WHEN the users reboot following the installation. For some users following instructions is not their forte. Also had one user with a profile that seemed to be a problem. An application of chkdsk /f and removing temporary files fixed him up and now he shows on the list of active directory users. Oh yea, he is now limited to only a handful of specific work related sites too! Untangle is good stuff! Now if only it has AD group support we would really be rockin'. Ron