While I’m trying to deploy my site from Visual Studio to a Windows Server 2012 R2 instance, I have to dig a lot for troubleshooting about Web Deploy related problems.
Here are some not listed in Microsoft documents:
- Visual Studio need both Web Deploy (Web Deployment Agent Service, MsDepSvc) and Web Management Service (WMSVC).
- You cannot install Web Management Service separately.
- The easy way to install the both is choose “Web Deploy 3.6 for Hosting Servers” Web Platform Installer.
- If you selected “Web Deploy 3.6” in another release, without “for Hosting Servers”, Web Management Service will not be installed.
- If you leave Web Deploy installed without Web Management Service, you could add it by install “Web Deploy 3.6 for Hosting Servers” but IT WILL NEVER WORK! You have to UNINSTALL existed Web Deploy first and then reinstall the “Web Deploy 3.6 for Hosting Servers”.
Microsoft fixed the problem about Windows Update working with WSUS, finally after nearly 2 months.
In our company, our major productive servers are hosted in vSphere as Windows-based virtual machines. Some of them need very big disks. Through the largest disk space supported in vSphere is 16TB (or maybe more, i dunno), I’m not interested to create such a big file in VMFS. It will be really a pain your *** when you have to move such a big file among datastores, even among data facilities by using portable hard drives.
Creating smaller disks instead of a big one for every Windows-based VM, IMHO.
Fortunately, Windows support to merge small disks as a big one, using dynamic disk function. There are 4 kinds of volume can be supported in such a condition: Spanned, Striped, Mirrored and RAID-5. You can consider them like JBOD, RAID-0, RAID-1 and RAID-5 functions in a simple legacy storage device.
Because data protection is existed in the SAN, Mirrored and RAID-5 volumes are not considered at all. Striped will make it a little faster when lots of virtual disks fight for limited IOPS resources within one datastore. But there is no way to extend any stripped volume (https://technet.microsoft.com/en-us/library/cc770938.aspx).
So, the useless volume format in a traditional world, spanned volume, is the best solution, maybe the only one. Next time when you need to create big virtual disks for Windows in any virtualization environment, don’t forget to consider using Spanned Volumes.
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.