I know I have been quiet recently.
I have a pretty good series of reasons. Business has been super up tempo (happens when you have great solutions that work technically and not just venture capital marketing), I was promoted to a Principal (not Principle) with a territory of Most of US (excluding the Eastern Seaboard), my team is three resources down (we are hiring), and I have been traveling like crazy to make it all work. How much travel.. well I have status on 4 airlines and this is how many nights at just the Marriott Brand of hotels… 149 (remember this excludes conferences as those don’t count)
Not to worry I have:
- A good 20 blogs in flight (need to be edited for length and ‘Murican).
- I have been working on a book tentatively entitled “What color is your cloud?”.
- I have several new pieces of hardware to post reviews and specifications.
- I have been traveling and speaking like a mad person, expect a few more posts about travel.
Last but not least I have 17 days of use or lose it vacation so I can focus on these kind of side projects! Yea free time!
So Expect a lot before the end of the year!
Windows 1809 was released today during the Microsoft Surface hardware announcement today. Lots of progressive updates.
I will be posting more about 1809 features in the near future.
The most interesting note for me is that enterprises now have a 30 month window of support for fall releases. Yes, 30 months!
Enjoy downloading today!
Solution: Run windows update via Command line wuauclt.exe /updatenow
Several of the most recent Windows Insider builds have had issues. Mainly performance delays of an hour. How did this miss Canary… but here we are. Good news the 17735 build came out that looks to address the overlay issue of Settings. Why is this important? Well you can’t get off this bad build until you run windows update. However, one of the bugs is the inability to run Windows update. Catch-22?
Command line to the rescue. If you are running a windows 10 tablet without a keyboard here is your method. You can skip several of these steps if you have a keyboard.
- Click and hold the start key (equivalent of Windows Key + X or right click)
- Select Windows PowerShell (Admin)
- If you are on 17733 you might have to come back to the device in 60 minutes before you are prompted for UAC
- Once in PowerShell you can type CMD
- This will open a command prompt in C:\windows\system32
- Type in and execute wuauclt.exe /updatenow
- Check start >> Reboot to see it you have a Update and Restart option
- If you don’t just wait or type in the keyboard command again
Heads in beds.
A dubious distinction of a business traveler is achieving lifetime status at anything. Million miles milestones with airlines or minimum level at a hotel chain. In another sign of my constant wanderlust and success of my employer I have now achieved the highest lifetime status at the Marriott corporation.
The timing couldn’t have been better as the merger of programs SPG, Ritz Carlton, and Marriott programs occuring in 2018 means I will be among the few who are grandfathered into:
NOTE: Members that reach 750 nights and 10 years at Platinum by December 31, 2018 will be grandfathered into Lifetime Platinum Premier Elite status (notified January 2019). In addition, members that achieve Marriott Rewards Lifetime Platinum under the legacy requirements by year end will also be grandfathered into Lifetime Platinum Premier Elite status. And, don’t forget that we’ll combine Lifetime activity across both Rewards and SPG toward qualification when members combine accounts in August. Beginning in 2019, qualification into Lifetime Platinum Premier Elite status will not be available. See FAQs for details.
Interesting that Platinum Premier Lifetime status will not be allowed going forward. Also nice to see Marriott changed the original statement about SPG not qualifying for Platinum Premier Elite status.
Looks like Marriott is still having some glitches as my most visited city Toronto On I have only visited once two months ago.
For everyone else here is how your status will change in August
As a member of the first console and online gaming generation… I wonder what my next gamification of my life will be.
See you all… somewhere… soon!
Opened up Hyper-V today and all of my VMs where missing… umm what?
So I tried to connect to a server (button far right)
“Hyper-V encountered an error trying to access an object on computer ‘localhost’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.”
Checked Services they are running
Checked optional components they are running
Tried to run PowerShell Get-VM… ERRORS!
Long story short it turns out that a recent uninstall had deleted a MOF
Run the following command from an Elevated (Administrator) command prompt or PowerShell. Winkey+X >> Windows PowerShell (Admin)
Sometimes an uninstaller for an application has unintended consequences! Good news it was an easy fix of just recompiling the MOF (Microsoft Object Format). WMI is awesome but so touchy.
I travel for work… a lot. Which means I am connecting to a lot of WIFI networks. Yes, I know security issues but hey I have to get work done no matter where I am.
Issue: Long logon / Logoff and Guest WIFI redirects failing
Recently, I was experiencing extraordinarily long Logon and Logoff times. It was highly infuriating and I didn’t have a clue what was causing it. A little digging gave me a method to see what was taking so long. This also led me to why I couldn’t connect to wifi gateways for guest logon.
Enable Verbose Logon Status Messages
To use enable verbose status messages by editing the registry, follow these steps:
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- Locate and then click the following registry key:
- On the Edit menu, point to New, and then click DWORD Value.
- Type verbosestatus, and then press ENTER.
- Double-click the new key that you created, type
1 in the Value data box, and then click
- Quit Registry Editor.
Note Windows does not display status messages if the following key is present and the value is set to 1:
With this enabled I noticed I was having a long time with network configurations as it was running through the entire network stack history.
The easiest method to clear the history is to run the following command line:
Note: -R is capitalized
-R (Reload) Purges and reloads the remote cache name table
Why just clear out the stack versus figure out the sort order? Well, mainly for expediency. Every time I connect to a network I only care about the network I am connecting to at that moment. As the initial logon process works well… but reconnecting to a history network didn’t…
During the 1803 upgrade I noticed a new user logon status message I hadn’t seen before: Waiting for Workplace Connectivity. More research coming…
The offical announcements for Windows 10 1803 have not gone out. However, it looks like there are a few canaries in the coal mine getting the 1803 update directly from Windows Update. In my case I forced a full update in the control panel and pop up comes Feature update to Windows 10, version 1803
The build number is 17134.1 which matches the most recent builds on Flighthub
For good or bad, it had NO names associated with the 1803 release. Just New Feature Update. So I was kind of correct here
I would expect announcements and more buzz here soon.
#WindowsInsiders #WindowsUpdate #Windows10 #WaaS #1803 #Windows1803 #Windows101803 #MVPBuzz