Displaying 3 results from an estimated 3 matches for "win10a".
Did you mean:
win10
2020 Jul 11
1
Help with external snapshots as backups
...I now just continue to backup the snapshots in the
eventuality of a crash, then use this original image backup and the
snapshots to restore it?
I suppose I would also periodically merge the snapshots back into the a
single snapshot to ease the process?
# virsh snapshot-create-as --domain dave-win10a win10a-state01
--diskspec
vda,file=/var/lib/libvirt/images/vm_snapshots/disk-overlay.qcow2,snapshot=external
--memspec
file=/var/lib/libvirt/images/vm_snapshots/mem-overlay.qcow2,snapshot=external
--atomic
Domain snapshot win10a-state01 created
# ls -lh vm_snapshots/
total 3.3G
-rw------- 1 q...
2020 Mar 05
1
Samba 4.12.0 on Fedora32: bind DNS still say "named: client @...: update 'fedora.loc/IN' denied"
...> DHCP script, the clients records no longer belong to the clients, so
> they will not be able to update them. Try deleting the records and
> allow
> the clients to recreate them.
Into DNS now there is no reference for these win10 clients or IP.
I have remove the first win10 client (win10a) from DNS before join it,
and I have try with another new win10 pc (win10b), before join it to
domain its IP/name does not exist into domain and DNS
This is the output of samba-tool dns query
cmd=[samba-tool dns query localhost fedora.loc @ ALL -Uadministrator]
Name=, Records=3, Children=0...
2020 Mar 05
2
Samba 4.12.0 on Fedora32: bind DNS still say "named: client @...: update 'fedora.loc/IN' denied"
Hi, I'm doing some tests of samba DC 4.12.0 + MIT (experimental)
Kerberos + Bind DNS + Dhcpd + Chronyd on Fedora 32 beta.
All work fine except this issue:
The dhcp work, and the script for record the name of clients into dns
is disable (like Rowland suggest).
https://lists.samba.org/archive/samba-technical/2020-February/134875.html
If I join a new windows client to domain all work fine and