Category: ConfigMgr

You may have noticed that when you deploy site roles to System Center 2012 Configuration Manager servers that more often than not content is distributed across one or more drives. In Configuration Manager 2012 you can configure the drives that are used by some roles, such as the Distribution Point, during deployment. There is however a simple alternative; for every dive you do not want to contain Configuration Manager files (note that WDS will still choose whatever drive it wants when you enable PXE, unless you install and configure before hand!) create a file in the root of that drive named NO_SMS_ON_DRIVE.SMS as illustrated below:

I’m working on an odd issue at the moment with System Center ConfigMgr 2012 RTM. I have a Primary Site and a Secondary Site, the Secondary Site is PXE enabled however PXE boot isn’t working, clients are getting the following error: PXE E-53 No boot filename Received

I’ve come across an issues with a Configuration Manager 2012 deployment where an ESXi 4.1 VM configured with an E1000 NIC will Crash / Hang at Boot just as Windows PE loads the GUI. The boot gets stuck on “Windows is Starting Up.” I’m unable to do anything other that hard-reset the VM.

I ran into an issue with a System Center Configuration Manager 2012 deployment recently where if I selected the Distribution Point to be PXE enabled and then imported a certificate from our PKI I was unable to view or configure any of the server roles anymore. I simply got “Not items Found” in the ConfigMgr console!

Working with Microsoft Support it was identified that our Certificate size exceeded 32K, which is larger than the buffer used by ConfigMgr. The XML assocaited with the Distribution Point was then being truncated leading to the error in the ConfigMgr console, as above.

Note; if your issue is affecting a SECONDARY SITE then see note at the bottom of the article.