I got it working. I had to remove the group membership portion of the script. If objFilesystem.FileExists("C:\windows\saplogon.ini") Then objFilesystem.DeleteFile "C:\windows\saplogon.ini", True End If objFilesystem.CopyFile "\\beaches\NETLOGON\saplogon.ini", "C:\windows\", True This is the working script. Thanks for all your help. On Thu, Apr 10, 2008 at 2:15 PM, Nelson, Jamie R < Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > Are you actually seeing the MsgBox prompts when you reboot the machine? > Did you have that in the original script you were having problems or did you > add those for troubleshooting after you implemented it as a startup script? > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 1:01 PM > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: Start up script GP > > > > This is the script. > > If objFilesystem.FileExists("C:\windows\saplogon.ini") Then > msgbox("1") > objFilesystem.DeleteFile "C:\windows\saplogon.ini", True > msgbox("2") > End If > msgbox("3") > objFilesystem.CopyFile "\\beaches\NETLOGON\saplogon.ini", > "C:\windows\saplogon.ini", True > msgbox("4") > > The message boxes tell me if it ran. > > On Thu, Apr 10, 2008 at 1:38 PM, Dave Palombi <dave.palombi@xxxxxxxxx> > wrote: > > Okay I have done what you have mentioned. It has ran today. To be sure, > I rebooted the machine and checked again. It has given me the lastest > time. The path is there and everything seems to be running. > > What is the next step. > > > > On Thu, Apr 10, 2008 at 1:31 PM, Darren Mar-Elia <darren@xxxxxxxxxx> > wrote: > > At the workstation, you can run RSOP.MSC and drill into the scripts > section (it looks just like the GP Editor namespace). It will tell you if > the script was being processed and when it last ran. > > > > Or, if you're not at the workstation, using GPMC's GP Results Wizard to > connect remotely to the machine and find out which GPOs and settings applied > during the last processing cycle. > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 10:29 AM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: Start up script GP > > > > How do I do that? I have never done that before. > > On Thu, Apr 10, 2008 at 12:01 PM, Nelson, Jamie R < > Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > > As Darren and I both suggested, also check RSOP and make sure the script > is actually being applied. > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 10:58 AM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: Start up script GP > > > > On windows vista, it works perfectly, but on windows XP it is not working > at all. > > This is very weird. I will try to put access on domain computers and we > will see what happens. > > On Thu, Apr 10, 2008 at 11:48 AM, Nelson, Jamie R < > Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > > If "Authenticated Users" has read access that should suffice. However, > I've seen weirdness before where access is denied until you actually add > "Domain Computers." Startup scripts run under the NT AUTHORITY\SYSTEM > context which is the equivalent of the machine's computer object. > > > > If it is a relatively small file, I would add it to the scripts/startup > folder of the GPO and copy it from there. Then you can be sure the machine > account is not being denied access. Also check RSoP and make sure the script > is actually being executed. > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 10:36 AM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: Start up script GP > > > > The location it is coming from is the netlogon folder that everyone has > access to. I do know that the script works because as a Domain admin it > copies the file over fine. It's only the users. > > On Thu, Apr 10, 2008 at 11:31 AM, Nelson, Jamie R < > Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > > Are you sure that your script is actually copying the file successfully? > Does the "Domain Computers" group have read access to the location you are > trying to copy from? > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 10:26 AM > > > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Re: Start up script GP > > > > I have done a gpupdate /force on the test computer. I have restarted the > test computer. It still does not work. > > Any ideas? > > On Thu, Apr 10, 2008 at 10:57 AM, Nelson, Jamie R < > Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > > Yes, startup scripts won't run at background refresh, even if you do a > gpupdate /force command. The machine will process the script policy but > won't actually execute the script unless you reboot. > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 9:49 AM > *To:* gptalk@xxxxxxxxxxxxx > > > *Subject:* [gptalk] Re: Start up script GP > > > > So you are saying for me to reboot the PC on top of replicating to all the > other domain controllers. > > On Thu, Apr 10, 2008 at 10:42 AM, Nelson, Jamie R < > Jamie.Nelson@xxxxxxxxxxxxxxxxxxx> wrote: > > Startup scripts don't run during a background policy refresh…the machine > actually has to be rebooted for them to execute. If you've already deployed > the Group Policy Preference extensions, you can also use that to copy files. > > > > *Jamie Nelson* | Systems Engineer | Systems Support, Information > Technology | *I N T E G R I S* *Health* | Phone 405.552.0903 | Fax > 405.553.5687 | http://www.integrisok.com > > > > *From:* gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Dave Palombi > *Sent:* Thursday, April 10, 2008 9:13 AM > *To:* gptalk@xxxxxxxxxxxxx > *Subject:* [gptalk] Start up script GP > > > > Hello, > > I have been trying to copy over a file to c:\windows before the users log > in. All users have domain users rights. (no access to anything) I need a > file copied over to c:\windows. I have added a start up script to the > computer configurations but when I do a gpresult it does not apply. I have > force a replication but it still does not seem to work. > > Dave > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > > > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > > > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > > > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > > > > > ------------------------------ > > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). > > > > > > > > > ------------------------------ > This e-mail may contain identifiable health information that is subject to > protection under state and federal law. This information is intended to be > for the use of the individual named above. If you are not the intended > recipient, be aware that any disclosure, copying, distribution or use of the > contents of this information is prohibited and may be punishable by law. If > you have received this electronic transmission in error, please notify us > immediately by electronic mail (reply). >