Well, I was able to figure this out myself. I had to add a CORS module to IIS10 and configure that in the TOEMS-API web.config.

Since updating to 1.5.6, I can't upload anything into my file modules. I'm getting the ole XHR 0 error. The UploadApiURL is setup correctly, nothing else has changed. Any thoughts?

@eruthon I don't know if this plays a role in this or not, but my understanding is that PXE settings are pushed to vlans via DHCP, so if machines on that vlan are still trying to only contact the main rig, it may be a DHCP configuration issue.

@eruthon I don’t use PXE yet, but I believe you need to go into the group settings and assign the machines to the com server on their vlan.

@eruthon Couple of quirks I forgot about.

Some permissions don't seem to copy over.

1. You'll need to make sure that iis_iusr has read and execute permissions for the Toec-API-129 folder.
2. Within the Toec-API-129 folder, you'll need to make sure iis_iusr has modify rights to the "private" folder. Be sure to apply permissions to child objects.
3. Open HeidiSQL, enter the root password (located in the connection string in the Toems-API web.config folder, and click open. At the top, click the user manager icon (looks like 2 people). Click root on (the one with the host as your servername), change the "from host" setting to Access from anywhere.

@theopenem_admin I wish I could say I was an expert, but I literally just started using this last thursday. However, I've been in systems management for 16 years so I've seen enough to figure things out quickly.

@eruthon what I think you'd actually have to do if you just want to use one actual system to run this on multiple network interfaces, is to:

1. Clone the TOEC-API site for each IP.
2. Bind each IP to the site in IIS
3. Setup a "com server" for each IP in the UI.
4. Modify the web.config for each com server and verfiydb.
5. Add them to the default cluster as passive servers with the multicast, TFTP, and imaging options.
   (edit) 6. Go into HeidiSQL, change the root account to have remote access. (almost forgot that)

That should do it I think.

@eruthon Upload/Deploy Direct to SMB is the last option under Admin Settings --> Imaging Client. To multicast across VLANs, you'd have to have a com server on each vlan and run the multicast session through there.

WIW, I have the same situation, and the only thing that seemed to work for me was to make sure that all storage settings were set to local, on the main server, and secondary com servers, and to make sure upload/deploy direct to SMB was disabled. Works like a charm after that.

FWIW, I have the same situation, and the only thing that seemed to work for me was to make sure that all storage settings were set to local, on the main server, and secondary com servers, and to make sure upload/deploy direct to SMB was disabled. Works like a charm after that.