MMS 2012

CM12 - Day 33 in the lab

Written by Brian Mason on .

We brought up a couple dozen clients on the site last night and today the CAS was just a sluggish pig. SMSExec wasn't doing anything (things like dataldr.log are dead since it gets that data from SQL from the primary sites now). But the CPUs were burning on SQL and even though this is a VM, the disk queue length was still under .05 (the underlying disks are like a dozen RAID 10 drives). So I shut down the VM and in Hyper-V manager, I cranked it from 2 GB min to 4 GB min and from 2 CPUs to 4. She's purring now.

Holy smokes, my primary was melting on CPU too. So I just gave it the same medicine. I was thinking the super lag between sites was the old-style transactional replication, but it was probably just the CPU limit.

MS CM Support Team

The Configuration Manager Support Team Blog

This is the Configuration Manager blog for the Microsoft support team. If you were looking for the SCCM 2007 blog then you are in the right place.
  • Configuration Manager Remote Tools and Remote Desktop fail to connect to client machines with NetBIOS names longer than 15 characters

    I recently came across an older, fairly common issue recently but I never see one of the potential workarounds mentioned so I thought I write it up here in case you run into it. With this issue, the System Center Configuration Manager 2007 (ConfigMgr 2007) Remote Tools and Remote Desktop tools fail to connect to client computers that have a NetBIOS name longer than 15 characters even though regular Windows Remote Desktop works fine.  When your try to start Configuration Manager 2007 Remote Tools you get following error: Unable to contact Host When you try to use the Configuration Manager 2007 Remote Desktop client you get this error: Remote Desktop can’t find the computer <client name>.This might mean that <Client name> does not belong to the specified Network. Verify the computer name and domain that you trying to connect to. When trying to ping the 15+ character NetBIOS name it works, but when we try to ping the truncated NetBIOS name it errors out with the below message: Ping Request could not find host client <truncated NetBIOS name> NOTE In DNS, a Host (A) record is created for the 15+ character NetBIOS name (e.g. Client-PC123456789) although in the Configuration Manager console and under Active Directory users and computers it shows the truncated name consisting of first 15 characters (e.g. Client-PC123456). Most people assume that if you have a NetBIOS name of more than 15 character (the standard, accepted limit), the only way to fix the issue is to shorten it.  While that’s definitely the preferred method, you might be able to get away by enabling "NetBIOS over TCP/IP" on the server and client.  If you have a server or client with an NetBIOS name longer than 15 characters and “NetBIOS over TCP/IP” is disabled then you’ll definitely get the errors mentioned above. To resolve this issue, ensure that both the Configuration Manager 2007 server and the client have NetBIOS over TCP/IP enabled. You can verify this by going to Network Connection -> TCP/IP properties -> Advanced -> WINS tab -> NetBIOS. Adeel Mohd Get the latest System Center news on Facebook and Twitter: App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/ The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

  • KB2509007 does not install correctly when installed at the same time as KB977203 or KB977384

    We recently discovered an issue that KB2509007 would not install properly if installed at the same time as either KB977203 or KB977384 via the PATCH= option in the " Setup Windows and ConfigMgr " task. We were able to reproduce the issue internally and...(read more)

MS CM Team Blog

System Center Configuration Manager Team Blog

The official blog of the Microsoft System Center Configuration Manager Product Group