WSMAN: System.String IdleTimeout value shockingly high

Tagged: 

This topic contains 2 replies, has 2 voices, and was last updated by Profile photo of Jeff Taylor Jeff Taylor 5 months, 3 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #37277
    Profile photo of Jeff Taylor
    Jeff Taylor
    Participant

    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
    Profile photo of Dave Wyatt
    Dave Wyatt
    Moderator

    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
    Profile photo of Jeff Taylor
    Jeff Taylor
    Participant

    Dave, Excellent thanks for clarifying buddy.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.