3 ms·
Does anyone else work on systems that take 3 hours to back up the DB, an hour to deploy, 1 hour to start up and a few hours for users to check out functionality
by rb808 11y ago
Does anyone else work on systems that take 3 hours to back up the DB, an hour to deploy, 1 hour to start up and a few hours for users to check out functionality before business opens on Monday? No to mention the federal regulations about what paperwork is required and who can even access production. Maybe I'm in the wrong site.
- RandomChance 11y agoHah, we (hopefully!) get an update window every 18 months! And a staging a new production like test environment starts with another $100K invoice.. And thank goodness Microsoft hard-coded in a 10 hour delay to ensure the KDS root key of a domain is propagated, even if I create it before I create additional domain controllers... Such fun!
- tumba 11y agoOff topic, but to create an immediately effective KDS root key, just set the effective time ten hours in the past. You can validate propagation by looking for the 4004 event in the KDS event log. This is probably not a good idea in production, but is useful when building/rebuilding a lab. Add-KdsRootKey –EffectiveTime ((get-date).addhours(-10)) See https://technet.microsoft.com/en-us/library/jj128430.aspx https://technet.microsoft.com/en-us/library/jj128430.aspx
- henrikschroder 11y agoLuxury!
- sz4kerto 11y agoHear, hear. I don't have any access to production. (Interestingly, that's just one more reason to fully automate stuff.)
- jventura 11y agoNo federal regulations or 3 hours to backup the DB, but in my previous job we had to build a deb package on a build server, then copy the package to the repo server, and finally ssh into the test/preprod/prod server to do the deployment (using sudo apt-get update). And I didn't have access to the production servers..
- brown9-2 11y agoAll of that could be automated.