w32time | Command line utility to measure process | Command Line Interface library

I just did a rewrite of your code.

I have removed variable $input, as that is an Automatic variable in PowerShell.

I also got rid of the second $Servers | ForEach-Object loop and made sure all parts of the code output a similar object to output in the GridView

According to this the +00.1323527 value you see is the actual offset between local time and the target computer time. If you’re seeing differences in the 0.00* range for actual offset, you can be highly confident that you have the correct system time. Anything with less than a second offset is reasonably good as well.

You can strip the time difference out like:

Your netstat shows the instance is listening on 127.0.0.1:80, 127.0.0.1:443 and 127.0.0.1:8172 (aka "localhost") for HTTP, HTTPS and Web deploy respectively. If you look at a working service like RDP its binding to 0.0.0.0:3389 (aka any/all IP's). Thats basically your issue - IIS is not listening on the servers network adapter / localhost is only available, well locally.

You can test this theory by rdp'ing to the server, and trying to connect via your instances public IP instead of localhost. My guess is this will fail, but localhost and 127.0.0.1 will still work. You would also be able to connect to web deploy locally - obviously thats a terrible/pointless idea - but same issue (can use putty or such to make a connection to prove its listening though).

You can just go into IIS and modify the site bindings in IIS Manager snapin- the IP address column should only contain * (When editing a binding, set the IP address to "All Unassigned"). I would guess they are currently localhost or 127.0.0.1?

Worth noting in theory IIS should backup its config at each change, so you should have a record of the old configuration in \windows\sytem32\inetsrv\history\cfgHistory_NNNNNNNNNN directory

The current IIS config is stored in inetsrv\config\applicationHosts.config. You can edit this file directly - but i would advise powershell or appcmd as they deals with the quirks of 32/64bit.

If you edit the config directly (stop the w3svc service first) remember to use a 64bit editor (like the builtin notepad.exe) to edit the 64bit config files (dont mess with the contents of SysWOW64\inetsvc - only use System32 even for 64bit files - its the "bitness" of the editor that determines which file Windows will modify)

NOTE Messing with applicationHosts.config can break IIS. Make sure you backup first, and i would strongly recommend using Powershell or AppCmd unless you fully understand the 32/64bit quirks (ie you make a change but it appears to be ignored).

See AppCmd (take a look at the backup/restore and the set binding examples) - https://docs.microsoft.com/en-us/iis/get-started/getting-started-with-iis/getting-started-with-appcmdexe

Also, if you edit the config, this is the reference: https://docs.microsoft.com/en-us/iis/configuration/

Is the script running locally on the target or from the server?

Credential objects are specific to the computer AND user account which creates them, so they are not transferable and can only be used on the computer which creates them.

Rename your lables :1 and :2 with :lab1 and :lab 2 then remove these lines:

This is the closest to what you want. It requires the choice command. There's still a blinking curser that is mildly annoying but you can solve that with third party commands if you wish.

One obvious thing to do is to pre-process your data file to remove the % signs. For example: