Unattended Install and RunOnce

Mike Glynn

unread,

May 8, 1997, 3:00:00 AM5/8/97

to

The NT4 Unattended installation supports the use of a RunOnce registry
entry that will run a script or batch file upon first login. Has nayone
used this and made it work? I have been unsucessful.

Kevin Wandtke

unread,

May 11, 1997, 3:00:00 AM5/11/97

to

I've used the RUNONCE as shown in the Automating guide. I ran a batch file
that did several NET USE commands to set up drive mapping then ran a
software distribution program (WinINSTALL) to load the software. We do
that rather than SYSDIFF (which I use for the real basic setup) because
it's easier to add patches, new programs, etc... But the RUNONCE worked
great!

Mike Glynn <gl...@earthlink.net> wrote in article
<#SqnPk9W...@uppssnewspub04.moswest.msn.net>...

Walter Lee

unread,

May 12, 1997, 3:00:00 AM5/12/97

to

When you do RUNONCE with autologon as administrator to local machine?
How do you specific where to logon to, " To the Domain" or " To the
local station" Because after unattended installation, on the Logon
Box, the domain is default to actual domain instead of local station ?
How do you get away from it?

My E-mail address is walte...@cellone-sf.com. Thanks a lot.

Bradley Plett

unread,

May 13, 1997, 3:00:00 AM5/13/97

to

>.... Could you tell me how to
>use the "Run" entry with a batch files and remove the Run entry from
>the registry. My E-mail address is walte...@cellone-sf.com

I'd rather you hire me <g>, but sure, I'll give away my secrets.
Sorry about the line wraps.

$OEM$\CMDLINES.TXT
==========
[Commands]
"rundll32 setupapi,InstallHinfSection DefaultInstall 128
.\Generic.INF"

$OEM$\Generic.INF
==========
; Run the additional batch file
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","SetupBat",0,"cmd
/c C:\Temp\SetupBat.bat"

$OEM$\C\Temp\SetupBat.bat
==========
rundll32 setupapi,InstallHinfSection DefaultInstall 128
C:\Temp\DelReg.inf

$OEM$\C\Temp\DelReg.inf
==========
[Version]
Signature = "$Windows NT$"

[DefaultInstall]
DelReg = DelReg

[DelReg]
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","SetupBat"

Walter Lee

unread,

May 13, 1997, 3:00:00 AM5/13/97

to

Thanks a lot. I am going to try it.

On Tue, 13 May 1997 15:56:24 GMT, ple...@cadvision.com (Bradley Plett)
wrote:

>>.... Could you tell me how to
>>use the "Run" entry with a batch files and remove the Run entry from
>>the registry. My E-mail address is walte...@cellone-sf.com
>
>I'd rather you hire me <g>, but sure, I'll give away my secrets.
>Sorry about the line wraps.
>
>$OEM$\CMDLINES.TXT
>==========
>[Commands]
>"rundll32 setupapi,InstallHinfSection DefaultInstall 128

>\Generic.INF"
>
>$OEM$\Generic.INF
>==========
>; Run the additional batch file
>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","SetupBat",0,"cmd
>/c C:\Temp\SetupBat.bat"
>
>$OEM$\C\Temp\SetupBat.bat
>==========
>rundll32 setupapi,InstallHinfSection DefaultInstall 128
>C:\Temp\DelReg.inf
>
>$OEM$\C\Temp\DelReg.inf
>==========
>[Version]
>Signature = "$Windows NT$"
>
>[DefaultInstall]
>DelReg = DelReg
>
>[DelReg]
>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","SetupBat"
>

Walter Lee
E-mail:walte...@cellone-sf.com

Walter Lee

unread,

May 14, 1997, 3:00:00 AM5/14/97

to

I have the same problem you have. I kicked off Office 97 installation
on Runonce. It did not work because the first actual login has not
finished. After first actual login, I kicked off Office
installation again. Then, this time works. Could you tell me how to

use the "Run" entry with a batch files and remove the Run entry from
the registry. My E-mail address is walte...@cellone-sf.com

On Fri, 09 May 1997 16:54:47 GMT, ple...@cadvision.com (Bradley Plett)
wrote:

>>The NT4 Unattended installation supports the use of a RunOnce registry

>>entry that will run a script or batch file upon first login. Has nayone
>>used this and made it work? I have been unsucessful.
>

>Yes, I've had this working. The thing I found, though, was that not
>all components of NT are available when RunOnce gets used during
>unattended installation. The RunOnce entry seems to get executed too
>soon (before the first actual login). For example, I was not able to
>do much in the line of networking (anything using "net use") at that
>point. What I ended up doing instead was using the "Run" entry with a
>batch file and then the last thing I do in the batch file is remove

>the Run entry from the registry.
>

>Good luck!
>Brad.

Bradley Plett

unread,

May 15, 1997, 3:00:00 AM5/15/97

to

>I also had this problem while using a SYSDIFF type of install. I found
>that to get the runonce to work after the autologon the runonce had to be
>the last statement in my cmdlines.txt. Here's what my cmdlines.txt looks
>like now:
>
>[Commands]
>".\regedit.exe /s .\autolog.reg"
>".\regedit.exe /s .\shortcut.reg"
>"rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\diff.INF"
>".\regedit.exe /s .\runonce.reg"
>
>If runonce is before rundll32 it runs too early.

Thank-you very much - I'll try that. This may explain the problem!

Brad.