C:> powershell
PS C:> Get-Command *foo*

e.g.:
PS C:> Get-Command *cert*
Lists all commands (functions, extensions etc) containing "cert".

You want to replicate a continually changing list of console sessions for tens or even hundreds of thousands of workstations, across a global network, for a report that no-one will ever read? I mean seriously, a report of some sort showing 200,000 people logged onto 250,000 devices (workstations, multiple logons, terminal servers, admin sessions etc) - what the hell are you going to do with it? Think enterprise scale here, not small business.

OK and now what are you going to do about the site that got disconnected because the WAN went down for 12 hours? Are those users still online? What happens when the 2Mbps link comes back up and you have to replicate 200,000 changes from the rest of the world? Lots of enterprises can't get 100Mbps WAN links for every site for tuppence a week - or indeed, for any price.

What will you do about notebooks not connected to the LAN? It's still a current logon. Someone is still accessing corporate information.

What about sessions that have been idle for 15 minutes? Is that still a logon? What about a session idle for a day? Over a weekend? (Don't give me that crap about "logging out is the policy" because users don't and won't do it).

The whole concept of having a single database with all current sessions, up to date, in a form that is usable, went out the door with NetWare (oh, and NetWare/VMS never told you who was on the network, it was about who was on the server). In case you didn't notice, there's a small difference. The horse has bolted, found a mare, had multiple foals, died, been picked clean, and its bones are now bleached in the sun. There's no point locking the barn door.

This was absolutely true for Windows 2008, and they wised up to their utter stupidity in R2 (seriously, MS, how do you promote using PowerShell as the next big thing for administration, then leave it out of half the platform)? The problem was that there were elements of the .NET Framework (on which PowerShell is built) that would not run on Core.

And I say this as someone who has deployed MS solutions for long enough that I figure they are effectively, but indirectly, paying my salary (I generally work for MS partners).

And the rest - often-times games are marked at $109 or even $119 for the first few weeks. Exclusivity "tax" I suppose. Worse is Steam and the like, with price differentials despite no difference in the cost of sale.

Well it's not like WE wanted him either!

Isn't it considered common knowledge that everything tastes like chicken?

No problem with fitting to paper - the printer knows what paper it has, and the PDF specifies a size. Match the two, or scale and fit to next size down.

The problem with PDF printing in isolation from anything else is dealing with the other options... like force greyscale mode, force colour mode, first page on letterhead, print 2-up, print double-sided, text vs photo mode ... and so on. Since PDF is page description, not print job description, using PDF by itself is insufficient.

I guess an option is have apps print to PDF as the intermediate format, but that still doesn't solve the paper selection, double-sided and finishing problems.

Did you miss the bit in the summary about how this is being done using an antenna printed on paper, using an inkjet to provide a very low cost of production? The 19th century I've read about didn't have inkjet printers or the nano-tech metallic ink to create them.

Do you reject any other advances in approach that "have been done before differently"? Drive a steam powered car (yes, I know they exist), because "converting liquid fuel to motion by burning it to create energy has been quite well known since the 18th century"?

And this comment explains WHY we need compulsory driving tests more than once. I've been driving for nearly 20 years, and I know there have been changes to the law - but that doesn't mean I shouldn't be re-tested to make sure I haven't picked up bad habits or forgotten things. Avid supporter of mandatory re-testing every ~ten years (that's two complete 5-year "Gold" licenses in my Australian state and I think it's pretty common across the country. If you take into account the 3 and 5 year licenses, then the first renewal at or after a 9 year window should mean a re-test - that'd be year 10 (5+5), 11 (3+3+5), 12 (3+3+1+5) or 13 (5+3+5) depending on how you played it - which seems adequate).

Pre-emptive paging. First, realise that swapping / paging just slows down access. Unless the page file / swap area corrupts the page somehow (bad RAID controllers and disks often did this in the NT3.51 and NT4 timeframes - KERNEL_DATA_INPAGE_ERROR is the BSoD you're looking for) the app/OS won't be hurt. Technically they won't even notice. Windows treats memory as transient, and backs pages into the pagefile even if memory is not under pressure. There are advantages and disadvantages, and a good system designer understands the differences between Linux and Windows and exploits the advantages of both where possible.

Perhaps using OSX without a mouse is considered "doing it the wrong way"?

Well, that excuse worked last time ...

3 amps loss in a power supply is 360W of waster heat for you 110 volt-ers, and 720W for us Antipodeans. Perhaps you meant 2.05A? And it's probably more like 10% given the lack of care factor nowadays. Why spend $20K R&D plus $5 per PSU to make the PSU 5% more efficient, when you can sell it for the same price and force the customer to pay for the power forever?

So you only had 1 server, and you had to rename it because some numpty decided that the name was spelled wrong?

Note being a USAnian, I am guessing here - but ISTR there's a law preventing you from suing the government? Basically - immunity from prosecution unless the government (dept) agrees to be sued, or something like that. And I always think, hearing something like that, the argument would be something like, "It's not in the national/public interest for you to be sue us, so no. Neener neener neener."

If I can summarise your argument then:

• The job pays a relatively standard clerk's salary;
• If you ever make a single mistake, you lose your job;
• If you are careful and conscientious, and take long enough to prove you're right, you lose your job.

So with that in mind, are you trying to tell us you've never ever made any kind of mistake in your job, nor taken the time to try to ensure you didn't? Who would take such a job?