WSMAN: System.String IdleTimeout value shockingly high

Welcome Forums General PowerShell Q&A WSMAN: System.String IdleTimeout value shockingly high

This topic contains 2 replies, has 2 voices, and was last updated by

 
Participant
2 years, 6 months ago.

  • Author
    Posts
  • #37277

    Participant
    Points: 0
    Rank: Member

    Wow....pretty sure we did not set this number:

    WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Shell

    Type Name SourceOfValue Value
    —- —- ————- —–

    System.String IdleTimeout 7200000

    The example on page 255 sounds a more reasonable 2,000 hours.

    Since the section stresses the importance of Administrator responsibility, how should I proceed for all of our 2008/2012 DCs?

  • #37303

    Member
    Points: 0
    Rank: Member

    7200000 is the number of seconds in 2000 hours. 🙂 Many of these sorts of things are stored as "number of seconds".

    60 * 60 * 2000

  • #37334

    Participant
    Points: 0
    Rank: Member

    Dave, Excellent thanks for clarifying buddy.

The topic ‘WSMAN: System.String IdleTimeout value shockingly high’ is closed to new replies.