Bruce-
I looked through your script that you had posted here previously (I'm assuming its the
same one you're having problems with). I didn't see anything that immediately popped
out. One thing I would suggest is to modify the script to add some debugging info at
key points, using the FileSystem
I am trying to troubleshoot why my logoff script
will not run for users. Whenever I run the RSoP it gives an error "the system
could not find the file specified." It doesn't say what file. RSoP will run for
my account. Other policies are being applied for the users but not the logout
script.
Thanks for everyone's feedback. OLDCMP is now released on my web site
(www.joeware.net). Here were the changes for V1.4.0
O Removed Default sort - records returned in the order AD returns them by
default
O If you specify a sort method and also select dhtml, it won't force the
server to do the sor
I have a former student (a PSS tech.) looking into the very same thing and
received a voicemail/email last night outlining precisely the behavior you
reference. The Microsoft definition of a lingering object (in my opinion
and this instance) is too strict and an unnecessarily "guarded" (my two
pen
Is it possible to import an S/MIME cert for an AD mail-enabled contact?
Andy
List info : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
Thanks Darren!
I will do that! I had the users
placed in the power users group and I tested by going out to Windows Update…
It didn’t work, but I think we’re going to push those out ourselves
anyway. Installing software after putting the user in power users
worked. Thanks for the h
Joe-
If I follow what you're asking for, I think you could use a machine-based Restricted
Groups Policy on a GPO linked to the LaptopUsers OU to accomplish what you want. In
most cases on XP, the local Power Users group should give a user sufficient rights to
install software. So, if you set up
Hey everyone out there!
Please advise: I’m working on getting a bunch of
laptops (Windows XP Pro) out (Windows 2003 AD) and want to create a group
policy that states: IF Laptop is in laptopUsers OU then – allow any user
to install software on it.
Maybe my logic is off, but here’
I did some tests and looks like method #2 (removelingeringobject)
won't work in described case. Apparently MS guys are checking that
object is not just "lingering" - it has to be also created more than
tombstone lifetime in the past. I tried both repadmin and rootDSE
attribute ways - no avail.
