Vista - PS or VB?

All,

If we are looking at using a single scripting platform from servers down to
workstations do we want to even eval PS yet or wait a few years until it is
fully matured?

Thanks!

IMO The answer solely depends on management style.

If you do a lot of quick and dirty one off scripts I would say Powershell is
far superior. So much better in fact you will find yourself not writing
scripts at all, but instead you write interactive solutions.

* If you do a lot of cross platform (server/workstation/XP/2000/2003/98)
then VBScript is still the best option. When dealing with lots of machines
it is best to reduce the number of dependencies. So unless your able to do
what you need from a central location (or at least a small amount of
servers) then Powershell isn't quite there yet.

* If you spend most of your day in the cmd shell... Powershell was made just
for you!

* You specify "from servers down to workstations." Can you clarify what you
generally trying to achieve. Basically determine if you can manage the
workstation from the server. At this point of time (for the next year I
would say) I wouldn't want to have to rely on powershell being installed for
my management solution to work. So unless you are able to achieve your goal
from a central location... stick with VBScript/Cmd.

"Ryan" <someone@somewhere.com> wrote in message
news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
> All,
>
> If we are looking at using a single scripting platform from servers down
> to workstations do we want to even eval PS yet or wait a few years until
> it is fully matured?
>
> Thanks!
>

Why not to use both? PS really works for me already. For many tasks I do not
see a reason for waiting a few years. For other supportive scripting tasks I
use and will use Perl, WSH, C#. Meanwhile my primary work is in C++. But if
you have doubts I would recommend to wait at least for a released version.

--
Thanks,
Roman

Currently we don't do a whole lot of scripting but we do use it for our
logon scripts right now and thats about it.

However...Now that we got rid of our last Novell box and are all AD we would
like to implement more scripting. We are a small shop (2 sys admins and 2 PC
techs) of which none of us have backgrounds in scripting or coding except
for logon scripts. This explains why we want to keep the environment
simplified so that if the other net admin (who doesn't do ANY scripting) has
to fix something while I am out its at least slightly easier.

The tasks we are really looking to script are:
Logon Scripts
User Creations - Copying a current user that is similar that is defined by
the manager
Exchange mailboxes
Home directories

Thanks!


"Brandon Shell" <tshell.mask@gmail.com> wrote in message
news:%23eSqNrK6GHA.4280@TK2MSFTNGP04.phx.gbl...
> IMO The answer solely depends on management style.
>
> If you do a lot of quick and dirty one off scripts I would say Powershell
> is far superior. So much better in fact you will find yourself not writing
> scripts at all, but instead you write interactive solutions.
>
> * If you do a lot of cross platform (server/workstation/XP/2000/2003/98)
> then VBScript is still the best option. When dealing with lots of machines
> it is best to reduce the number of dependencies. So unless your able to do
> what you need from a central location (or at least a small amount of
> servers) then Powershell isn't quite there yet.
>
> * If you spend most of your day in the cmd shell... Powershell was made
> just for you!
>
> * You specify "from servers down to workstations." Can you clarify what
> you generally trying to achieve. Basically determine if you can manage the
> workstation from the server. At this point of time (for the next year I
> would say) I wouldn't want to have to rely on powershell being installed
> for my management solution to work. So unless you are able to achieve your
> goal from a central location... stick with VBScript/Cmd.
>
> "Ryan" <someone@somewhere.com> wrote in message
> news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
>> All,
>>
>> If we are looking at using a single scripting platform from servers down
>> to workstations do we want to even eval PS yet or wait a few years until
>> it is fully matured?
>>
>> Thanks!
>>
>

Giving your requirements... I would say your a long way from being able to
select powershell as your sole scripting language. If your goal is to only
use one language... VBScript is it. That said... For each task my
recommendation follows
Logon Scripts
- No Option here Vbscript or Batch is it

User Creations - Copying a current user that is similar that is defined
by the manager
- Both do this equally... Powershell had more flexibility and faster
change management

Exchange mailboxes
- Definitely Powershell (specifically in Exch12.) VBScript (IMO) has
lacked in the Exchange department.

Home directories
- I like Powershell for this as well. Powershell Filesystem access is
wonderful.

"Ryan" <someone@somewhere.com> wrote in message
news:e$nC3zK6GHA.2380@TK2MSFTNGP02.phx.gbl...
> Currently we don't do a whole lot of scripting but we do use it for our
> logon scripts right now and thats about it.
>
> However...Now that we got rid of our last Novell box and are all AD we
> would like to implement more scripting. We are a small shop (2 sys admins
> and 2 PC techs) of which none of us have backgrounds in scripting or
> coding except for logon scripts. This explains why we want to keep the
> environment simplified so that if the other net admin (who doesn't do ANY
> scripting) has to fix something while I am out its at least slightly
> easier.
>
> The tasks we are really looking to script are:
> Logon Scripts
> User Creations - Copying a current user that is similar that is defined by
> the manager
> Exchange mailboxes
> Home directories
>
> Thanks!
>
>
> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
> news:%23eSqNrK6GHA.4280@TK2MSFTNGP04.phx.gbl...
>> IMO The answer solely depends on management style.
>>
>> If you do a lot of quick and dirty one off scripts I would say Powershell
>> is far superior. So much better in fact you will find yourself not
>> writing scripts at all, but instead you write interactive solutions.
>>
>> * If you do a lot of cross platform (server/workstation/XP/2000/2003/98)
>> then VBScript is still the best option. When dealing with lots of
>> machines it is best to reduce the number of dependencies. So unless your
>> able to do what you need from a central location (or at least a small
>> amount of servers) then Powershell isn't quite there yet.
>>
>> * If you spend most of your day in the cmd shell... Powershell was made
>> just for you!
>>
>> * You specify "from servers down to workstations." Can you clarify what
>> you generally trying to achieve. Basically determine if you can manage
>> the workstation from the server. At this point of time (for the next
>> year I would say) I wouldn't want to have to rely on powershell being
>> installed for my management solution to work. So unless you are able to
>> achieve your goal from a central location... stick with VBScript/Cmd.
>>
>> "Ryan" <someone@somewhere.com> wrote in message
>> news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
>>> All,
>>>
>>> If we are looking at using a single scripting platform from servers down
>>> to workstations do we want to even eval PS yet or wait a few years until
>>> it is fully matured?
>>>
>>> Thanks!
>>>
>>
>
>

Brandon...

Thank you for your input! You are thinking the same way I was thinking. We
are going to be going to EX 12 and thats what brought on the whole PS
discussion.

One last question...can PS be built into a HTA? I know when we want to be
able to create a lot of what we do and will do into HTAs in the future.

Maybe it will be best to do two languages.

Thanks again!
Ryan

"Brandon Shell" <tshell.mask@gmail.com> wrote in message
news:esn0h6K6GHA.1188@TK2MSFTNGP05.phx.gbl...
> Giving your requirements... I would say your a long way from being able to
> select powershell as your sole scripting language. If your goal is to only
> use one language... VBScript is it. That said... For each task my
> recommendation follows
> Logon Scripts
> - No Option here Vbscript or Batch is it
>
> User Creations - Copying a current user that is similar that is defined
> by the manager
> - Both do this equally... Powershell had more flexibility and faster
> change management
>
> Exchange mailboxes
> - Definitely Powershell (specifically in Exch12.) VBScript (IMO) has
> lacked in the Exchange department.
>
> Home directories
> - I like Powershell for this as well. Powershell Filesystem access is
> wonderful.
>
> "Ryan" <someone@somewhere.com> wrote in message
> news:e$nC3zK6GHA.2380@TK2MSFTNGP02.phx.gbl...
>> Currently we don't do a whole lot of scripting but we do use it for our
>> logon scripts right now and thats about it.
>>
>> However...Now that we got rid of our last Novell box and are all AD we
>> would like to implement more scripting. We are a small shop (2 sys admins
>> and 2 PC techs) of which none of us have backgrounds in scripting or
>> coding except for logon scripts. This explains why we want to keep the
>> environment simplified so that if the other net admin (who doesn't do ANY
>> scripting) has to fix something while I am out its at least slightly
>> easier.
>>
>> The tasks we are really looking to script are:
>> Logon Scripts
>> User Creations - Copying a current user that is similar that is defined
>> by the manager
>> Exchange mailboxes
>> Home directories
>>
>> Thanks!
>>
>>
>> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
>> news:%23eSqNrK6GHA.4280@TK2MSFTNGP04.phx.gbl...
>>> IMO The answer solely depends on management style.
>>>
>>> If you do a lot of quick and dirty one off scripts I would say
>>> Powershell is far superior. So much better in fact you will find
>>> yourself not writing scripts at all, but instead you write interactive
>>> solutions.
>>>
>>> * If you do a lot of cross platform (server/workstation/XP/2000/2003/98)
>>> then VBScript is still the best option. When dealing with lots of
>>> machines it is best to reduce the number of dependencies. So unless your
>>> able to do what you need from a central location (or at least a small
>>> amount of servers) then Powershell isn't quite there yet.
>>>
>>> * If you spend most of your day in the cmd shell... Powershell was made
>>> just for you!
>>>
>>> * You specify "from servers down to workstations." Can you clarify what
>>> you generally trying to achieve. Basically determine if you can manage
>>> the workstation from the server. At this point of time (for the next
>>> year I would say) I wouldn't want to have to rely on powershell being
>>> installed for my management solution to work. So unless you are able to
>>> achieve your goal from a central location... stick with VBScript/Cmd.
>>>
>>> "Ryan" <someone@somewhere.com> wrote in message
>>> news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
>>>> All,
>>>>
>>>> If we are looking at using a single scripting platform from servers
>>>> down to workstations do we want to even eval PS yet or wait a few years
>>>> until it is fully matured?
>>>>
>>>> Thanks!
>>>>
>>>
>>
>>
>

In theory I don't see why not you couldn't use Powershell with HTA. It would
require coding at a different level than scripting, but to be honest... I'm
like yourself... just a network engineer that uses scripts to make my life
easier... I'm not a coder.

I would say its wise to maintain the skill set in both languages.

"Ryan" <someone@somewhere.com> wrote in message
news:eyfoDCL6GHA.1012@TK2MSFTNGP05.phx.gbl...
> Brandon...
>
> Thank you for your input! You are thinking the same way I was thinking. We
> are going to be going to EX 12 and thats what brought on the whole PS
> discussion.
>
> One last question...can PS be built into a HTA? I know when we want to be
> able to create a lot of what we do and will do into HTAs in the future.
>
> Maybe it will be best to do two languages.
>
> Thanks again!
> Ryan
>
> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
> news:esn0h6K6GHA.1188@TK2MSFTNGP05.phx.gbl...
>> Giving your requirements... I would say your a long way from being able
>> to select powershell as your sole scripting language. If your goal is to
>> only use one language... VBScript is it. That said... For each task my
>> recommendation follows
>> Logon Scripts
>> - No Option here Vbscript or Batch is it
>>
>> User Creations - Copying a current user that is similar that is defined
>> by the manager
>> - Both do this equally... Powershell had more flexibility and faster
>> change management
>>
>> Exchange mailboxes
>> - Definitely Powershell (specifically in Exch12.) VBScript (IMO) has
>> lacked in the Exchange department.
>>
>> Home directories
>> - I like Powershell for this as well. Powershell Filesystem access is
>> wonderful.
>>
>> "Ryan" <someone@somewhere.com> wrote in message
>> news:e$nC3zK6GHA.2380@TK2MSFTNGP02.phx.gbl...
>>> Currently we don't do a whole lot of scripting but we do use it for our
>>> logon scripts right now and thats about it.
>>>
>>> However...Now that we got rid of our last Novell box and are all AD we
>>> would like to implement more scripting. We are a small shop (2 sys
>>> admins and 2 PC techs) of which none of us have backgrounds in scripting
>>> or coding except for logon scripts. This explains why we want to keep
>>> the environment simplified so that if the other net admin (who doesn't
>>> do ANY scripting) has to fix something while I am out its at least
>>> slightly easier.
>>>
>>> The tasks we are really looking to script are:
>>> Logon Scripts
>>> User Creations - Copying a current user that is similar that is defined
>>> by the manager
>>> Exchange mailboxes
>>> Home directories
>>>
>>> Thanks!
>>>
>>>
>>> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
>>> news:%23eSqNrK6GHA.4280@TK2MSFTNGP04.phx.gbl...
>>>> IMO The answer solely depends on management style.
>>>>
>>>> If you do a lot of quick and dirty one off scripts I would say
>>>> Powershell is far superior. So much better in fact you will find
>>>> yourself not writing scripts at all, but instead you write interactive
>>>> solutions.
>>>>
>>>> * If you do a lot of cross platform
>>>> (server/workstation/XP/2000/2003/98) then VBScript is still the best
>>>> option. When dealing with lots of machines it is best to reduce the
>>>> number of dependencies. So unless your able to do what you need from a
>>>> central location (or at least a small amount of servers) then
>>>> Powershell isn't quite there yet.
>>>>
>>>> * If you spend most of your day in the cmd shell... Powershell was made
>>>> just for you!
>>>>
>>>> * You specify "from servers down to workstations." Can you clarify what
>>>> you generally trying to achieve. Basically determine if you can manage
>>>> the workstation from the server. At this point of time (for the next
>>>> year I would say) I wouldn't want to have to rely on powershell being
>>>> installed for my management solution to work. So unless you are able to
>>>> achieve your goal from a central location... stick with VBScript/Cmd.
>>>>
>>>> "Ryan" <someone@somewhere.com> wrote in message
>>>> news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
>>>>> All,
>>>>>
>>>>> If we are looking at using a single scripting platform from servers
>>>>> down to workstations do we want to even eval PS yet or wait a few
>>>>> years until it is fully matured?
>>>>>
>>>>> Thanks!
>>>>>
>>>>
>>>
>>>
>>
>
>

If you're going to E12, then needing that skillset is a given.

Security considerations may have some bearing on the need to adopt PS down
to the workstation level because of the ability to enforce an execution
policy that isn't there with other scripting options.

(IMHO)

"Ryan" wrote:

> Brandon...
>
> Thank you for your input! You are thinking the same way I was thinking. We
> are going to be going to EX 12 and thats what brought on the whole PS
> discussion.
>
> One last question...can PS be built into a HTA? I know when we want to be
> able to create a lot of what we do and will do into HTAs in the future.
>
> Maybe it will be best to do two languages.
>
> Thanks again!
> Ryan
>
> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
> news:esn0h6K6GHA.1188@TK2MSFTNGP05.phx.gbl...
> > Giving your requirements... I would say your a long way from being able to
> > select powershell as your sole scripting language. If your goal is to only
> > use one language... VBScript is it. That said... For each task my
> > recommendation follows
> > Logon Scripts
> > - No Option here Vbscript or Batch is it
> >
> > User Creations - Copying a current user that is similar that is defined
> > by the manager
> > - Both do this equally... Powershell had more flexibility and faster
> > change management
> >
> > Exchange mailboxes
> > - Definitely Powershell (specifically in Exch12.) VBScript (IMO) has
> > lacked in the Exchange department.
> >
> > Home directories
> > - I like Powershell for this as well. Powershell Filesystem access is
> > wonderful.
> >
> > "Ryan" <someone@somewhere.com> wrote in message
> > news:e$nC3zK6GHA.2380@TK2MSFTNGP02.phx.gbl...
> >> Currently we don't do a whole lot of scripting but we do use it for our
> >> logon scripts right now and thats about it.
> >>
> >> However...Now that we got rid of our last Novell box and are all AD we
> >> would like to implement more scripting. We are a small shop (2 sys admins
> >> and 2 PC techs) of which none of us have backgrounds in scripting or
> >> coding except for logon scripts. This explains why we want to keep the
> >> environment simplified so that if the other net admin (who doesn't do ANY
> >> scripting) has to fix something while I am out its at least slightly
> >> easier.
> >>
> >> The tasks we are really looking to script are:
> >> Logon Scripts
> >> User Creations - Copying a current user that is similar that is defined
> >> by the manager
> >> Exchange mailboxes
> >> Home directories
> >>
> >> Thanks!
> >>
> >>
> >> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
> >> news:%23eSqNrK6GHA.4280@TK2MSFTNGP04.phx.gbl...
> >>> IMO The answer solely depends on management style.
> >>>
> >>> If you do a lot of quick and dirty one off scripts I would say
> >>> Powershell is far superior. So much better in fact you will find
> >>> yourself not writing scripts at all, but instead you write interactive
> >>> solutions.
> >>>
> >>> * If you do a lot of cross platform (server/workstation/XP/2000/2003/98)
> >>> then VBScript is still the best option. When dealing with lots of
> >>> machines it is best to reduce the number of dependencies. So unless your
> >>> able to do what you need from a central location (or at least a small
> >>> amount of servers) then Powershell isn't quite there yet.
> >>>
> >>> * If you spend most of your day in the cmd shell... Powershell was made
> >>> just for you!
> >>>
> >>> * You specify "from servers down to workstations." Can you clarify what
> >>> you generally trying to achieve. Basically determine if you can manage
> >>> the workstation from the server. At this point of time (for the next
> >>> year I would say) I wouldn't want to have to rely on powershell being
> >>> installed for my management solution to work. So unless you are able to
> >>> achieve your goal from a central location... stick with VBScript/Cmd.
> >>>
> >>> "Ryan" <someone@somewhere.com> wrote in message
> >>> news:%2373ueYK6GHA.4552@TK2MSFTNGP05.phx.gbl...
> >>>> All,
> >>>>
> >>>> If we are looking at using a single scripting platform from servers
> >>>> down to workstations do we want to even eval PS yet or wait a few years
> >>>> until it is fully matured?
> >>>>
> >>>> Thanks!
> >>>>
> >>>
> >>
> >>
> >
>
>
>

Ryan,

If you are going to be using Exchange Server 2007 you will need to be
at leastbasically literate in PowerShell since the Exchange Management
Shell in Exchange Server 2007 uses PowerShell technology. The Exchange
Management Shell has a full range of E2007 management commands. The
Exchange Management Console (the GUI tool) doesn't.

Be aware that the Exchange Server 2007 Beta 2 is using norms e.g.
install directories not consistent with the PowerShell RC2 ones. Watch
for a later build of E2007 that is fully PowerShell compatible.

Andrew Watt MVP

On Thu, 5 Oct 2006 14:00:22 -0500, "Ryan" <someone@somewhere.com>
wrote:

>Thank you for your input! You are thinking the same way I was thinking. We
>are going to be going to EX 12 and thats what brought on the whole PS
>discussion.