Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal CMDB

Discovery > Discovery Modules > Enterprise Applications > Microsoft Exchange Server by PowerShell Discovery > How to Configure PowerShell Remoting

How to Configure PowerShell Remoting

This task describes how to enable PowerShell remote access.

This task includes the following steps:

Launch the PowerShell configuration

In the PowerShell command prompt run the winrm quickconfig.

Note From the moment that the PowerShell configuration is launched, you must differ between the server side configuration and client side configuration.
Configure the server-side machine
On the server, depending on the authentication method that will be used, perform the following steps:
1. Run cd WSMan:\localhost\Service\Auth.
2. Run dir and verify that the required authentication type is enabled, that is, the State = True. If the required authentication type is disabled, run "et-Item <AuthTypeName> True. By default, Kerberos and Negotiate are enabled.
3. Run cd WSMan:\localhost\Service and verify that IPv4Filter or IPv6Filter are set to either "*" or to any other valid value for your environment.
4. Run cd WSMan:\localhost\Listener, and then dir. Verify that the listener actually listens to the required IPs. By default, the listener listens to all IPs if the value "*" is used.
5. If you made any changes, restart the winrm service by running the restart-service winrm command.
Configure the client-side machine
On the client machine, perform the following steps:
1. Run cd WSMan:\localhost\Client\Auth.
2. Run dir and verify that the required authentication type is enabled, that is, the State = True. If the required authentication type is disabled, run Set-Item <AuthTypeName> True.
  
  Note The allowed protocols must coincide with the ones configured on the server side.
3. Run cd WSMan:\localhost\Client.
4. Run dir and check value of TrustedHosts. By default, the value is empty so that no connection outside is possible. TrustedHosts is an ACL field where the allowed values are a domain name or a list of domain names and an IP address or a list of IP addresses. The value may have a special symbol "", meaning that any destination or any symbol can appear in any part of the specified destinations list. If the only value is "", then the client is allowed to connect to any host. This is the recommended value.
  
  To change the value for TrustedHosts, use Set-Item TrustedHosts <Value>.
  
  Note No translation from FQDN to IP is done while validating the ACL. This means that if the connection is performed by IP and only an FQDN is listed in the TrustedHosts field (or vice versa), the connection will not be allowed.
5. If you made any changes, restart the winrm service by running the restart-service winrm command.