Michael- Anything is possible, so a DC reboot *might* help. A couple of questions. Where are you defining this policy? Is it on a GPO linked to someplace in AD or on the local GPO? If an AD-linked one, then have a look on the DC that the workstation is authenticating to (echo %logonserver% from the workstation). Look under SYSVOL\<domain>\policies\<guid of your GPO>\ADM and see if the changes you added to system.adm made it into that file. Also, look in that same folder in the machine sub-folder for a file called registry.pol. That is the file that hold any Admin Template policy you define. Its not quite a text file, but you can open it in notepad nonetheless. You should see a bunch of registry paths in there, which correspond to the settings you've made. Look for the path you've defined to verify its making it into the pol file on that DC. If its not, then look at the same file on your PDC role holder DC to see if its there. If it is, then you could have an FRS replication problem. You could try manually copying the registry.pol file from the PDC to the DC that your test workstation is using and see if that fixes anything.
Darren -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Wassell Sent: Friday, April 02, 2004 11:46 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) Does anyone think that a reboot of the DC might shed some light? Not that it is even an option right now, but I might be able to sneak one over the weekend 0:-) I've seen stranger things happen and somehow everything comes back to life when the DC is restarted... Perfect example: Boss' personal folder somehow caused explorer.exe to stop responding from any computer when accessed (including the server it was stored on). However, the folder contents could be copied using explorer, and a directory listing could be viewed from command prompt. Restart the DC, BAM! (Emeril style) everything's fine. I couldn't think anything except WTF?!?!?!. For anyone thinking it was probably because the folder had/has a mass abundance of garbage files in it, it wasn't that. Viewing "Open Files" from the compmgmt snapin on the server showed that desktop.ini was being accessed from within the folder by the hung process, but even closing every instance didn't fix the problem. That was the "Monday surprise". Sorry. I had to vent. 2 more hours to go ;-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Wassell Sent: Friday, April 02, 2004 1:58 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) There must be something I'm doing wrong then... I have no idea what it might be but it must be something I guess I'll just go RSOP my brains out and hopefully I'll catch something :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:49 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) that really is odd i took the text, pasted it into notepad, opened my local policy, imported the adm, filtered the view, enabled it...and it created the registry key fine... are there other settings in the same policy that are getting applied? |---------+----------------------------------> | | "Michael Wassell" | | | <[EMAIL PROTECTED]| | | om> | | | Sent by: | | | [EMAIL PROTECTED]| | | tivedir.org | | | | | | | | | 04/02/2004 12:36 PM | | | Please respond to | | | ActiveDir | | | | |---------+----------------------------------> >----------------------------------------------------------------------- -----------------------------------------------| | | | To: <[EMAIL PROTECTED]> | | cc: | | Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) | >----------------------------------------------------------------------- -----------------------------------------------| The registry is not being accessed at all from any of my attempts. I've even gone as far as to run a registry monitor to see if the registry is even being accessed and it is not. I have modified the system.adm file (created by default) to include the code and forced the GPO that does not apply either. I havn't run the registry monitor during boottime, but I have tried restarting numerous times and the registry is not changed in any way. I have modified the code to create a key also to see if the key is created and it is not. As a temporary solution (the application was only distributed to a limited amount of users) I have made the modifications manually to my own registry, extracted them and pushed them out to all of the workstations that are having the problem. Users have not been taught or instructed on how to use the new software yet so I have a bit of time to toy with thankfully. Definately a head scratcher.... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Seielstad Sent: Friday, April 02, 2004 1:18 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) Really... Hmm. Printers are generally profile specific, and the issue you're having sounds like it is user specific. Are you seeing the GPO get applied (verifying the registry settings) but they aren't working, or is the registry not being changed at all? As far as permissions, I believe GPO's are applied as localsystem - so there shouldn't be a perms problem. Not 100% sure what to tell you - other than verify the registry is actually being changed. Roger -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. From: Michael Wassell [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 12:58 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) Unfortunately not in this case Roger :-( Although, I do appreciate the advice. This particular printer is automatically created from an installer, which in turn creates the printer object underneath the HKLM hive. This allows for every user that logs into the workstation to have the printer automatically created, but unfortunately there is a bug causing the properties of the printer object to point to the %USERPROFILE%\Temp folder of the user that installed the client. Hence, insufficient rights when the user attempts to print to the printer object, which is why I'm trying to design the GPO to change the value in the registry to point to a folder all users have rights to (C:\temp). Would this inconsistency prevent the .ADM from functioning properly? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Seielstad Sent: Friday, April 02, 2004 12:50 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Custom .ADM (Code Included) Printers are per-User configurations, not per system wide in general. Try this as a CLASS USER -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. From: Michael Wassell [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 10:37 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] OT: Custom .ADM (Code Included) In the process of building a custom .ADM file for controlling specific registry keys. The problem I am having is that it does not seem to be modifying the key when the GPO is applied/enforced. I've been pulling my hair out all morning I can't seem to see any reason why this would be happening and I was hoping someone would be kind enough to enlighten me :-) Maybe there is a permissions issue with GPO in the subkey I am trying to modify? I don't know... TIA! (Code below) CLASS MACHINE CATEGORY !!Deployed CATEGORY !!EskerFax POLICY !!EskerPrinterOutput KEYNAME "Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\Lanfax for Outlook Printer\PrinterDriverData" EXPLAIN !!PrinterOutputLocation_Help PART !!PrinterOutputLocation EDITTEXT REQUIRED VALUENAME "Output Directory" END PART END POLICY END CATEGORY END CATEGORY [Strings] Deployed="Deployed Software" EskerFax="Esker Fax Client" EskerPrinterOutput="Esker Fax Client Configuration" PrinterOutputLocation_Help="Printer output temporary file location" PrinterOutputLocation="Printer output temporary file location" AcceptDefaultValue="Default Setting" SpecifyTempLocation="Specify desired log location" 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/ 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/ 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/ 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/
