Going on a Get-Date - Series - pr0mpthttps://www.pr0mpt.com/series/going-on-a-get-date/Going on a Get-Date - Series - pr0mptHugo -- gohugo.ioenWed, 03 Feb 2016 13:25:34 +0200Going on a Get-Date…part 1https://www.pr0mpt.com/2016-01-27-going-on-a-get-date-part-1/Wed, 27 Jan 2016 13:37:17 +0200Robert Prüsthttps://pr0mpt.comhttps://www.pr0mpt.com/2016-01-27-going-on-a-get-date-part-1/ Simple issues, simple solutions?

Recently I’ve been doing quite some break-fix cases, which didn’t quite make blogging a high priority.

It did on occasion provide me with nice little gems that I decided to spend a little personal time on, because I thought it would be better to force myself to use PowerShell instead of resolving things manually or through a GUI. Also, I thought these issues would be “simple, quick solutions”, which turned out to be a bit too optimistic.

]]>Going on a Get-Date…part 2https://www.pr0mpt.com/2016-02-03-going-on-a-get-date-part-2/Wed, 03 Feb 2016 13:25:34 +0200Robert Prüsthttps://pr0mpt.comhttps://www.pr0mpt.com/2016-02-03-going-on-a-get-date-part-2/As mentioned previously in my first part of this Get-Date series, I had run into some issues that were seemingly easy to resolve, yet proved to be a bit more hassle than expected.

Funny enough, the second issue where I ran into date issues was just a day or so apart from the first, so I thought I’d resolve my issues with the knowledge I had obtained previously.

The Problem

I had received an Excel sheet which contained various information, one column being Warranty dates. Now the issue was that the Excel sheet was generated on a system which had NL-NL Culture configuration, while my machine is running on EN-US configuration.

]]>