When I change operating systems, I do a clean reinstall of the new OS. I backup all my data and downloaded apps. I go to the manufacture's sites to get the latest drivers for motherboard, controllers, printers, etc. I verify everything will work on the new OS. Usually, I end up replacing hardware and upgrading software. I am always amazed by how much of my hardware and software does not support the new OS properly. It also cleans up all the legacy crap of the former OS. WinSXS and Windows Upgrade folders are filled with it. Next, Do I want to replace the hard drives or other hardware? You can find that newer OS and older chipsets don't blend well. Is your hard drive old or too small? Great time to replace it.
Sysprep can be tricky and troublesome.
I am working on my CompTIA Linux+ cert. Watched all the videos on this site. I created CentOS and Ubuntu server to practice on both flavors. I decided to play with Wordpress, PHP, and MySQL along the way.
I am considering getting some HP 7.2K 4TB drives and doing SAS Hardware RAID 10 of 8TB. It would cost about $600 for 4 of them. I have a DL320e Gen8 server with hardware RAID and a SD card with VMWare 6 U3 on it.
I moved everything off my Ubuntu web server into Wordpress on a CentOS 7 server. Ubuntu 16.04.5 was 580GB thick provisioned taking up a lot of space. Backed it all up. It will go away and be recreated as a Ubuntu thin provisioned Word Press server with the latest PHP, MySQL and WordPress on it. I will get another SSL cert for it.
I see I can get plugins for Wordpress that migrate sites to other servers. Yes, they work. Even the pro ones are not expensive.
My VMWare 6 U3 server can create virtual hard drives. How about 4 separate hard drives installed as thin provisioned drives.
1.) /boot 30 GB, probably overkill but I don't always cleanup the old stuff.
2.) / 50GB, My CentOS 7 server with all the LAMP components uses 4.7 GB.
3.) swap of 10 GB. I will give it 6GB of RAM. I doubt I will ever need a swap partition but 10GB isn't that much space to worry about
4.) /var of 500GB. I other CentOS 7 Wordpress server has my 4 websites on it. 308GB out of 500GB. I can create another website and split off my parents and siblings stuff from my wife and children.
What do you think? I can expand each drive as needed. Thin provisioning doesn't use the space like thick. I have never done multiple hard drives in Linux installs. I will go back to my old RAID method of installing separate RAID volumes for each partition. I don't need to screw around trying to move stuff off CentOS 7 to expand a single drive install. I have room to do this 4 drive setup in VMWare.
[root@CENTOS7WEB boot]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 47G 4.6G 42G 10% /
devtmpfs 2.9G 0 2.9G 0% /dev
tmpfs 2.9G 0 2.9G 0% /dev/shm
tmpfs 2.9G 18M 2.9G 1% /run
tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
/dev/sda1 28G 229M 28G 1% /boot
/dev/sda2 503G 285G 219G 57% /var
tmpfs 581M 0 581M 0% /run/user/0
This is my CentOS 7 Wordpress server. I have been thinking about the web sites growing as I add content. Reinstalling and moving WP to a new server is a pain and a half. It is installed on VMWare 6 U3. One hard drive. Can I add a second hard drive and move sda3 to it and then expand the first hard drive to expand /sda2?
Can I create a /var/www2 on a new hard drive and put the virtual host on it.
chown -R apache:apache ,/var/www2 Word Press uses apache:apache for its rights. 755 / 644 for its rights.
3rd time that a major change to the firmware has done something like this. I wish they had a validation tool that could check our configuration for these issues. In the former release they said to X and this release is Y. The release notes are not enough to go through and check for all the changes that need to be made.
When you create your new AD server, DNS should migrate automatically. DHCP has a neat export using Netsh. You will have to clean up the old dhcp server lists once all your servers are decommisioned. I would not do it till then in case you need to revert back due to issues. Don't upgrade the functional level till you are done and don't need to revert back.
I called Fortinet. I am on 5.6.4. They recommended going to 5.6.5. It could help with the SSh putty issue. We removed a port 22 virtual ip that was not connected to any server. Virtual IPs can cause issues even when not connected to a policy. The web server virtual IPs they recommended using the actual WAN interface instead of any. In 5.6.3 and above, they said if you use any on the VIP interface if can toggle between the two connections. They turned on some routing features that were disabled in a previous version. So tonight, I am going to 5.6.5. 6.02 is out but most of the features are for enterprise networks. I also upgraded the forticlient to the latest version. Ticket still open for testing tomorrow.
I figured the VPN policy would have prevented it. The underlying firmware has bugs that will cause these issues from other areas of the configuration.