Shaun Cassells at MyITForum.com

SMS 2003 and ConfigMgr 2007, PowerShell, Scripting, Finance, Fitness and Fun

News

Locations of visitors to this page

October 2009 - Posts

Where is registry HKLM\Software\Microsoft\SMS\Components\ on a x64 operating system?

I was recieving Message ID: 2719 source: SMS Server Component: SMS_INVENTORY_DATA_LOADER

HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size

due to MIF's being over the default of 5mb.  Problem is the registry key is not in the location specified beause the server is 64 bit (x64)

Look here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Components\SMS_EXECUTIVE\Threads\SMS_INVENTORY_DATA_LOADER

 

 

How to check if Service Principle Name (SPN) is enabled?

While troubleshooting recently, I came across an instance where I needed to verify a SPN was still set correctly for a remote SQL instance.

  1. Go to your SQL box
  2. Navigate to:
    1. X64 - :\Program Files (x86)\Support Tools
    2. X32 - :\Program FIles\Support Tools
  3. Run Setspn.exe -L <ComputerName>

or

  1. Install ADSIEdit.msc
  2. Locate the server you wish to verify
  3. Right Click Propteries
  4. Scroll down to servicePrincipalName

Results are returned.

ConfigMgr 2007: Distribute Software returns "not enough server storage is available to process this command"

"not enough server storage is available to process this command"

when you google you will find several refrences to an IRP stack size issue in windows NT4.  This is not related.

The issue you are running into is covered in this blog post

http://blogs.technet.com/smsandmom/archive/2008/03/10/configmgr-2007-distribute-software-updates-wizard-returns-not-enough-server-storage-is-available-to-process-this-command.aspx 

Test: Open up the Computer Managment (compmgmt.msc) >> Shared Folder >> Sessions

If you see your ConfigMgr / SCCM service account listed a bunch of times and idle.  Then the blog post above will fix your issue.