Damn thats more impressive than what i have in production at work now

I just tried actually booting to my other win10 partition, the one that i didnt update yet.... First time it didnt work. Went back to bios screen, tried again, and after not letting me choose which win10 to use(again) it loaded up the un updated volume and i was able to login to it.
Now ive just rebooted back into win10 on my ssd, all is good.

I thought this might have happened to me last night when i was installing the Anniversary Update. during the update it would restart and after choosing to boot off sda1 from grub(i have many boot options), it would go straight to the updating of the win 10 installation on my ssd instead of asking me if i wanted to boot win10 off ssd or another win10 installation i have on a different hdd. Just rebooted now and all is good though, the partitions show up and are bootable.

dont forget to check afterwards if everything is ok with
dcdiag /v
repadmin /showrepl
repadmin /replsum

Am I the only IT guy that gets a salary anymore? I much enjoy salary rather than having to fill out a timecard every day. Also, if things are good i go home a bit early.
My home lab:
4930k with 32GB Ram, a couple TB storage, half a dozen vms. Going to add some managed switch in there at some point just havent done it yet. Also have a much lamer lab here at work that i am slowly building up using old stuff. Currently a XS 7 server with a vm on it to test gpu passthrough performance eventually(Solid Edge on a vm). Havent got around to testing it yet.
I would hire somebody without a lab, esp if it was an entry level help desk type situ.

I did something similar a while back with ancient win2k3 server serving AD, DNS, DHCP, file, print services. I demoted, removed AD, removed dns and dhcp. Then i p2v'd it.
It really is very simple to do.

Try moving your vdi while vm is running, to another SR, very exciting as you dont know if you will get the dreaded, 'The VDI mirroring cannot be performed" and your vdi just disappears. Luckily it is just detached and back in its original SR. Seems to only happen with windows vms for me

@BRRABill You mean just migrating a running vm that is a AD DC? Done it many times.

Are you sure? I think the account id is still 500 for administrator(this is the RID on the nt offline pw tool), and it should still use the C:\Windows\System32\config\SAM to store it.
You could try it without risk i think
Also found this
https://adsecurity.org/?p=1714 may not be helpful, but informative at least.

I assume you cant get this thing booted normally and that is why you need this?
Otherwise ntdsutil should be used while logged in as domain admin.
If so,
You might be able to use the nt offline pw reset tool (ive used it many times, just never on a dc).
www.chntpw.com/download
You can load this up and then see if it will alow you to change the local admin pw. It wont make any changes (just reads) til you tell it to.

What version of WinServer?

Always good to see this info every quarter, thanks again!

Fixed it. the local server lvm service was 'stealing' the block device before iscsi could get it and serve it out. I ended up going into lvm.conf and adding a global filter option.
Would be nice if the novel of commented lines in lvm.conf would have mentioned when this could/should be used. A normal filter option didnt ever work. But it was a redhat doc i found with a sentence that mentions iscsi devices for vms might have to use the global filter option.

I am stumped here with this problem. I setup a raid 10 array with mdadm made a vg and lv, configured iscsitarget and successfully get the SR to show up in XenServer using Xencenter. I can even load vms on it and do everything it should be able to. Until i reboot the iscsi storage. Then i get
(

Then of course the test vm wont load correctly. vgs and lvs and pvs all show what i think to be incorrect data after the reboot as well. Certainly not the same as when it is working.
After reboot lvs and vgs:

Just be careful here; dont go around deleting things if you arent sure. If the non existent domain is only listed on one of the DCs, shut down the dns server service(or the whole dc) on that dc, reboot the pcs that cant login and they should be available again.

@wirestyle22
Ok, you need to get on your DCs and look at the DNS. I bet that in your dns under Forward lookup zones for at least one of the DC is listed that non existent domain. Further i think that within that non existent dns domain is listed the pcs which are not available for logon.

And this Domain1 you mention, used to be a domain hosted on this dc but has been renamed or removed??

Is your email working correctly? Are all your domain computers authenticated correctly with your dc?

In your OP, by ADSync do you mean the Azure AD Sync tool?

What does the DC say? Its logs may be overflowing with useful info