Posts made by theopenem_admin

I could try building the latest version of iPXE but it may take a few days

can you try using the ipxe snp only or snp file

It means you have a duplicate computer name or install ID, or that computer needed to re-provision for some reason. Just apply that reset request and if it goes away you are good, if it then knocks off a different computer then those 2 computers are somehow duplicated.

There is a new 6.13.4x64-updated kernel available, can you give it a try?

These are the 3 intel rst drivers that most people need for dell drive detection in RAID.

https://www.intel.com/content/www/us/en/download/720755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-11th-up-to-13th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19512/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-10th-and-11th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-8th-and-9th-gen-platforms.html

There is also one newer one 20.1 I think, it's hard to track down.

Yes, it does the whole dism thing. The driver need to be in inf format, that's how winpe works, you can't just drop an exe into winpe, the drivers need to be extracted. For them to show up in the winpe builder page, you need to add them as a file copy module with the is driver option checked. I typically just add all of my drivers to a single zipped upload, but you can add multiple files to the module if you want.

I'm not sure I'm following you. This already exists, When you build WinPE you just need to select which drivers you want to add to it. I have all the RVST drivers packaged together and I just check the box when I want to embed it into the WinPE, no problems with drives being detected.

It is technically possible to send WinPE over http but the problem is that it breaks secure boot, so I have not included it. If you haven't already seen this page, it goes over the pros and cons of each imaging environment.

https://docs.theopenem.com/imaging/imaging-environments.html

Yea, Microsoft is making things difficult. The nature of the program which allows remote commands to execute causes the false positive. I've submitted a request to get it allowed, but I highly doubt they will approve it.

Impersonation only works when running as a service, won't work at login since it runs under that users context.

You could also just try increasing the max connections.

In the my.ini file just add something like
max_connections = 1024

you can check the existing max_connections with a query:
SHOW VARIABLES LIKE "max_connections";

Not really sure what else to try. You could try adding the following to your connection string in web.config for the clientapi to try and close connections faster.

ConnectionIdleTimeout=5

<add name="toems" connectionString="server=localhost;port=3306;database=theopenem;Uid=root;Pwd=password;Allow User Variables=True; ConnectionIdleTimeout=5;" providerName="MySql.Data.MySqlClient" />

or disable pooling

Pooling=false

<add name="toems" connectionString="server=localhost;port=3306;database=theopenem;Uid=root;Pwd=password;Allow User Variables=True; Pooling=false;" providerName="MySql.Data.MySqlClient" />

Sorry, that is beyond the scope of Theopenem and is not available.

There wouldn't be any way to do this currently. The next version will provide a way to write your own SQL queries.

You need to create an image cleanup policy.
https://youtu.be/ZmMzStsFnEI?t=1269

Alternatively when using the image prep tool, just uncheck the Enable WinLogon Finalizing Background option.

I would start by increasing the memory available to Mariadb. You want it to be about 80% of your available memory to get as much of the working set into memory as possible.

In c:\program files\mariadb\data\my.ini
Change or add this line.
innodb_buffer_pool_size=12GB

make sure it's under the [mysqld] section and not the [client] section.

Then restart mariadb service.

Thanks. 1.5.7 is behind schedule it's shaping up to be much larger than anticipated and facing some challenges. It's probably still a couple months away. Mainly just going through the forum and implementing suggestions.

Definitely not want you want to do. You probably just need to create boot files in admin settings->pxe-> global boot menu, also in pxe settings select the correct bootloader and click update, that will copy the correct files to the correct location.

Yes, just copy the images folder from the old to the new, but you will need manually recreate the images in the webui, using the same name.

It doesn't need to say 60, it's just returning your checkin time.