Writing an HTML routine is not that difficult, but it??™s certainly not
a one-liner.
441 Chapter 13: Windows PowerShell
WINDOWS POWERSHELL AND .NET
Windows PowerShell was created out of the need to have a scripting language that could
easily interface with .NET managed code. With so much of Microsoft??™s own products
being developed in .NET managed code, it seemed natural to offer a solution to make
it simple for administrators (non-developers) to reap the benefits of having so many of
these .NET interfaces available. In fact, if something is .NET enabled, it can almost certainly
be managed with Windows PowerShell. This is great news since most, if not all, of
Microsoft??™s flagship products will be shifting toward leveraging the .NET Framework.
The good news for Windows administrators all over the world is that more and more of
Figure 13-5. HTML file created by running Get-ChildItem through ConvertTo-HTML
442 Microsoft Windows Server 2008 Administration
these systems will be completely available to us for automation using Windows Power-
Shell. These products will not only ship with .NET interfaces that can easily be used by
developers, but they will also supply their own set of cmdlets that allow administrators
to use Windows PowerShell for automating management tasks.
WINDOWS POWERSHELL, SCRIPTING, AND SECURITY
Naturally, a powerful command-line??“based shell supports the ability to be scripted.
Pages:
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468