Thank you for your post. When you were running the ITScript, were you ensuring that this was being run against a machine group or set of machine groups? I've tested the script running with a machine group and it reported the correct machine name and the correct time on that machine.
Hi Anthony. Thanks.
Yes. I have run the script directly on the server and on the machine group and it still gives me same local time as on the console.
I'm sure I run this before and got local time then.
Anyone has a suggestion?
If that is still the case where you're seeing the wrong information, please open a support case here so that we can investigate that. That issue would be something of a support related item and should be addressed as such.
I opened a case - and got the answer: It works as designed!
Sorry, but I'm not agree to this.
Description says: "This script gets the local date and time of the target system(s)"
Make no sense to me that if I'm scanning targets all around the world to get target local time (to estimate deployment time frames)- I only get local console time back (same as I'm trigger the script from) Why should I use the script then?
I have raised a change request for this - please wote for a change.
BR / Mike