recently, i attended a presentation by Winternals called "Understanding Malware: Spyware, Viruses, and Rootkits". from what i understand, it was an abbreviated version of the presentation at teched. for what it was worth (free), it was pretty good. it was a couple of days after russinovich's blog about sony's drm rootkit. timing couldn't have been more perfect. it was more or a less a pitch for recovery manager. it's a pretty cool tool by its own right. as a mvp, i received a free copy to try out. i wasn't really inspired to do it until i saw their demo...
anyway, i thought it was pretty cool that at the end of the slidedeck, one of the many resource links they listed was the microsoft mvp site! scoring even higher, they sent a trial key and slidedeck the next day. to top it all off, i received a package today from winternals. it was completely unexpected. it's a large, black tin box.
i took the lid off to read "Relax, Marcus". kudos to their marketing. that was clever. underneath the pamphlets and thank you note (for attending the presentation) was a hammock. :) nice stuff. wish all vendors were that creative and thoughtful. anyway, if you get a chance to attend this presentation in your city, be sure not to miss it.
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
Comments
Post a Comment