@scottalanmiller said:
@Martin9700 said:
(Invoke-WebRequest ifconfig.me/ip).Content
Sweet, just tried it here, works great.
Still like the output from my script better--more PowerShellish. It's also quite a bit faster (the ifconfig.me site seems pretty sluggish).
Not sure, but I did find that this works though:
(Invoke-WebRequest ifconfig.me/ip).Content
OK, doesn't look like it's user agent it's looking at. I've fed a couple of different curl agents into it and still getting the full HTML:
http://www.useragentstring.com/pages/curl/
Could prolly feed this into a RegEx pretty easily to pull the number out of it... but while it's the letter of the law (one-liner) it's hardly the spirit!
<sigh> Oh, the poor poor puppies....
Yeah, curl must be identifying itself (maybe as a browser type). When I use Invoke-Webrequest I'm getting the full HTML. I do have a PowerShell equivalent to do this:
http://community.spiceworks.com/scripts/show/2327-what-is-my-ip-get-whatismyip
But would have been cool to have a one-liner 
It's buried in there in the HTML. Does curl strip that out?
I'm concerned that something is missing from your Network Scan though. This is a cool feature, though!
I even have a PowerShell function for creating Google charts
@scottalanmiller said:
The moon lacks the necessary gravity for a long term colony. We don't have the technology to make people live on the moon, not in the same way. Mars is a viable long term colony location for which we are ready to live on today. The only issue with Mars is getting there, not living on it.
Not entirely true, a VERY recent study (it was on Facebook, so it has to be true) said that with today's equipment failure rates current plans to inhabit Mars would fail. But as a stretch goal it's fantastic, and as Elon Musk once noted it shouldn't be a national priority, but we ought to at least spend as much money on it as we do lipstick research (which is in the hundreds of millions).
Is there anything you find yourself doing over and over again? Can you PowerShell that? If you're doing mostly desktop support write a script that you could give an end-user and have them run to do some basic troubleshooting for you. You may never actually give it to them, but that's ok, sometimes the exercise is worth it.
Write an inventory script that'll gather basic computer information and output it as a custom object. Then take those objects and make an HTML report out of them
I love using Select-String. Nothing quite as cool as taking a huge log file, parsing out EXACTLY what you want out of it and making a custom object. Version 5 of PowerShell now has the ConvertFrom-String cmdlet that'll make doing this much easier than using RegEx. But where's the challenge?!?!
For our desktop guys I recently wrote a tool that troubleshot network connectivity, web site being up, a few pings. There's always things you can work on that will help you. What do you do more than once? It's probably a candidate for automation.
@JaredBusch said:
Amazing? Not quite. Instructive? Definitely.
I left the same feedback I leave each year on a basic session I attend.
They need to try and get more advanced sessions that run maybe a double session or session and a half in time.
We wanted to do a more advanced session along with the Introduction one, but since Jeffrey Snover was there doing his JEA session they didn't want three PowerShell sessions going. I was thinking a session on tool building would be interesting, but it was a no go. Sorry!
As for the time, I don't disagree, but they only give us the 45-50 minutes (with 10 minutes set aside for Q&A) so we tried to cram in as much as we could while covering the basics to get you started.
Just to be clear, this isn't actually a solar panel, it's a solar concentrator. So you'd have this and a tiny little solar panel off to the side to soak it all up. Promising, but I wonder how useful it would be in real life. Still, it makes the mind wonder! Plenty of non-visible light out there, so I would think making a clear solar panel would be very possible... maybe not as efficient as a normal one, but anything would be better
Another difference between bash and PowerShell! In the PowerShell community you'd be disqualified We simply define a one liner as a single stream. It's really semantics as all the OS's involved can copy/paste multiple lines without trouble. Have to admit, it makes your one-liner a bitch (can I say that here?) to read!!
Only problem I see, is it's not really a one liner. If I'm reading it right (and I may not be) then a semi-colon is a command separator? That means it's really a dozens of lines script that you've just forced into a single line.
@garak0410 Yep, used to use them all the time in High School. Had my own BBS but I couldn't bring it online until after 6pm--after that my parents were fine with it 
Wrote it myself too... actually got so large that I used up all the memory on my C64--never said I wrote it well! To initialize the disk database took HOURS on a single 5 1/4 floppy. Loved that. I can remember someone dialing in late late at night and I'd bounce out of bed (it was in my room) and watch what they were doing. How cool was that!!
Automation so rarely survives the person who put it in too. It's a tough situation, because there are very real benefits to it.