some background: when a new sms_def.mof is placed in inboxes\clifiles.src\hinv data loader should pick it up, realize it's new, compile it, and convert it to a policy.
i found something interesting. i use a different mof for my domain controllers since grabbing local accounts means grabbing all domain accounts. the reason i'm telling you this is because i moved the dc mof file into the \hinv directory then renamed it. it didn't do anything with the file.
i tried again except this time, i copied the dc mof file locally, renamed it to sms_def.mof and dropped it in \hinv. this time, data loader did its work. hmmmm.
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