This project is read-only.


Can you update to 3.99


Hi cburke007. Thank you for this wonderful piece of software. It really helps to have something that can audit and document an existing farm. If you have the time, can you please update it to conform to the newer standards that the Auto-installer seem to be following now (3.99). It looks like Brian made some schema changes and several attributes are now generated as elements instead.

Thanks once again for sharing!
Closed Sep 2, 2015 at 10:10 AM by cburke007


cburke007 wrote Sep 2, 2015 at 10:09 AM

I just uploaded the new changes. Let me know if you have any issues!


hexiumcoza wrote Sep 7, 2015 at 1:03 PM

Thanks once again! I don't have a test environment ready at the moment where I can test the generated XML but I did try to load a generated file into the AutoSPinstaller web-site to see if it is able to parse the file ( It gives the following error:

There is an issue with the XML. Please check that its a valid XML and that it is at least 3.98. Error: Illegal state: must be END_ELEMENT

I'm not sure if this is due to the fact that you generate a lot more XML than what is actually needed by the autospinstaller and that the parser is perceiving the additional XML as faulty. Those tests may not be present in the actual autospinstaller installation script

Kind regards

cburke007 wrote Sep 15, 2015 at 11:02 AM

At the moment I cannot recommend using AutoSPInstallerGUI or AutoSPInstaller Online with output from the SP_Audit script. These tools read in the XML, and then write a whole new XML file when you save that only maintains the information explicitly needed for AutoSPInstaller to run.

This drops any "extraneous" information from the XML document and would render the XML useless for any migration functions executed by SPMigTK.ps1. The XML itself is well-formed. I suspect there is specific node checking going on in ASPI Online to make sure it fits exactly what is expected by AutoSPInstaller and no more.

Right now, using the Transform menu option in SPMigTK.ps1 is the best way to modify the XML to fit a new Farm being built from the config data of the source Farm. Any additional things that need to be edited should be done manually.