Windows 10 --- How to fix Sysprep fail

Sysprep is a tool for IT administrators who want to prepare an installation of Windows for duplication.

In Windows 10 or Windows 8 platform, the serveral Microsoft Store Apps have built in that maybe encounter some isssue when execute the Sysprep tool.

The cause is that Sysprep has an additional provider that's added in Windows 10 and Windows 8 to clean Appx packages and to generalize the image.

If an all-user package that's provisioned into the image was manually deprovisioned from the image but not removed for a particular user, the provider will encounter an error while cleaning out this package during sysprep. The provider will also fail if an all-user package that's provisioned into the image was updated by one of the users on this reference computer.

To resolve this issue, remove the package for the user who's running sysprep, and also remove the provisioning.
The steps is as follows:
1. Unplug the Internet connection to prevent Microsoft Store from updating apps

2. Run the Import-Module Appx on PowerShell cmdlet.
3. Run Import-Module Dism on PowerShell cmdlet.

Remove the package
4. Open SetupErr.log and notice the error entries
5. Run Get-AppxPackage -AllUser | Select-String
6. Run Remove-AppxPackage -Package

Remove the provisioning

7. Run Remove-AppxProvisionedPackage -Online -PackageName

So do that maybe can fix Sysprep fail.

Systemback --- How to create systemback live system on lubuntu 16.04

Although we can get the upgrade setup of Ubuntu/Lubuntu from Browser Search, we also find out some case will fail if follow these steps. "If we can do the image snapshot or backup before upgrade begin, maybe we have chance to rollback to the initial state.", I think.

Systemback is a good utility that can be used to backup and restore Ubuntu/Lubuntu systems. I will create the complete backup of the live system including user configuration files and data as ISO, and save them in an external hard disk. That is to create the live Ubuntu system as the booted USB or ISO, and boot your system using it in-case of any problems.

It is very simple to install Systemback utility in Ubuntu 16.04 LTS.(#1)
At first, add Systemback PPA by using sudo add-apt-repository ppa:nemh/systemback command.

Next to update the software sources by using sudo apt-get update command

Finally, install Systemback using by sudo apt-get install systemback command

Once the installation is finished, Launch Systemback in Applications-> System Tools-> Systemback and supply the password to key in this dialog box.

The default interface look like as follows:

To click on "Live system create" button and supply the name of (new) live system, replacing "auto". We will set the Working directory (/home)  where you store live image and iso. This directory must be a writable linux filesystem - no fat, exfat, fat32 nor ntfs directories or partitions can be used for storage. If ready, click on "Create new" button to go ahead.

The systemback displays a progress bar

To wait for your Live system creation to finish as the following notification.

After Systemback has finished creating the new live system, we can write the system directly to a pen (USB flash) drive or DVD.

USB drive
Insert a flash drive、 click on the circleback green arrow to refresh it, the "Write target" box will display a flash drive and the "Write to target" Live operation becomes ungrayed and available.
To select a created live image and a target drive next to click on "Write to target".

The dialog box will show up and click on Start to go ahead.

Systemback will writes the selected image to your flash drive and a progress bar is displayed.

Finally, the live system image will success to be write to the Flash drive.

ISO or DVD
We also can create an .iso from the created live image if the .sblive file is not larger than 4 GB (#2). To select a new live image next to click on Convert to ISO.

So do that we can create the entire the system as live bootable ISO and write the ISO to DVD or USB drive next to boot it.

[Reference]：
(#1). systemback version limitation
https://launchpad.net/systemback
This PPA contain the stable version of Systemback.

Currently supported Ubuntu releases:
- 14.04.X LTS
- 15.04
- 15.10
- 16.04.X LTS
- 16.10
* DEVELOPMENT AND SUPPORT ENDED

newer versions of systemback
*https://launchpad.net/~sonicwalker/+archive/ubuntu/sonicos+dev

(#2).Why systemback "Convert to ISO" button is disabled?

This is a file system limitation. If the .sblive file is larger than 4 GB, the conversion to a .iso file is not possible.

How to workaround this problem to generate the ISO manually?
   1. Decompress the .sblive image:
       $ mkdir sblive
       $ tar -xf /home/BeforeUpgradeOS_1.sblive -C sblive

   2. Rename the syslinux to isolinux:
       $ ls -al sblive/syslinux/*.cfg sblive/

       $ mv sblive/syslinux/syslinux.cfg sblive/syslinux/isolinux.cfg
       $ mv sblive/syslinux sblive/isolinux

       $ ls -al sblive/syslinux/*.cfg sblive/

   3. Install mkisofs from https://sourceforge.net/projects/cdrtools/
     3-1.Install the packages via some third party PPA
       $ sudo add-apt-repository ppa:brandonsnider/cdrtools

       $ sudo apt-get update
       $ sudo apt-get install cdrecord mkisofs

     3-2.Install the packages via source compiler
       $ sudo apt install aria2

       $ aria2c -s 10 https://sourceforge.net/projects/cdrtools/files/alpha/cdrtools-3.02a09.tar.gz

       $ tar -xzvf cdrtools-3.02a09.tar.gz
       $ cd cdrtools-3.02
       $ make
       $ sudo make install

   4. Generate the ISO file:
       Normal BIOS Mode
       $ modemkisofs \
          -iso-level 3 -r -V "sblive" -cache-inodes -J -l  \
          -o /media/davidwa/MyBackup/sblive.iso \
          -c isolinux/boot.cat \
          -b isolinux/isolinux.bin \
          -no-emul-boot -boot-load-size 4 -boot-info-table \
          -no-emul-boot \
          sblive

       UEFI Mode
       $ mkisofs \
          -iso-level 3 -r -V "efisblive" -cache-inodes -J -l  \
          -o /media/davidwa/MyBackup/efisblive.iso \
          -c isolinux/boot.cat \
          -b isolinux/isolinux.bin \
          -no-emul-boot -boot-load-size 4 -boot-info-table \
          -eltorito-alt-boot \
          -eltorito-boot boot/grub/efi.img \
          -no-emul-boot \
          sblive

 

   So do that we did make a iso file over than 4GB size

VMware Workstation 14.0.0 --- How to convert a virtual disk from growable to preallocated on Lubuntu 16.04

In general, we create a virtual disk with growable type for saving the disk space on vmware environment. For performance thought, maybe need to change the disk type for reducing the count of the defrage/compact disk.
By the virtual machine settings, we can know whether the disk is preallocated or not in the disk information.

Once decide to do this, we have to shut down the virtual machine because the disk can’t be converted if it’s powered on or suspended.
To convert the virtual disk by using the following command
$ vmware-vdiskmanager -r < original disk > -t < type > < target disk >

Note:
1). The location is the sames as one.
2). In using the -t flag, VMware virtual disk (vmdk) types has the following choice.

• 0 : single growable virtual disk (single .vmdk file)
• 1 : growable virtual disk split in 2Gb files (multiple 2GB files)
• 2 : single preallocated virtual disk (single file)
• 3 : preallocated virtual disk split in 2Gb files (multiple 2GB files)
• 4 : preallocated ESX
• 5 : compressed for streaming

When successfully finish the convert, we need to replace the original Disk file with the new disk. The action flow is as follows:
AS-IS

TO-BE

Now we can boot it normally.

Lubuntu 16.04 --- The Fcitx-Chewing input method cannot show the Chinese fonts.

Due to the Lutuntu 16.04 install process select the Englisht language, my system language is in English by default. If want to install the additional language as Chinese character, we need to launch "Language Support" item as follows:

At first, the keyboard input method switch to the "fcitx" mode based on the personal behavior.

When click "Install / Remove languages ..." button, we can select the prefer language as "Chinese Traditional" to be installed.

Note:
If the language support is trigger in the first time, the system will directly tell us that the language support is not installed completely and ask us whether want to install them now.

After install and reboot, we will choose the right language next to log on the system.

In the moment, the system will ask us whether will change the language of the profile folder to the current "new" language? By you decide!

To click the Penguin icon for configuring "fcitx" input method.

Add "Fcitx-Chewing" to the current input method.

When switch to Fcitx-Chewing mode and want to key in Chinese font by document editor, we find out the input screen is blank and cannot show any words.

By searching the Google, we find out maybe kill "fcitx-qimpanel" process can resolve this problem. It it is true by doing "killall fcitx-qimpanel" command next to key in the Chinese font again, we will disable "fcitx-qimpanel" fucntion when the system boot by doing the following process.

Reboot and log on again for verify whether the problem can be resolved.

If the problem still exist, maybe need to install the "Qt Quick" module

Reboot again and almost the blank screen will be resolved.