Best posts made by sudburr

I want to explicitly document changing the password for root for MySQL without needing to re-run the installer as the Wiki suggests.

mysql_secure_installation

Enter current password for root:	<enter>
Set root password?			y
New password:				<new password>
Remove anonymous users?			y
Disallow root login remotely?		y
Remove test database and access to it?	y
Reload privilege tables now?		y

Then we need to change everywhere FOG references the old password without rerunning the installer.

sed -i.bak "s|snmysqlpass='<oldpassword>'|snmysqlpass='<newpassword>'|g" /opt/fog/.fogsettings
sed -i.bak "s|DATABASE_PASSWORD', \"<oldpassword>\"|DATABASE_PASSWORD', \"<newpassword>\"|g" /var/www/html/fog/lib/fog/config.class.php
reboot

I’m working on that second sed command’s escape sequence just now. EDIT - completed

Is there anywhere else that needs to be changed? The purpose of this is to avoid re-running the installer just for the sake of a changed MySQL password.

To add PXE boot capabilities to an Oracle VirtualBox machine you must add a version-matching ExtensionPack (.vbox-extpack)).

For Oracle VirtualBox 5.1.10, download from Index of /virtualbox/5.1.10 then add it to your Oracle VirtualBox via menu Preferences > Extensions

What we use for our M72z with BIOS - f6kt43a :

For Legacy Network Boot (undionly.kpxe):

- POWER UP / hold [F1]
- Menu EXIT  \ OS Optimized Defaults = [disabled]

- Depress:  [F9] … to load setup default configuration

- Menu Startup \ Primary \ Automatic \ Error Boot Sequences
1st device = [Network 1]
2nd device = [SATA 1]

For UEFI Network Boot (ipxe.efi):

POWER UP / hold [F1]
- Menu EXIT \ OS Optimized Defaults = [ENABLED]

- Depress:  [F9] … to load setup default configuration

- Menu Security \ Secure Boot \ Secure Boot = [disabled]

- Menu Startup \ Primary \ Automatic \ Error Boot Sequences
1st device = [Network]
2nd device = [SATA]
3rd device = [USB HDD]

- Menu Startup \ CSM = [disabled]
- Menu Startup \ Boot Mode = [UEFI]

I just tested this out with 1.3.5 RC5

If it’s your OS partition just drop this into your unattend.xml

<settings pass="specialize">
	<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
		<ExtendOSPartition>
			<Extend>true</Extend>
		</ExtendOSPartition>
	</component>
</settings>

@kyle.heath In Windows 7, some drivers for newer devices must be installed after drivers for older devices are installed with a reboot in between and vice versa.

And as @Quazz said, you can quite simply dump your entire library of drivers into ‘c:\windows\inf’, but you will still be limited by Windows 7’s ability, or inability to prioritize driver installation order.

I think a regular predictable interval might help. Like the first Monday (or whatever) of every odd/even month. Something people can pop into without an invite.
More than just a hangout but like a (dare I say it?) mini-Genius bar for FOG.

I’m not entirely sold on this new software and its interface. I’m finding it cluttered.

My biggest peeve right now is the sorting.

Viewing a forum post with more than a couple of replies is tedious.

Instead of viewing a simple ascending chronological list of post and replies from top to bottom, eg:

A post
b reply
c reply
d reply
pagination (which I’ve turned off for my probile)
e reply
f reply

This new style of:

A post
z reply
y reply
x reply
w reply
pagination
A post
v reply
u reply
t reply
s reply etc…

Forcing the user to the bottom of the last page/post then rescrolling back up through the posts and backwards through the pages (if pagination is turned on) is time consuming. I’m puzzled why this particular wheel was reinvented instead of sticking with the simple ascending chronological.

You can also use sysprep to expand the system partition, or a simple setupcomplete.cmd script to expand using a diskpart script.

@ty900000 I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.
Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

Lookin’ forward to checking it out Monday morning. Thanks for all your hard work!

Whoa… how do I edit an existing post of mine?

Don’t all cultures read top to bottom? I find reading bottom to top jarring and slow.

You need to break your request down to two things.

1. Creating or `Mastering’ an OS for distribution.
2. Capturing an image for distribution

If you’re looking for the first, I recommend starting your journey with Microsoft documentation ( http://go.microsoft.com/fwlink/?LinkId=162739 ), and the Windows 7 Resource Kit.

For the second, start with what Wayne said.

Microsoft Windows Server 2016 Hyper-V Core (10.0.14393.0) and Microsoft Windows Server 2016 Standard (10.0.14393.0) are both fine.

Whether it is this RC or happened between 1.3.4 and now, I like what you’ve done to the UEFI network boot. It has solved an issue I had with Lenovo M72z being unable to successfully use any EFI exit type from the FOG menu.

I’m going to blame the 3 day old migraine I’m trying to think through… yah, that’s it.

I agree with Wayne. Ditch Ubuntu if you can. Go for at least Debian 8.2 or my new fave, CentOS 7.1.

Moving from Ubuntu to Debian solved 2 big workaround headaches.

Moving from Debian to CentOS removed 4 more workarounds for me

@Tom-Elliott Legacy machine cannot boot UEFI, ergo cannot boot UEFI no matter the source.

You got a Dell OptiPlex 790 to UEFI network boot successfully ?? Ooh, I gotta try this.

Am I correct?

By the looks of it, the command:

yum update -y

is the CentOS equivalent of what’s used by Ubuntu and Debian:

apt-get clean &&
apt-get update &&
apt-get upgrade -y &&
apt-get dist-upgrade -y &&
apt-get autoremove -y &&
apt-get autoclean -y &&

So I :

mysql -u root -p
DROP DATABASE fog;
mv /opt/fog /opt/fog.old

Then launched the installer and I’m your uncle.