new kimsufi and own iso or windows 180 days license

Status
Not open for further replies.
3 comments
ok sc74 wrote this tutorial
The way to install windows is quite simple, you just need to install the proxmox OS, create a VM (KVM) and then install Windows as normal. Finally since the server has an ipv4 limitation you need to setup an internal lan ip and route external ports to it (for control through remote desktop or VNC or whatever you want to use). It's quite straight forward to setup external internet access for the Windows KVM vps you create since you can just follow the instructions here: OVH : Proxmox under the section "create a vm nat".So to begin with... install VPS Proxmox VE 3.1 (64bits) on your kimsufi control panel. Now login with ssh / putty to your kimsufi server. Once in go to the folder
/var/lib/vz/template/iso/
and either upload or wget your Windows Server (or other OS) template iso into that folder. For mine, I registered for the 180 day Windows Server 2008 license and used wget to download the iso direct from the Microsoft site. You'll also want to download the virtuo drivers ISO which at the time of writing can be found at:
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-74.iso
Ok so that's the iso's done.
Now before making the VM you'll want to create the vmbr2 bridge as per the tutorial at OVH. It's quite straightforward if you just edit using vi or nano the file
/etc/network/interfaces
and add to the bottom:
auto vmbr2
iface vmbr2 inet static
address 192.168.0.254
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
Now do this in ssh to bring the bridge up:
ifup vmbr2
This will create a virtual LAN you can use to assign IP's to your Windows (or other KVM OS) system. You can assign any ip within 192.168.0.1 - 192.168.0.253.
Ok so the next thing is to create your Windows KVM.
Login to your proxmox control panel at: https://your.ip:8006, and login with your root user and password. Now go to "create VM". Assign it whatever VPSID you want, now go to the next tab (OS) and select win2k8. Next go to CD/DVD and select the windows ISO image you uploaded earlier (not the virtuo drivers one yet!). Next comes the hard disk, set the BUS to VIRTIO and also set the disk size to whatever size you want it to be, everything else can be left as default. Now go to CPU and set the number of CPU Cores you want the Windows KVM to have access to, sockets should almost always be 1. Be sure to set the Type to "host" as well, so your Windows KVM has full access to your CPU's extensions. Next go to memory and set the amount of ram you want Windows to have (I recommend at least 1.5GB).
This next bit is important, go to the network tab and select your bridge as vmbr2 (the one you created earlier) and set the model to VIRTIO. Finally, confirm and finish. Now once it's made go find it under the node section on the left (under datacenter) and click on it, then start it up (top right). Open up console (requires java, say yes to all the pop ups or try different internet browser if it doesn't load properly).
Now to get the best drivers (VIRTIO) working you'll need to switch over the ISO your using mid installation (it won't find your HDD until you install the virtuo drivers during the Windows install). You can switch the ISO by going to the Hardware tab under your KVM in proxmox and selecting CD/DVD Drive then going back to console and refreshing on the select HDD screen of the windows install. Now to install the drivers you'll need to go to load drivers (in the console / install window) and select your ISO / Virtual Disc, open it up and choose Windows 7 / amd64 and it should find 3 drivers for you. select and install them / click next. Now switch back to your Win2k8 ISO or whatever windows version your installing, and continue the install as normal.
Once the install is done, you just need to edit your network settings to assign your KVM a private ip. This is done by going to your desktop in console (once installed and rebooted) and finding > networking and sharing center > local area connection > properties > click TCP IPv4 > click properties. Now assign your Windows KVM a private ip selecting use the following IP address and inputting (for example - use whatever ip you want in the range discussed earlier):
ip : 192.168.0.1
subnet mask 255.255.255.0
gateway : 192.168.0.254 (ip vmbr2 on the host)
DNS: 8.8.8.8 and 8.8.4.4 (or whatever DNS you want to use, this is googles)
Click ok > ok > then close. You server should now have outside connectivity to the internet!!!
Ok so now you need to enable remote desktop in your firewall (should be easy enough to do if you know the OS well enough) and also set remote desktop to being on, you can do the latter part by going to Control Panel > system and security > system > remote settings > and allow remote desktop connections (more or less secure version) whichever you prefer.
Right, finally you'll want access to your Windows KVM desktop via remote desktop (since console is slow and not very good). To do this just login to your kimsufi server by SSH and enter the following as root:
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 3389 -j DNAT --to 192.168.0.1:3389
(ASSUMING your using the ip 192.168.0.1, if not changed the ip above to yours).
You should now have access to the Windows KVM from your pc over the default Remote desktop port of 3389 using the internet ip of your kimsufi server (the one OVH gave you not the 192.168 ip).
 
Hi,
The easiest way to install windows on a OVH/Kimsufi dedicated server is to use the OVH Panel inbuilt windows installation feature.
Just use one of the following keys (corresponding to your desired windows os version) and add them in OVH panel as a SPLA license.
After than perform the installation directly from OVH Panel and once done, remove the key from ovh panel and you will get a unactivated genuine windows installed, :)


[h=2]Windows Server 2012 R2 and Windows 8.1 Client Setup Keys
[/h][h=3][/h]
Operating system editionKMS Client Setup Key
Windows 8.1 Professional
GCRJD-8NW9H-F2CDX-CCM8D-9D6T9
Windows 8.1 Professional N
HMCNV-VVBFX-7HMBH-CTY9B-B4FXY
Windows 8.1 Enterprise
MHF9N-XY6XB-WVXMC-BTDCT-MKKG7
Windows 8.1 Enterprise N
TT4HM-HN7YT-62K67-RGRQJ-JFFXW
Windows Server 2012 R2 Server Standard
D2N9P-3P6X9-2R39C-7RTCD-MDVJX
Windows Server 2012 R2 Datacenter
W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9
Windows Server 2012 R2 Essentials
KNC87-3J2TX-XB4WP-VCPJV-M4FWM


[h=2]Windows Server 2012 and Windows 8 Client Setup Keys
[/h][h=3][/h]
Operating system editionKMS Client Setup Key
Windows 8 Professional
NG4HW-VH26C-733KW-K6F98-J8CK4
Windows 8 Professional N
XCVCF-2NXM9-723PB-MHCB7-2RYQQ
Windows 8 Enterprise
32JNW-9KQ84-P47T8-D8GGY-CWCK7
Windows 8 Enterprise N
JMNMF-RHW7P-DMY6X-RF3DR-X2BQT
Windows Server 2012
BN3D2-R7TKB-3YPBD-8DRP2-27GG4
Windows Server 2012 N
8N2M2-HWPGY-7PGT9-HGDD8-GVGGY
Windows Server 2012 Single Language
2WN2H-YGCQR-KFX6K-CD6TF-84YXQ
Windows Server 2012 Country Specific
4K36P-JN4VD-GDC6V-KDT89-DYFKP
Windows Server 2012 Server Standard
XC9B7-NBPP2-83J2H-RHMBY-92BT4
Windows Server 2012 MultiPoint Standard
HM7DN-YVMH3-46JC3-XYTG7-CYQJJ
Windows Server 2012 MultiPoint Premium
XNH6W-2V9GX-RGJ4K-Y8X6F-QGJ2G
Windows Server 2012 Datacenter
48HP8-DN98B-MYWDG-T2DCC-8W83P


[h=2]Windows 7 and Windows Server 2008 R2
[/h][h=3][/h]
Operating system editionKMS Client Setup Key
Windows 7 Professional
FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Windows 7 Professional N
MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Windows 7 Professional E
W82YF-2Q76Y-63HXB-FGJG9-GF7QX
Windows 7 Enterprise
33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows 7 Enterprise N
YDRBP-3D83W-TY26F-D46B2-XCKRJ
Windows 7 Enterprise E
C29WB-22CC8-VJ326-GHFJW-H9DH4
Windows Server 2008 R2 Web
6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Windows Server 2008 R2 HPC edition
TT8MH-CG224-D3D7Q-498W2-9QCTX
Windows Server 2008 R2 Standard
YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise
489J6-VHDMP-X63PK-3K798-CPX3Y
Windows Server 2008 R2 Datacenter
74YFP-3QFB3-KQT8W-PMXWJ-7M648
Windows Server 2008 R2 for Itanium-based Systems
GT63C-RJFQ3-4GMB6-BRFB9-CB83V


[h=2]Windows Vista and Windows Server 2008
[/h][h=3][/h]
Operating system editionKMS Client Setup Key
Windows Vista Business
YFKBB-PQJJV-G996G-VWGXY-2V3X8
Windows Vista Business N
HMBQG-8H2RH-C77VX-27R82-VMQBT
Windows Vista Enterprise
VKK3X-68KWM-X2YGT-QR4M6-4BWMV
Windows Vista Enterprise N
VTC42-BM838-43QHV-84HX6-XJXKV
Windows Web Server 2008
WYR28-R7TFJ-3X2YQ-YCY4H-M249D
Windows Server 2008 Standard
TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Standard without Hyper-V
W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
Windows Server 2008 Enterprise
YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 Enterprise without Hyper-V
39BXF-X8Q23-P2WWT-38T2F-G3FPG
Windows Server 2008 HPC
RCTX3-KWVHP-BR6TB-RB6DM-6X7HP
Windows Server 2008 Datacenter
7M67G-PC374-GR742-YH8V4-TCBY3
Windows Server 2008 Datacenter without Hyper-V
22XQ2-VRXRG-P8D42-K34TD-G3QQC
Windows Server 2008 for Itanium-Based Systems
4DWFP-JF3DJ-B7DTH-78FJB-PDRHK




 
Status
Not open for further replies.
Back
Top