<feed xmlns="http://www.w3.org/2005/Atom"><title>excel</title><id>https://evotec.xyz/fr/tags/excel/index.atom.xml</id><updated>2019-05-12T12:46:24.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/fr/tags/excel" /><link href="https://evotec.xyz/fr/tags/excel/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>What do we say to writing Active Directory documentation?</title><id>https://evotec.xyz/fr/blog/what-do-we-say-to-writing-active-directory-documentation</id><link href="https://evotec.xyz/fr/blog/what-do-we-say-to-writing-active-directory-documentation" /><updated>2019-05-12T12:46:24.0000000Z</updated><summary>It’s no secret that nobody likes creating documentation. I don’t like it, and you don’t like it, even documentation lovers don’t like it. But while you can live without documentation, you really shouldn’t. And I am not talking here only about documentation that is only useful in the onboarding process of new employees or documentation concerning introducing someone to some concepts to get them easily start. I’m talking about documentation for your live environment where you know what you have, how you have set it up, but is still the same after one week, one month, or one year? Usually, not so much. And one of the worst mistakes admin can do is assume that his environment doesn’t change, things are as they were when they were set up.</summary><category term="Active Directory" /><category term="dashimo" /><category term="documentation" /><category term="documentimo" /><category term="excel" /><category term="excelimo" /><category term="powershell" /><category term="pswindocumentation" /><category term="Windows" /><category term="word" /></entry><entry><title>PSWinDocumentation – Export to Word, Excel, SQL of AD, AWS, Exchange, O365 Exchange, O365 Azure AD</title><id>https://evotec.xyz/fr/blog/pswindocumentation-export-to-word-excel-sql-of-ad-aws-exchange-o365-exchange-o365-azure-ad</id><link href="https://evotec.xyz/fr/blog/pswindocumentation-export-to-word-excel-sql-of-ad-aws-exchange-o365-exchange-o365-azure-ad" /><updated>2018-09-23T20:39:26.0000000Z</updated><summary>Today I’m pushing forward with PSWinDocumentation project. I’ve fixed some bugs but I also added a couple of new features. I did lie a bit in the first sentence because this time it’s not all me. I got help from Mateusz Niemczyk who is a certified AWS engineer working for Euvic with me on some projects. If you’ve not yet guessed where I got him involved from the introduction – yes we’re adding basic AWS data support to PSWinDocumentation. But that’s not all…</summary><category term="Active Directory" /><category term="aws" /><category term="Azure AD" /><category term="excel" /><category term="exchange" /><category term="export" /><category term="office 365" /><category term="powershell" /><category term="pswriteexcel" /><category term="PSWriteWord" /><category term="sql" /><category term="Windows" /><category term="word" /></entry><entry><title>PSWinDocumentation – Version 0.1 with Word / Excel export</title><id>https://evotec.xyz/fr/blog/pswindocumentation-version-0-1-with-word-excel-export</id><link href="https://evotec.xyz/fr/blog/pswindocumentation-version-0-1-with-word-excel-export" /><updated>2018-08-23T20:07:04.0000000Z</updated><summary>A few weeks ago I’ve released my first version of PSWinDocumentation. It was simple, one command module where you start it and get some basic AD stuff into Microsoft Word document. Today… I’m releasing a new version that has a bit bigger feature set. Are you ready for it? Let’s go!</summary><category term="active directory" /><category term="ad" /><category term="excel" /><category term="powershell" /><category term="scripts" /><category term="windows" /><category term="word" /></entry></feed>