I've read where it is not recommended to install Vault's Admin tools (web server) on a domain controller and yet thiere is a workaround link on how to do this.
Can someone tell me if the workaround works? Or whyshould I stay away from installing it on a dc?
Also, I've read that if I am migrating from VSS to Vault 3.05.2833, that I should not use Source Safe d patch. I should downgrade to c. patch. Since I am starting with Vault 3.05, do I really need to downgrade to c patch? Why is this so. The information I read only pertained to Vault 2.0 migration.
Thanks
Tom
Upgrade Question
Moderator: SourceGear
The new Vault 3.0.5 installer handles installation on a domain dontroller much better than previous versions. There were issues on domain controllers such as the lack of an ASPNET account, access rights to directories, etc. We've still run into configuration challenges on DC's that have been recently promo'd, etc.
If you have another machine that's not a domain controller, and can install Vault there, you may have fewer installation issues.
If you are planning to import your database into Vault, we still recommend using the Microsoft 6.0c Hotfix version. The Import Tool communicates with the VSS database via the Microsoft automation component, and we've found threading issues with VSS 6.0d's automation component. The 6.0c Hotfix version has been the most reliable in terms of the automation component.
If you have another machine that's not a domain controller, and can install Vault there, you may have fewer installation issues.
If you are planning to import your database into Vault, we still recommend using the Microsoft 6.0c Hotfix version. The Import Tool communicates with the VSS database via the Microsoft automation component, and we've found threading issues with VSS 6.0d's automation component. The 6.0c Hotfix version has been the most reliable in terms of the automation component.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager