I had the same issue, and ended up packaging Visual Studio 2015 in an appstack, as detailed on this thread.
The I added SQL Server Management Studio 2016 to the same stack and that works a treat. If you don't want/need VS, you could see if a similar method could be applied to applying the key as in the above thread?
I am experiencing the exact same issue, did anyone manage to resolve this one?
Thanks very much for any assistance here.
1 person found this helpful
I was able to package SSMS 17.1 successfully. You have to run the visual studio CA reset tool when the appstack is mounted. You should be able to find the DDConfigCA.exe in your appstack and add it to run in the startup.bat file on the appstack.
For 17.1, the tool is located in
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\DDConfigCA.exe
Link to 17.1
I ran into the same issue as well we fixed it by using the base image as the provisioning machine for the SQL server management studio, It seems MS put some kind of SID check into the free software and it sees the new machines the app stack is attached to as different then where it was provisoned and boom your get the dumb message.... Its actually the visual studio piece of ssms thats doing it.... leave it to MS to put a license on free software sigh....
But just use your base image of the machines you will attach the app stack to provision and you will be good to go just remember to take off any other agent etc... before provisioning.
Can also confirm that we had to provision on the Master Image for both SQL Server Management Studio 2008 and 2014 and Visual Studio 2013. Otherwise would run into the same invalid license issue. Thanks Microsoft.
Sorry to bring this thread to life again but I'm experiencing the same problem now. I'm trying to put SSMS 17.1 on the appstack along with Visual Studio. I have used the volume license key that is injected through startup.bat and it appears to be working fine for Visual Studio as it opens fine and shows as licensed. Another option that didn't try is to simply name the msdn licenses and have user sign in to Visual Studio. Anyway. The problem seems to be wiht SSMS where when you launch it it's fine but as soon as you try to connect to any db the invalid license pops and says that reinstal is required. Once we close the error it shuts down SSMS.
Did anyone experience that? Would someone care to share a recipe? Thank you
Did you confirm that your provisioning machine is a direct clone of your parent image? Usually this is a sign of that, like a few of the earlier comments see. I see this after doing windows updates on the build machine too, which I delete if I do, and then reclone a new one.
I see let me try that and I'll post the reults