There are some recent updates to Server 2012 and R2 that have been causing lots of people issues in deploying Windows 10 to client computers as an upgrade. The most common issue is a loss of connectivity from the client computers to the local WSUS deployed and a no longer functioning admin interface for WSUS. Microsoft in their great wisdom has outlined the steps to resolve this, but didn’t make it particularly obvious prior to install. You can find the steps at the following link.
Pretty simple over all – you launch an elevated command prompt, run this line:
"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing Following that, launch the local server manager dashboard and hit the 'add roles and features'. Under the add features portion, open up the .net framework section and add 'HTTP activation' to your server. This won't require a reboot, so follow though by hitting next and so on until it starts the task. Once completed, you can restart the server or simply restart the WSUS service. Like magic, you should be back in business. If you have SSL enabled on your WSUS server, you should review the above link for further details.
Did you get shivers down your sysadmin spine? I did. Years of practice, and I still run into the most intricate and ridiculous problems when administering or deploying a SP install. 15 years in production from MSFT and they still don’t have it right. Here are some lessons I learned in the last 24 hours of trying to deploy a SP 2013 SP1 server to 2012 R2.
“The tool was unable to install Application Server Role, Web Server (IIS) Role.”
- Don’t patch your 2012 R2 server before you try to deploy it. Why? If you aren’t paying close attention to different security patches obtained from MS or from your local WSUS, you can run into this issue right here. I thought I was being a smart fellow having my server set up and patched before running the SP 2013 SP1 (this even happens with the SP1 media) disc and the prerequisite installer. A few hours of arguing with “Error: The tool was unable to install Application Server Role, Web Server (IIS) Role” will eventually lead you down to a few things. You may have forgotten to allow your local server install to call home to MSFT to get installation packages; which you can edit the local group policy if you don’t have a gpo for it. The next is that you likely updated your .net 4.5 installation to 4.6 which causes this behaviour in a SP rollout.
- It’s going to be more efficient use of your time to wipe out the virtual machine and start over than try to patch the endless issues you can run into when trying to resolve some of the errors, such as this one. The post linked is a great resource if you want to try to pull out of the nosedive and it’s relatively easy to perform. I gave it a shot; to no avail. The errors persisted. I even ran the MSFT .net clean up tools. No love.
- In reference to point 1.; The SP install will run perfectly and reboot a few times if you aren’t up to date and have enabled appropriate package retrieval via GPO or security policy.
- Once you are all installed and running, you can safely patch the server and SP farm.
- Run the prerequisite installer first. It’s in the root folder of the ISO; and aptly named.
- If after using the script from the post over at SomeShinyObject still causes your installation to hang during the “Web Services IIS” portion of the preparation, close the ‘Server Manager’ Window. That will allow your installation to complete.
- Now you can run the setup.exe from the ISO. Punch in your key, accept the notes on the requirements (SQL 2008 etc.)
- Note that you can’t have a licensed copy of SP installed, and then use a trial version of Project Server on top of that. There is no workaround for that error. Again, you will be put back to the point where you need to wipe and start over – install SP as a trial so that you can install Project Server as a trial too.
- Try not to shed too many tears doing the same work over and over.
- Real devs do it in production. Sysadmins test it on dev first.
Trend Micro has announced two critical security vulnerabilities in Apple’s Quicktime for Windows. At this time it would be wise to remove any version of Quicktime from computers in a Windows operating system environment until a patch is available. There appears to be rumours of Apple advising that support for Quicktime on the Windows platform has been dropped; but for now Apple has yet to comment on the matter.
If you are apt to be safe than sorry, you can find the Quicktime uninstaller in the Programs and Features menu on current Windows platforms. Highlight the application and look for the ‘uninstall’ button near the top of the window.
The WordPress team has released version 4.5 of their platform today. As with most minor revision updates there isn’t a lot to review in the release. There are no security notes on the page but rather a list of enhanced features, deprecated packages and commands. One of the smoother additions is the inline link editing which speeds of the entry of links into posts and other content.
Another notable feature is the roll out of on the fly responsive review of your content and site. This allows simple tools to see how content will look on mobile and tablet devices while in the editing screens.
A new variant of malware based on the Chromium project has come to light – and it’s trying to trick users into thinking it is Google Chrome. The troublesome part of this ‘efast’ product is that it is doing a really good job of it. The purpose of the malware is to inject ads into otherwise harmless pages; and further could take end user data and sell it to nefarious advertisers among others. When downloading free software always remain vigilant of the source of your download as well as any ‘free’ offers that are bundled with the installer. Simply reading the steps during what many people like to skip over during the license agreement will reduce the pervasiveness of their malware.
It’s been noted before that Windows 10 has been downloading in the background for users of Windows 7 and 8. Now it appears that the update is selected by default – allowing for accidental deployment of a massive update. The aggressive nature of the Windows 10 roll out is causing a lot of grief for users in all kinds of scenarios. It’s a large download – which would slow some networks and connections. This could also cause issues with available space on machines with little to spare (like some with smaller SSD’s). It’s a really good idea to pay attention to the optional updates on the list as you run them.
Microsoft’s quote on the matter:
As part of our effort to bring Windows 10 to existing genuine Windows 7 and Windows 8.1 customers, the Windows 10 upgrade may appear as an optional update in the Windows Update (WU) control panel. This is an intuitive and trusted place people go to find Recommended and Optional updates to Windows. In the recent Windows update, this option was checked as default; this was a mistake and we are removing the check.
This won’t be news to anyone in the technology industry – but Adobe Flash has a vulnerability that has been exploited in the wild again. At this time there is no patch available from Adobe to cover all affected versions, but users should keep an eye out for updates if you are running it in your browser. Firefox and Internet Explorer require updates to be done manually (or via the optional automated updater software from Adobe, installed to your desktop). Google Chrome users will automatically update when a flash update is released, but may need to restart the Chrome application.
It’s a good time to note that adblockers and noscript are always good options for the security conscious. A small learning curve to the latter, it’s a great tool to prevent websites from running content without you deliberately clicking on it first.
Check back with Adobe for an update as soon as this latest exploit is patched.