This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Question on the Exchange 2007-2010 Statistics with PowerShell Template

trilobite_rex over 8 years ago

Hi. I have powershell 2 on both the host and client I am trying to do this with. The winrm has been completed on both

H:\>winrm set winrm/config/client @{TrustedHosts="*.*.*.*"}

Client

NetworkDelayms = 5000

URLPrefix = wsman

AllowUnencrypted = false

Auth

Basic = true

Digest = true

Kerberos = true

Negotiate = true

Certificate = true

CredSSP = false

DefaultPorts

HTTP = 5985

HTTPS = 5986

TrustedHosts = *.*.*.*

So then when I go to run the stats it still gives me the error message that

Output: ==============================================

Message: Wrong version argument. Should be 2007 or 2010.

We are using Exchange 2007.

Any ideas/help is always greatly appreciated.

0 aLTeReGo over 8 years ago

Is this true for all components within the template? If not, which one(s) are returning this error?
Cancel
Vote Up 0 Vote Down

Cancel
0 trilobite_rex over 8 years ago in reply to aLTeReGo

All of them.
Cancel
Vote Up 0 Vote Down

Cancel
0 trilobite_rex over 8 years ago

So I have done some tweaking and changed from x32 to x64 and now I get test failed with down status.
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 8 years ago in reply to trilobite_rex

From what you describe it would appear you have not specified the appropriate script arguments for each component within the Application Template.
Cancel
Vote Up 0 Vote Down

Cancel
0 trilobite_rex over 8 years ago in reply to aLTeReGo

So I did that and now I get this.

attachments.zip
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 8 years ago in reply to trilobite_rex

Based on the error being returned it appears the user account you are using (which are the same as those used to manage the node) is not an Exchange Administrator. I would suggest either changing the credentials and use an account that is an Exchange Administrator or grant the account you are currently using Exchange Administrator rights.
Cancel
Vote Up 0 Vote Down

Cancel
0 trilobite_rex over 8 years ago in reply to aLTeReGo

Probably a dumb question but how would I tell what account it was. my personal account was the one that did the scans and added the nodes
Cancel
Vote Up 0 Vote Down

Cancel
0 christopher.t.jones123 over 8 years ago in reply to trilobite_rex

Under the node details is where it can be determined what creds are being used for managing the node.
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 8 years ago in reply to christopher.t.jones123

Based on the image002.png you posted above the application is inheriting its credentials from the node. In that same place you can change the credentials used by the application. You can also create new shared application credentials for monitoring application under [Settings -> SAM Settings -> Credentials Library]. Alternatively you can update/change/add/remove credentials used for managing nodes under [Settings -> Manage Windows Credentials]
Cancel
Vote Up 0 Vote Down

Cancel