It's the standard process for setting up IIS with SSL. You need to assign a certificate to the sites in inetmgr, then update your com server url to use https url and port.

@theopenem_admin said in I cannot connect with remotely:

Just delete the remotely directory and reinstall it.

I was able to successfully re-install Remotely after deleting the directory, following the installation instructions, and changing the policy I had in place to "force re-install" temporarily until I forced all devices to check in.

I appreciate the help. I love this project and still trying to get my school to get the full service.

It's up to each user. Most people don't have success with multicast but it's there if you want to try it. It sounds like 25 devices is too much for your network / storage. I would just make it lower, that's the point of the queue. Once it's queued you can walk away.

It's on the com server image settings.

@deathraymind Double checked this video to be sure the certificates were installed in the correct place https://youtu.be/v213zRQTOFY?si=_ZMni6fO1dL4U3dm&t=1323 and they werent so i fixed it. The client logs now say this ```2023-09-05 11:53:59,375 INFO [4] ServiceTriggerAction - Checking For Startup Policies
2023-09-05 11:54:00,032 INFO [4] PolicyRunner - No Policies For Trigger Startup Were Found For This Computer
2023-09-05 11:54:00,032 INFO [4] ServiceTriggerAction - Check In Time Set To 60
2023-09-05 11:54:00,032 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete.

And the computer shows as provisioned. I then followed the second video and it now shows in the group.

Yea, that list only adds things that it finds, never removes. You would need to write your own sql query to accomplish this for the current version.

It won't automate it for you, but you have full control over the pxe boot menus to boot whatever you want.

You just need to setup a com server on that network, then just delete the com server that was installed on the main server.

@theopenem_admin Perfect. TY.

@theopenem_admin AH! I didnt even realize that was the account it was looking for. OK, I created a deployment user and was able to log in and the application started. Thanks!

@theopenem_admin Yep, that solved it. Thank you

@theopenem_admin Thanks! Not sure why I am having trouble with creating one then. Is there a place in the docs with prerequisites that I missed? I'm getting the "Unknown Error Occurred While Determining Minimum HD Size" error.

@jonsjsbs IDK. I re-uploaded it and then re-deployed and it seemed to work fine. Thanks!

Got it. Figured it out.

Problem solved

That's it.

For anyone interested, here is a solution (more accurately a workaround) for using different menus with Proxy DHCP depending on BIOS or EFI boot.

I stumbled on the solution as I was trying to add the command console to ipxe by rebuilding my own. My first build would result in a boot loop where ipxe would ask again for DHCP and load itself back again. ipxe.org has a solution for breaking the infinite loop, and this was the solution to using different menus.

Here's a little help to get started with rebuilding your own ipxe.efi:
Go to https://ipxe.org/download, make sure you have the necessary packages listed (gcc, binutils...), clone the repository git clone https://..., and go in the folder ipxe/src.
WARNING: At first, try to compile it the way it is before making changes, and if you do, don't make too many changes before trying to build it again as your changes will break the build.
Begin by editting the file config/general.h to enable/disable various features. Note that there are commented lines, and they begin with a variety of #define and #undef. Thus, enabling HTTPS means changing the line #undef DOWNLOAD_PROTO_HTTPS to #define DOWNLOAD_PROTO_HTTPS. As such, uncommenting a line may not be enough to enable the feature, same goes for commenting in a line may not be enough to disable the feature.
For BIOS boot, you may want to edit config/console.h. See an example here.
Create a file init.ipxe and add the following content:

#!ipxe dhcp chain proxy/efi64/pxelinux.cfg/default.ipxe

In true TOEM fashion, this should run the proper file which contains the menu for EFI64 boot. You may technically do anything you want here.
Finally, compile the ipxe file with the command make -j4 bin-x86_64-efi/ipxe.efi EMBED=init.ipxe, and this is the resulting file bin-x86_64-efi/ipxe.efi.