This is the first post in what will be a multi-part series about what not to do as a manager or leader. For better or worse in the last year I have had the “opportunity” to witness a lot of things that I wouldn’t recommend any manager or leader do if they want to be
Installed the WSUS Server Role on Server 2012. Installation completes successfully and it comes up with the post installation configuration wizard. I click to start the wizard, and it fails immediately. I open up the log file created and see the text below. 2013-08-12 14:17:06 Postinstall started 2013-08-12 14:17:06 Detected role services: Api, Database, UI,
List of supported Operating System’s and migration scenarios is listed here. In my case I am going to migrating a WSUS deployment from Server 2008 R2 running SQL 2005 to Server 2012 Standard with SQL 2008 R2 SP1. Review considerations and system requirements can be found here. First step is to install and configure the
I needed to migrate a SharePoint 2010 site on Server A to a SharePoint 2013 site on Server B. Because my 2010 site was using classic mode authentication, there were some extra steps involved to make sure that user permissions were carried over. Below are the steps I used to accomplish this. Step #1: Backup
Had some fun the last two days trying to setup a HP LaserJet 4300 printer to be deployed via Group Policy Preferences to our work at home users utilizing a Citrix Xen Desktop environment. This post is mostly for my notes in case I run into this again, but hopefully someone may find it useful.