What do you use for your logon scripts.

[Kyle]

I was just wondering what you all use/prefer to use for your log on scripts?

 

Do you use .vbs, .bat, cmd etc?

 

DO you use a mixture or do you stick to one file type and if so why?

 

After visiting a couple of our primary schools i noticed they all use different, (depending on who set them up)

[john]

I use .bat for all mine at all my sites

[DMcCoy]

I used to use cmd, everything is vbs now though

[GrumbleDook]

vbs here too (apart from me ... but I like .bat files)

[wesleyw]

VBS, bat and EXE here depending on need. I write quite a few progs to run at login/logoff and startup/shutdown so I have an audit trail of every PC when they are on or off and when pupils and staff login and logout.

 

Wes

[tarquel]

.bat and .cmd mainly

 

Nath

[Geoff]

Whatevers easiest. eg, drive mapping is a .cmd but printer mapping is a .vbs

[ChrisH]

VBS and a batch script. Depends what it needs. I am not going to write the extra three lines of code in VB if a simple batch script will do it in one line.

[webman]

RM CC3 does it all for us so we don't have to change any.

[ajbritton]

Whatever seems easiest at the time. Mostly .VBS with a smattering of .CMD and a hint of compiled .AU3

[nsherin]

Simple .bat files do the job for us here.

[NetworkGeezer]

@AJBritton

Hmmm I wonder about the compiled AutoIT scripts though. Doesn't this require both the interpreter and script to extracted from the EXE and then load and finally executed.

Wouldn't this slow down the logons or at least mean that you wouldn't have a guranteed time line?

 

@everyone else

VBS has some nice stuff in it but it feels slightly sluggish compared to KiX even with overhead of having to load the interpreter. Yeah I know VBS is builtin to windows so no problem about deployment, especailly as KiX tends to have more version changes.

[Gatt]

KiXtart scripts for most stuff and is used to call.

Batch files for BGInfo Wallpapers

VBS for Printers & Renaming Mapped Drives

[WithoutMotive]

Kixtart scripts for everything

[ajbritton]

@AJBritton

Hmmm I wonder about the compiled AutoIT scripts though. Doesn't this require both the interpreter and script to extracted from the EXE and then load and finally executed.

Wouldn't this slow down the logons or at least mean that you wouldn't have a guranteed time line?

 

Have to say that I've never noticed a delay when executing a compiled AutoIT script. Most logon time is spent processing group policy anyway.

 

Whatever scripting language you use, the interpreter will have to load and execute.

 

I tend to use AutoIT when I need a user interface or to do automation. In these cases, absolute speed is not really a concern.

[plexer]

batch for logon scripts that map network drives at the moment.

vbs for printers and tweaking other settings.

 

Ben

[kingswood]

batch for logon scripts that map network drives at the moment.

vbs for printers and tweaking other settings.

 

Ben

 

Same here. But I am learning VBScript and other things at the moment and might change things in the future at some point. Traditionally I have loved batch scripts- but my HND course has moved us away from "easier" to "bloody learning curve"

[pete]

Batch for drives, vbs for printers and WMI queries. Stuff gets prototyped in batch scripts usually.

 

A few of my scripts are in perl, since scriptomatic can export to perl (and python), and I can then get a (linux) monitoring box to run the scripts against workstations.