Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with OpenID
Advertise on LowEndTalk.com

In this Discussion

Install Windows on any Wholesaleinternet preconfigured server using QEMU-KVM
New on LowEndTalk? Please read our 'Community Rules' by clicking on it in the right menu!

Install Windows on any Wholesaleinternet preconfigured server using QEMU-KVM

edanedan Member
edited April 2016 in Tutorials

WSI has Core2Duo box @ $10/month and they don't provide KVM services for their preconfigured server.

Preconfigured Servers Cannot be Modified: Our preconfigured servers are designed for quick deployment. Preconfigured servers hardware (CPU/RAM/HDD) or bandwidth cannot be added or modified. Operating system options for preconfigured systems are limited to available selections on order form. KVM services are not provided for preconfigured servers.

But WSI provide SystemRescueCD and we can install Windows or any other OS using QEMU but w/o KVM support. The Sysrcd lack of KVM module and it can only install 32 Bit OS (tested on WSI). Such a waste if we snap a preconfigured servers with more than 4GB RAM.

Previously I've asked them via their ticket system to add Grml https://grml.org/ (because of KVM module already enabled) and finally now they add it on their reload OS options, nice!

Start the Windows installation on WSI

First reload the OS and choose Grml. Open the SSH console using the password provided.

# CAREFULL Wipe your hard disks. Let say we want to install the Windows in /dev/sda

dd if=/dev/zero of=/dev/sda bs=1M count=1
partprobe

If you need temporary folder for the ISO. Need big RAM on this case. Depend on the ISO size.

mount -t tmpfs -o size=4000m tmpfs /mnt

Or if we have RAM less than 8GB we just need to creating small partition, put the ISO file there and don't touch it during Windows installations.

Note: My WSI $10 box have second HDD so just I put my ISO inside it.

Download the ISO to /mnt folder:

wget -P /mnt http://example.com/win8-64.iso

Download and extract the portable qemu-kvm. /tmp folder is enough for this portable qemu-kvm.

wget -qO- /tmp http://notfor.pro/content/files/vkvm.tar.gz | tar xvz -C /tmp

Excute the qemu-kvm:

/tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -enable-kvm -cpu host,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot once=d -vnc :1

Open the VNC viewer and visit your IP:1 to starting the installations.

Network and Driver

After finished, enable the RDP and turn-off the firewall temporary. You can add the network driver using:

pnputil.exe -a c\yourdriver.inf

Note: In my case Windows already have the driver but I still add the driver to the DriverStore .

WSI use static IP so we must set the IP provided by WSI manually. Example:

IP: 63.141.x.x
Gateway: 63.141.x.x
Subnet Mask: 255.255.255.252

And we need to use DNS server provided by WSI also. Pick one below.

# First DNS server
192.187.107.16
69.30.209.16

# Second DNS server
208.67.220.220
208.67.222.222

This is what the support staff tell me when I can't connect even I already enable the RDP, install the network driver, and turn-off the firewall temporarily but I am enabling the DHCP.

Those are the DNS we set, once the service is online the client can change them to whatever they wish to use. 

Double check everything and reboot your server.

Troubleshot

Qemu can boot existing Windows installations so you just need to load the Grml, extract the portable qemu-KVM and reconfigure the Windows again.

/tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -enable-kvm -cpu host,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot c -vnc :1

If you can't connect to RDP you can creating netsh script to set the static IP automatically during startup or logon.

Credit to WSI

WSI staff is very helpful on this process, from debugging, even they are willing to add Grml because of SystemRescueCD limitations.

How about another provider

You can use the same method on any other provider out there as long as they have rescue system. Eg. OVH (SYS, Kimsufi), Hetzner, Leaseweb, etc.

DigitalOcean seems have recovery ISO so perhaps you can install Windows on their VPS lineup. Let me know if you managed to install Windows on DigitalOcean.

[Source]

Edit: hope they get more sales because they are very helpful on this process :)

Tagged:
«1

Comments

  • A question, and thanks for the tutorial.

    All of these preconfigured servers, don't have KVM access, but have some kind of rescue mode, or OS reinstall functions?

  • edanedan Member
    edited April 2016

    @yomero said: A question, and thanks for the tutorial.

    All of these preconfigured servers, don't have KVM access, but have some kind of rescue mode, or OS reinstall functions?

    Yes they have rescue mode, they have two type SystemRescueCD (KVM disabled) and Grml (KVM enabled) so pick the Grml.

    And now WSI is limitless.

    Thanked by 1yomero
  • I am using libvirtd and qemu-kvm on Centos then install Windows on top. Is your method more efficient than this approach?

  • edanedan Member

    @david_W said: I am using libvirtd and qemu-kvm on Centos then install Windows on top. Is your method more efficient than this approach?

    Well yes and its more faster of course.

  • @edan said: Well yes and its more faster of course.

    Faster in terms of performance? According to my understanding, the method you posted still running Windows within KVM. May be Grml has less overhead than CentOS minimal?

  • edanedan Member

    @david_W said:

    @edan said: Well yes and its more faster of course.

    Faster in terms of performance? According to my understanding, the method you posted still running Windows within KVM. May be Grml has less overhead than CentOS minimal?

    No its installed directly to the box (bare metal sever). Grml is just to install the Windows.

  • @edan said: No its installed directly to the box (bare metal sever). Grml is just to install the Windows.

    Ah, I get it now, KVM is for running the Windows PE and have VNC access.

    Formatting my idle C2D box now xD

    /tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -enable-kvm -cpu host,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot once=d -vnc :1
    
  • edanedan Member
    edited April 2016

    david_W said: Ah, I get it now, KVM is for running the Windows PE and have VNC access.

    Formatting my idle C2D box now xD

    And now I am running Windows in my $10 box. Its Dell Optiplex 760 :)

    Thanked by 1netomx
  • Thank you for sharing this, the awesome folks at verelox now have this as well in their cp.

    Thanked by 1Verelox
  • edanedan Member

    @raptorpeanutbuttr said: Thank you for sharing this, the awesome folks at verelox now have this as well in their cp.

    It more faster to install using this method compared to using virtual media in iDRAC, ILO etc.

    Most provider use DHCP, tested on OVH (SYS, Kimsufi) and Online.net so we don't need to configure the static IP. We just need to enable the RDP and disable the firewall temporarily. Please note when enabling the firewall don't use the "Use recommended settings" because sometimes it block the RDP again but visit the "Turn Windows Firewall on or off" and enable it from there.

  • RodneyRodney Member

    edan said: Eg. OVH (SYS, Kimsufi), Hetzner, Leaseweb, etc.

    Hetzner offers KVM for free for 2 hours (or longer if the device is not needed elsewhere or you're willing to pay) so you could use that. They also have windows ISOs available for mounting. I don't think a Windows installation should take longer than an hour so that's probably the easiest method of installing windows with your own license.

  • edanedan Member

    Rodney said: Hetzner offers KVM for free for 2 hours (or longer if the device is not needed elsewhere or you're willing to pay) so you could use that. They also have windows ISOs available for mounting. I don't think a Windows installation should take longer than an hour so that's probably the easiest method of installing windows with your own license.

    Yes the easiest is using KVM over IP. I also use that method in the past but it still slower when mapped the virtual media. Let say the ISO file size is 3.5GB and with home connections 10mbps for download and upload 1mbps it can take aged (not every people have 100mbps+ upload speed). Sometimes I use KVM over IP if I can't connect to RDP and fix the problems (missing the network driver etc.).

    On my case I put the ISO in my other machine with 1Gbps connections so using wget to download the ISO it only take minutes.

  • RodneyRodney Member

    If they have the ISO on their Samba share you can just use that. (They have Windows, ESXi and some Linux distros)

  • spammyspammy Member

    I tried to launch the QEMU and got this:

    Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory

    Any idea?

  • FredQcFredQc Member

    I don't see Grml in the reload list ?

  • edanedan Member
    edited May 2016

    @spammy said: I tried to launch the QEMU and got this:

    Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory

    Any idea?

    So you are using SystemRescueCD. Remove the

    -enable-kvm

    And change the cpu options to use qemu32 or qemu64, the -cpu host options only available if KVM module loaded.

    So it should:

    /tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -cpu qemu32,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot once=d -vnc :1
    

    FredQc said: I don't see Grml in the reload list ?

    Yes seems only available in my account. Here is their reply about it:

    We don't use dhcp servers. All of our ips have to be statically set. So if you decide to use qemu to reload an OS how exactly are you planning on setting the ip addresses, because while you are in QEMU your network adapter is a virtualized network adapter, if you set the ip addresses on this virtualized network adapter the changes won't stick when you reboot into the real OS because it will be a new adapter (the real physical network adapter).

    I really don't want to enable something for everyone until this is fixed, because we will have a lot of people who install windows and will then ask us to fix their network settings.

    While in QEMU actually you will find the network adapter name, eg. "Ethernet". We can creating netsh scripts during logon, if Ethernet belong to QEMU than our real adapter usually Ethernet 2, if you are not sure you can add multiple ethernet name. Delete the scripts after we can connect to RDP.

    netsh interface ipv4 set address name="Ethernet 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    
    netsh interface ipv4 set dns name="Ethernet 2" static 192.187.107.16
    
    netsh interface ipv4 add dns name="Ethernet 2" 69.30.209.16 index=2 
    
  • spammyspammy Member

    edan said: So you are using SystemRescueCD.

    Thanks for your help, nope I am using the grml though (2014.11, is that the version you have)? Not sure why KVM is not enabled.

    I will try to use the sysrescue to see if I can get any luck there.

  • tyktyk Member

    Hi, What's the difference between this way and directly use qemu install windows on Debian?

  • spammyspammy Member

    @tyk said: Hi, What's the difference between this way and directly use qemu install windows on Debian?

    If you read a few posts above the answer is right there:

    https://www.lowendtalk.com/discussion/comment/1662407/#Comment_1662407

  • spammyspammy Member

    edan said: So it should:

    /tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -cpu qemu32,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot once=d -vnc :1

    I can confirm this works, happily installing Windows now :)

  • _Nic_Nic Member

    Can I use this way for custom Linux installation (manual disks partitions configuration) with Linux netinstall .iso?

  • edanedan Member

    spammy said: Thanks for your help, nope I am using the grml though (2014.11, is that the version you have)? Not sure why KVM is not enabled.

    Is the CPU support virtualization? if yes than its weird.

    Please run:

    /tmp/kvm-ok

    spammy said: I can confirm this works, happily installing Windows now :)

    I am using task scheduler to setup the static IP.

    _Nic said: Can I use this way for custom Linux installation (manual disks partitions configuration) with Linux netinstall .iso?

    Yes, you can to install any OS actually.

    Thanked by 1_Nic
  • isalemisalem Member
    edited May 2016

    aaah ... my E6550 supports Virtualization, but i found out its disabled in the bios .. i'm guessing i'll have to go the other way then without it

    Unless someone knows a way to enable it without the need to go there? :P

    EDIT: Nevermind, a ticket to support quickly solved this! Punching through setup now, thanks! :)

  • edanedan Member

    isalem said: EDIT: Nevermind, a ticket to support quickly solved this! Punching through setup now, thanks! :)

    Bingo! :)

  • spammyspammy Member

    @edan said:

    spammy said: I can confirm this works, happily installing Windows now :)

    I am using task scheduler to setup the static IP.

    Sorry to bring this thread up again, but may I know why you need to do that? Can you just set static IPs in the IPv4 configuration in Windows and static DNS as well?

    The reason why I am asking is I have this weird issue that when I boot up through QEMU everything works fine, I was able to log into the server through VNC viewer and the internet works.

    Once I set up the static IP the connection is lost to the Internet (however I can still see Windows in the VNC viewer), however when I reboot the server just never come back up. I have enabled ping and RDP but it doesn't respond to ping nor RDP.

    Tried it no less than 10 times so far with no luck :(

  • edanedan Member
    edited May 2016

    spammy said: Sorry to bring this thread up again, but may I know why you need to do that? Can you just set static IPs in the IPv4 configuration in Windows and static DNS as well?

    The reason why I am asking is I have this weird issue that when I boot up through QEMU everything works fine, I was able to log into the server through VNC viewer and the internet works.

    Once I set up the static IP the connection is lost to the Internet (however I can still see Windows in the VNC viewer), however when I reboot the server just never come back up. I have enabled ping and RDP but it doesn't respond to ping nor RDP.

    Tried it no less than 10 times so far with no luck :(

    What is your network interface name when in QEMU? eg. Ethernet. If Ethernet belong to QEMU usually when we booting the real HW it become Ethernet 2 or Ethernet 3 than you can creating netsh scripts and set the static IP during logon/startup for this network device name, I am using task scheduler. Example scripts:

    netsh interface ipv4 set address name="Ethernet 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    
    netsh interface ipv4 set dns name="Ethernet 2" static 192.187.107.16
    
    netsh interface ipv4 add dns name="Ethernet 2" 69.30.209.16 index=2 

    The IP address order: client IP, subnet mask, and gateway IP.

    You can try to use similar step with this http://www.howtogeek.com/138159/how-to-enable-programs-and-custom-scripts-to-run-at-boot/ make sure to execute the scripts again if it fails "if the tasks fails, restart every" under settings

    Thanked by 1spammy
  • spammyspammy Member

    @edan said:

    You can try to use similar step with this http://www.howtogeek.com/138159/how-to-enable-programs-and-custom-scripts-to-run-at-boot/ make sure to execute the scripts again if it fails "if the tasks fails, restart every" under settings

    Another question, is there any way to get the VNC to work on PC rather than tablet? I changed the VNC to -usbdevice mouse but for some reason when I used the VNCViewer on PC the program gets disconnected after a second, tried it on multiple PC and both RealVNC and RoyalTS as well.

    It works perfect on my tablet though, just using tablet as a device to edit scripts and so on might not be the easiest thing in the world.

  • edanedan Member
    edited May 2016

    spammy said: Another question, is there any way to get the VNC to work on PC rather than tablet?

    I don't think any differences between PC vs tablet, I found zero problems when connected to the VNC using PC (TightVNC).

    Thanked by 1spammy
  • pepijndpepijnd Member
    edited June 2016

    @spammy said:

    @edan said:

    You can try to use similar step with this http://www.howtogeek.com/138159/how-to-enable-programs-and-custom-scripts-to-run-at-boot/ make sure to execute the scripts again if it fails "if the tasks fails, restart every" under settings

    Another question, is there any way to get the VNC to work on PC rather than tablet? I changed the VNC to -usbdevice mouse but for some reason when I used the VNCViewer on PC the program gets disconnected after a second, tried it on multiple PC and both RealVNC and RoyalTS as well.

    It works perfect on my tablet though, just using tablet as a device to edit scripts and so on might not be the easiest thing in the world.

    Also had some problems with VNC. Try to use TightVNC. If port 1 doesn't work, try 5901. (I use port 1 on the command line and 5901 in TightVNC. I don't know why it works.)

    Edit: Tested on Kimsufi KS-4C and it works fine.

    Thanked by 1spammy
  • emre22emre22 Member

    for me it works only with 512 ram only and during the vnc installation at "windows is starting" my vnc viewer -> connection gracefully closed

    can somebody help me out with that?

  • edanedan Member
    edited June 2016

    @emre22 said: for me it works only with 512 ram only and during the vnc installation at "windows is starting" my vnc viewer -> connection gracefully closed

    can somebody help me out with that?

    This because you are putting the ISO in RAM. You need at least 8GB RAM if you doing this.

    You can try to creating partition for the ISO using fdisk http://www.howtogeek.com/106873/how-to-use-fdisk-to-manage-partitions-on-linux/ try to creating 2 partitions and put your ISO in partitions 2. If you have 250GB disk, partition 1 -> 200GB, partition 2 -> 50GB. Make sure to format your second partition using mkfs.ext4 and mount it.

    Edit: regarding partitions you can even creating 1 partition and leave other space as unallocated space, Windows setup will do the rest.

    Thanked by 2emre22 WalrusBug
  • emre22emre22 Member

    well I got now a second hdd on my server. how can I download the iso to the second one?

  • edanedan Member
    edited June 2016

    @emre22 said: well I got now a second hdd on my server. how can I download the iso to the second one?

    Format those drive and mount it to /mnt folder.

    Edit: Google it for more info.

  • VereloxVerelox Member, Provider

    @emre22 said: well I got now a second hdd on my server. how can I download the iso to the second one?

    edan said: Format those drive and mount it to /mnt folder.

    Here are the commands for this, assuming that the secondary drive is at /dev/sdb (execute fdisk -l to make sure):

    dd if=/dev/zero of=/dev/sdb bs=1M count=1 #Wipe /dev/sdb, this will erase all data and partitions
    
    mkfs.ext4 /dev/sdb #Format the partition to ext4
    mount /dev/sdb /mnt #Mount /dev/sdb to /mnt
    

    You can download the ISO and store it at /mnt afterwards, which would store it on your second HDD:

    wget -O /mnt/file.iso http://urltoiso.tld/file.iso
    
    Thanked by 2edan emre22
  • I have read your tutorial about WSI install windows,I have a C2D E8200 and installed windows server 2003 successfully and using a script to set the network to static IP,but it doesn't work after reboot.What should I do?

  • edanedan Member

    @wenxhwork said: I have read your tutorial about WSI install windows,I have a C2D E8200 and installed windows server 2003 successfully and using a script to set the network to static IP,but it doesn't work after reboot.What should I do?

    What is your network interface on QEMU? make sure its match. You can write multi line with multiple network interface name.

    netsh interface ipv4 set address name="Ethernet 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    
    netsh interface ipv4 set dns name="Ethernet 2" static 192.187.107.16
    
    netsh interface ipv4 add dns name="Ethernet 2" 69.30.209.16 index=2 
    
    netsh interface ipv4 set address name="Ethernet 3" static 63.141.x.x 255.255.255.252 63.141.x.x
    
    netsh interface ipv4 set dns name="Ethernet 3" static 192.187.107.16
    
    netsh interface ipv4 add dns name="Ethernet 3" 69.30.209.16 index=2
  • edan said: a

    @edan said:

    @wenxhwork said: I have read your tutorial about WSI install windows,I have a C2D E8200 and installed windows server 2003 successfully and using a script to set the network to static IP,but it doesn't work after reboot.What should I do?

    What is your network interface on QEMU? make sure its match. You can write multi line with multiple network interface name.

    netsh interface ipv4 set address name="Ethernet 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    > 
    > netsh interface ipv4 set dns name="Ethernet 2" static 192.187.107.16
    > 
    > netsh interface ipv4 add dns name="Ethernet 2" 69.30.209.16 index=2 
    > 
    > netsh interface ipv4 set address name="Ethernet 3" static 63.141.x.x 255.255.255.252 63.141.x.x
    > 
    > netsh interface ipv4 set dns name="Ethernet 3" static 192.187.107.16
    > 
    > netsh interface ipv4 add dns name="Ethernet 3" 69.30.209.16 index=2

    In QEMU it shows Inter(R) PRO/1000 MT Network Connection,and in Grml it's Qualcomm Atheros AR8131

    I added Ethernet2 & 3 just now and reboot but still failed to ping and connect RDP.

  • edanedan Member

    wenxhwork said: In QEMU it shows Inter(R) PRO/1000 MT Network Connection,and in Grml it's Qualcomm Atheros AR8131 I added Ethernet2 & 3 just now and reboot but still failed to ping and connect RDP.

    No I mean the network interface name under "Network Connectons".

  • edan said: /tmp/qemu-system-x86_64 -net nic -net user,hostfwd=tcp::3389-:3389 -m 2048M -localtime -enable-kvm -cpu host,+nx -M pc -smp 2 -vga std -usbdevice tablet -k en-us -cdrom /mnt/win8-64.iso -hda /dev/sda -boot once=d -vnc :1

    @edan said:

    wenxhwork said: In QEMU it shows Inter(R) PRO/1000 MT Network Connection,and in Grml it's Qualcomm Atheros AR8131 I added Ethernet2 & 3 just now and reboot but still failed to ping and connect RDP.

    No I mean the network interface name under "Network Connectons".

    I noticed it called Local Area Connection,and I tried to add a new connection called Ethernet but failed.

  • edanedan Member

    wenxhwork said: I noticed it called Local Area Connection,and I tried to add a new connection called Ethernet but failed.

    It should named:

    netsh interface ipv4 set address name="Local Area Connection 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    
    netsh interface ipv4 set dns name="Local Area Connection 2" static 192.187.107.16
    
    netsh interface ipv4 add dns name="Local Area Connection 2" 69.30.209.16 index=2 
    

    And so on.

  • @edan said:

    wenxhwork said: I noticed it called Local Area Connection,and I tried to add a new connection called Ethernet but failed.

    It should named:

    netsh interface ipv4 set address name="Local Area Connection 2" static 63.141.x.x 255.255.255.252 63.141.x.x
    > 
    > netsh interface ipv4 set dns name="Local Area Connection 2" static 192.187.107.16
    > 
    > netsh interface ipv4 add dns name="Local Area Connection 2" 69.30.209.16 index=2 
    > 

    And so on.

    I tried but still failed. Does it the problem of the driver? 2003 doesn't have the driver of Atheros AR8131? I tried to install 8131 driver via VNC but it says no device found. BTW,how can you install win8-64? I loaded the iso but failed,showing can't allocated memory.

  • netomxnetomx Member

    Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

  • @netomx said: Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

    That's cool but it's not that easy for me,I've been trying for days,still failed :'(

  • netomxnetomx Member

    @wenxhwork said:

    @netomx said: Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

    That's cool but it's not that easy for me,I've been trying for days,still failed :'(

    Tell us your error, then. Maybe we can help :)

  • @netomx said:

    @wenxhwork said:

    @netomx said: Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

    That's cool but it's not that easy for me,I've been trying for days,still failed :'(

    Tell us your error, then. Maybe we can help :)

    The problem is that the server can't be online once after reboot. I did all the things,using script to change IP,close firewall and enable RDP,but still failed. I used QEMU to recheck the script and sure that the script works. And it's hard to debug because I don't know where to find error logs.

  • edanedan Member

    wenxhwork said: I tried but still failed. Does it the problem of the driver? 2003 doesn't have the driver of Atheros AR8131? I tried to install 8131 driver via VNC but it says no device found.

    For driver using pnputil:

    pnputil.exe -a c\yourdriver.inf

    BTW,how can you install win8-64? I loaded the iso but failed,showing can't allocated memory.

    Read this comments https://www.lowendtalk.com/discussion/comment/1726797/#Comment_1726797

    Do you use task scheduler?

    @netomx said: Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

    Ask them to add free additional HDD so becomes 2 x 250GB (Soft Raid 1)

    Well C2D CPU, 4GB RAM, 2 x250GB @ $10/m for US dedicated server is so da** cheap :)

    Thanked by 1netomx
  • netomxnetomx Member

    wenxhwork said: The problem is that the server can't be online once after reboot. I did all the things,using script to change IP,close firewall and enable RDP,but still failed. I used QEMU to recheck the script and sure that the script works. And it's hard to debug because I don't know where to find error logs.

    first of all, PLEASE do NOT use 2003! It is EOL. It seems the problem is with your network driver, pal.

  • @edan said:

    wenxhwork said: I tried but still failed. Does it the problem of the driver? 2003 doesn't have the driver of Atheros AR8131? I tried to install 8131 driver via VNC but it says no device found.

    For driver using pnputil:

    pnputil.exe -a c\yourdriver.inf

    BTW,how can you install win8-64? I loaded the iso but failed,showing can't allocated memory.

    Read this comments https://www.lowendtalk.com/discussion/comment/1726797/#Comment_1726797

    Do you use task scheduler?

    @netomx said: Bravo @edan . Kudos for you! $10 for a Win dedi sounds very nice!

    Ask them to add free additional HDD so becomes 2 x 250GB (Soft Raid 1)

    Well C2D CPU, 4GB RAM, 2 x250GB @ $10/m for US dedicated server is so da** cheap :)

    Thanks,I'll try again

  • @netomx said:

    wenxhwork said: The problem is that the server can't be online once after reboot. I did all the things,using script to change IP,close firewall and enable RDP,but still failed. I used QEMU to recheck the script and sure that the script works. And it's hard to debug because I don't know where to find error logs.

    first of all, PLEASE do NOT use 2003! It is EOL. It seems the problem is with your network driver, pal.

    But I can't install win8 or server 2008 due to memory allocate problem,I'll try again once the another HDD is installed.

Sign In or Register to comment.