A few thoughts: a) Loosely coupled code allows greater reuse (SOA and all that jazz). I'd recommend one script to output data to an XML file or ini file (or whatever format) in whatever schema you decide. Another script picks that up and creates a Word document. Then, from now on you have one script to create Word documents for whatever documentation scripts you create
b) Having done a ton of Office automation ~15-20 years ago, if you are having to use the COM object model, then there's resources out there if using VB/VBA/VBScript - that might be easier than trying to use PowerShell (or .NET natively) Cheers Ken From: Webster [mailto:webs...@carlwebster.com] Sent: Monday, 28 January 2013 10:18 PM To: NT System Admin Issues Subject: New Article on Documenting a XenApp 6.5 Farm New Article: Documenting a Citrix XenApp 6.5 Farm with Microsoft PowerShell and Word - Version 3 http://carlwebster.com/documenting-a-citrix-xenapp-6-5-farm-with-microsoft-powershell-and-word-version-3/ Thanks Webster ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
