@Fernando-Gietz Thanks, now its working!
Posts made by kAs1m
-
RE: Access Control Plugin
@Fernando-Gietz I’m sorry. I’m trying to hide Access Control plugin managment button from accessing by technician-role useres. Doing it by adding additional rule as said in post 103025, and its doing nothing, this button still there, as you can see on my screenshot.
-
RE: AD credentials disappears
@Sebastian-Roth Didn’t has time, sorry. The whole PLUGIN thing was actually new to me, so now after quick navigation in settings, I’ve explored PLUGINSYS checkbox. Thank you, now I’ll sped some time to investigate all of the “mainline” plugins. Thank you for advising me to use this plugin.
PS
Aaan,d I could’t find any functionality that I’ve implemented, also the whole thing seems not working, because I couldn’t restrict Support role from accessing “Access Controls”, where they can revert everything back.
I also reported to this topic about last problem: /topic/10918/access-control-plugin/10 -
RE: AD credentials disappears
@Sebastian-Roth Thanks, I think many lazy admins will appreciate full automatic reg process.
PS
Also, I forgot to comment out this section in /var/www/fog/lib/fog/fogpage.class.php:
/sprintf(
‘<label for=“adEnabled”>%s</label>’,
_(‘Join Domain after deploy’)
) => sprintf( //#hidden
‘<input id=“adEnabled” type=“checkbox” name=“domain”%s/>’,
(
$useAD ?
’ checked’ :
‘’
)
),/This will remove “Join Domain after deploy” checkbox from web ui compleatly(else you’ll notice that you can see AD admin pwd, if you create new host, check this checkbox and click show password button)
-
RE: AD credentials disappears
I’ve solved it myself.
Now quick reg applies AD settings to host.
Add AD settings in web ui:
Settings - Fog Settings - Active Directory Defaults
Then replace code in /var/www/fog/lib/reg-task/registration.class.php
With this:
https://www.pastiebin.com/5d6c4867436bcDo not forget to chown www-data:www-data /var/www/fog/lib/reg-task/registration.class.php
after.PS
And one more thing, maybe someone needs it. If you have multiple admins in your organisation and some of them have just support rights, but not domain admins, you cant hide all ad admin passwords from viewing it in the web ui:
find this code in /var/www/fog/lib/pages/fogconfigurationpage.class.php :
default:
$type .= ‘<input type=“password” name=“${service_id}” value="’
. ‘${service_value}" autocomplete=“off” class=’
. ‘“form-control” id=“${service_name}”/>’;and replace it with this:
default:
$type .= ‘<input type=“password” name=“${service_id}” value="’
. ‘" autocomplete=“off” class=’
. ‘“form-control” id=“${service_name}”/>’;also find this code in /var/www/fog/lib/fog/fogpage.class.php :
) => sprintf(
‘<div class=“input-group”>’
. ‘<input id=“adPassword” class=“form-control” type=’
. '“password” ’
. ‘name=“domainpassword” value=“%s” autocomplete=“off”/>’
. ‘</div>’,
$ADPass
),and replace with this:
) => sprintf(
‘<div class=“input-group”>’
. ‘<input id=“adPassword” class=“form-control” type=’
. '“password” ’
. ‘name=“domainpassword” value=“%s” autocomplete=“off”/>’
. ‘</div>’,
‘#hidden’//$ADPass
),Also, do
mv /var/www/fog/lib/db/mysqldump.class.php /var/www/fog/lib/db/mysqldump.class.php.bak
to prevent from backing up whole mysql db/ -
RE: AD credentials disappears
I think I understands now, but is there a way to quick reg host and auto join domain?
-
AD credentials disappears
Hello! I’m trying to automate the process of joining into domain for new PC’s, so I’ve created a group in fog web ui, named AD, and added my domain admin credentials in Active Directory section of the group:
After I clicking Update, everything seems fine, and credentials still here, but if I go to, for example, Hosts page and then back to groups, list all groups, and selecting my AD group, the credentials isn’t here anymore…
Fog ver. is 1.5.7
-
RE: Can't deploy latest win10x64uefi with 1.5.5
@Quazz said in Can't deploy latest win10x64uefi with 1.5.5:
Wow, you’re so fast with answers! I really appreciate that!
As I’ve said in the firs post, I’m using Hyper-v second generation VM based on UEFI.
AAAAND! It seems that I’ve got some progress(really hope so).
What i’ve done:
Downloaded latest binary zip of rEFInd: https://sourceforge.net/projects/refind/files/0.11.4/refind-bin-0.11.4.zip/download
extracted /refind/refind_x64.efi ; drivers_x64 from this folder
Renamed refind_x64.efi to refind.efi, renamed drivers_x64/ntfs_x64.efi to drivers/ntfs.efi, renamed /drivers_x64 to /drivers.
Chmod 644 chown fog:www-data to this files|folders, moved them to /var/www/fog/service/ipxe, removed comment symbol from this line:
#scan_driver_dirs EFI/tools/drivers,drivers
in /var/www/fog/service/ipxe/refind.conf.
And I’ve just deployed my image with only one error at the end:
“failed initialization of the interactive login process” or something like this, it’s translated from Russian. -
RE: Can't deploy latest win10x64uefi with 1.5.5
@Quazz said in Can't deploy latest win10x64uefi with 1.5.5:
@kAs1m Interesting
Firstly, thanks for your answer!
But, unfortunately, it seems that I’ve write my first post with mistakes, so you didn’t get it(Eng isn’t my main language, obviously).
This Error occured ONLY if I prefer NETWORK BOOT in VM options and then, chainboot my prepared Windows system via rEFInd option in exit options.
If I’m using efi file-boot(bootmgrfw.efi) in VM’s “bios”-like options everything is alright, Windows continues to install normally with autoanswer file, then loads the desktop.PS
On a VM where I’ve deployed image, then turned VM off, then change the boot option from network to efi, and waited for WIN setup till launching to desktop - I cat switch boot option back to network, and it’s working. So the problem is that I have to manually switch boot option to EFI after i deployed image and back to network after it first boot. -
RE: Can't deploy latest win10x64uefi with 1.5.5
So, here’s the crash report:
https://imgur.com/a/8fO7BO4
And the dump: https://drive.google.com/file/d/1dvOXjVpbSLlb3DUa0NzMgHMRHZ9eTiO1/view?usp=sharing -
RE: Can't deploy latest win10x64uefi with 1.5.5
@Quazz said in Can't deploy latest win10x64uefi with 1.5.5:
?
- No, didn’t catch the error code, it only gaves qr code now, if it’s important, i’ll try to make a screenshot with BSOD, and also will try to find the dump.
- Yes, did everything according to that instruction.
- I’m using autoanswer file.
- Starting with a clean install.
- Is there a way to debug the procedure? And post vital info in this thread?
-
RE: Can't deploy latest win10x64uefi with 1.5.5
I’m also getting BSOD before this error.
Other(grub-based) exit options getting this error:
Could not boot: Exec format error (https://ipxe.org/2e008081) -
Can't deploy latest win10x64uefi with 1.5.5
Hi there, everyone! Need your assistance.
Architecture:
Hyper-v vm with generation-2 vm, based on uefi.
Fog version is 1.5.5 (installed on ubuntu 16.04)
Win 10x64 efi, version 1809 build 17763.107
FOG menu config: uefi exit type: refindefi
I’ve manage to customize my win setup(with this article: https://www.theitcave.com/post/561), then used sysprep on it.
The problem:
If I restart my computer after sysprep is done and then using fog’s ipxe.efi to boot through network, and then in FOG menu using default option boot from hdd, it starts booting with refindefi option(Other option not wirking at all, nothing happens when you press enter on “boot from hdd”), I’m getting error during win installation process:
“The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.”
And this happens even if I didn’t installed FOG client at all.
Also, it’s not happening if, in VM settings, I’m choosing to boot from boot-ffile instead of network boot, EVEN if fog client installed and fog service isn’t disabled. Windows installs normally.
PS
And thank you to all who involved in this incredible project! -
RE: Imaging Linux systems, UUID for swap not matching on deployed systems. Eh?
So, it’s still even in FOG 1.4.4…
If you want to deploy debian-based(mint in my case) distribs propertly, i made a
workaround, just copy-paste it in terminal(as root), change sda5 to your swap partition name, right before you get ready to made an image(before clicking the capture button). Then made a capture task and reboot the machine.
[CODE]
echo ‘#!/bin/sh’ > /usr/bin/fst.sh
echo ‘OLDUID=$(grep swap /etc/fstab |grep -v “#” |cut -d’ ’ -f1)’ >> /usr/bin/fst.sh
echo ‘NEWUID="UUID=$(ls -la /dev/disk/by-uuid/ |grep sda5|rev|cut -d’ ’ -f3|rev)"’ >> /usr/bin/fst.sh
echo ‘sed -ie “s/$OLDUID/$NEWUID/” /etc/fstab’ >> /usr/bin/fst.sh
echo ‘crontab -u root -l | grep -v ‘/usr/bin/fst.sh’ | crontab -u root -’ >> /usr/bin/fst.sh
echo ‘rm /usr/bin/fst.sh’ >> /usr/bin/fst.sh
chmod +x /usr/bin/fst.sh
(crontab -u root -l ; echo “@reboot /usr/bin/fst.sh > /dev/nul 2>&1”) | crontab -u root -[/CODE]