Upgrading Windows 10 Disconnect your VMs?

So how many of you upgraded your machines to Windows 10 Technical Preview? Go ahead ... raise your hands. I will! My work desktop is a lovely Dell Precision T7610 with Core i7 processor, 32 GB of RAM, 2 TB of storage and nice dual monitors form me to spread my work out onto. The Windows 10 Technical Preview program has been great on this rig and I can't wait to see what the team will do next.

However, I came in this Monday and started to do some work on my Hyper-V Virtual Machines that I host on this system. With 32 GB of RAM and dual NICs, I setup one for all of my VMs to connect while the other NIC is for my main OS. However, none of my VMs could get out of the main box. I checked and the cables were all plugged in. The system looked happy. What was I to do?

First, I noticed that the virtual NIC on the VMs showed that the cable was "disconnected". Now, I am a bit slow on the uptake sometime but how can a virtual NIC connected to a virtual switch be disconnected. Looking through my system, I couldn't find a virtual cable that I had to plug in. Maybe that will be something for HoloLens but I couldn't tell you because I haven't gotten my rig yet. So, that indicator gave me a suspicion around the connectivity.

Second, I went into the NIC settings on the computer/VM host to validate that the NIC was indeed connected to the network and it was happy there. Of course, it was happy and said that all should be well. This led me to think that the virtual switch was not working right.

Third, I went into the VM settings for the NICs and "removed" the cable setting the virtual switch to "Not Connected" applying that setting. After doing that, I put the setting back to my virtual switch that I use for my network connectivity ... still no go. Something tells me this is the switch.

Taking in my work so far, I set all VMs using this virtual switch to "Not Connected", thus unplugging them from the virtual switch. I removed the virtual switch and saved the settings. Then, I created a new virtual switch connected to that NIC validating that all settings worked. Once the virtual switch was recreated, I "plugged" the virtual machines in. Logging in to each machine, I verified that indeed all connectivity was returned and they were all happy. Good thing too as I needed to test some RegEx expressions for IIS URL Rewrite Tool.

I hope this helps you in your troubleshooting and maybe gives you a quick resolution to check prior to more troubleshooting.

Windows 8, the Mail App, and CA Roots

I know I am a big-time geek. I use my TechNet subscription from Microsoft and run many servers at home since I am not always very technical at my job as Director of IT. It is a management position, not a technical position. In setting up Windows 8 on my ASUS EP121, I wanted to use the Mail App to check on my personal mail accounts. I do have several and hoped to get the main boxes into the app. It has been a fight to get one account on and using a troubleshooting tool to get it done. Here's the info on all this …

As I stated, I have a TechNet account and run many of my own servers as testing grounds for Microsoft technologies. One of these servers is an Exchange 2010 system for e-mail. I also have my own Active Directory for my home network along with my own internal Certificate Authority for SSL Certificates. By importing the CA root, I can create certificates for my internal systems and websites. I implemented my own CA root and have my Exchange server utilizing it for its SSL certificates.

After installing the Consumer Preview of Windows 8, I tried to setup my personal Exchange account to the Mail App. After spending about 2 hours on the issue, I could not get a connection. I was tired of hitting my head against the wall and ended up connecting to my Windows 7 desktop using Outlook 2010. *sigh*

I was hoping that the Release Preview of Windows 8 and the apps would fix this. I was wrong. Hitting the forums and answers sites, I am finding I was not the only one. Many people fixed this by buying SSL certificates from a public CA like GoDaddy, Comodo or VeriSign. I was determined not to have to do this. If Microsoft wanted to support enterprise users, this is a need. They will want to use Win RT to connect to their work mail servers and many companies use their own CA.

After posting into the Answers forum, I got a PM from one of the forum moderators and a person working with Microsoft, either a vendor or Blue Badge. They wanted more information and to have me run some tools. In the course of several contacts, I did exactly what they asked and provided more and more logs. Eventually, they said that it was definitely a problem with my SSL Certificate and would I run Fiddler to look and see what the problem is. I installed the Beta copy of Fiddler for Windows 8 (v4.3.9.9 beta) and installed the Win 8 Loopback Extensions to capture the Metro app. Post installation of Fiddler and its add-on, I fired up Mail. To my amazement, it connected and synced my mail, calendar, and contacts. Everything was working as it should normally. A quick run through of my settings in Fiddler to ensure I was not ignoring SSL problems and a couple of other tests, I found myself with a working Mail app.

After reporting this to the forum moderator, I still not have heard anything from him other than "we are still working on the issue" posts. I find it an interesting solution to this issue. I wonder if this has anything to do with known SSL/HTTPS issues in MetroTwit on the Windows 8 Desktop. I also can say that the Metro IE will not pull up HTTPS pages properly but they work in the Desktop version of IE 10. I hope they fix some of these protocol oddities soon as the release to manufacturing is around the corner.


UPDATE 1: I also found that the Skydrive app does not work with Fiddler running and working for the Mail App in my case. More information on this issue is located at the Microsoft Answers Page on the issue.