Evil rumour? .bat vs .vbs for logon drive mapping...

[Miscbrah]

Morning.

 

Just tinkering with my new domain here and giving some thought to mapping drives for staff at logon. I SEEM to remember from my hazy and distant technician past some wise old sage telling me NOT to use batch files full of 'net use wossname' to map drives, and instead use vbs scripts full of 'objNetwork.MapNetworkDrive wossname' with the thinking being that loads of staff calling this single batch file is worse than loads of staff calling a vbs file.

 

Is this true or is this not true and neither is better/worse? We're not on Win7 JUST yet, so this is me keeping it XP friendly until the summer...

 

Anyone feel like mythbusting for me?

 

Cheers!

[jonnykewell1]

we use a bat file and have no issues whatsoever.

[Miscbrah]

we use a bat file and have no issues whatsoever.

 

Thanks fellow MCDST!

[jonnykewell1]

hahaha

[Michael]

There's no difference. You can write a single .bat or .vbs file so all staff are using the same file at logon.

 

When you deloy a 2008 R2 server, along with XP/7 clients, you can deploy network drives via GPO. I no longer have any logon scripts, only a couple of Startup scripts which install anti-virus (if not installed) and deploy wireless configuration settings if not installed.

 

The only catch with XP is you must ensure KB934729 is installed, otherwise it will fail. You can deploy this with WSUS. Windows 7 will work with GPP out the box.

[MYK-IT]

There's no difference. You can write a single .bat or .vbs file so all staff are using the same file at logon.

 

When you deloy a 2008 R2 server, along with XP/7 clients, you can deploy network drives via GPO. I no longer have any logon scripts, only a couple of Startup scripts which install anti-virus (if not installed) and deploy wireless configuration settings if not installed.

 

The only catch with XP is you must ensure KB934729 is installed, otherwise it will fail. You can deploy this with WSUS. Windows 7 will work with GPP out the box.

 

Ditto here.

[zag]

and deploy wireless configuration settings if not installed.

 

Thats quite cool, any chance of a sample script?

 

I always wondered if you could set the wireless settings up using a script.

[Michael]

Have a look here. The only catch is only Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support the netsh wlan command.

 

XP does not recognise this command, (even if you set it to deploy) it would just be ignored.

[Michael]

The only other catch is the computer in question must be plugged in via Ethernet once to receive the wireless configuration. After this it will work wirelessly.

 

By setting the policy and linking it, then typically imaging, running Sysprep and joining the domain, the computer must be plugged in via Ethernet first time anyway, so this just saves an additional job setting the wireless config manually.

[Miscbrah]

There's no difference. You can write a single .bat or .vbs file so all staff are using the same file at logon.

 

When you deloy a 2008 R2 server, along with XP/7 clients, you can deploy network drives via GPO. I no longer have any logon scripts, only a couple of Startup scripts which install anti-virus (if not installed) and deploy wireless configuration settings if not installed.

 

The only catch with XP is you must ensure KB934729 is installed, otherwise it will fail. You can deploy this with WSUS. Windows 7 will work with GPP out the box.

 

 

I had NO idea! I'm installing that sod immediately.

 

TA!!!