Skip to main content

misc: atlanta smug 6/13/07

southeast management user group (atlanta)! it's coming up again. mark your calendars and get registered. sign up link below... look forward to seeing you there. 
   8:30-9:00am  Light Breakfast
 
  9:00-10:00am  Introduction to System Center Configuration Manager 2007
 
 10:00-11:00am  Using System Center Data Protection Manager 2007 to protect
                and recover Exchange Server, Microsoft SQL Server, SharePoint
                Portal Server, as well as Windows file services
 
 11:15-11:30am  Break
 
 11:30-12:30pm  (Working Lunch) - Using System Center Operations Manager 2007
                to meet Regulatory Compliancy Needs
 
  12:30-1:45pm Deploying Vista Today with SMS 2003 and Deploying Vista and
                Windows Server 2003 in the future with System Center
                Configuration Manager 2007
 
   1:45-2:00pm Break
 
   2:00-3:30pm How to monitor your Core Infrastructure and Distributed
                Applications with System Center Operations Manager 2007
Registration Links Event Title : Charlotte Southeast Management User Group Meeting June 6 Event ID : 1032340757 Event URL : http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032340757&Culture=en-US Event Title : Atlanta Southeast Management User Group Meeting June 13 Event ID : 1032340758 Event URL : http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032340758&Culture=en-US Event Title : Raleigh Southeast Management User Group Meeting June 26 Event ID : 1032340759 Event URL : http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032340759&Culture=en-US
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 »