OS Guide: Slipstream Updates Using DISM and OSCDImg *Updated

We have found out that we need to have the May Servicing Stack Update (SSU) KB4132216 _and_ the latest SSU which is currently KB4465659 in the Updates_WinServ folder we drop the Cumulative Update into for the Windows Server 2016 slipstream run.

• Article: OS Guide: Slipstream Updates Using DISM and OSCDImg

Note that the current version of the script points to Server 2019. Please use that as a base to tweak and create a set of folders for Windows Server 2016 and Windows 10 updates.

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

New PowerShell Guides and DISM Slipstream Process Updated

We've added two new PowerShell Guides:

• New-VM Template: Single VHDX File
• New-VM Template: Dual VHDX File

We've also updated the page with some tweaks to using DISM to update images in the Install.WIM in Windows Server. The process can also be used to slipstream both Servicing Stack Updates (SSUs) and Cumulative Updates (CUs) for both Windows Server and Windows Desktop.

Thanks for reading! :)

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

Mellanox SwitchX-2 MLNX-OS Upgrade Stall via WebGUI and MLNX-OS to Onyx Upgrade?

Yesterday, we posted about our OS update process and the grids that indicated the proper path to the most current version.

A catch that became apparent was that there were two streams of updates available to us:

1. image-PPC_M460EX-3.6.4112.img
2. onyx-PPC_M460EX-3.6.4112.img
• ETC
• 

As can be seen in the snip above we read an extensive number of Release Notes (RN) and User Manuals (UM) trying to figure out what was what and which was which. :S

In the end, we opened a support ticket with Mellanox to figure out why our switches were stalling on the WebGUI upgrade process and why there was a dearth of documentation indicating anything about upgrade paths.

The technician mentioned that we should use CLI to clean-up any image files that may be left over. That's something we've not had to do before.

Following the process in the UM to connect via SSH using our favourite freebie tool TeraTerm we connected to both switches and found only one file to delete:

• WebImage.tbz

Once that file was deleted we were able to initiate the update from within the WebGUI without error on both switches.

Since we had MLNX-OS 3.6.4112 already installed the next question for the tech was, "How do we get to the most current version of Onyx?"

The process was as follows:

1. Up to MLNX-OS 3.6.4112
2. Up to Onyx 3.6.6000
3. Up to Onyx 3.6.8008

As always, check out the Release Notes (RN) to make sure that the update will not cause any problems especially with in-production NICs and their firmware!

Happy News! Welcome to Onyx

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

Mellanox SwitchX-2 and Spectrum OS Update Grids

We're in the process of building out a new all-flash based Kepler-64 2-node cluster that will be running the Scale-Out File Server Role. This round of testing will have several different rounds to it:

1. Flat Flash Intel SSD DC S4500 Series
• All Intel SSD DC S4500 Series SATA SSD x24
2. Intel NVMe PCIe AIC Cache + Intel SSD DC S4500
• Intel NVMe PCIe AIC x4
• Intel SSD DC S4500 Series SATA SSD x24
3. Intel Optane PCIe AIC + Intel SSD DC S4500
1. Intel Optane PCIe AIC x4
2. Intel SSD DC S4500 Series SATA SSD x24

Prior to running the above tests we need to update the operating system on our two Mellanox SwitchX-2 MSX1012B series switches as we've been quite busy with other things!

Their current OS level is 3.6.4006 so just a tad bit out of date.

The current OS level for SwitchX-2 PPC switches is 3.6.8008. And, as per the Release Notes for this OS version we need to do a bit of a Texas Two-Step to get our way up to current.

Now, here's the kicker: There is no 3.6.5000 on Mellanox's download site. The closest version to that is 3.6.5009 which provides a clarification on the above:

Okay, so that gets us to 3.6.5009 that in turn gets us to 3.6.6106:

And that finally gets us to 3.6.8008:

Update Texas Two Step

To sum things up we need the following images:

1. 3.6.4122
2. 3.6.5009
3. 3.6.6106
4. 3.6.8008

Then, it's a matter of time and a bit of patience to run through each step as the switches can take a bit of time to update.

A quick way to back up the configuration is to click on the Setup button then Configurations then click the initial link.

Copy and paste the output into a TXT file as it can be used to reconfigure the switch if need-be via the Execute CLI commands window just below it.

As always, it pays to read that manual eh! ;)

NOTE: Acronym Finder: AIC = Add-in Card so not U.2.

Oh, and be patient with the downloads as they are _slow_ as molasses in December as of this writing. :(

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

OS Guide: Slipstream Updates and Drivers Using DISM and OSCDImg

We've posted another guide to our Web site.

• OS Guide: Slipstream Updates and Drivers Using DISM and OSCDImg

Using the script on this page in an elevated CMD allows us to take the base Install.WIM for Windows Server 2016 and slipstream the latest Cumulative Update into it.

Then, the script copies the updated Install.WIM into two separate folders where we keep two sets of installer files/folders. One is a Bare version that has only the Windows installer files. The other contains a whole host of drivers, BIOS and firmware updates, and a copy of the newly minted .ISO file. We use the FULL version for our USB flash drives (blog post) that get permanently plugged into all server systems we deploy.

This script is constantly updated.

Another will be posted at a later date that also includes the ability to update the Install.WIM file with drivers.

UPDATE 2018-06-04: Fixed the link!

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Web Site
Our Cloud Service

Remote Desktop Client: An authentication error has occurred. *Workaround

Updates last night included one for CredSSP CVE-2018-0886.

For those of us that are hesitant to patch our servers the instant a patch is available we'll be seeing RD Clients unable to connect for the period prior to our regression testing and release cycle.

Remote Desktop Connection

An authentication error has occurred.
The function requested is not supported.

Remote Computer: SERVERNAME
This could be due to CredSSP encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660

For now, the workaround on the remotely connecting RD Clients is to set the following registry key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters]
"AllowEncryptionOracle"=dword:00000002

Copy and paste the above into Notepad and Save As "CredSSP.REG" in a quickly accessible location.

Double click on the created file and MERGE. An elevated Registry Editor session would also allow for import via the FILE menu.

Once the above registry setting is in-place reboot the client machine and the connection should work.

Happy Patching! :)

UPDATE 2018-05-09 @ 10:47 MST: A caveat:

It is better to update the server backend, if possible, before making the above registry change.

If that is _not_ possible, then after the updates have been applied on the server(s) make sure to _change_ the registry setting to its most secure setting.

UPDATE 2018-05-10 @ 17:38 MST:

Update sources:

• Windows Server 2012 R2 Updates List
• KB4103725 fixes the issue but may require a manual from the console/desktop reboot!
• Windows Server 2016 Updates List
• KB4103723 fixes the issue but requires a reboot

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Web Site
Our Cloud Service

Windows Server 2016 July 18, 2017 CU is Important!

The July 18, 2017-KB4025334 (OS Build 14393.1532) Update is _important_!

There are fixes in there for a lot of cluster specific products.

• iSCSI
• S2D
• ReFS
• DeDup
• MPIO
• NTFS

The specifics are in the Microsoft page linked to above as is a download link.

We are in the process of updating our base Install.WIM image (blog post) with this update as I write this!

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service
Twitter: @MPECSInc

Windows Server 2016 March 2017 Update: Full & Delta Available

We can download both the full March Cumulative Update or there is now a Delta available.

Delta Update Windows Server 2016

The update is quite critical for those of us that run clusters on Windows Server 2016.

• Addresses issue which could cause ReFS metadata corruption
• Several fixes for Enable-ClusterS2D cmdlet for setting up Storage Spaces Direct
• Addresses issue with Update-ClusterFunctionalLevel cmdlet during rolling upgrades if any of the default resource types are not registered
• Optimization to the ordering when draining a S2D node with Storage Maintenance Mode
• Addresses servicing issue where the Cluster Service may not start automatically on the first reboot after applying an update
• Improved the bandwidth of SSD/NVMe drives available to application workloads during S2D rebuild operations.
• Addresses issue with all flash S2D systems with cache devices where there was unnecessary read data from both tiers that would degrade performance

A full list is here: March 14, 2017—KB4013429 (OS Build 14393.953)

The Delta Update can be used to update our .WIM files for our Windows Server 2016 flash drive based installers (Blog post How-To).

Note that the last Cumulative Update took a good hour to run on our VMs and nodes. This one is sounding like it may take as long or longer depending on whether the Delta of full Cumulative Update gets installed.

Here’s a direct link to the Microsoft Update Page for KB4013429.

Happy Patching! ;)

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Installing Windows: Updating Drivers for Boot.WIM and Install.WIM

We have a number of clients that are going to be on Windows 7 Enterprise 64-bit for the foreseeable future.
Most, if not all, of the laptops we are deploying today require a few BIOS tweaks to turn off uEFI and SecureBoot prior to beginning the setup process.
Once that is done, the laptops we are deploying today have wired and wireless network, chipsets, and USB 3 ports that have no drivers in the Windows 7 Boot.WIM or Install.WIM files. So, we would be left stranded when trying to deploy an operating system (OS) via flash!
Given the amount of application updates most of our clients have we decided to avoid using MDT or other imaging software to deploy a new laptop. The time savings would be negligible since we’d be stuck running all of the application updates or new installs post OS deployment anyway.
Also, when installing an operating system via USB 3 flash drive with decent read speeds it only takes a few minutes to get through the base OS install. Windows 10 can have an entire OS install done in a few minutes.
The following instructions assume the files have already been extracted to a bootable flash drive to use for installing an OS on a new machine.
Here’s a simple step-by-step for updating the drivers for a Windows 7 Professional Install.WIM:

1. Dism /Get-WimInfo /WimFile:D:\sources\install.wim
• Where D: = the flash drive letter
2. Dism /Mount-Wim /WimFile:D:\sources\install.wim /Name:"Windows 7 PROFESSIONAL" /MountDir:C:\Mount
• Change C: to another drive/partition if required
• NOTE: Do not browse the contents of this folder!
3. Dism /Image:L:\mount /Add-Driver /Driver:C:\Mount_Driver /Recurse
• Again, change C: to the required drive letter
• We extract all drivers to be installed or updated to this folder
4. Dism /unmount-Wim /mountdir:L:\mount /commit
• This step will commit all of the changes to the .WIM file
• NOTE: Make sure there are _no_ Windows/File Explorer, CMD, or PowerShell sessions sitting in the C:\Mount folder or the dismount will fail!
5. Dism /unmount-Wim /mountdir:L:\mount /Discard
1. Run this command to dismount the .WIM

The following is the process for updating the WinPE Boot.WIM:

1. Dism /Get-WimInfo /WimFile:D:\sources\boot.wim
2. Dism /Mount-Wim /WimFile:D:\sources\boot.wim /Name:"Microsoft Windows Setup (x64)" /MountDir:C:\Mount
3. Dism /Image:C:\mount /Add-Driver /Driver:C:\Mount_Driver /Recurse
4. Dism /unmount-Wim /mountdir:C:\mount /commit

The above process can be used to install the newest RAID driver into a Windows Server Boot.WIM and Install.WIM to facilitate a smoother install via flash drive.
Currently, we are using Kingston DTR3.0 G2 16GB flash drives as they have good read and decent write speeds. Please feel free to comment with your suggestions on reasonably priced 16GB and 32GB USB 3 flash drives that have good read and write speeds.
Good to us is ~75MB/Second read and ~35MB/Second write.
Thanks for reading! :)
Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Server 2016 January 10 Update: KB3213986 – Cluster Service May Not Start Automatically Post Reboot

The January 10, 2017 update package (KB3213986) has a _huge_ caveat for those updating clusters especially with Cluster Aware Updating:

Known issues in this update:

Symptom
The Cluster Service may not start automatically on the first reboot after applying the update.

Workaround
Workaround is to either start the Cluster Service with the Start-ClusterNode PowerShell cmdlet or to reboot the node.

For those managing large cluster deploys this situation definitely leads to a need to evaluate the update procedure for this particular update.

Please keep this in mind when scheduling this particular update and have update resources set up to mitigate the problem.

Note that as of this writing, the cluster service stall on reboot is a one-time deal as far as we know. Meaning, once the update has been completed and the node has successfully joined the cluster there should be no further issues.

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Warning: Sage 50 2016 Server Manager will Reboot Without Prompting

We were installing the database manager on the backend server for a client.

It started the .NET 4.5.2 FULL installer then suddenly disappeared after a few minutes.

So, keep in mind that this one will need to be done when no one is accessing that backend server! Or for that matter that the user that we are working on setting up or updating will have their machine reboot spontaneously.

Also, Sage released this version as an “update”. We received quite a few calls from our accounting firms when they could no longer connect to their Sage/Simply data on the server.

In the end, it turned out that no prompt was given to the user that the “update” was actually an “upgrade”. 

Yo, Sage! A little warning would be appropriate please.

EDIT: Updated a bit for specifics.

Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book

Cluster-Aware Update Runs: How Long?

When one needs to provision a new Windows Server 2012 RTM/R2 cluster one of the time factors to keep in mind is the Cluster-Aware Update runs that will happen once the cluster has been brought up.

The above is a new Windows Server 2012 R2 four node cluster that we finished configuring last night.

The first CAU run started around 2300Hrs. As can be seen each node took about an hour to run through the process.

Even though we are not too far into the product release cycle for R2 one needs to keep in mind the update maintenance process if one is not using an up-to-date image for deployment. This would be especially true if deploying 2012 RTM or 2008 R2 clusters.

Cluster node configuration:

• Intel Server System SR1695GPRX2AC with RMM
• Intel Xeon Processor X3470, 32GB ECC, 120GB Intel SSD RAID 1, Dual Intel SAS HBAs

Some important Cluster update tracking links:

• TechNet: List of Failover Cluster Hotfixes for Windows Server 2012
• Microsoft Support: KB2784261 Recommended hotfixes and updates for Windows Server 2012-based failover clusters
• Microsoft Support: KB2920151 Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters

Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen ASP Project
Find out more at
Third Tier: Enterprise Solutions for Small Business

Exchange 2013 OWA Comparison: RTM to CU1

We are happy to report that after walking through all of the troubleshooting steps we needed to that Exchange 2013 CU1 installed successfully on one of our Exchange 2013 RTM greenfield deploys.

Note that there were 18 steps to the whole process _after_ completing the AD prep steps and installing the required components on Server 2012.

This is a shot of Exchange 2013 RTM OWA:

This is a shot of Exchange 2013 CU1 OWA:

We now have the SPAMfighter folder listed.

One thing we noticed is that OWA loaded a _lot_ faster on the new platform than it used to on RTM.

As always, _test_ updates in a lab setting before wondering out and running them on production systems.

We had a System State and a full ShadowProtect backup of this particular setup before we jumped in as a just-in-case.

Given that some of the RTM bugs were critical at this site we jumped into CU1 right away on a production system.

So far, we can report that things are back to normal. So far . . .

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Might want to hold off on Exchange 2013 CU1

We ran into a hiccup with applying CU1 in the "Prerequisite" stage. We backed off with essentially no changes made, at least the routine did not jump into running the actual update and this morning we have no mail flow.

In the mean time, things are not working. :(

The above is OWA and mail flow is not coming in or going out.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Update KB2750149 Breaks Hyper-V 2012 Failover Clusters

It seems that a recent update is wreaking havoc on Hyper-V 2012 Failover Clusters.

• Microsoft Forums: Failover cluster manager crashing after updates
• KB 2750149: An update is available for the .NET Framework 4.5 in Windows 8, Windows RT and Windows Server 2012
• The update in question.

If updates have not been run as of yet then avoid this one.

If things are not working as expected after a round of updates and this one was included uninstall and hopefully things come up as they should.

Error quote from the Forums post:

A weak event was created and it lives on the wrong object, there is a high chance this will fail, please review and make changes on your code to prevent the issue.

Version=1
EventType=AppHangB1
EventTime=130022261829914481
ReportType=1
Consent=1
ReportIdentifier=26cc3e6a-5a82-11e2-93f7-782bcb53a584
IntegratorReportIdentifier=26cc3e6b-5a82-11e2-93f7-782bcb53a584
NsAppName=mmc.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=mmc.exe
Sig[1].Name=Application Version
Sig[1].Value=6.2.9200.16384
Sig[2].Name=Application Timestamp
Sig[2].Value=50109efd
Sig[3].Name=Hang Signature
Sig[3].Value=5707
Sig[4].Name=Hang Type
Sig[4].Value=138496
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.400.8
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=c8c0
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=c8c0bc8698a6964e5cded02ffc06ca16
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=5707
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=c8c0
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=c8c0bc8698a6964e5cded02ffc06ca16
UI[3]=Microsoft Management Console is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Management Console
AppPath=C:\Windows\System32\mmc.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
NsPartner=windows
NsGroup=windows8

We tend to wait on updates with our managed clients.

It seems that regression testing for updates has not been up to the same standard it has been in the past at Microsoft.

So, we test here in-house beforehand. It is a part of our service offering.

Hat Tip: SBS Diva

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Windows Phone 7 Update 7.10.8112.7

We just got offered the following:

The more info link takes us to this page:

• Windows Phone update history

Note that the latest listed update on the Windows Phone site says 7.10.8773.98 and ours says 7.10.8112.7. That's quite the difference.

A bit of searching brought us to this page:

• Mobile Tech World: Windows Phone Tango roll out has started. Update your phone manually to build 7.10.8773.98

According to the above site 7.10.8773.98 is Tango and provide an update method though we are a bit wary of using a third party tool to run this process.

Of course, the above was written while the update was running. Once it was completed though the following showed up:

It seems that Tango will be on the phone today.

We shall see if it makes a difference with the phone.

From what I can see, nothing outright. Still no mobile hot spot. :(

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Simply Accounting 2012 Update Release D May Require a Database Manager Update

We have received some calls from users unable to open their Simply 2012 files on the server after updating their client to Release D.

So, we ran the update on the server to make sure that whatever changes the updated client was looking for could be found on the server:

Note that a Restart Now is NOT needed.

Simply start the Simply Accounting Database Connection Manager in the server's Services.msc:

Once the back end was updated the users still could not use their recently used file list. They needed to go in and open the file manually before the update would pop its information up in the client.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Microsoft Updates for Hyper-V RSS Feeds

Here are some Microsoft updates Web lists with RSS feeds for the Hyper-V Role and Server:

• TechNet: List of Failover Cluster Packages Updated After the Release of Windows Server 2008 R2 Service Pack 1 (SP1)
• 
• Note that the proper RSS feed looks to be the last one.
• TechNet: Hyper-V: Update List for Windows Server 2008 R2
• 
• Again the last one.

There will be additional feeds once Windows Server 8 gets its name and is released to manufacturing.

Hat Tip: Susan Bradley

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Stuck at Configuring Windows updates – Do not turn off your computer. Try This First Before Anything Else

Lately when setting up a new server or updating a production server that has been up for a few months we have been seeing the following:

Windows Server 2008 R2 Enterprise

Configuring Windows updates
32% complete
Do not turn off your computer.

What we have discovered is that after waiting five minutes we can CTRL+ALT+DLT and the log on screen will show up. Sometimes it may take 10, 20, or even 30 minutes or more before we see the log on screen but it does eventually come up.

For whatever reason though the server can be left all to itself in the above state and stay there until we hit the keys.

This is our first step now before running into the update recovery steps that may be required if this does not work.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Windows Phone 7 Update to 7.10.8107.79 Now Here

After plugging the HD7 in the following window came up:

The keyboard issue has been seen off and on over the last month. The voicemail issue was indicated as being fixed with the last update so we shall see if it happens this time around.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.