<feed xmlns="http://www.w3.org/2005/Atom"><title>import-clixml</title><id>https://evotec.xyz/es/tags/import-clixml/index.atom.xml</id><updated>2019-06-23T10:12:27.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/es/tags/import-clixml" /><link href="https://evotec.xyz/es/tags/import-clixml/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Export-CliXML and Import-CliXML serialization woes</title><id>https://evotec.xyz/es/blog/export-clixml-and-import-clixml-serialization-woes</id><link href="https://evotec.xyz/es/blog/export-clixml-and-import-clixml-serialization-woes" /><updated>2019-06-23T10:12:27.0000000Z</updated><summary>I’ve been working today trying to deliver to one of my Clients Active Directory documentation. To my surprise, something that worked fine for a very long time has started to provide weird results. So, after spending about 8 hours taking apart a few of my PowerShell modules trying to find out what is wrong finally, I’ve found it: Export-CliXML / Import-CliXML. Those two commands are great. I’ve used them multiple times with great success (or so I thought).</summary><category term="Active Directory" /><category term="export-clixml" /><category term="import-clixml" /><category term="powershell" /></entry></feed>