Technology Log

Greetings fellow admins! Here is another good one that I spent a few hours digging into WMI and SMSProv verbose logging. Plus some random WMI class calls. Hopefully this will help you fill in somethings missing from the SDK/MSDN documentation. $wmidate = new-object -com Wbemscripting.swbemdatetime $date = get-date -format g $wmidate . SetVarDate( $date , $true ) [ void ] ( $thisInstance = ( [ wmiclass ] " \\localhost\root\sms\site_COP:SMS_ActionAccountResult " ) . createinstance() ) [ void ] ( $thisInstance . ActionID = 1 ) [ void ] ( $thisInstance . StartTime = $wmidate . value) [ void ] ( $thisInstance . Put()) $date = get-date -format g $wmidate . SetVarDate( $date , $true ) [ void ] ( $thisInstance = ( [ wmiclass ] " \\localhost\root\sms\site_COP:SMS_ActionAccountResult " ) . createinstance() ) [ void ] ( $thisInstance . ActionID = 2 ) [ void ] ( $thisInstance . ActionData = 'syncType,fullSyn

Well came across another interesting one today. We had an OSD package that wasn't working in run from dp. Ended up being an issue very similar to the issue that occurs if you have a pull dp under a secondary site. Based on some talks with support on the other issue, here is a handy query to identify the issue. You can also give this query and the results to CSS to help them resolve your issue faster. -- Broken Packages select cdpm.SiteCode, ContentID,ServerName,AccessType,URL,URLSubPath,URLProtocol,vpkg.Name from ContentDPMap as cdpm join v_Package as vpkg on vpkg.PackageID = cdpm.ContentID where cdpm.AccessType = 2 --UNCProtocol and cdpm.URLSubPath = '\' --Packages with issues only have a '\' and vpkg.PkgFlags = (vpkg.PkgFlags | 0x80) --Limit to only show packages with the 'Copy To Package Share' flag set Now for the !!!!!!DON'T TRY THIS AT HOME (Production)!!!!!! section. I recommend that you contact CSS but to help point them in the right