![]() The important thing is to use a backup tool that creates an image backup of your boot/system drive. Back it up before you lose it!Īny time you make major changes to a Windows system, such as installing a major application suite like Microsoft Office or performing an OS upgrade or repair, it’s a good idea to begin that process with a complete backup. Thus, the most important bit of advice I can dispense for those who must venture beyond Step 1 is this: make a complete backup of your system to provide a source for files and information that might otherwise go missing. Some steps involve additional work to restore the prior state of your PC more or less back to where it was prior to taking that step. The amount of time and effort required for each step goes up incrementally. (The only remaining step at that point would be to replace the system on which the software is running, and that’s outside the scope of this story.) Keep working through the steps in order until you reach the end, and you are bound to fix the vast majority of problems. If that doesn’t fix what’s broken, advance to the next step. The idea is to first try the initial step in the sequence. That said, most of these approaches also work with Windows 7 and 8 (with slight variations), and the advice here applies almost identically to Windows 11, which Microsoft is gradually rolling out to Windows 10 users whose hardware can support the new OS via Windows Update from October 2021 into early 2022. I’ve now updated it for the latest versions of Windows 10. I initially wrote this story in 2016, but as Windows 10 has evolved over time, some of the steps have changed a bit. When that happens, users would be well advised to break out the following routine to help them set things back to rights. This often takes the form of worsening performance or stability, and can originate from damage to, loss of, or corruption of Windows system files typically found in the C:\Windows folder hierarchy. It would be good subnetting practice.Sometimes a Windows 10 system starts misbehaving to the point where repair is needed. I guess I could've configured the network to have even fewer Hosts, but meh. I don't plan on having a huge amount of devices/services running in the virtual environment so I figure this would be plenty of space. I chose a pretty basic Class C network, 192.168.10. Once DC Promotion was completed and I was able to log into it I then started to configure DHCP on the DC. Nooby mistake, but glad I ran into it here in my virtual environment. That's where I saw that my local user account password would be my Domain password after the promotion. On the third time I finally slowed down and actually READ the prompts during the installation (reading is good BTW). I was simply able to revert back to before I made those changes. This saved me a TON of time having to restart fully. #Protip: Make sure to create checkpoints while working in Hyper-V. I thought I must've misconfigured ADDS installation so I reverted back to before I installed it. I didn't want this #DC to potentially interfere with the rest of my network so that's why I made this choice.Īfter #ADDS installed and the server rebooted I could not log back into it with my domain credentials. This was important as I currently have my ISPs router to handle #DHCP and #DNS. I created a new virtual #switch and made it so only internal devices would be able to communicate with it. I had forgot to connect my server to a virtual #network. I ran into a prerequisite error that my #TCPIP settings were not configured properly. Once it booted for the first time, I then started to install #ActiveDirectoryDomainServices through #ServerManager and Promote the server to a #DomainController. I was then able to complete the initial setup of my Server 2022 instance. I re-downloaded the ISO file and mounted it to the VM, and it booted. After more #troubleshooting and reading I figured it must've been something to do with the ISO file I got from #Microsoft. I continued to have issues trying to get the VM to boot to disc even though I had Virtualization turned on. Next, I worked on getting an Evaluation copy of #WindowsServer2022 installed in a VM. Not sure how I would've been able to install Hyper-V without that turned on, but oh well. After a ton of reading and watching how-to videos, I figured out that for some reason #Virtualization was turned off on my CPU. I hope the services turned on and ready to go, however, every time I would try to get a VM booted up I would get errors. I started off my night by trying to get #Hyper-V working on my #desktop. It was great getting to work with a bunch of technologies from scratch! Got to work on my #Virtual #HomeLab project tonight.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |