I recently set up a new Windows 10 machine. After eight years with only Apple devices, I finally wanted to fetch up with the PC and Windows world again.
For a day or two, I tried to connect my laptop to my NAS at home. I checked firewalls, credentials, server settings, usernames, network. I checked it double, triple, quadrupplewise. I tried almost any permutation. Eventually, I gave up.
At a very last attempt, I tried the option to map a network drive. After entering user credentials again and again, finally Windows 10 came up the very first time with a useful error message.
“This shares requires the obsolete SMB1 protocol…” is quite some information one can work with.
Enabling SMB1 turns out to be quite easy. Head to Turn Windows Features on or of and scroll down to SMB 1.0/CIFS File Sharing Support. There check SMA 1.0/CIFS Client to enable SMB1 support.
Once done, connection to servers providing (only) SMB1 will work again on Windows 10.
You own a MacBook Pro? You run Boot Camp? You run Mac and Windows? You want to upgrade to Windows 8 but you still hesitate because Apple has not released a new Boot Camp version supporting Windows 8? First of all: I did it. I have to admit, I haven’t spent a single though on drivers before I upgraded to Windows 8 – and still I just blog from Windows 8 on my MacBook Pro.
What happens when I upgrade?
If you upgrade, some devices will work some won’t.Even if the Microsoft Upgrade Assistant does not show any incompatibilities with any of the MacBook’s devices in its report, they probably won’t work.
After installing, Windows 8 will show various devices in the Devices list indicating, there are no drivers available. Other’s simply won’t be detected at all, e.g. Windows8 won’t be able to detect the MacBook Pro’s WiFi at all. Function key, keyboard backlight won’t work and the graphics chipset might reset the screen resolution between the MacBook’s native resolution and something about 800×600 from time to time.
Where to get the Windows 8 drivers for my MacBook Pro?
To solve the driver issues, you simply start the Boot Camp Assistant from your Mac OS and follow the instructions until you find yourself faced with the following dialog.
Chose Download the latest Windows support software from Apple and continue. In the following step follow the on screen instructions either burning a DVD/CD or copying the files to a USB drive or any folder accessible from Windows (don’t drop the files to the Mac OS’s partition, though).
Will it blend work?
Restart Windows 8 and insert the disc, stick and select the setup.exe in the WindowsSupport folder. This will install a whole bunch of drivers.
Based on Apple’s Boot Camp 4.0 FAQ , the Windows Support Files contain the following drivers
Apple Keyboard Support
Apple Remote Driver
Atheros 802.11 Wireless
Boot Camp control panel for Microsoft Windows
Boot Camp System Task Notification item (System Tray)
Intel Chipset Software
Intel Integrated Graphics
Marvel Yukon Ethernet
Cirrus Logic Audio
Startup Disk control panel for Microsoft Windows
Once installed and the machine restarted, everything seems to work fine, the Windows Bluetooth and Boot Camp icons are shown in the notification area, light sensor, FaceTime camera and sound work perfectly and the graphics card runs smooth like butter.
One last word on function keys – they won’t work out of the box. You have to start the Boot Camp Control Panel from the tray and switch to the Keyboard tab.There check the Use all F1, F2… box.
Windows 8 on the MacBook Pro is a great experience even without touch display and retina. Upgrading without checking for the drivers of course was a greenhorn mistake. However, I hoped (yes I know indeed, hope is not a strategy) during the inplace upgrade, Windows will keep the drivers. However, the fact that all drivers still work, clearly shows that the driver architecture from Windows 7 to Windows 8 did not change at all. That’s good as manufacturers do not need to update drivers in a hurry based on a new architecture, but on the other side it shows that there are not that many improvements how Windows deals with the hardware. But again, maybe this is not necessary at all.
Before you upgrade to Windows 8, run a backup! I did so using Acronis True Image 2013. Even without thinking about drivers, I was not sure whether the upgrade process with Boot Camp on the machine will maybe brick my box. Also run a backup of you Mac OS partition using Time Machine.
Said that kids, please bear in mind, that this worked fine on my machine, and might fail on yours. Also there is probably no support from Apple for Boot Camp 4.0 running Windows 8.
Once you run through the purchase process (they accept credit card or PayPal), at one point after the download finished, the Windows Upgrade Assistant comes up with the following dialog:
Because you’ve waited for so long you are quite impatient and go straight for the first option because you think you can create the media later one… If done so, the Upgrade Assistant will install Windows 8. Eventually, there won’t be any option to create the media later on.
What now? If you just need the files, you can turn on hidden files in Windows Explorer (it’s now in the Ribbon). You will see a folder ESD on the root of your drive containing a Windows folder with the downloaded installation files. Go ahead and make a backup if required.
If you try to create an .iso file using the Upgrade Assistant again, you probably fail by getting the following result.
In case you still need (or just want) the .iso file, there is a way to obtain it. First of all, check your mail for the order confirmation of your Windows 8 copy. At the very top of the mail, you will find a link to download Windows again.
Following the link, you will download the Windows 8 Setup (windows8-setup.exe). Once started this will straight let you choose whether to install, download or to postpone the installation as seen above. Chose Install by creating a media and either choose to burn a DVD to to copy the files on a USB stick (3GB required, though).
You will be asked to choose the place where to save the .iso file, after which the download process starts immediately.
That’s all you have to do. Whether you have been impatient, clicked to fast, did not read carefully or just clicked ‘next’, ‘next’, ‘next’, there is still a way to get the .iso file afterwards.
If the upgrade really works from Windows XP up to Windows 7, Microsoft might be possible to shift many users to the next generation of Windows. While the price for previous Windows upgrades was quite high, many users kept their former version of Windows until they bought a new personal computer, obtaining a new OEM version of Windows.
Nowadays, computers used at homes definitely last longer than the average Windows life cycle and quite a lot personal computers outside in the wild might see at least two version of Windows until being replaced.
Therefore, personally I welcome this move by Microsoft, considering to upgrade even more than one of my licenses to the new Windows version. Even though, this might be a strategic move by Microsoft to keep market share, existing customers definitely gain by the relatively low prices by upgrading even from previous Windows version. This might be quite an advantage as one has to buy each and every Mac OS version on the way upgrading from previous versions.
After a recent data loss, I had to restore several backups from various sources. Unfortunately, some of these backups were made on a Windows Server 2003 machine. However, it seems that Windows 7 does not come with any possibility to restore these backups out of the box, though.
The Windows NT Backup – Restore Utility seems to be the solution for this issue. During installation you might get the notification to turn on Removable Storage Management – on Windows Vista.
However, this is one of the features not available in Windows 7 anymore. Fortunately, Microsoft did release another version of this tool for Windows 7. Even the tool itself is now called Windows NT Backup Restore Utility for Windows 7 and for Windows Server 2008 R2 you will find it only as Update for Windows 7 x64-based Systems (KB974674) on the Web – of course this would be the exactly what you are going to look for, yes?
Once downloaded the right bits and installed, you will see the familiar UI of the former backup tool.
Simply follow the Restore Wizard to access your old backups.
This will install the required adapters and devices. Do again a cd %windir%system32drivers and check for the First cd %windir%system32drivers, check for the file vmnetadapter.sys file.
After a reboot of the host system, the NAT settings for the VMware network adapters should work again. Switching to bridged mode will probably result in another message.
Reason for the message saying
The network bridge on device VMnet0 is not running. The virtual machine will not be able to communicate with the host or with other machines on your network.
Failed to connect virtual device Ethernet0.
might be the missing VMware Bridge Protocol on the according host network adapter.
Got to Network and Sharing Center and select Change adapter settings. Choose the network connection you want to use with your VMware network adapter, right-click, select Properties, Install, Service and finally Add. This will allow you to select the VMware Bridge Protocol. In case the entry is not listed, select Have Disk… and navigate to %ProgramFiles(x86)%VMwareVMware Workstation.
After installing the VMware Bridge Protocol restart the VMware Workstation and choose the bridged mode for the network adapter.
In this article I provide the final steps how to virtualize a Windows Server 2008 installation.
You probably run into the same problem that Windows Server 2008 won’t be able to recognize the virtual hard disk you have planned to installed it on. Get the corresponding SCSI drivers as floppy image from the VMware site. Select the image and connect the drive.
Now say ‘Browse‘ and choose drive ‘A:‘ – don’t forget: After selecting the .flp image you also have to connect the drive. Otherwise Windows cannot read the device.
Click on ‘Next‘ and after a few seconds the hard disk will be found. The currently available drivers for Windows Server 2003 seem to work fine also for Windows Server 2008.
Installing the VMware Tools might be a good idea. You can find the image at /usr/lib/vmware/isoimages/windows.iso or just install them from the VMware management console’s menu. While the image is mounted go to ‘Device Manager‘ and install the drivers for the network adapter which probably does not work yet.
In a previous post, I told about he first steps in virtualizing a Windows Server 2008. In this article I describe how to proceed after, the request for my own RIPE subnet was approved. Now I can concentrate on the next point: Installing VMware. Since I want to set up this machine for visualization, I have to perform a few steps first. That way, this post will be mostly about my fight with Debian Linux which is the host system.
After logging in, I just realize that updating the package database might be not the worst idea. Consequently, I do so and install some Norton Commander like tool for real men
apt-get install mc
This actually makes things much easier.
Now, I have to activate IP forwarding in /etc/sysctl.conf by the adding
and bringing the additional IP on the host system by adding
up ip add 192.168.1.1/29 dev eth0
to /etc/network/interfaces. Additionally, I have to add some host-route (by using my gateway 192.168.0.1) so my new subnet is reachable by adding
to eth0 in /etc/network/interfaces. Installing iproute by a
apt-get install iproute
restarting the interface by calling
finally makes my IP ping-able. Quite a fight so far if you don’t do this on a regular base. Additionally I installed the powersave package and reconfigured several settings to increase the performance in /etc/powersave.
I just got the tip to put my virtual machines to the separate disc. Since I have one spare 400GB disc. I have to create some partition and to format it.
cfdisk /dev/sdb mkfs -t ext3 /dev/sdb1
Let’s create some directory for the virtual machines and mount the disc
mkdir VMsmount -t ext3 /dev/sdb1 /Vms
Now some final tweak at /etc/fstab by adding
/dev/sdb1 /VMs et3 defaults 0 0
and I am done.
Finally I start installing the VM. I was pointed to some German How-To written by Till Brehm which is includes quite detailed instructions.
Some prerequisites are required before I start. I do the required 220 MB update by
VMware can be downloaded from http://www.vmware.com/download/server/. I skip the management console since I will use it on my Windows workstation and focus only on the server and management interface binaries using:
wget http://download3.vmware.com/... tar xvz VMware-server-*.tar.gz cd vmware-server-distrib ./vmware-install.pl
Now, I simply accept the defaults for the following installation. only at one point I had to tell the script that my virtual machines will be located at /VMs. No I have to continuing with the management interface
tar xvfz VMware-mui-*.tar.gz
The Web-based management interface seems to work perfectly after installing.
After installing the management console on Windows I run into some trouble. During compilation of the corresponding modules, the VMware script was not able to start the inetd service. Therefore, I was not able to connect to the VMware server. After restarting the service manually it worked perfectly and I set up my virtual machine.
Now, I have to copy the installation files for the Windows Server 2008.