Friday, 28 February 2014

ConfigMgr 2012 - Random problems I've encountered

Back to ConfigMgr main menu

This post will include issues I've encountered while deploying ConfigMgr 2012 for customers.They are in random order but I hope they can help others when they are in difficulty. I will add to the post as I encounter further issues worth mentioning.

ConfigMgr 2012 DP - The self signed certificate could not be created for DP

ConfigMgr 2012 - Reports not running  

ConfigMgr 2012 and McAfee  

ConfigMgr 2012 - create new boot images  

ConfigMgr 2012 / SCCM 2012 Task Sequence fails with BCD error  

OSD Task Sequence fails on preparing network connections in Windows PE  

Failed to sync update. Error The Microsoft Software License Terms have not been completely downloaded and cannot be accepted  

Windows Intune Setup: The software cannot be installed, 0x800b0101 

WSUS Service will not start Error 193: 0xc1

ConfigMgr 2012/1E Nomad - Downloading (0% complete) 

Alternate Login IDs cannot be used with ConfigMgr 2012 and Windows Intune 

Installing Configuration Manager - Visual Studio Invalid license data. Reinstall is required


  1. hi Gerry,
    a really helpful blog. but can I ask have you come across mac flaps with 2012sp1 if so how do you get around these with out turning off WOL

    1. This isn't something I've experienced personally. I am aware of the danger though. See here

    2. do you know if this is a bug with 2012 sp1 or does this effect all version of 2012?

      also is there a difference between wake on proxy and wake on lan?

    3. Wake-up-Proxy was only introduced in SP1 and it still available in R2. It is a supplement for Wake-On-LAN rather than a replacement. You can read about it here

      There is a great big warning on this page. You have to be careful. It's not a bug but expected behaviour.

      "During this process, the IP-to-MAC mapping for the sleeping computer remains the same. Wake-up proxy works by informing the network switch that a different network adapter is using the port that was registered by another network adapter. However, this behavior is known as a MAC flap and is unusual for standard network operation. Some network monitoring tools look for this behavior and can assume that something is wrong. Consequently, these monitoring tools can generate alerts or shut down ports when you use wake-up proxy.
      Do not use wake-up proxy if your network monitoring tools and services do not allow MAC flaps."

  2. sorry to be a pain but I read the document and I cant see if it says you can enable wol with out using wop. if this can be done how and wont this stop the mac flaps?