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.
Another awful variant of ransomware has been discovered in the wild on the web by a group of researchers. To their credit, they already have a working decryption tool, and a method of testing to see if the messages you are receiving are from the same variant. You can get the removal tool by clicking here for the Jigsaw ransomware decryption tool.
The scare tactic with Jigsaw is the threat of file deletion after every hour of non-payment in bitcoin to the attackers. This malware also warns of deleting another 1000 random files on each PC reboot. As this ransomware has already been beaten the researchers your best method to fight back is to download the tool from bleepingcomputer linked above before trying anything else. The tool to identify what type of ransomware you may be infected with you can get the tool courtesy of Mr. Gillespie here. Thanks to everyone at the @MalwareHunterTeam for taking this garbage out quickly.
Stay safe out there, and the most important thing to remember:
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.