Profile cover photo
Profile photo
Elliot Huffman
45 followers -
It all depends on your point of view.
It all depends on your point of view.

45 followers
About
Posts

Hello world,

Well this will be the last post for a bit.
I don't think that people seem too like my posting, I am actively losing followers. Sooo I am going to hold off on posting.

Wrapping things up:
Did some photography this Sunday at the Aiken & Augusta Gem And Mineral Societies' rock and gem show. The pics turned out great and after I get them backed up, you will be able to find them on Tumblr and Pinterest.

The ELADS system is ready for production. A successful deployment of windows 10 pro has been performed and on Wendsday the deployment should commense at the school.

HDD decommissioning is continuing to chug along nicely. One of the HDDs are not working with Windows, which means that I am going to have to manually destroy the platters instead of doing a gutman wipe.

I may go to posting on Facebook but that is just a thought at the moment.

See you around!

Hello world,

I have been struggling to UEFI boot my ELFS project but I have finally got it working. It goes something like this:
When I booted the WIM file the system hung and rebooted after the WIM file was loaded to ram and the boot process started.
In the past I have had little glitches where if you boot the PE image it would hang for some reason on wininit. This was not the case as it rebooted too.
I opened the BCD file and low and behold I found that the UEFI boot config was pointing to the winload.exe file instead of the winload.efi file. I made sure that the new BCD config was saved as I explicitly set that previously.
After positive validation, I attempted to do another UEFI boot. It worked this time and on top of that, it passed SecureBoot validation!

After getting ELFS booted, I was able to use the toolkit to identify a dieing hdd in my main desktop. I then powered down the system and removed it. The spinning disks are set up in a storage spaces resilient pool. So removing one of the 4 was not and issue.
The issue is that I do not have a replacement. I do have an equivalent drive running through decommissioning. If it tests that it is not failing, I can use it as a replacement.

See you around!

#ElliotLabs, #Windows, #ELFS, #UEFI, #BCD, #Diagnostics, #WindowsPE

Post has attachment
Hello world,

The first batch of drives have finally finished secure erasing.
As such I have started the next batch of drives in the diagnostics phase.

My desktop has had one of it's spinning drives start to fail. Fortunately it is in a mirrored storages spaces setup. No data has been lost.

Work continues on the TechNet vLabs auto configuration tool (check out my github gist's to take a peek). The next step for it is to add DFS config. The storage spaces auto provision properly as of yesterday (woot woot!).

Finally I have ordered a good case, data cable and screen protector for my phone. I have also ordered a smart card to increase security at eLabs and to get familiarized with the technology.

See you around!
Photo

Hello world,

Yesterday:
So, I started rebuilding the HTTP server module for ELSAA. Is there a pretty good. I have the initial rewriting done and will start testing on my next ELSAA foray.

Today:
I did some Consulting work with my awesome new client.
I finished setting up the WDS server. The WDS server is separate from the DHCP server. So I can figure out a DHCP server option 66 and 67 two points to the WDS server externally. Initial test boot using retail boot WIM from Windows 10 installation disc worked marvelously well. Will be reconfiguring ELADS on server shortly.

See you around!

#ELADS, #ElliotLabs, #Consulting, #ELSAA, #DHCP, #WDS, #HTTP, #testing, #Windows

Hello world,

The wierdest thing happened to me:
The git lab instance seemed to fix itself. I forced it off one more time after still trying to isolate the issue and it stopped going in into some sort of IO loop.

I am still going to update the ELSAA instance for the server though.
Because of this I started prepping the tools for building the new config. I updated the git client, toolkit and the test VM. I should start tomorrow on the rebuild.
After the rebuild is finished, I will redeploy the http server. This should optimize the performance of the server by implementing a more.simple architecture.

My dad also wants to have a site built for him so I started to get that dev enc set up too.

See you around!

Post has attachment
Hello world,

Well I did it again, I forgot to post yesterday.
Sssooooo here is a recap:
I built the latest tweaks of ELFS and it all worked marvelously well! The lock screen works, firefox now works.
Time will tell if the 72 hour limit remover works.
I have started the HDD wipes again on the system for the last two drives (the two 750GB drives).

Today:
I am still trying to correct gitlab, I have not tried the back and reinstall method yet as I have a checkpoint that I am using as a base starting point for attempting to fix gitlab in the meantime. If I break something or fail trying to run a fix then I roll back to the checkpoint.

Based upon the way it is running, I am thinking that the database may be corrupt. Just a theory at the moment...

See you around!

#ElliotLabs, #ELFS, #SecureDeletion, #HardDrive, #Security, #limit, #WindowsPE, #Windows, #Firefox, #Restart, #Hyper-V, #Checkpoint, #Debugging, #Troubleshooting, #database, #Theory, #Corrupt
Photo
Photo
3/2/18
2 Photos - View album

Hello world,

Today I started a deployment of ELADS at a client site. So far so good!

An update on ELFS:
I forgot to remove the 72hour limit for execution that exists in Windows PE, sooo the secure hdd wipe did not finish on the two 750gb server drives.
I have tweaked the build process with the below but have not tested:
Removal of the time limit
added a screen locking mechanism (attempt, am not sure if compatible with Windows 10)
Attempted at fixing Firefox. (Disabled file compression)

See you around!

Hello world,

Well today has good and bad news,
the good news is that 4 of the 6 HDDs have finished secure data erasing. The other two are still chugging along.

The bad news is that GitLab on my cloud server vHTTP server instance is going absolutely bananas (crazy amount of memory and disk usage).
I think I am going to need to reinstall gitlab (after a backup of course, I have some awesome projects on it).

Since I have to do maintenance on the http server, I am planning on upgrading ELSAA to support wildcard subdomains for letsencrypt and apache.
At the same time I am going to disable ddclient on my http instance since my router is now natively doing that. I am not removing it from ELSAA though, it is a handy program to support.
Also since I am going to add wildcard support to ELSAA, I am going to update the collabora code support to support the new bare metal package instead of a docker instance. This should optimize resource usage and simplify the management experience that ELSAA provides.

See you around!

Hello world,

ELADS reconfiguration has been finished and is ready for testing.

The system has been designed to be UEFI booted however if the system is somehow not UEFI booted, it has been configured to install Windows 10 in a BIOS setup.
Domain join has been added (normally ELADS runs in workgroup mode).
Driver integration has been completed.
Automatic BIOS updating has been integrated.
Operating system configuration has been updated to the latest version of Windows 10.

Since the computers are on a domain, application deployment will be processed by group policy. (this is subject to change)

Man, I have had quite the headache today. It started a little after lunch today :(
Hopefully it will be gone for tomorrow.

See you around!

#ELADS, #Windows10, #Windows, #Microsoft, #ADDS, #ActiveDirectory, #UEFI, #BIOS, #BIOSFlash, #UEFIFlash, #Reimage, #GroupPolicy, #Deployment, #Project, #ElliotLabsLLC, #ElliotLabs

Hello world,

Most of friday was spent with a client coordinating a project.
Saturday I went to a screening of a new hope with a live orchestra.
It was awesome :)

On Saturday I also tried to get ELFS to boot but it did not boot, the Bootmgr system kept finding a code integrity failure with winload.
After getting the error i realised that when I was patching winload to allow loading of unsigned drivers I inadvertently broke the boot system.
Sooo to fix this I removed the code signing patch. It really isn't that important to me, just a feature that I wanted to add just to have it.
After removing it. I was able to boot ELFS modern Low RAM on my new cloud server.

Today I used ELFS to start wiping the previously tested HDDs so I can get more desk space.

Also today: I am rebuilding ELADS for the friday client.

See you around!
Wait while more posts are being loaded