At the Chipotle Grill, Pittsburgh

On a drinking cup:


Chips are RAD! Chips might seem
so little, so inconsequential… but what if we didn’t have chips, HOW WOULD WE EAT SALSA? WITH A SPOON??? And then what would make salsa different than SOUP? And would people want to put soup on their burritos? That would be weird. I don’t mean to judge, but I think most people would rather NOT PUT SOUP ON THEIR BURRITOS. And don’t even get me started on how chips can move guacamole. OH SWEET GUACAMOLE. The tiny, lowly underappreciated chip is the salty triangle delivery method that surpasses all others in guacamole transport. If there were a chip appreciation society, I would probably join it (as long as they didn’t meet on Wednesday nights, because I have my ceramics class on Wednesday nights, and next week I’m making a bowl) But on any other night, I would be happy to meet up with folks and talk about how AWESOME CHIPS ARE. Actually, if no one else is going to start a society, I might have to get on that…

Long UNC File Paths and MDT Replication

I had some trouble recently with replication of content in my LiteTouch distribution shares. Apparently the sync mechanism being used by the Deployment workbench is sensitive to path length. If you have an application that has a full share path that is greater than 260 characters, replication will fail. (Come to think of it, this is a CIFS limitation, isn’t it?)

To cure this, we needed to hunt down the offending files. Real UNIX guys likely would find this easy. I had to muck about with Powershell a bit to get something that was helpful:

gci "\" -recurse `
   | foreach {$_.PSPath.Split(":")}  `
   | ? {$_.length -gt 251}

So, we are using “gci” (get-childitem) to recurse all contents of the offending parent directory, then using “foreach-item” to runa check on every child. We use “PSPath.Split” to split the path into UNC and PS Drive Provider components. We then use “?” (short for where-object) to select only strings where the path is longer than a specified length… say, 250, to allow some padding identification of potentially problematic temp files used during workbench replication.