Content Distribution Magic

This post is inspired by a question submitted on my previous post: Content Distribution: The Myth. The question was about how ConfigMgr determines if files are different when deciding whether or not to replicate them to distribution points. Specifically, the requestor wanted to know whether a simple name change to a file would cause ConfigMgr…

What’s New in Office 365?

As most of you know Office 365 and its services are updated on a monthly and quarterly release cycle. With last month’s SharePoint and Exchange conference Microsoft has continued to tell the world that new features and functionality will come to Office 365 first and then, after some time, come to the on-premises versions on…

Taking my OpsMgr with me… Wrap-up

If you are working with Operations Manager and you want to use it on a mobile platform or through a non-Silverlight web interface check out the series of blog posts entitled "Taking OpsMgr with me". The series links are below with products highlights so you can quickly identify which potential solution you would like to…

Configuring the Azure Rights Management Connector with a Windows FCI File Server

On March 4th, 2014, Microsoft announced the availability of integrating on-premise File Classification Infrastructure (FCI) file server with the Azure Rights Management service using the Azure RMS Connector. http://blogs.technet.com/b/rms/archive/2014/03/04/windows-server-fci-file-classification-now-supports-azure-rms.aspx “FCI refers to the File Classification Infrastructure, a capability in Windows Server-based File Servers using the File Server Resource Manager feature which enables the server to…

Content Distribution: The Myth

A quick post to dispel a common ConfigMgr myth about content distribution. The functionality in question is what happens when you change the source location of a package (or any content since they’re all technically packages on the back-end)? I’ve seen it stated multiple times by multiple folks that ConfigMgr will re-copy all of the…

Hyper-V Replication between two workgroup servers

  Enabling Hyper-V between two workgroup servers requires issuing self-signed certificates with makecert.exe and a registry key to bypass the revocation check. The reason why makecert is required is because the certificate Enhanced Key Usage must support both Client and Server authentication, and the default IIS certificate CSR wizard does not include the client EKU.…