I don’t know if this is me being stupid (likely so...
# microsoft-rds
c
I don’t know if this is me being stupid (likely so these days). I have an RDS2016 farm, with what needs to be Office 2013. Office has been installed with KMS keys and ADBA is being used and i’m using BISF. For some reason though, activation isn’t happening once I domain join the Packer built RDS image. I was able to jump on manually and activate it using “OSPP.vbs /act” and then all was good. So given that I am automating the build, and it doesn’t seem to want to activate itself - is a one-time scheduled task the best way to get rid of my issue. Thoughts?