Diskpart Create UEFI Partitions

diskpart /s drive:\CreatePartitions.txt


select disk 0
clean
convert gpt
rem == 1. System partition =========================
create partition efi size=100
rem ** NOTE: For Advanced Format 4Kn drives,
rem ** Change this value to size = 260 **
format quick fs=fat32 label="System"
assign letter="S"
rem == 2. Microsoft Reserved (MSR) partition =======
create partition msr size=16
rem == 3. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools ===
shrink minimum=500
rem ** NOTE: Update this size to match the
rem size of the recovery tools
rem (winre.wim) **
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 4. Recovery tools partition ================
create partition primary
format quick fs=ntfs label="Recovery tools"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume

dism using .bat


set image=%~dp0Win10.wim
Dism.exe /apply-image /imagefile:%image% /index:1 /ApplyDir:W:\

Force WP always use HTTPS

Add this two lines to the .htacces file (located in the wp folder)


RewriteCond %{SERVER_PORT} !^443$
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

Chrome's pac file not working after upgraded to 1703

Thanks to info from below link, I'm able to troubleshoot my proxy problem with Chrome.
https://www.chromium.org/developers/design-documents/network-stack/debugging-net-proxy

To troubleshoot, in chrome, chrome://net-internals/#events
It gives you all sorts of information.

The pac file works in IE and Firefox but not in chrome after I upgraded to 1703.
The fix for now is start Chrome with command-line flag:
--winhttp-proxy-resolver

OSX install pkg in terminal


cd /
sudo mkdir /Volumes/mnt
sudo mount_afp afp://server/mnt /Volumes/mnt
sudo cp -R /Volumes/mnt/software.pkg /folder
sudo installer -pkg /folder/software.pkg -target / 
sudo shutdown -r now

* If you get permission denied while installing/coying the pkg from server, it is worth to check permission set on the pkg file.