with similar considerations for Remote Desktop.<\/p>\n\n\n\n
Install Windows on the new SSD<\/h4>\n\n\n\n
Use keys from old system, or buy new ones. Create partition to reserve space for Linux later. Leave free space at beginning of drive.<\/p>\n\n\n\n
Use rufus.exe to create bootable USB Flash drive from ISO image. Use MFT partition table instead of GPT, if the install target is an old system with BIOS.<\/p>\n\n\n\n
On EFI system, everything went smoothly.<\/p>\n\n\n\n
On older BIOS system, Windows complains that there is no EFI partition, and install will likely fail. No, it won’t. There IS NO EFI.<\/p>\n\n\n\n
Set the system name.<\/p>\n\n\n\n
I suggest setting the volume name of the C: drive to “Win OS” or something similar, for easy ID when Linux mounts it.<\/p>\n\n\n\n
(In my case) set a static IP address.<\/p>\n\n\n\n Windows keeps the local time on the hardware real-time clock on the computer. Linux uses Universal time (like GMT). This means that every time the OS changes, the time will be wrong until synced with the internet. My preferred fix is to set this registry key in Windows:<\/p>\n\n\n\n In Windows Explorer, right click on the folder(s) or drive(s) you wish to share. Note that these shares are not easily browseable by Linux, but in Ubuntu, one can open Files, choose Other Locations, then Connect to Server at the bottom.<\/p>\n\n\n\n Additionally, because this is all in-house, I set permissions to Full Control for Everyone.<\/p>\n\n\n\n Windows 10 complains if its own Defender Firewall is turned off. It’s impossible to disable the warnings. The easiest thing for me to do would be to simply turn the Firewall off, and ignore the warnings that continually nag, since my computers are all in the house, and don’t have high-value data on them. But the more elegant solution is to turn the Firewall ON, and add exceptions as necessary.<\/p>\n\n\n\n Most programs create their own exceptions when installed, but I find that I have to manually add an exception for File and Printer Sharing. In addition, the firewall blocks Using Ubuntu, so use Startup Disk Creator to create usb flash drive for install.<\/p>\n\n\n\n Use gparted to delete the dummy partition, and convert it into free space. install linux there.<\/p>\n\n\n\n Set the system name, same as the Windows system name above.<\/p>\n\n\n\n Set a static IP address, identical to the address used for Windows.<\/p>\n\n\n\n Most of my computers are on DHCP, but some are static. The hostname of the computer is not always recognized. In Linux, editing Windows has a similar file, which is at Here are the contents of my \/etc\/samba\/smb.conf file. Notable settings are highlighted in RED<\/span>.<\/p>\n\n\n\n On Windows, Linux shares may not show up when browsing the Network. To access them, in Windows Explorer, go to \\\\MyLinuxBox, where that is the name of the Linux machine. If “MyLinuxBox” can’t be found, try pinging it first from Windows, then try again. If that doesn’t work, then try \\\\192.168.1.104, with the numerical IP address of the Linux machine. A list of shares offered should be shown. Map the desired one to a drive letter if you don’t want to type it manually every time.<\/p>\n\n\n\n Even though windows has its own Remote Desktop, Linux doesn’t work seamlessly with it, neither as a Client nor a Server. To avoid fuss, I just install tightvnc on the Windows machines. I set the Server to run as an Installed Service, and to accept connections with just a password. I used to use UltraVNC, but the included viewer has trouble displaying a large window sent from Linux. The tightvnc viewer has no such problems. Unfortunately, tightvnc is now basically a Windows only solution. There is an old, somewhat buggy version available for Linux, but it hasn’t been supported for years.<\/p>\n\n\n\n That password set above is saved on the default keyring in Linux, which is generally the Login keyring. That normally gets unlocked when I log in, so no trouble. But on a computer that I want to be headless, there’s a problem. The VNC server won’t run on the remote computer until it’s logged in, so I must auto-login. But if I auto-login, the Login keyring doesn’t get unlocked, and the VNC Server can’t retrieve the saved password, so makes up its own on the fly. I can’t connect with the password I previously chose.<\/p>\n\n\n\n The solution is as follows: in Linux, launch the app for Passwords and Keys. Right-clock on the new Keyring, and make it the Default. <\/p>\n\n\n\n With the Insecure Keyring set as default, go to Settings -> Sharing -> Remote Desktop, and set the password again. It should appear under Insecure Keyring as something like “Gnome Remote Desktop”, possibly two keys. At that point, go back to the Login keyring, and delete the correspondingly-named keys. Finally, right-click on the Login keyring, and set it to be Default once more.<\/p>\n\n\n\n The fastest way is usually to take the data drive out of the old system and put it in the new, then copy data over from C: to C:. Most of my data is on a separate drive (i.e., D:), which can be moved over in its entirety.<\/p>\n\n\n\n Alternately, a shared folder could be used to do the copy, but that will be limited to the speed of the network. Serial access to the drive through SATA clocks in at about 200 MB\/sec.<\/p>\n\n\n\n Don’t forget Download directories, anything on the Desktop. Also, in my case, I have a few old DOS programs in C:\\bin<\/p>\n\n\n\n My Linux data is small enough that it can be transferred through a USB flash drive.<\/p>\n\n\n\n Don’t forget the Downloads and Public directories.<\/p>\n\n\n\n In my case, the motherboard is an ASRock Z370m-itx\/ac . Press F2 during startup to get into EFI setup. Under ACPI, must configure system to power on from PCI Express.<\/p>\n\n\n\n In some systems, it might be power on from PCI, or LOM (Lan on Motherboard).<\/p>\n\n\n\n Enable WOL on the NIC through Linux. It may already be set from Windows.<\/p>\n\n\n\n It’s already on (“Wake-on: g”), previously set from Windows. But if it wasn’t:<\/p>\n\n\n\n In Windows, I use a program called MC-WOL.EXE, configuring a shortcut to call it.<\/p>\n\n\n\n I associate nicknames with MAC addresses in the following file:<\/p>\n\n\n\n I finally created an alias so that all I need to do to wake the other computer is type “wake front” or “wake back” :<\/p>\n\n\n\n If I wanted to retain any cards, memory, or drives from the old system, this would be the time to get them. Actually, I usually do such severe upgrades, that there is little worth salvaging. On my most recent system, the only thing I retained was some aftermarket thumb screws that make the case easier to open.<\/p>\n\n\n\n If there are hard disks in the old system, wipe them of personal data. Some people just remove the disks, entirely, but I’m more surgical about it. I delete my obvious personal data from both Operating Systems, then delete my user account, leaving an Administrator with no password. Then I run ccleaner to overwrite all free space on the disks, which can take 6 hours. This leaves intact operating systems, so if I sell it on craigslist for $5, the person can use it right away.<\/p>\n\n\n\n If there is a CD or DVD drive, make sure you didn’t leave something in it.<\/p>\n","protected":false},"excerpt":{"rendered":" This article is mainly for myself, to remind me what to consider when moving computers. I have two desktop type computers, which back each other up from time to time, and one of which backs up to external storage. I’m to cheap to pay for Cloud storage, at least for the amounts that I use. … Continue reading Manual Move of Data and Settings to New Computer(s)<\/span> ![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/07\/DisableFastStartup.png\")
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/08\/RealTimeIsUniversal.png\")
Create (Samba) Shares on the new Windows<\/h4>\n\n\n\n
Create Firewall Exceptions on new Windows<\/h4>\n\n\n\n
ping<\/code> by default. I have to go to Advanced Settings -> Inbound Rules, and choose all the File and Printer Sharing rules for echo (ICMPv4 – in), and set all 6 to YES.<\/p>\n\n\n\nInstall Linux on the new SSD<\/h4>\n\n\n\n
Edit the hosts file<\/h4>\n\n\n\n
\/etc\/hosts <\/code>resolves this. Here is what mine looks like. Only the red lines are my additions:<\/p>\n\n\n\n127.0.0.1 localhost\n127.0.1.1 ItxBox\n192.168.1.152 pididu\n192.168.1.152 pididu.com\n192.168.1.156 optiplex\n192.168.1.157 itxbox<\/span>\nThe following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters<\/pre>\n\n\n\nc:\\Windows\\System32\\Drivers\\etc\\hosts<\/code><\/p>\n\n\n\nCreate (Samba) Shares on the new Linux<\/h4>\n\n\n\n
#\nSample configuration file for the Samba suite for Debian GNU\/Linux.\n#\n#\nThis is the main Samba configuration file. You should read the\nsmb.conf(5) manual page in order to understand the options listed\nhere. Samba has a huge number of configurable options most of which\nare not shown in this example\n#\nSome options that are often worth tuning have been included as\ncommented-out examples in this file.\n- When such options are commented with \";\", the proposed setting\ndiffers from the default Samba behaviour\n- When commented with \"#\", the proposed setting is the default\nbehaviour of Samba but the option is considered important\nenough to be mentioned here\n#\nNOTE: Whenever you modify this file you should run the command\n\"testparm\" to check that you have not made any basic syntactic\nerrors.\n======================= Global Settings =======================\n[global]\nBrowsing\/Identification\nChange this to the workgroup\/NT-domain name your Samba server will part of\nworkgroup = FAMILY\navoid protocol SMB1 so that Windows 10 won't complain\nclient min protocol = SMB2\nclient max protocol = SMB3\nserver min protocol = SMB2\nserver max protocol = SMB3<\/span>\nWindows Internet Name Serving Support Section:\nWINS Support - Tells the NMBD component of Samba to enable its WINS Server\nwins support = yes\nname resolve order = bcast host\nserver string is the equivalent of the NT Description field\nserver string = %h server (Samba, Ubuntu)\nNetworking\nThe specific set of interfaces \/ networks to bind to\nThis can be either the interface name or an IP address\/netmask;\ninterface names are normally preferred\n; interfaces = 127.0.0.0\/8 eth0\nOnly bind to the named interfaces and\/or networks; you must use the\n'interfaces' option above to use this.\nIt is recommended that you enable this feature if your Samba machine is\nnot protected by a firewall or is a firewall itself. However, this\noption cannot handle dynamic or non-broadcast interfaces correctly.\n; bind interfaces only = yes\nDebugging\/Accounting\nThis tells Samba to use a separate log file for each machine\nthat connects\nlog file = \/var\/log\/samba\/log.%m\nCap the size of the individual log files (in KiB).\nmax log size = 1000\nWe want Samba to only log to \/var\/log\/samba\/log.{smbd,nmbd}.\nAppend syslog@1 if you want important messages to be sent to syslog too.\nlogging = file\nDo something sensible when Samba crashes: mail the admin a backtrace\npanic action = \/usr\/share\/samba\/panic-action %d\n# Authentication\nServer role. Defines in which mode Samba will operate. Possible\nvalues are \"standalone server\", \"member server\", \"classic primary\ndomain controller\", \"classic backup domain controller\", \"active\ndirectory domain controller\".\n#\nMost people will want \"standalone server\" or \"member server\".\nRunning as \"active directory domain controller\" will require first\nrunning \"samba-tool domain provision\" to wipe databases and create a\nnew domain.\nserver role = standalone server\nobey pam restrictions = yes\nThis boolean parameter controls whether Samba attempts to sync the Unix\npassword with the SMB password when the encrypted SMB password in the\npassdb is changed.\nunix password sync = yes\nFor Unix password sync to work on a Debian GNU\/Linux system, the following\nparameters must be set (thanks to Ian Kahan <kahan@informatik.tu-muenchen.de<\/a> for\nsending the correct chat script for the passwd program in Debian Sarge).\npasswd program = \/usr\/bin\/passwd %u\npasswd chat = Enter\\snew\\s<\/em>\\spassword:* %n\\n Retype\\snew\\s<\/em>\\spassword:* %n\\n password\\supdated\\ssuccessfully<\/em> .\nThis boolean controls whether PAM will be used for password changes\nwhen requested by an SMB client instead of the program listed in\n'passwd program'. The default is 'no'.\npam password change = yes\nThis option controls how unsuccessful authentication attempts are mapped\nto anonymous connections\nmap to guest = bad user\n#### Domains\n#\nThe following settings only takes effect if 'server role = primary\nclassic domain controller', 'server role = backup domain controller'\nor 'domain logons' is set\n#\nIt specifies the location of the user's\nprofile directory from the client point of view) The following\nrequired a [profiles] share to be setup on the samba server (see\nbelow)\n; logon path = \\%N\\profiles\\%U\nAnother common choice is storing the profile in the user's home directory\n(this is Samba's default)\nlogon path = \\%N\\%U\\profile\nThe following setting only takes effect if 'domain logons' is set\nIt specifies the location of a user's home directory (from the client\npoint of view)\n; logon drive = H:\nlogon home = \\%N\\%U\nThe following setting only takes effect if 'domain logons' is set\nIt specifies the script to run during logon. The script must be stored\nin the [netlogon] share\nNOTE: Must be store in 'DOS' file format convention\n; logon script = logon.cmd\nThis allows Unix users to be created on the domain controller via the SAMR\nRPC pipe. The example command creates a user account with a disabled Unix\npassword; please adapt to your needs\n; add user script = \/usr\/sbin\/adduser --quiet --disabled-password --gecos \"\" %u\nThis allows machine accounts to be created on the domain controller via the\nSAMR RPC pipe.\nThe following assumes a \"machines\" group exists on the system\n; add machine script = \/usr\/sbin\/useradd -g machines -c \"%u machine account\" -d \/var\/lib\/samba -s \/bin\/false %u\nThis allows Unix groups to be created on the domain controller via the SAMR\nRPC pipe.\n; add group script = \/usr\/sbin\/addgroup --force-badname %g\n###### Misc\nUsing the following line enables you to customise your configuration\non a per machine basis. The %m gets replaced with the netbios name\nof the machine that is connecting\n; include = \/home\/samba\/etc\/smb.conf.%m\nSome defaults for winbind (make sure you're not using the ranges\nfor something else.)\n; idmap config * : backend = tdb\n; idmap config * : range = 3000-7999\n; idmap config YOURDOMAINHERE : backend = tdb\n; idmap config YOURDOMAINHERE : range = 100000-999999\n; template shell = \/bin\/bash\nSetup usershare options to enable non-root users to share folders\nwith the net usershare command.\nMaximum number of usershare. 0 means that usershare is disabled.\nusershare max shares = 100\nAllow users who've been granted usershare privileges to create\npublic shares, not just authenticated ones\nusershare allow guests = yes\n======================= Share Definitions =======================\nUn-comment the following (and tweak the other settings below to suit)\nto enable the default home directory shares. This will share each\nuser's home directory as \\server\\username\n;[homes]\n; comment = Home Directories\n; browseable = no\nBy default, the home directories are exported read-only. Change the\nnext parameter to 'no' if you want to be able to write to them.\n; read only = yes\nRoderick: consider home network to be low security, nothing\nreally valuable. Make me the creator of all files written to\nshare\nforce user = young<\/span>\nFile creation mask is set to 0700 for security reasons. If you want to\ncreate files with group=rw permissions, set next parameter to 0775.\n; create mask = 0700\ncreate mask = 0777<\/span>\nDirectory creation mask is set to 0700 for security reasons. If you want to\ncreate dirs. with group=rw permissions, set next parameter to 0775.\n; directory mask = 0700\ndirectory mask = 0777\nBy default, \\server\\username shares can be connected to by anyone\nwith access to the samba server.\nUn-comment the following parameter to make sure that only \"username\"\ncan connect to \\server\\username\nThis might need tweaking when using external authentication schemes\n; valid users = %S\nUn-comment the following and create the netlogon directory for Domain Logons\n(you need to configure Samba to act as a domain controller too.)\n;[netlogon]\n; comment = Network Logon Service\n; path = \/home\/samba\/netlogon\n; guest ok = yes\n; read only = yes\nUn-comment the following and create the profiles directory to store\nusers profiles (see the \"logon path\" option above)\n(you need to configure Samba to act as a domain controller too.)\nThe path below should be writable by all users so that their\nprofile directory may be created the first time they log on\n;[profiles]\n; comment = Users profiles\n; path = \/home\/samba\/profiles\n; guest ok = no\n; browseable = no\n; create mask = 0600\n; directory mask = 0700\n[printers]\ncomment = All Printers\nbrowseable = no\npath = \/var\/spool\/samba\nprintable = yes\nguest ok = no\nread only = yes\ncreate mask = 0700\nWindows clients look for this share name as a source of downloadable\nprinter drivers\n[print$]\ncomment = Printer Drivers\npath = \/var\/lib\/samba\/printers\nbrowseable = yes\nread only = yes\nguest ok = no\nUncomment to allow remote administration of Windows print drivers.\nYou may need to replace 'lpadmin' with the name of the group your\nadmin users are members of.\nPlease note that you also need to set appropriate Unix permissions\nto the drivers directory for these users to have write rights in it\n; write list = root, @lpadmin<\/pre>\n\n\n\nEnable VNC on new Windows<\/h4>\n\n\n\n
<\/a>Enable VNC on New Linux<\/h4>\n\n\n\n
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/07\/Sharing.png\")
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/09\/PandK.png\")
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/09\/InsecureDefault.png\")
Copy Data from Existing Windows to New System<\/h4>\n\n\n\n
Copy Data from Existing Linux to New System<\/h4>\n\n\n\n
Make Wake-on-LAN (WOL) Work on New System<\/h4>\n\n\n\n
Enable WOL in EFI or BIOS<\/h5>\n\n\n\n
Enable WOL in Windows<\/h5>\n\n\n\n
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/07\/MagicPacket-1.png\")
Enable WOL in Linux<\/h5>\n\n\n\n
$ ifconfig<\/span>\nenp0s31f6<\/span>: flags=4163 mtu 1500\ninet 192.168.2.107 netmask 255.255.252.0 broadcast 192.168.3.255\ninet6 fe80::f423:5566:3f80:2e4e prefixlen 64 scopeid 0x20\n\n...\n\n$ sudo ethtool enp0s31f6<\/span>\nSettings for enp0s31f6:\nSupported ports: [ TP ]\nSupported link modes: 10baseT\/Half 10baseT\/Full\n100baseT\/Half 100baseT\/Full\n1000baseT\/Full\nSupported pause frame use: No\nSupports auto-negotiation: Yes\nSupported FEC modes: Not reported\nAdvertised link modes: 10baseT\/Half 10baseT\/Full\n100baseT\/Half 100baseT\/Full\n1000baseT\/Full\nAdvertised pause frame use: No\nAdvertised auto-negotiation: Yes\nAdvertised FEC modes: Not reported\nSpeed: 1000Mb\/s\nDuplex: Full\nAuto-negotiation: on\nPort: Twisted Pair\nPHYAD: 1\nTransceiver: internal\nMDI-X: off (auto)\nSupports Wake-on: pumbg\nWake-on: g<\/span>\nCurrent message level: 0x00000007 (7)\ndrv probe link\nLink detected: yes\n<\/pre>\n\n\n\n$ sudo ethtool -s enp0s31f6 wol g<\/span><\/pre>\n\n\n\nInitiate WOL from Windows<\/h5>\n\n\n\n
![\"\"](\"http:\/\/pididu.com\/wordpress\/wp-content\/uploads\/2023\/07\/WinWOL.png\")
<\/figure>\n\n\n\nInitiate WOL from Linux<\/h5>\n\n\n\n
$ sudo apt install etherwake<\/pre>\n\n\n\n
$ cat \/etc\/ethers\n70:85:c2:5d:8b:90 front\n00:21:9b:77:25:78 back<\/pre>\n\n\n\n
$ cat .bash_aliases\nalias wake='sudo etherwake -i enp0s31f6 '<\/pre>\n\n\n\n
Install Programs on All Operating Systems as Needed<\/h4>\n\n\n\n
\n
Make Sure Peripherals Work on Both Operating Systems<\/h4>\n\n\n\n
\n
Remove Hardware, if Desired, from Old System<\/h4>\n\n\n\n
Scrub the Old System Before Discarding<\/h4>\n\n\n\n