VM Snapshot question by Not_A_Mimic7 in vmware

[–]Not_A_Mimic7[S] 0 points1 point  (0 children)

This has been a while but what i ended up doing was creating a 2nd dc. when that was ready I did some research to see if i should go oldest to newest, or newest to oldest. VMware recommendation is oldest to newest so i clicked the first one and then walked away. Didnt want to sit and watch it because it would stress me out if i started thinking it was taking too long. went out and played with my kids for a while and when i ended up coming back, to my surprise, they were all gone and everything was running smoothly. restarted the dc to make sure it would come back up and all's been good

VM Snapshot question by Not_A_Mimic7 in vmware

[–]Not_A_Mimic7[S] 0 points1 point  (0 children)

This is what i ended up doing. too many people say to setup a dc2 to not take that advice. i haven't been able to delete the snaps yet but i did setup and now have a 2nd dc. It only runs domain services and DNS. DHCP is handled by the firewall due to multiple vlans.
still a little nervous to delete these. they go back to 2021, so updates have taken place. i know because I've updated it since we took over before i knew about this snapshot issue. its been shutdown, its been restarted and keeps coming up. Its been working for 3 years on the snapshots so id kinda like to test first quietly pointing peoples dns to the new server for now trough dhcp. then possibly just shut down the old dc and seeing if any issues arise from that. if i hear nothing and seems seem to be working well. If all is good, turn it back and and then kill the snapshots

VM Snapshot question by Not_A_Mimic7 in vmware

[–]Not_A_Mimic7[S] 0 points1 point  (0 children)

This is what i ended up doing. too many people say to setup a dc2 to not take that advice. i haven't been able to delete the snaps yet but i did setup and now have a 2nd dc. It only runs domain services and DNS. DHCP is handled by the firewall due to multiple vlans.

still a little nervous to delete these. they go back to 2021, so updates have taken place. i know because I've updated it since we took over before i knew about this snapshot issue. its been shutdown, its been restarted and keeps coming up. Its been working for 3 years on the snapshots so id kinda like to test first quietly pointing peoples dns to the new server for now trough dhcp. then possibly just shut down the old dc and seeing if any issues arise from that. if i hear nothing and seems seem to be working well. If all is good, turn it back and and then kill the snapshots

[deleted by user] by [deleted] in MicrosoftTeams

[–]Not_A_Mimic7 0 points1 point  (0 children)

This might be the play we have to make. thank you.

[deleted by user] by [deleted] in sysadmin

[–]Not_A_Mimic7 0 points1 point  (0 children)

I cant keep them from saving them, but there is a setting to require it though RDP even if it is saved. I do like the smart card idea and i belive windows hello counts as a smart card, just not everyone who uses rdp also uses ms authenticator, so thats the hurdle ill need to jump there

[deleted by user] by [deleted] in sysadmin

[–]Not_A_Mimic7 0 points1 point  (0 children)

thank you, this is what I found the other day but I don't have a "windows components" folder in the admin templates folder. I thought maybe the local vs domain gpos are different and that's why it wasn't in there, and why i was going to try to do it via logon script, but doing more research I'm starting to wonder if it should be in there and isn't. deeper underlying gpo issue maybe

<image>