Configuration Manager Version and Build Numbers
This article lists all the version numbers for Configration Manager 2012 and “CB”, and how to tell which version you’re running.
This article lists all the version numbers for Configration Manager 2012 and “CB”, and how to tell which version you’re running.
I have been struggling a bit with adding .NET Framework 3.5 on a few systems (and reference image for MDT). The posts on MSDN and TechNet are good, but not always crystal clear.
Here is how I solved the issues we were experiencing…
I know many IT folk have been waiting for the updated Administrative Templates for Update 1 to ensure a smooth rollout…
First of all, the way http.sys works on newer Windows versions is a very useful feature.
The reason behind http.sys is to have a single system service that listens on the all-important port 80 and be a mediator to different applications and services…
To update the DAG members with new patches the process should be managed to prevent all of the DAG members from being offline at the same time.
You can move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
In System Center 2012 Configuration Manager, Microsoft added the capability to automatically remove software
update content from distribution points when that content is related to expired updates.
After installing Windows Server 2012 and booting up you are welcomed by the new, greatly improved Server Manager.
This new tool is however not compatible with previous server versions out-of-box.
Ran into this problem this morning when installing Service Pack 1 for Windows 2008 R2. Service Pack installs successfully, but after we couldn’t login via remote desktop services. The fix was easy to deploy…
After upgrading to WordPress 3.4 category URLs stopped working.
When browsing to address (with Chrome and Firefox) one gets This webpage has a redirect loop.
I’ve recently stumbled upon the Browser Choice-problem. We do not want this patch deployed on our clients…