
Part III: Working with PowerShell in a Production Environment
388
netsh interface set interface name = “$Interface1” newname = “$Interface1_New”
netsh interface set interface name = “$Interface2” newname = “$Interface2_New”
netsh interface ip set address name=”$Interface2_New” source=static “$IP” “$Subnet”
netsh interface ip set dns name=”$Interface2_New” static none none
netsh interface set interface “$Interface2_New” enable
$Install_Directory=”C:\EX2007”
Cd $Install_Directory
./Setup.com /role:m
Summary
This chapter described the implementation and management of a two - node SCC cluster. The first half of
the chapter described the individual components and how through PowerShell these install steps are
automated. Before PowerShell, performing an automated install would have required knowledge of
batch scripts, Visual Basic, and a hodgepodge of unattended files and still would not have provided the
same result as using PowerShell. Using PowerShell in conjunction with system and application
commands provides for an easier, more efficient use of scripts to perform common administrative tasks.
The power of having .NET functionality built in allows for manipulation of variables, objects, and data
that is more robust and has a better framework.
(continued)
c13.indd 388c13.indd 388 12/17/07 3:58:09 PM12/17/07 3:58:09 PM