Lets start off with a little background. I've been working with GSS 3.0 since Beta 1 and have ALWAYS had problems on the install. Everything worked except for SQL. In order to get SQL to properly work i needed to download it from Microsoft and then install it separately and then it worked properly.
When working with another piece of software that installed it's own database it came to me that i may be having the same problem with GSS that i had with that software. The software would fail to install it's own SQL because it created a user and password that did not meet our DOMAIN security settings (we need a 14 character password). Luckily this software documented that and that allowed me to figure out a way around it. GSS not so much.
In order to get around the password policy i had to unjoin the computer from the domain, install the software and re-join the computer.
So i thought i'd do this with GSS.
Guess what, it worked perfectly. No issues, no errors, everything worked perfectly fine. Joined the computer back to the domain and all still seems to be well.
I hope this helps people who have been having installation issues. We should not have to work around solutions for a paid product that's supposed to be and enterprise piece of software.
On a separate note, to Symantec support people - when choosing the "operating system on which product is running" you may want to update that a little bit. Windows 2012 has been out for a while let alone 2012r2 and in case you didnt know 2003 is EOL very soon so you could probably remove that and Windows XP from the list of where the software is running because people really shouldn't be using it for much longer.
-Steve