Before you launch PowerShell 3.0, remember to right-click and: 'Run as Administrator',
otherwise you get an error message when your try Update-Help.
Recollect that Update-Help is new in v3.
It is best to launch the plain command-line version of PowerShell, Update-Help is one
instance where the ISE version seems a little flaky, or it could just be
that I was using the CTP 2 beta version of PowerShell 3.0.
As usual, working with non-English versions of PowerShell 3.0 can be a
trial. One technique is to download the help files by using the
Save-Help cmdlet, then import by appending the -source parameter.
# Prepare to Schedule an Update for Help If ((Get-Date).DayOfWeek -eq "Friday") {Update-Help}
Save the above PowerShell command, for example: Update.ps1. Take a
note of your full path: e.g. D:\PShell\Update.ps1. Then run
this file as a scheduled task. See more about using
PowerShell to schedule a task.
Free Monitor for Your Network: SolarWinds Real-time Traffic Analyzer
The main reason for monitoring your network is to check at a glance which
servers are available. If there is a network problem you
want an interface to show the scope of the problem immediately.
Even when all servers and routers are available, sooner or later you will be curious to
know who, or what, is hogging the precious network's bandwidth. A GUI
showing the top 10 users always makes interesting reading.
Another reason to monitor network traffic is to learn more about your
server's response times and the consumption of resources. To take the pain out of
capturing frames and analysing the raw data, Guy recommends that you download a copy of
the SolarWinds
free Real-time NetFlow Analyzer.
Problems with Help Files
For a scripting language PowerShell has always had above average help for
its commands. The sheer volume of cmdlets in PowerShell 3.0 mean that
Microsoft needed a new strategy for making sure the information was
accurate.
With PowerShell 1.0 the help files were cast in stone. If there were
typos or more serious errors there was no easy way to update the
information. Matters improved in PowerShell 2.0 with the -online
parameter which directed requests to updates online. However, one has
to remember to append that command, it did not change the local help files.
In PowerShell 3.0 Microsoft came up with the idea of built-in cmdlet to
refresh the help files when errors are fixed back at PowerShell
head-quarters.
Summary of PowerShell's Updateable Help
The first point to remember is that this cmdlet is only available on
PowerShell v 3.0 and later. I found Update-Help particularly difficult
to configure so that it delivered the package of revised help files.
If you like this page then please share it with your friends
