After several weeks testing, I’m sad to tell you all that at least currently, Windows 10.0.14394 (aka 1607) still cannot work with WSUS.
Problem: If there is Windows related package push from WSUS, svchost processes on Windows clients keep crashing.
Check this for details: https://social.technet.microsoft.com/Forums/windows/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral
I’m testing to add the boot.wim files from Windows 10 1607 (10.0.14393) installation discs to Windows Deployment Services on Windows Server 2012 R2.
Test 1: Add x86 and x64 boot files to WDS
Test 2: Add drivers to boot files.
Failed with WDS client on Windows Server 2012 R2.
Succeeded with WDS client on Windows Server 2016 TP5 connected to the target WDS.
Test 3: Create discover images.
Passed but failed in Test 6.
Test 4: Create x64 capture image.
Test 5: Boot from boot files.
Test 6: Boot from discover images embedded in ISO files.
Failed with error: WdsClient: There was a problem initializing WDS Mode.
Try to use other images created from WDS clients of Windows Server 2016 TP5: failed in the same way.
Test 7: Boot from x64 capture image.
Test 8: Capture an instance of Windows 10.0.14393.
Instance for test: Windows 10.0.14393.10 x86 with up-to-date Office 2016.
Test 9: Deploy an instance of Windows 10.0.14393 through WDS.
To make deployment more convenient, we use Windows Deployment Services in our company. All images related is not the originals. Usually, we install Office products into a clean Windows instance before capturing. That’s is really a good way to save lots of time in every deployment.
The problem found is: if Office 2013/2016 is installed with Windows 7, even after sysprep run, the captured image is still not working well. If this image is deployed on another hardware, not the same one which is used to create this image, Office cannot be activated by KMS located in our company and error is 0x4004F00D.
To avoid that: At the very end before capturing, sysprep audit mode for example, run OSPPREARM.exe from Office folder to remove all data related to activation. This file can be found in “Program Files\Microsoft Office\OfficeXX”. Of course, if Office 32bit is loved in 64bit OS, “Program Files (x86)” should be a good replacement.
After OSPPREARM run, you may want to run “cscript ospp.vbs /dcmid” from the same folder to check the result. “Not Found” displayed is predicted.
BTW, if Windows 10 is used instead, this step is not necessary at all.
In Windows 10 releases, lots of apps are pre-installed. Different than in Windows 8/8.1, most of these apps cannot be uninstalled by GUI.
If you want to remove them, you still can do that by using powershell.
1 Start powershell with administrator privilege.
2 Enter these 2 commands to prepare the workspace.
3 Enter this command to show all installed package.
Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
You will see some apps listed. The packages with status Installed are ready for your further removal.
4 Use this command to remove one app.
Remove-AppxPackage -Package packagefullname
The packagefullname is the text listed by step 3. Usually, it starts with Microsoft and end with 8wekyb3d8bbwe.
You need to repeat the step 4 for each app you want to remove.
Not all apps, Microsoft Edge for example, can be removed but most can.
In one datacenter of my company, there was a strange problem last month of VMware vSphere.
Here is our structure:
SqlServer instance for vSphere is installed dedicated on cluster server. SqlServer version is 2012 Enterprise and Windows is 2012R2 Standard
vCenter is installed on another server.
After we applied July patches from Microsoft and restart the vCenter server, nearly all services from VMware cannot start. In event viewer, one event said:
The VMware Inventory Service service terminated with the following service-specific error:
As the request from VMware support, I uninstalled all updates related and reboot but it won’t help. I thought there may be some error related to the database connection. I ran the connection test from ODBC setup window, test finished succeeded. So I collected and submitted the log file generated from vCenter server command line. You know it’s really huge.
2 weeks later, I got an email from the high level engineers of VMware. By digging the log, they found that the vCenter cannot connect to SqlServer and the tcp service port is specified. At that moment, thanks to documentation I wrote :), I found that tcp service port is different than it should be. When I checked the SqlServer, I found the reason really weird: the TCP port of this instances is modified, automatically and silently. Due to I really used vSphere client just before upgrading Windows, I’m quite sure this issue is related to at least one of the patch which applied on the database cluster, launched by Microsoft in July 2016. And after a search, there is another instance of SqlServer which has the port changed. Due to the port changed and our firewall policy is set based tcp port, the client, vCenter in this issue, cannot connect to this SqlServer instance. After the port setting changed back and instance restarted, vCenter is back to normal.
Don’t ask me why ODBC test passed without any problem. If you know the answer, I’m listening as well.
After the ISO file of Windows installation disc downloaded, it’s possible to build a USB stick instead of burning a DVD disc.
To do that, you need a USB stick not less than 8GB as well as a working Windows. During the process, all data on this USB stick will be removed.
Phase 1: Preparing the USB stick
- From Windows client, run DiskPart as administrator. A console will be shown with the prompt “DISKPART> ” (without quotes, the same below).
- Enter “list disk” and press Enter. All disks will be shown with a number.
- Enter “select disk x” and press Enter. Replacing x with the number of disk shown in the step 2. If you run the step 2 again, you can see a star before the disk you selected.
- Enter “clean” and press Enter to clean the drive.
- Enter “create partition primary” and press Enter to create a partition filled this drive.
- Enter “format fs=fat32 quick” and press Enter to format this partition quickly with FAT32.
- Enter “active” and press Enter to mark this partition as active.
- Enter “assign” and press Enter to assign a letter to this drive.
- Enter “exit” and press Enter to quit DiskPart.
Phase 2: Copy files into this drive.
You just need to copy all files within the ISO file into this drive, making the root of this drive the same as the ISO file system. Do not put these files into any sub folder.
Phase 3: Optional, only if the Install.wim larger than 4GB.
If Install.wim is larger than 4GB, you cannot put it into this drive because no file larger than 4GB can be put into a FAT32 based partition beyond the limitation. You have to split it into smaller files. All other files should be copied as described in Phase 2.
To do that, you need to run this command:
DISM /Split-Image /ImageFile:d:\sources\install.wim /SWMFile:e:\sources\install.swm /FileSize:4096
It will split the install.wim from drive D into the USB stick drive E. Change these paths in your case.
Now you can use this USB stick to boot your computer and start the installation process like from the disc.
The sad thing is if you had to prepared this stick through Phase 3, the installation will be slower due to merging process, but nothing will be different in your installed system.