10 years for me lol

InstaBlaster...

i will try

Because windos3 sucks, you can only rent it forever, Linux: living without the pimps

You need proper hardware for that (which is only worth the cost, if you make around 200k a month or so). iSCSI isn't designed for sharing, ISCSI in fact isn't a share and there is no communication between clients and server. As soon as multiple clients write data to it, each client overwrites data that others wrote and data gets corrupted easily from that, so server would have to be able to monitor what each client writes to prevent that. Needles to say, hardware that can do that, doesn't come cheap

@@Kilzu1 I already found a solution and it's not ISCSI

@@rachserg please share

@@rexsovelllejes9383 CGRU - AFANASY

Update the bios/firmware of your computer and nic. Also make sure you aren't blocking anything firewall wise for the ports it would need to work. I use to have issues like that with WDS and it was usually the Nic or nic driver. Alternatively you could try a usb nic (or another kind) and try to boot off it.

@@kristopherleslie8343 thanks. Already disabled firewall. Will try USB nic.

I have the same issue and I think its due to my client pcs having a Realtek Inbuilt nic and the Image does not have the drivers for it. Does anyone know how to install the drivers for other NICs prior to booting?

No problem

Yes you can. I use ccboot. Having 64 clients on one server

@@vincem.exclusive9151 that's with ccboot, this method only works with one computer being booted because of a lack of a write back file

You are genius! Thank you for detailed information :) can u help me to slove biggest quistion for me? Are Cloud Computer really is installed on cloud`s?

Did you maneged to find a solution?

1. Boot this image using Hyper-V or any VM software which supports VHDX image. 2. Install any kind of software you need. 3. Disable "fast startup" in control panel and shutdown the VM. 4. Use this modified VHDX to boot yout diskless system.

Thanks

no

A tradução é automática. Culpa do KZfaq e não do produtor de conteúdo.

Yes there is a limit of users and yes, you can use it in a company. Firstly you need server motherboard with EEC RAM support and enough ECC RAM (iSCSI blocks get data corruptions quite easily when there are more than 1 computer writing data to it, more simultaneous connections there is, more likely some data will corrupt and amount of RAM basically also plays a part, since all data will be written to cache first, then to drives or sent to clients for faster response) and CPU with enough power (basically any intel XEON or AMD Ryzen 5000 or EPYC CPU with ECC support, ECC RAM is a must, unbuffered non-ecc ram has 0 tolerance towards data corruption and memory errors). Secondly you need SAS controller and either SAS or SATA drives. SAS drives have maximum transfer speed around 1.5 GB/s (12Gb/s and here RAM is important, most SAS drives buffer gets filled in less than 0.5 seconds) and tolerates well simultaneous reads and writes, SATA has maximum of 750 MB/s (6Gb/s) and tolerates better either read or write but not both at the same time which is why you should use slow, but durable SATA NAS drives. It is recommended to use SAS controller, but SATA and SAS drives are completely optional. You also need enough storage space for it, if you plan to use it for booting, then 60GB * x computers is minimum I would go for (later about this), now for apps and such, you really need to think how much storage is required in total and split it between each computer and leave bit of headroom. Thirdly you need network card which supports iSCSI Storage over Ethernet technology (without it, you can connect clients to iSCSI only by using iSCSI initiator program) and 100Gb/s bandwidth (that is if you plan to boot multiple computers, basically total required bandwidth is x amount of computers * x bandwidth speed they use + around 20% extra for headroom), also sfp is recommended if you want physically more durable interface compared to Ethernet. You also need a switch which switching speed is by far more than total bandwidth of your net work (for example 20 computers using 10Gb/s ethernet has maximum bandwidth off 200Gb/s, so i'd say for that you need switch which can handle at least 350Gb/s) Fourthly for windows each computer requires individual license and if computers don't share same hardware, you need to create individual iSCSI blocks (if you have ever cloned systems, it's pretty much the same. Difference is that boot drive still exists, it's on the iSCSI block shared to your PC and your computer will write data to it as if it would be physically connected to your computer), it is recommended to make separate blocks for each computer, that way you avoid whole world of pain once something goes wrong. Also you need Switch or router with TFTP support. Thing that wasn't shown. PXE server also has another server, it's called TFTP server, you need to setup TFTP redirection from your switch or router (TFTP doesn't use TCP/UDP traffic for PXE) to your TFTP server IP and boot files used for PXE boot, otherwise you won't be connected to PXE server automatically and you need to setup server to use right bootfiles manually and hope it works (each NIC manufacturer uses different bootfiles, so boot file setup is always "try each one by one until it works" effort and hence, lot less of a hassle to do from router or switch settings). Fifthly it's good idea to get yourself UPS (uninterruptible power supply) with re-chargeable batteries that can keep your server on long enough, to give you time to react (8 hours is good if you want to avoid models, which scream loud enough to make your ears bleed or send shutdown command to all devices connected to it, once main power goes off). Also it's good to get at least 2 switches with spanning tree protocol support to eliminate single point of failures (almost all managed switches have that, one model that I can recommend is Cisco SG300 or Catalyst series). All these will give you less headache if one of your ethernet cables breaks or gets disconnected or there's a power outage. Last you need backups (and no, raid is not an option since even RAID arrays need to be backed up). iSCSI blocks will get corrupted eventually and although ECC RAM and simple windows built in disk repair tool is able to fix issues 90% of the time, there are cases like power shortages, server having to reboot due to updates, hard drive failing etc. you need to think about "What if" scenarios and prepare for them in advance. Amount of users is limited to how much bandwidth your network can handle, how much storage space you need and how many users Operating system and how many computers license allows if not using individual license for each computer. Also keep in mind, for single computer, iSCSI share is basically good enough (there's no point in making your home pc to use iSCSI boot, you can use iSCSI for games and home folders etc. without the boot thingy since windows 10 comes with iscsi initiator tool. Also if you have USB 3.1 gen 2 port, you can just buy external hard drive or NAS station with USB 3.1 gen 2 port and you might even get faster transfers compared to iSCSI just by plugging the usb cable to your PC and connecting hard drives to station, Ethernet and SFP both require optimization and network configuration since it's not a direct physical connection)

Oh and I would really prepare hardware and schedule testing out the thing first. iSCSI works wonderfully on single computer, but 2 or more can easily cause data corruption, so you do need to run ALOT of "What will break things and what will corrupt data" kind of tests. For home users, iSCSI is FAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAR from being cheap, you really need to invest money on hardware and have more than plenty of storage for backups and such.

Yes

How many? It depends on the server.

Using this method only one pc can be connected at a time, I tried with 2 and when the second pc started booting it cut disk access for the first one

We're actually using ccboot for diskless in our office. Less maintenance, less heat, less electricity because there's no hdd on each client. Downside is when your server goes down.

Wait, that's weird

Waiting that it will also boot over other peoples IPv4 and IPv6.

the same you,

with me than no such device and i can fix it

They are a many diskless systems but not a free!!