Close

## [Obsoleted] Windows 10.0.14393 cannot work with WSUS, yet

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

## .NET Core 1.0.0 VS 2015 Tooling Preview 2 failed to setup due to VS2015 Update 3 related issue

Due to some reason unknown, Setup of Microsoft .Net Core 1.0.0 VS 2015 Tooling Preview 2 may not started with error about VS 2015 Update 3, even Update 3 is installed well.

Luckily, we can pass the check by using command parameter SKIP_VSU_CHECK=1

Do remember to start cmd with admin privilege, or you will see this error.

## Add Windows 10 (1607/14393) boot files to WDS on Windows Server 2012 R2

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
Passed.

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.
Passed.

Test 5: Boot from boot files.
Passed.

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.
Passed.

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.
Passed.

Test 9: Deploy an instance of Windows 10.0.14393 through WDS.
Passed.

Hi. I built an ASP.net side powered by SignalR recently. The function is easy that dynamically load from a URL provided from SignalR into a div from browser side. It works like a charm in IE, Edge and Chrome. The JavaScript written in the web page is simple:

• SignalR 2.2.0 and jQuery 2.2.3 are selected;
• Connect SignalR at beginning;
• When SignalR disconnected, reconnect;
• When SignalR event raised, call one method to pull the data from URL specified and set as content of a div; and,
• Call the method mentioned above at beginning to load the initialization data.

Then, I need to do the same thing in one Raspberry Pi 3. I choose Windows IoT with UWP to build the basis. UWP app is quite easy, only one WebView control is embedded with the starting URL set to the page of that ASP.net website. According to only Insider Preview version can support Raspberry Pi 3, build 14295 is selected, which is the latest one can be found from official site.

After this app deployed and started in Raspberry Pi 3, it acts quite different. The initialization data is shown without any problem. But no more SignalR event is proceeded. By debugging on the server side, SignalR OnConnected, OnDisconnected and OnReconnected are called repeatedly and frequently.

Due to no more information can be grabbed from app running in Raspberry Pi 3, I have no clue at first. The good thing is I made a similar solution before. The only difference between these 2 apps, is the previous one use iframe instead of div. Despite of no reason observed, after I change the div into iframe and make the data surrounded by html and body tags which filling div previously , the problem vanishes away.

## Office 2013/2016 Activation Issue with Windows 7 deployed by captured images

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.

## UWP Developing: Don’t forget the firewall on IoT devices

After I deploy my UDP based application to Raspberry Pi 2 running Windows IoT 10.0.10586, this application receives nothing, just like running in a normal Windows computer.

I guess that maybe something related to firewall, but:
1 There is no article related to target that. As the time I’m writing this post, googling “Windows IoT firewall” returns nothing related.
2 There is no page for firewall configuration in Windows IoT utilities site.

Fortunately, a test proved that there is a built in Windows IoT.
By using PowerShell connection, I send the netsh command to create an exception of firewall. It accepted and the my application started to receive package after then.

Related command for reference:
netsh advfirewall firewall add rule name=”A name for this exception” dir=in action=allow protocol=UDP localport=12345

Hope this helps.

## UWP Developing: Local network protocal stack issue

I’m working on developing a Universal Windows App (Windows 10 IoT) recently. My app includes a UDP server for receiving packages.

The issue I found is:
When the UWP running on local computer, the datagram sent by local console application cannot be received.

Normally, while developing a socket based network application, another application for making and sending test packages should be prepared. The problem is, for testing UWP application, either the tester should be prepared as UWP application, or this tester can only be used on another computer laying on the same network.

## Warning: Do not apply MS16-004 / KB3114503 on SharePoint Server 2013

There is something wrong within this packaged launched and pushed by WSUS January 2016. Microsoft keeps telling us M\$ has fired all testers, or should be.

If you have installed this patch, all lists from all SharePoint sites will suck like this:

Lots of errors repeatly: typeError: Cannot read property ‘replace’ of undefined

The quick fix is remove the edit menu. And the final solution is applying January 2016 CU.

No matter MS16-004 / KB3114503 is installed or not, you may want to install the January 2016 CU. Therefore, it’s not necessary to apply this package IMHO.

## Best Practice: Move Windows Server VM from vSphere to SCVMM (2012 R2)

Due to the removal of P2V wizard in SCVMM 2012 R2, we need to to this migration manually.

In this scenario, we will move a Windows Server VM hosted in vSphere/ESXi 6 to SCVMM/Hyper-V 2012 R2.
We need:

• A working SCVMM 2012 R2 with Hyper-V, and the client tool for management.
• A working vSphere 6 with ESXi, and the client tool for management.
• A network shared folder which can be accessed with read-write permission by VM, Hyper-V (optional) and the computer which the client tool of SCVMM located.

Here are the steps:

1. Download the tool disk2vhd from https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx and decompress it into the network shared folder.
IP Address. If it’s set to automatic, make announce to your network admin to either set the VM to fixed IP address, or rebinding the MAC address later.

• System CPU and memory.
• OS Release name and bit wide, e.g. Windows Server 2008 Standard 32bit.
• Hard disks and partitions structure.
3. Run the disk2vhd at the network shared folder from VM. I suggest you not to copy it to the VM. All partitions which belong to the same hard disk should be exported to the same file at the SAME time. And all partitions from different disk should NOT be in the same exported file.
For the VM running Windows Server 2003 (R2 included, x86 x64 included), do NOT check the option for virtual-pc. It will prevent the success from installing Hyper-V integration services.
This step may take a while.
4. Create a new VM in SCVMM by using the correct name, CPU, memory, OS release name. For my test, I cannot create a VM without hard drive. So just delete it after the creating finished.
5. Copy the file(s) created from step 3 into the folder of the new VM.
Due to the Windows bug of calculating free space of the host drive instead of the cluster volume disk, you may be prompted with an error said no enough disk space left for the VHD files.
In this case, you need to execute the copy from Hyper-V, not form another computer. If your Hyper-V is installed without the full OS, aka Windows Hyper-V Server, you may have to do this by using cmd. The command for mapping a network shared folder as a driver is:

net use x: \\path\to\your\shared\folder

If you need to specify the account for accessing that folder:

net use x: \\path\to\your\shared\folder password /User:domain\account

After VHD files copying, use this to unmap the folder:

net use x: /d

6. Adding the VHD files to the new created VM by correct sequence.
7. Shutdown the old VM and boot the new one.
8. Log into the new VM, uninstall the VMware tools and shutdown the OS. If your VM is using Windows Server 2003 and you are using Remote Desktop to access SCVMM, now you have to use keyboard to finish this job.
9. Install Hyper-V integration services. For Windows Server 2012 and above, it’s optional but recommended. For Windows 2008 R2 and previous, it’s necessary.
10. Start the VM again and set the IP addresses of network interface cards.
11. Mark or remove the old VM for avoiding conflicts.

Hope this work-though helps.

## Removing preinstalled apps in Windows 10

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.

Steps:
1 Start powershell with administrator privilege.

2 Enter these 2 commands to prepare the workspace.

Import-Module Appx Import-Module Dism

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.