Scheduled Tasks:
Execute .bat file, from the folder, choose une day
.bat File:
sqlcmd -S .\SQLEXPRESS -E -Q “EXEC sp_BackupDatabases @backupLocation=’C:\where_to_put_bak_file\’, @databaseName=’db_name’, @backupType=’F'”
L | M | M | G | V | S | D |
---|---|---|---|---|---|---|
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
Scheduled Tasks:
Execute .bat file, from the folder, choose une day
.bat File:
sqlcmd -S .\SQLEXPRESS -E -Q “EXEC sp_BackupDatabases @backupLocation=’C:\where_to_put_bak_file\’, @databaseName=’db_name’, @backupType=’F'”
Steps:
C:\Windows\System32\Spool\Printers
Stop spool service
delete all files
start spool service
Assign both your Windows partition and your EFI partition a drive letter. The EFI partition by default is not assigned a drive letter, but you can use diskpart to assign a letter temporarily. Then make sure you know which drive letter each partition is assigned in the environment you’re using. When you’ve got both partitions assigned a drive letter and you know which partition has which drive letter, modify the example command below as needed. In the command below, the EFI partition is X: and the Windows partition is C. Change those as needed for your setup:
C:\Windows\System32\bcdboot C:\Windows /s X:
That will cause the EFI bootloader files from your Windows partition to be copied onto your EFI partition, which should get it working.
If it doesn’t work, try formatting your EFI partition as FAT32 just to erase it and start from scratch, then try running that command again. Again, that command is what Windows Setup runs when it first installs Windows in order to set up the EFI partition, so it should be able to get you a working EFI partition again.
c:> mklink /d c:\some\directory \\some_server\some_share
This will create a folder named c:\some\directory which will show the content of the share \\some_server\some_share.
This will work also with a remote disk with i.e. \\some_server\C$.
Types of Virtual Switches
External – This type of switch is bound to the physical network cards located in the host. As you would imagine, they provide VMs located on these switches with access to the physical network the Hyper-V host is connected to. The External switch can also share management traffic as well as VM traffic on the same switch and this is one of the options that can be set when creating the external switch.
Internal – This switch is not bound to a physical network card so only allows traffic between VMs and the host itself. However, a new addition to the Internal switch functionality in 2016 is the addition of the NAT forwarding internal switch which does allow external connectivity via NAT from the Hyper-V host.
Private – This type of switch is only used for virtual machines to communicate with each other. This type of switch might be useful for certain specific types of traffic such as cluster network if only using one host as it can’t be utilized between hosts.
https://www.google.com/search?client=firefox-b-d&q=install+rsat+windows+10+1909
and
https://gallery.technet.microsoft.com/Install-RSAT-for-Windows-75f5f92f
Download the ps1 Powershell file and execute it.
from root or sudo:
nano /etc/default/grub
find the row with GRUB_CMDLINE_LINUX_DEFAULT
and complete with:
“quiet video=hyperv_fb:1920×1080”
or the resolution you want; save and exit
update-grub
reboot the vm
Pure Line theme by Theme4Press • Powered by WordPress Paolo Pizzolongo Chi è veramente ricco non ha bisogno dei soldi
Recent Comments