Skip to main content

sms: sms 2003 sp2 schema extension

so you ran the schema extension you say, and it ran so fast that you didn't notice it had finished? if you're upgrading from SMS 2003 to SP2, the included schema "extension" doesn't do very much at all. in fact, from a practical standpoint, nothing is extended. an existing attribute is linked to an existing class. if you're a sms administrator and can't convince your ad administrators to run it, just show them this. here's a log of a proper run:

<03-30-2006> Modifying Active Directory Schema - with SMS extensions.
<03-30-2006> DS Root:CN=Schema,CN=Configuration,DC=bladerunner,DC=int
<03-30-2006> Attribute cn=MS-SMS-Site-Code already exists.
<03-30-2006> Attribute cn=mS-SMS-Assignment-Site-Code already exists.
<03-30-2006> Attribute cn=MS-SMS-Site-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Roaming-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Default-MP already exists.
<03-30-2006> Attribute cn=mS-SMS-Device-Management-Point already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Name already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Address already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-High already exists.
<03-30-2006> Class cn=MS-SMS-Management-Point already exists.
<03-30-2006> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Class cn=MS-SMS-Server-Locator-Point already exists.
<03-30-2006> Class cn=MS-SMS-Site already exists.
<03-30-2006> Class cn=MS-SMS-Roaming-Boundary-Range already exists.
<03-30-2006> Successfully extended the Active Directory schema.

i've marked the relevant lines you need to look for in your schema log. you can check this manually too with the active directory schema snap in (schmmgmt.msc). under classes, locate mSSMSManagementPoint. take a look at the optional attributes. you should see dNSHostName now.

Comments

  1. This was my problem, and was corrected after set fullcontrol permission to both class and atributte to a one in all machine sms 2003 installation where sms and sql server were running on the smae server
    just correct a little fix to your advise look for atributte DNS-Host-Name and class MS-SMS-Management-Point

    ReplyDelete
  2. This was my problem, and was corrected after set fullcontrol permission to both class and atributte to a one in all machine sms 2003 installation where sms and sql server were running on the smae server
    just correct a little fix to your advise look for atributte DNS-Host-Name and class MS-SMS-Management-Point

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m