Set-ExchangeServer is looking for the identity of a named server, you
cannot change lots of servers without introducing a PowerShell loop
construction.
Set-ExchangeServer -Identity YourServer
Note 1: Set-ExchangeServer -Identity YourServer does
not change anything unless you add a parameter such as StaticGlobalCatalogs.
Let us employ PowerShell's internal help to research more parameters:
Get-Help Set-ExchangeServer
PowerShell's own help reveals parameters such as: StaticGlobalCatalogs,
StaticDomainControllers, and ErrorReportingEnabled.
Guy Recommends:
The SolarWinds Exchange Monitor
Here is a
free tool to monitor your Exchange Server. Download and
install the utility, then inspect your mail queues, monitor the Exchange
server's memory, confirm there is enough disk space, and check the CPU
utilization.
This is the real deal - there is no catch. SolarWinds provides this
fully-functioning freebie, as part of their commitment to supporting
the network management community.
Note 6: You can reverse this command by using the $false.
Guy Recommends: A Free Trial of the Network Performance Monitor
(NPM)
SolarWinds'
Network Performance Monitor
will help you discover what's happening on your network. This
utility will also guide you through troubleshooting; the dashboard will
indicate whether the root cause is a broken link, faulty equipment or
resource overload.
What I like best is the way NPM suggests solutions to network
problems. Its
also has the ability to monitor the health of individual VMware
virtual machines. If you are interested in troubleshooting, and creating
network maps, then I recommend that you try NPM now.
This PowerShell cmdlet is for changing Exchange Server 2010 attributes in
Active Directory; for example, static global catalog or error reporting.
Set-ExchangeServer does
nothing unless you add a parameter such as StaticGlobalCatalogs.
If you like this page then please share it with your friends
Please write in if you see errors of any kind. Please report any factual mistakes, grammatical errors or broken links, I will be happy to not only to correct the fault, but also to give you credit.
Windows Management Instrumentation (WMI) is
most useful for PowerShell scripting.
SolarWinds
have produced this
Free WMI Monitor to take the guess work out of which
WMI counters to use for applications like Microsoft Active Directory,
SQL or Exchange Server.