Skip to main content

Posts

Showing posts from November, 2007

mom: ad remote topology discovery failed to execute...

i forgot all about this thing.  it started cropping up in my environment but couldn't figure out why.  after awhile, it finally dawned on me.  the agent was reinstalled, but the computer table was never adjusted.  yeah, i wish i was making this up.  this happens when you monitor DCs in an untrusted forest or domain.  here's the article .  i particularly love the way it says this: WORKAROUND To work around this issue, install a separate MOM management group in each untrusted forest. Note This issue has been known to be partially resolved by the following method. First, apply MOM 2005 SP1. Then, use the Active Directory Topology Discovery script to enable the server fully qualified domain names (FQDNs) to be added to the Computer table. However, when you use this method, most of the scripts will continue to log errors. of course, it doesn't tell you how to resolve this.  in the onepoint database, there's a table called "computer".  there's

sms: sms 2003 recipes...

awhile back, greg ramsey and warren byle wrote this magnificent book called sms 2003 recipes: a problem-solution approach . it's the equivalent of the active directory cookbook for sms. it has all kinds of scripts that can help automate your environment. now, the best part is, the scripts are all free and available for download. it's a little cumbersome trying to find it... so for your reference, here's the link .

sms: reporting access denied after applying sp1...

maybe this is old news. maybe i'm just getting around to hearing about it... or maybe we finally did something right? now we're seeing the problem. here's the deal... recently, we decided to move from our current tier administrative approach to a three-tier approach which truly separates user, server, and domain functions so that we can minimize accidental screw ups to some degree. in doing this, our server admin accounts were added to the sms servers. our user accounts were removed. keep some of the base functionality, we left our user accounts in our sms reporting groups. apparently after applying windows server 2003 sp1, there are some changes that need to occur for launching sms web reporting if your account is a member of the sms reporting users group but not the local administrators group. trying to launch results in an error like this: Server object error 'ASP 0178 : 80070005' Server.CreateObject Access Error /SMSReporting_093/ReportsNav.asp, line 1

misc: 1e roadshow: enterprise solutions

i sent this out to the subscribed members of the atlanta smug. thought anyone else that's in the atlanta area might be interested in going. here are the details! obviously it's a british thing... look how tea is presented before coffee. anyway, drop me a line or leave a comment if you're going. would love to meet up! register here... 1E Road Show: Enterprise Solutions Atlanta Road Show, US: Thursday, 29 November 2007 Emory Conference Center Hotel 1615 Clifton Road Atlanta GA 30329 Tel: 404 712 6000 Website : www.emoryconferencecenter.com Location/Map : http://www.emoryconferencecente r.com/maps.html Note : Detailed event information will be provided on confirmation of registration. Morning – Technical Session 08:30 am – 09:00 am Registration and reception with tea & coffee 09:00 am – 09:30 am Guest introduction and their IT challenges - Courtney Austin, Marketing Manager and Bruce Walter, Business Manager, 1E 09:30 am – 10:45 am Microsoft Sys

misc: dsquery vs powershell...

as a part of trying to familiarize myself with powershell, i figured converting some of my favorite dsquery commands to it would be as good of a measure as any. the problem was, i had a hell of a time figuring it out! thankfully, hal was nice enough to help out... in order to get displayname and streetaddress from dsquery, you'd use a command like this: dsquery user -samid myUser | dsget user -display oh wait a second... there is no switch for streetaddress. all you'll get is something like this: display My User (Test) let's try that again... dsquery * -filter "(&(objectcategory=person)(samaccountname=myUser))" -attr displayname streetaddress in my case, i have multiple lines in my streetaddress attribute, which throws off the entire format. this is something i wanted to avoid so i seeked powershell as the answer (instead of writing a vbscript to handle it.) displayname streetaddress My User (Test) 2000 My Test A

ds: password complexity rules...

in case you're asked for it, like i am, all the time, as in ... yesterday, today, tomorrow... Do not contain all or part of the user's account name. Contain characters from three of the following four categories: English uppercase characters (A through Z). English lowercase characters (a through z). Base-10 digits (0 through 9). Non-alphanumeric (for example, !, $, #, %). extended ASCII, symbolic, or linguistic characters. i believe in cases where it refers to "part of the user's account name" it specifically means 3 or more characters in a row. for example, since my name is "marcus" i can't have the letters "arc" or "rcu" or "mar" in my password. it's not referenced in the following article but is referenced in a sql 2005 article. anyway, here's more detail from the article ...

ds: ad attribute editor (adae)...

heard of this tool? just saw it come through activedir. check it out here: http://www.fcsovelto.fi/adae . here's a small blurb of what it does: ADAE (Active Directory Attribute Editor) enables you to add your own property pages (tabs) to the Active Directory Users and Computers. This way you can view and/or modify predefined attributes, such as user's EmployeeID, or any new attributes you or your applications have added to AD. look carefully on the page. read/write version costs money . read version is free.