Recently had an issue with a backup software that would get stuck in START_PENDING status at every startup. This caused it to be unable to be uninstalled, repaired, or forcefully removed and re-installed. Here is how we fixed it:
1. Find out the Service Name of the service by looking for it in the Services control panel:
2. Open command prompt as administrator
3. To get the PID type in – sc queryex [Service Name]
4. To kill the errant process type in – taskkill /f /pid [PID]
5. To remove the process type in – sc delete [Service Name]
One I had removed the process I restarted the server just to make sure then re-installed the software.
If your company needs help troubleshooting software issues, then contact us for assistance.
Every modern business has one thing in common – the internet.
Businesses are using computers, smart phones, tablets, etc. to connect to the internet for research, shopping, advertising, or any number of things. With a connection to the internet comes the need for routers, switches, wireless, and other network hardware to distribute internet connectivity across the company. There are malicious people on the internet that are setting traps and trying to break into companies which necessitate the use of tools like antivirus, internet filtering, spam filtering, and other protective measures. There are also people who work from their homes and need to have a way of tunneling safely into the network to use the resources there.
All of this has to be managed by someone in the company or you can contract with a managed IT service provider.
If your company needs help managing all the things connected to your internet, then contact us for assistance.
Make sure Hyper-V Host has CPUs than the combined total of CPUs for all servers being restored as these static until after the VMs are completely restored. If there is not enough CPU resources then the VMs will not boot.
Make sure Hyper-V Host has more than the combined total of RAM for all servers being restored as these settings are static until after the VMs are completely restored. If there is not enough memory then the VMs will not boot.
Create a SET NIC Team on the server (if you have multiple NICs)
Open Powershell as administrator
User the New-VMSwitch command to setup an external virtual switch to connect to for live connections
The AllowManagementOS is needed if you are using the same NIC team to access the VM host
Setup secondary Internal vSwitch to allow for testing before deploying
Setup Synology LUN targets for each VM to be restored. Make sure that they are big enough to hold all the full uncompressed size of the entire thick provisioned hard drives for the entire server.
Connect each LUN to the iSCSI Initiator on the VM Host. Make sure to bring them online, initialize them, and give them a drive letter. Synology needs this because it uses the SMB protocol to transfer the files during restore.
Make sure to allow the File and Printer Sharing app through the Windows firewall and open port 5986 to allow HTTP traffic for WinRM to allow Synology to query the Hyper-V settings.
Add the Hyper-V Host to the Active Backup for Business app.
Synology Active Backup Restore to Hyper-V
Open the Active Backup for Business app
Click on the Physical Server tab on the left
Select the server and click the Restore button
Select the point in time to restore from
Choose Restore to Microsoft Hyper-V
Choose Full Virtual Machine Restore
Change the Restore Name
Select a folder on the Hyper-V Host to place the configuration files
Select a folder on the Hyper-V Host to place each of the restore VHD files
Select a Virtual Switch on the Hyper-V Host to connect the VM to
Confirm the settings by clicking on the Done button.
After:
The VMs will boot with a single NIC and no network settings. Keep them offline and add additional NICs as needed to match the original setup. Then configure the NICs as before upon reboot. Make sure to connect to Internal Test Switch for initial steps.
Check hardware configuration of CPUs and RAM to determine if adjustments can be made. In particular, the RAM settings can be changed to startup, minimum, and maximum to allow for distribution of resources to VMs that have heavier workloads.
Boot VM to make sure it is functioning correctly. (first bootup can take upwards of 15 minutes)
Convert the VM from Gen1 to Gen2
Download Windows 10 ISO – https://www.microsoft.com/en-us/software-download/windows10
