dc3 keeps crashing and should be redeployed using the vmware 2012 template.
Let us know what name/cpu/ram/disk you want, and we're happy to do whatever - (I don't see a releng specific 2012 template (there is a 2008R2 winforest template out there), so offering ours in place.)
We need 2012 R2. 120 gb Disk 8 gb RAM at least 2 virtual cores (4 preferable)
We have a pretty benign 2012R2 template that we can deploy from, so we can ship that. I'm inclined for 2 cores until proven otherwise, since this seems to run lightly. 120g on the main disk is prior art, so we'll do that unless you say you want it on a separate disk. We can't give you dc3 as a name since it's already in use.. Do you want a new number, or a 'temp-dc3' thing that you'll rename away from later?
All on point. temp-dc3 will work and we can rename after we decomm the old dc3
Alright, temp-dc3.ad.mozilla.com has been deployed. Initial administrator password set, gpg'd and emailed to Q. Disk extended out to 120G, 2 CPU, 8G RAM. Let me know if you need anything else.
Attempting to DC promo the machine it said it required a reboot. Several reboots did not resolve this issue. After a deep rabbit hole dive many many attempts to resolve, research shows this issue is damn near impossible to resolve without a reinstall. I removed the new machine from the domain can we get a new template deployed?
Is there anything that you need us to do during the deploy to help prevent the black hole treatment? Let me know, and I can destroy temp-dc3 and redeploy.
NO I have to disable protected mode and make sure all the RPC services are turned on before I try to add the AD features. That "should" stop the issue from reoccurring.
Alright, per convo with Q, temp-dc3 destroyed, and a new temp-dc3.ad.mozilla.com deployed. password is set the same as the last one emailed in comment 5. Let me know if you need anything else.
Dcromo and primary replication is done. NSClinet checks now working correctly and are re-enabled. NXLOG exporting events. Closing bug.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Can I clean up the old DC3? I see in bug 1336790 that the temp-dc3 has been put in its place and declared stable. Let me know.
Can we say if things look good after Friday 6/16 we kill off the old VM?
Fine by me. Will poke again post Friday.
it is now post Friday. :) Can I kill off the old VM?
Alright, old dc3 killed, new dc3 renamed and SVMO'd. Thanks!
Whiteboard: [vm-create:2][vm-delete:1] → [vm-create:2][vm-delete:2]
You need to log in before you can comment on or make changes to this bug.