Your script looks about right although I can't test at the mo, you don't need a compiler just put it in a text file with notepad or something and make the extension .vbs job done ;)
Printable View
Your script looks about right although I can't test at the mo, you don't need a compiler just put it in a text file with notepad or something and make the extension .vbs job done ;)
I hope you are right I will test it out. Is there anything else I should take into consideration.
I am basically building a new network from the ground up, trying to write tutorials and protocols for the network as I go along so others that follow don't get stuck like I am.
As you can tell I am not a Net Admin but I am learning fast and I am for sure documenting everything I know that much from other stuff.
- MilitantEidolon
There are a lot of things to take into account, just read, read and read some more this wouldn't be a bad place to start though http://www.microsoft.com/windowsserv...c/default.mspx . One of the things I wish I had known about when I started was pstools http://www.sysinternals.com/ntw2k/fr.../pstools.shtml
It is a great free suite of tools for remotely doing things on NT/2000/XP machines, you can run tasks, log people off, reboot, check what processes are running on their machine, very very useful, trust me.
Oh yeah and get good at googles search options, you are going to need them.
Attached is the logon script that I tried to use... (Correct syntax I think) The only thing is that I never tested the Network part because I have no drives to map too. Another note, some AV scanners (such as Norton AV 2004) will not allow vbs scripts to run due to their popularity in VXing (virus-writing). You may need to disable that feature, or something of that sort otherwise it may not run.
Norton asks whether the script should be allowed or not. Tell it to allow it "always" and it will stop complaining.
I have decided to skip the login script and just use roaming profiles how does that sound?
- MilitantEidolon
The main disadvantage with roaming profiles is you get some users who like to keep their files on their desktop (ie in their profiles). When they log on this can lead to fairly long log on times and a sharp rise in network traffic, especially at 9 in the morning or when ever your users start work.
Using roaming profiles for doing what ?
Can you be more specific? Roaming profiles will not map network drives for you as far as I know they just let users take their settings around with them. This is fine if they usually stay at one computer but sometimes move but if they are moving all the time it can be a pain. I mean apart from anything a roaming profile takes your default printers and everything around with them. This means that they have to check which printer they are sending to when they move to a different room etc. The network traffic is also a bit of a downside as has already been mentioned. I would say mapping drives it definately a job for logon scripts, you could put the shortcuts in the all users desktop folder for all machines with a script.
Well the reason I have chose roaming profiles is because it infact does map drives and keeps all the users files (My Documents - Start Menu) and so on. The roaming profiles (at least in Win 2003) are a really slick way to keep users happy.Quote:
Roaming profiles will not map network drives for you as far as I know they just let users take their settings around with them.
- MilitantEidolon