A couple of weeks ago I was thinking that I should blog that it’s a pity that Windows Management Framework (including PowerShell) could be not distributed through WSUS anymore. In the past it was available on through WSUS, but it was removed (expired) at some point due to some issues.
This meant to deploy PowerShell you could not deploy it through regular WSUS, but you had to either:
Include it in your base image
Install it manually
Install it using scripting
Install it using GPO
Install it using WSUS add-on solutions to deploy 3rd party packages. Example solutions include, but are not limited to Local Update Publisher (LUP), WSUS package publisher, SolarWinds patch manager.
Install it using enterprise systems management software. Example solutions include, but are not limited to System Center Configuration Manager (SCCM), Altiris, Landesk Management Suite, Tivoli Endpoint Manager (BigFix)
Install it using Intune
At many customers of ours this meant that PowerShell was left at version 2.0 for older operating systems unfortunately. For newer operating systems luckily version 3.0 was shipped by default. Still the version would never be updated in most cases.
The links above provide include a course outline and a link to register for the Jump Start. And even if you can’t join live, the recordings will always be made available at a later time so you can watch whenever it suits you better.
PowerShell DSC is becoming increasingly important and I personally also still need to learn more about it and look forward to it.
Last week Mark Minasi presented a webinar made possible by http://www.learnit.com called: “The Case for PowerShell: Why To Learn-PowerShell So You Needn’t Leave-Industry”. The recording can be found here.
In this webinar he explains why ICT administrators need to be(come) familiar with PowerShell. He also explains the basic principles of PowerShell to help lower the threshold for people that have been shying away from command line interfaces (CLI) and scripting in the past. He does this by explaining how PowerShell is different from by example the CLI and Visual Basic Scripting (VBS).
I share his opinion about the necessity to learn PowerShell and therefore I hope I can help spread the message.
Even though it seemed for a while that MSDN and Technet subscribers would not get early access to the latest Windows versions, Microsoft decided to listen to customer feedback and reconsidered.
As a result, they just made the RTM versions of Windows 8.1 and Windows Server 2012 R2 available for MSDN and Technet subscribers. General availability for both Windows 8.1 and Windows Server 2012 R2 is still October 18. For the official statement, read this blog post.
Today I helped a colleague troubleshoot a couple of systems were unable to activate using Key Management Service (KMS). Basically for this situation it boiled down to this:
Determine for the KMS service
Which server is hosting the KMS service.If an SRV record has been added for KMS DNS auto discovery, run from CMD: nslookup -type=srv _vlmcs._tcp
If the server hosting the KMS is functioning correctly:
Check if the server is up and running.
Check if the “Software Protection” service (sppsvc) is running.
Verify if the KMS service is listening on port 1688: telnet localhost 1688
Verify the KMS status. Run from CMD: slmgr.vbs /dli
Verify if a KMS key is installed and activated.
Verify if the minimum threshold for activation is being met.
Verify if other clients are able to activate using KMS. Even though the output of “slmgr.vbs /dli” gives you an indication, you can use the “Volume Activation Management Tool” (VAMT) for more insight and functionality.
Verify that a VLK key is being used.
For clients that are not able to activate
Verify if the correct KMS server can be resolved correctly: nslookup -type=srv _vlmcs._tcp
Verify if the KMS can be contacted: telnet <KMS FQDN or IP> 1688
If this is not the case, perform a traceroute to determine potential causes. Reasons could include:
No default gateway configured on the client to reach the KMS.
No route configured on the client to reach the KMS.
Firewall on the client is blocking the traffic.
Firewall on the server is blocking the traffic.
If it is a VM, the virtual network might be misconfigured.
Routing on the network is not correct.
Firewall on the network is blocking traffic.
Clear any previous (mis)configuration: slmgr.vbs /ckms
Attempt activation: slmgr.vbs /ckms
NOTE: If you have lots of systems where you need to clear configuration and then attempt activation, you can also perform slmgr.vbs on remote computers using: slmgr.vbs TargetComputerName [username] [password] /parameter [options]
If you haven’t been able to resolve the issue, you might want to take a look here:
With PowerShell it is relatively easy to reverse a string:
$str = “gnirtsdesrever”
$str[-1..-($str.length)] -join “”
Some of you might ask: Why would anyone want to do this ? Well, since the start of the year Usenet DMCA takedowns have begun to occur automatically, very quickly and very often. This means many movies and TV series on Usenet / News Groups are being taken offline very quickly.
Counter measures to prevent takedowns by uploaders include:
The use of encrypted links to NZB files.
The use file names that make it harder to find copyrighted files.
A lot of people have been complaining and discussing the absence of the start button and the start menu and that the shutdown/restart options where too hard to access.
Personally I simply press CTRL+ ALT + DELETE, click the power icon and choose the action to perform. Or I press the physical power button on my laptop, pc or tablet.
I also don’t really need the start button/start menu. I added my most used apps on the modern/metro start screen and/or added them to my desktop and taskbar. Other apps I simply search for by starting to type on the modern/metro start screen.
The lack of a start button does irritate a lot when you’re accessing Windows 8/2012 through RDP or any other remote method. Trying to access the hot corners to switch between the metro/modern start screen and the desktop can sometimes be hard, especially on laggy connections (ILO/RSA/DRAC). The same is true for accessing the charms bar (which you use to restart/shutdown).
The re-added start button does solve the switching between the metro/metro start screen and the desktop I described above,but the charms bar is still an issue. You can use the start button for restart/shutdown though.
What I hate most though, is that the start button is simply a button. It doesn’t include the start menu people want to access their programs and settings in a way to are accustomed to. To make it even worse the re-added official start button makes it harder to use some 3rd party start button/menu replacements that were working well (but this will probably be sorted out soon since 8.1 has only been released a couple of days). Classic shell still works well though: http://www.classicshell.net/
Even though I think Microsoft has been doing a lot of great things lately, the way they’re handling the start button/start menu isn’t one of them in my opinion. People want the start button and the start menu they’ve grown used to and that has been available for many Windows versions. This start button without the start menu will probably lead to more disappointed users because they expect the start menu to be included with the start button. I think this will also hurt adoption in the enterprise. All in all I think it’s a missed oportunity
The preview version with this start button is not the final version. While I don’t expect Microsoft to re-add the start menu before the finl release, I sure hope they prove me wrong. If you want to have the start menu back, be sure to voice your opinion. This did work for the Xbox one, where Microsoft changed course with regards to Digital Rights Management (DRM).
Even though the start button isn’t what many people have hoped for, there are a lot of other great improvements to Windows 8.1 and Server 2012 R2 though. I’ll try to post more about it in the next couple of weeks.
Last week I visited my dad. He is not very familiar with computers and mainly uses it for mail, internet and viewing and editing photos. Despite my expectations, it really surprised me how fast he got used to Windows 8 (with a custom start menu).
This time though, he had some questions with regards to mail. While I was showing him how to do it, I noticed that his pc was relatively slow. Even though he doesn’t have a super fast laptop, it wasn’t this slow before.
When I took a closer look I saw that the issue was caused by high disk usage / load (I/O). At first it seemed like this was caused by TiWorker.exe which is part of Windows Modules Installer Worker and is used for installing updates. Since there were updates pending I decided to install these first just in case a fix might have been released. While these were downloading and installing I googled and found that more people were having similar sounding issues but with also high cpu usage/load. One of the the advises was to install KB2771431. This update was already installed, so it didn’t solve my issues either. I then turned off other programs that were disk I/O intensive like the backup tool Crashplan that was performing a scan and the virus scanner. Unfortunately the issue remained.
I gave the system some time just in case this was some sort of maintenance job. As the issue remainedI tried checking the system files with SFC /scannow and some files were fixed, but the disk usage was still very high.