Nowadays there is a big gap between developers and infrastructure operations. The problem is that they exist in two different worlds. They use different terminology and approaches, have distinctive strategies and goals, varying sets of knowledge, and even a different mindset. How can we work together like this, and who can join us?
We should all think not only in terms of our technical field, but also about the people we are doing this for. Customers don’t just require a solution itself. They also need to support and monitor this solution, manage it, integrate it with existing solutions and data flows, deploy new instances and restore failed ones. When a solution contains a number of components that can run on various servers and be moved from one to another, there is a lifesaving property that should be provided – the system should be self-descriptive. In other words, it should provide some interface to track its state and components in an easy way.
How can we achieve this? Here are some ideas and technologies to use for developers who want to do something really great.
Continue reading “Support Manifesto”
On the MS Ignite new thing, Nano Server was announced. The idea is to get smallest footprint for the Windows Server ever. Now it is possible to try it. In general it is quite straightforward. First you need to download the technical preview of new Server from here. “There you will find the gate to hell, opened before you. You must find the courage to step through that gate …” (c) oops ). No, not that bad.
After you have downloaded the image you can mount it and find a folder called NanoServer. There will be the wim image of the server and some additional folder with packages wich can be additionally added to the new installation. Next you need to follow the link here and read the documentation. What I did is just wrapped the doc into a small script which shows the steps in brief
$dism = "D:\temp\NewDism\dism.exe"
$imageFile = "D:\VMs\Virtual Hard Disks\nanoServerBaseLine2.vhd"
$mountDir = "D:\temp\mountdir"
$convert = "D:\Temp\Convert-WindowsImage.ps1"
& $convert -SourcePath E:\NanoServer\NanoServer.wim -VHDPath $imageFile -VHDFormat VHD -Edition 1
& $dism /Mount-Image /ImageFile:$imageFile /Index:1 /MountDir:$mountDir
& $dism /Add-Package /PackagePath:E:\NanoServer\Packages\Microsoft-NanoServer-Guest-Package.cab /Image:$mountdir
& $dism /Image:$mountdir /Apply-Unattend:D:\VMs\Unattend.xml
copy D:\VMs\Unattend.xml $mountDir\Windows\panther
& $dism /Unmount-Image /MountDir:$mountdir /Commit
New-VM –Name testNanoVM –MemoryStartupBytes 1GB –VHDPath $imageFile -SwitchName Internal | Start-VM
Hey, here is a great stuff out there. This script is able, so to speak, to convert an ISO file into VHD(x) file, that can be easily attached to the VM. Basically you take ISO, convert it, attach VHD to a Vm and voila, you are done. So what to do to achieve this? Easy, just download the script! And after that just:
.\Convert-WindowsImage.ps1 -source D:\X64FRE_SERVER_EVAL.ISO `
-Edition ServerDataCenterEval -VHDPath 'D:\VMs\Virtual Hard Disks\CONTOSO-DC1.vhdx' `
-VHDFormat vhdx -VHDPartitionStyle GPT