Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am in the process of building a new windows domain (migration from Novell) and need to write a login script to map network drives/printers. In the past I have used vbscript mixed in with a little wmi as needed. I am considering using Powershell and am wondering if this is a good choice or if there are even better options. The network is small ~ 20 xp machines and 5-10 printers.

share|improve this question

closed as primarily opinion-based by HopelessN00b Dec 5 '14 at 10:50

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

My investigations into powershell ...… – Tubs May 22 '09 at 10:21
up vote 2 down vote accepted

I still use vbscript, because that is what is available on older versions of windows still used on our network without adding additional software. I frequently want my startup and login scripts to work on newly installed machines.

share|improve this answer

Take a look at Group Policy Preferences, if you don't have any Win2K Pro. No scripts and lots of options and filtering, including WMI like filtering only no scripting necessary. It also has a lot of other features like pushing shortcuts/files/regkeys/printers etc.

I just finished (this past weekend) a migration from Novell to Microsoft. It certainly eases my short term pain of no ZenWorks replacement(Buying LANDesk next quarter).

You should definitely take a look.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.