[shahed26]

Hi
i want to run a CMD file , which has reg tweaks and silent install application switches. It works on vista by placing a cmd file in "sources\$OEM$\setup\scripts" folder, but in server 2008, how do i run a cmd file at first logon to apply my reg tweaks and setup my silent apps, i couldn't run WPI, or cmd files by placing it in $OEM$ on server DVD ISO. Does anybody know how to get cmd files running on first logon?

Thanks

This post has been edited by shahed26: 05 June 2008 - 01:38 PM

[joe43wv]

My guess would be to create a batch file to execute those scripts and place the batch file in the first logon file.

[shahed26]

joe43wv, on Jun 5 2008, 08:42 PM, said:

My guess would be to create a batch file to execute those scripts and place the batch file in the first logon file.

Thanks, will try that, never used the "bat" extension before, its always been "cmd"

[shahed26]

No, still does not work.. the first thing i get on first logon is to create a password after that its the normal desktop, no batch or cmd files run..

[shahed26]

joe43wv, on Jun 5 2008, 08:42 PM, said:

place the batch file in the first logon file.

is there such a folder "logon folder" to place a batch file to get it running?

This post has been edited by shahed26: 05 June 2008 - 08:31 PM

[aviv00]

open gpedit.msc
check the picture

Attached File(s)

•  123.png (73.4K)
  Number of downloads: 47

[shahed26]

aviv00, on Jun 6 2008, 10:15 AM, said:

open gpedit.msc
check the picture

Thanks, but i wanted to run the script only at RunOnce in first logon, eg, "WPI" on first logon after installation.

It works fine on vista when i place a "cmd" file on $oem$ folder, but not on server.. am sure there is a way, but can't seem to figure it out..

This post has been edited by shahed26: 06 June 2008 - 07:04 AM

[joe43wv]

shahed26, on Jun 5 2008, 10:30 PM, said:

joe43wv, on Jun 5 2008, 08:42 PM, said:

place the batch file in the first logon file.

is there such a folder "logon folder" to place a batch file to get it running?

Ya I think if you edit the runonce registry key that could take care of it.