Skip to main content

systems management server 2003 account review tool

this is an interesting tool. i didn't realize it was out. basically does an assessment of the defined accounts in use with your sms installation. here's a small blurb about it. check the link to get more info...
The new Microsoft Systems Management Server (SMS) 2003 Account Review Tool is designed to assess the use of SMS accounts in a central site or child sites and alert you to account configurations that might increase security risk in your environment.Supported Operating Systems: Windows Server 2003; Windows Server 2003 R2 Datacenter Edition (32-Bit x86) You must run the tool on a primary site server. Before the Account Review Tool assesses the account usage in your SMS hierarchy, it performs an environment check. If any of the following conditions are not true, the Account Review Tool will fail the environment check and will not run the account assessment.
  • The site server where you run the Account Review Tool must be a member of a Microsoft Windows NT 4.0 domain or an Active Directory domain.
  • The tool skips any primary sites in the hierarchy that are not running SMS 2003.
  • The site server where you run the tool must be running Microsoft Windows Server 2000 SP4a or a later version.
  • The SMS site database server must be running Microsoft SQL Server 2000 SP3 or a later version.
  • The site running the tool must be running in SMS 2003 advanced security mode. The Account Review Tool checks any child sites that are also in advanced security. If the Account Review Tool encounters a child site that is running in standard security, the tool skips that child site and generates a warning message.
  • The account running the tool must have membership in the SMS Admins group and administrative rights to all SMS objects.
  • The account running the tool must have at least db_datareader privilege to the SMS site database and group membership in the SMS Admins security group.
Labels:

Comments

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
11 comments
more »

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
3 comments
more »

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
3 comments
more »