You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to set or override the 600 second default timeouts used Connect-SQL? In our environment, a 5-10 second connection timeout is more than enough to know if it's online. I'm building a script that iterates instances and invokes dsc resources for each. I have some instances that can be offline temporarily. I have to manually include or skip them or endure a 600 second delay. I might have to port test each instance before invoking the resource. It does seem like a custom connect timeout could be a feature in the module.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is there any way to set or override the 600 second default timeouts used Connect-SQL? In our environment, a 5-10 second connection timeout is more than enough to know if it's online. I'm building a script that iterates instances and invokes dsc resources for each. I have some instances that can be offline temporarily. I have to manually include or skip them or endure a 600 second delay. I might have to port test each instance before invoking the resource. It does seem like a custom connect timeout could be a feature in the module.
Beta Was this translation helpful? Give feedback.
All reactions